Windows Rt Drivers

One of Windows’ greatest strengths is its compatibility with millions of peripherals. Due to its complete dominion of the PC market, manufacturers must ensure that their devices work with Windows — and for the most part, they do. The one exception to this rule is the period immediately following the release of a new version of Windows, and Windows 8 and RT are certainly no exception to the rule.

In the case of Windows 8, hardware support is virtually unchanged from Windows 7 and Vista — but in some cases, hardware vendors still need to issue new drivers that Windows 8 will agree to install. If you are upgrading from Windows XP (which you are probably running on a 32-bit system), you may have some issues with older peripherals that never had their drivers updated to Vista/7/8.

Aug 06, 2019  If your Surface isn’t listed above—for example, if you have an older product like Surface RT—that means.msi update files are not currently available for that device. We recommend connecting to Windows Update to update those Surface models. Here’s how: Select the Start button, then select Settings Update & security Windows Update.

In both cases, though, the solution is to make sure that updated drivers exist for the peripherals that you own. The Windows 8 upgrade assistant will generally tell you which peripherals are incompatible with the new OS — but you can also check manufacturer websites for updated drivers, too.

Windows

Windows RT

Windows RT, the cut-down version of Windows 8 that runs on ARM rather than x86, is another matter entirely. You can’t upgrade to Windows RT — you can only buy devices with Windows RT pre-installed — so there’s no upgrade assistant to tell you whether your peripherals will continue to work. There is a Microsoft Windows RT Compatibility Center website, but how many consumers will actually seek out that website before buying a Windows RT tablet for themselves, or a loved one this Christmas?

In general, the hardware compatibility landscape for Windows RT is good. Most simple peripherals that you own, such as mice, keyboards, printers, USB flash/hard drives, and digital cameras will work just fine with Windows RT.


Support starts to break down with devices that have complex functionality or use non-standard protocols, however. Most notably, none of Apple’s iOS devices will work with your Windows RT tablet (including the Surface RT). This is due to Apple using a non-standard, proprietary protocol which Windows RT does not support. While the Microsoft site doesn’t explicitly list the iPhone 5, we assume the new Lightning connector and protocol is not supported either. Again, this means your iPhone, iPad, and iPod will not work with Windows RT.

Surface Rt Firmware Update

Also not supported by Windows RT are USB scanners and webcams, stylus pens, and other funky input methods (many-button mice, trackballs). Your USB keyboard will work, but only basic media buttons are supported (volume, mute, play/pause, etc.). PS/2 peripherals are not supported. Headsets and microphones are supported for playback and recording, but additional hardware buttons (mute, hold) may not work. Any of the above features included in other devices (such as a multifunction printer (MFP)) will also not work with Windows RT.

On the flip side, devices that support MTP (media transfer protocol), which covers most other smartphones and portable music/media players, will work with Windows RT. Windows RT also supports the Xbox 360 gamepad (and other XNA-compatible gamepads), and most DLNA-enabled receivers (such as your Xbox, smart TV, etc.) should support Windows RT’s “Play To” function (where your current song/video is played through your TV).

Windows Rt Drivers

Will peripheral support improve?

By now you have probably worked out that Windows RT supports most basic, simple peripherals — but is completely incompatible with whole swaths of complex and multifunction peripherals. This is because Windows RT uses class drivers; generic drivers written by Microsoft that support for whole classes of devices (removable storage, input devices, printers, etc.) If the class driver doesn’t exist — such as for webcams and scanners (capture devices) — then the device isn’t supported. It is possible for device makers to produce third-party drivers for their products, but at the moment these drivers are few and far between (the shift from 32/64-bit x86 to 32-bit ARM will take a while to recover from).

Moving forward, it’s possible that Microsoft will add further peripheral support/compatibility to Windows RT, but we’ll simply have to wait and see. It still isn’t clear how or when Microsoft intends to roll out major Windows RT updates.

Now read: Windows 8: The tablet review (or Windows 8: The desktop review, if you prefer)

-->

Although Surface devices are typically automatically updated with the latest device drivers and firmware via Windows Update, sometimes it's necessary to download and install updates manually, such as during a Windows deployment.

Download MSI files

To download MSI files, refer to the following Microsoft Support page:

  • Download drivers and firmware for Surface
    Installation files for administrative tools, drivers for accessories, and updates for Windows are also available for some devices.

Deploying MSI files

Driver and firmware updates for Surface devices consisting of all required cumulative updates are packaged in separate MSI files for specific versions of Windows 10.

The MSI file names contain useful information including the minimum supported Windows build number required to install the drivers and firmware. For example, to install the drivers contained in SurfaceBook_Win10_17763_19.080.2031.0.msi requires Windows 10 Fall Creators Update version 1709 or later installed on your Surface Book.

To view build numbers for each version, refer to Windows 10 release information.

Surface MSI naming convention

Beginning in August 2019, MSI files use the following naming formula:

  • Product > Windows release > Windows build number > Version number > Revision of version number (typically zero).

Example:SurfacePro6_Win10_18362_19.073.44195_0.msi :

ProductWindows releaseBuildVersionRevision of version
SurfacePro6Win101836219.073.441950
Indicates key date and sequence information.Indicates release history of the update.
19: Signifies the year (2019).
073: Signifies the month (July) and week of the release (3).
44195: Signifies the minute of the month that the MSI file was created.
0: Signifies it's the first release of version 1907344195 and has not been re-released for any reason.

Legacy Surface MSI naming convention

Legacy MSI files prior to August 2019 followed the same overall naming formula but used a different method to derive the version number.

Example:SurfacePro6_Win10_16299_1900307_0.msi :

ProductWindows releaseBuildVersionRevision of version
SurfacePro6Win101629919003070
Indicates key date and sequence information.Indicates release history of the MSI file.
19: Signifies the year (2019)
003: Signifies that it’s the third release of 2019.
07: Signifies the product version number. (Surface Pro 6 is officially the seventh version of Surface Pro.)
0: Signifies it's the first release of version 1900307 and has not been re-released for any reason.

Look to the version number to determine the latest files that contain the most recent security updates. For example, you might need to install the newest file from the following list:

  • SurfacePro6_Win10_16299_1900307_0.msi
  • SurfacePro6_Win10_17134_1808507_3.msi
  • SurfacePro6_Win10_17763_1808707_3.msi

The first file — SurfacePro6_Win10_16299_1900307_0.msi — is the newest because its VERSION field has the newest build in 2019; the other files are from 2018.

Supported devices

Downloadable MSI files are available for Surface devices from Surface Pro 2 and later.

Note

There are no downloadable firmware or driver updates available for Surface devices with Windows RT, including Surface RT and Surface 2. Updates can only be applied using Windows Update.

For more information about deploying Surface drivers and firmware, refer to: