Download Drivers And Firmware For Surface

[Klacee Sawatzky]

Howyou manage Surface driver and firmware updates may vary depending on your environment and organizational requirements. In larger organizations, IT admins typically stage deployments internally and allocate time to test upgrades before rolling them out to user devices.

This article is intended for IT professionals and technical support agents and applies to Surface devices only. If you're looking for help to install Surface updates or firmware on a home device, see Download drivers and firmware for Surface.

While enterprise-grade software distribution solutions continue to evolve, the business rationale for centrally managing updates remains the same: Maintain the security of Surface devices and keep them updated with the latest operating system and feature improvements. This IT practice is essential for sustaining a stable production environment and making sure that users aren't blocked from being productive.

When Windows 10 reaches end of support (EOS) on October 14, 2025, Microsoft will no longer release security updates, bug fixes, time zone updates, or technical support from Microsoft. To learn more, including transition options for organizations needing more time, see Plan for Windows 10 EOS with Windows 11, Windows 365, and ESU

Microsoft Intune admin center is the recommended solution for large organizations to manage Surface updates. Configuration Manager allows you to synchronize and deploy Surface firmware and driver updates with the Configuration Manager client. Integration with Intune lets you see all your managed, co-managed, and partner-managed devices in one place. The Microsoft Surface Management Portal is a centralized place in the Microsoft Intune admin center where you can self-serve, manage, and monitor your organization's Intune-managed Surface devices at scale.

The Microsoft Deployment Toolkit (MDT) is a free tool for automating Windows deployment. It uses the task sequence engine from Configuration Manager, and can also install drivers and software updates during the deployment.

Configuration Manager and MDT both use the Windows Preinstallation Environment (Windows PE) during the deployment process. Windows PE supports only a limited set of basic drivers such as network adapters and storage controllers. Drivers for Windows components that aren't part of Windows PE might produce errors. You can prevent such errors by configuring the deployment process to use only the required drivers during the Windows PE phase.

By having Device Firmware Configuration Interface (DFCI) profiles built into Intune, Surface UEFI management extends the modern management stack down to the UEFI hardware level. DFCI supports zero-touch provisioning, eliminates BIOS passwords, provides control of security settings (including startup options and built-in peripherals), and lays the groundwork for advanced security scenarios in the future. For more information, see the following resources:

To maintain a stable environment, we strongly recommend that you keep parity with the most recent version of Windows 10. For best practice recommendations, see Prepare servicing strategy for Windows client updates.

We have majority of our workstations are Surfaces devices. When we use the SCCM firmware/driver upgrade service and download all required, it is showing hundreds or less that require the upgrade even though we know there are 1000 - 2500 surface devices in the environment or more.

Thanks for the insight I agree with the point on SCCM using detection rules to determine applicability or compliance of devices when it comes to updates. which is why this is so weird. If no surface devices showed as requiring the updates, I would definitely be looking into the detection method being used, but the fact that some devices are showing a requiring these updates indicates the detection method is sound (or it appears to be).

Upon imaging a Surface Laptop 2 with our basic image from the older Surface laptop model the Surface Hid Mini Driver driver fails to power and thus the keyboard doesn't work. if I revert back to 03/27/2017 driver it works fine... but then the laptop automatically updates itself to the latest version that brakes again. I have blocked the update in WSUS.

Is anybody aware of a fix for the latest driver? Does the PC somehow think its a Surface Laptop 1st gen and somehow downloading the incorrect driver possibly? I also downloaded the latest firmware/driver package from MS and tried that version and it also doesn't work. Seems to be the same exact version that gets downloaded from Windows Update.

@WC_KStil did you ever get the specific version of the driver that works? I keep running into this issue every update cycle. I have a surface laptop 2 and the "Surface Hid Mini Driver" flakes out every update. I've tried the all of the drivers from Download Surface Laptop 2 Drivers and Firmware from Official Microsoft Download Center :

I've tried uninstalling the driver and re-installing but that never seems to work, even disabling the driver and re-enabling doesn't work. I'm not sure what happens in UEFI entry, but that seems to make it work again for me. Beware - your mileage may vary!!! This seems to be a very common issue but different tasks seem to work for different people. I sure hope Microsoft can fix this as it is a pain as it usually happens when I really need to get some work done!

Sign in and select Surface Laptop 2 and input your Surface's serial number. Click on Download and Save it to your desktop. Do not download the Recovery Image directly on the USB drive but on the Downloads folder on the computer.

@GBowlsby - this worked perfectly. Frustratingly, I'd foolishly listened to other ideas with consequences that'll now cost me even more time (somehow our AI/ML needs to intercept bad or half-arse solutions with ones that actually work :)) Regardless to my live 'en learn: Thanks!

In 2015, I had the privilege of attending the Microsoft Ignite conference on the Gold Coast. While I loaded up my schedule with plenty of sessions on Azure and Office 365, I also made sure to attend as many Surface-centric events as possible: And I managed to get to quite a few. One of the biggest take-aways from the event, was two-fold: How insistent certain some of the Microsoft people were, that Surface devices always get and run the most up-to-date drivers and firmware possible; And how those updates should be deployed via the Surface Driver/Firmware installers instead of relying on solutions such as Microsoft Update.

The Intel HD Graphics drivers for the Surface Pro* 3 are customized by Microsoft* specifically to give the best possible experience on the Surface Pro 3 for the user. I would strongly recommend only using the Intel HD Graphics drivers found on the Microsoft support site for the Surface Pro 3 found here: -us/download/details.aspx?id=38826 Download Surface Pro 3, Surface Pro 2, and Surface Pro firmware and driver packs from Official Microsoft Download Center

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

Contributor of System Center Dudes. Based in Montreal, Canada, Senior Microsoft SCCM consultant, working in the industry for more than 10 years. He developed a strong knowledge of SCCM and MDT to build automated OS deployment solution for clients, managed large and complexe environment, including Point of Sale (POS) related projects.

For home users, the update will be applied with the standard Windows Update process and delivered in stages. For businesses, firmware update management by WSUS or SCCM is not yet available. (Feature is included in the latest SCCM Technical Preview 1706 but not yet in the latest 1702 production version)

Microsoft Surface firmware contains multiple drivers, software, and UEFI updates. Most releases do not upgrade all drivers, firmware and UEFI at once. Some releases only update one or two component, while others will update pretty much everything. Having an inventory of each of those components would be huge to maintain and managed throughout releases.

I ran Dell update again. It reports my system up-to-date. Windows update show version available is 0.1.10.0. Device Manager reports version 1.8.0 installed. How do I kill Windows attempt to install apparently incorrect firmware?

Some folks are leery of going into the registry to do things and much prefer making changes via the GUI. It is those folks that I had in mind when I posed the above question intended to be for Alex, since I quoted Alex.

Device Installation settings is under Settings\System. But it includes all things from other Mfg, such as icons that depict your h/w like printers, and apps from other mfg including drivers. Best to use GP or regedit specific for drivers in WU.

Controller: HPE Smart Array P408i-a SR Gen10 in Embedded Slot

Device: Logical Drive 1

Severity: Warning

Message: This logical drive has Unrecoverable Media Errors Detected on Drives during previous Rebuild or Background Surface Analysis (ARM) scan.

Errors will be fixed automatically when the sector(s) are overwritten.

Backup and Restore are recommended.

3a8082e126