Type Thunderbolt in the Windows search box and choose Thunderbolt Software from the search results. Right-click the Thunderbolt icon in the system tray in the lower right corner of your screen. Click Settings and select Details to show the firmware version. Note: You may need to click the caret to show the Thunderbolt icon in the system tray as shown in the screenshot below. Understood, but then it seems like the 1st generation does not support Windows 10?! The issue we're facing and why I've been asking for an firmware update: When booting up the opened laptop within the docking station with one external monitor via VGA cable works perfectly fine. Look at the value that is entered for it. If it says EFI, then your Windows 10 was installed from a UEFI BIOS. If it says BIOS, your system was installed running a Legacy BIOS. It is possible to change the BIOS firmware after installing Windows, and changing it doesn’t have any impact on the operating system itself.
I am having some real problem with the SP3 in a corporate environment. We have to have McAfee Drive Encryption installed by policy but it keeps locking up the Surface and not letting it boot. It is a known problem with McAfee DE and older versions of the surface UEFI BIOS, so my IT dept have allowed me to take DE off the device temporarily to get the firmware updated to the latest version.
The problem is, I can't seem to make the updates stick. I have installed the latest driver package from the MS download site, and the UEFI driver version in the Device Manager is showing as the latest 3.11.950 version. However, when I boot into the BIOS (Power + Volume UP), the version displayed is an older 2.x.x version.
Is this correct? Or should the version on the BIOS screen match the driver version?
If not, how can I confirm the flashed version of the UEFI code?
If so, how can I force-flash the UEFI code because Windows Update/MS Driver package doesn't seem to work.
Windows supports a platform for installing system and device firmware updates via driver packages that are processed by using the UEFI UpdateCapsule function. This platform provides a consistent, reliable firmware update experience, and it improves the discoverability of important system firmware updates for end-users.
The UEFI firmware update platform guidance is intended for SoC vendors and OEMs who are building hardware platforms that run Windows. The UEFI firmware update platform is supported by the following operating system versions:
- Windows 8
- Windows 8.1
- Windows 10 for desktop editions (Home, Pro, Enterprise, and Education)
- Windows 10 Mobile
UEFI firmware update support in Windows 10
All systems that run Windows 10 for desktop editions should implement UEFI firmware updates by following the UpdateCapsule-based update process described in this section of the documentation.
Devices that run Windows 10 Mobile can follow the UpdateCapsule-based process used for Windows 10 Desktop. These devices can also follow the binary update process, which performs a binary update to the storage partition which contains the UEFI firmware.
Microsoft strongly recommends that devices running Windows 10 Mobile should update UEFI firmware by using the binary update process. Devices that run Windows 10 Mobile can use the UpdateCapsule-based process only in scenarios where the binary update process cannot be used. For example, if the partition layout of the device prevents the UEFI firmware from being updated by using a binary update package.
For more information about .spkg packages for Windows 10 Mobile, see Creating packages.
Overview of the UEFI firmware update platform
There are two types of firmware that can be serviced via Windows: system firmware and device firmware. System firmware is responsible for providing critical boot and runtime services to the system as a whole, and device firmware is associated with a particular device integrated into a system. Such device firmware typically works together with a device driver, allowing the OS to expose the device to OS-level services and applications.
System firmware updates
System firmware updates for UEFI-based systems will be deployed as device driver packages (INFs). Windows will use information provided by the platform to ensure that the update package only applies to appropriate systems. A firmware update package contains a binary file containing the system firmware image. After the firmware update package is on the end-user's system, Windows will use the UEFI UpdateCapsule function to hand-off the firmware payload to the platform firmware for processing.
Deploying the update as a driver package allows the firmware update process to align with many existing deployment and servicing tools, and ensures simple update package authoring for hardware vendors.
The fact that the firmware update is delivered as a driver package does not mean that the update is written as an actual driver. The driver package will contain an INF file and a binary file containing the system or device firmware image.
Device firmware updates
For the purposes of updating device firmware, the device firmware can be assigned to one of these two categories:
UEFI-updatable device firmware.
This device firmware can be updated using a device driver package leveraging the same mechanism as system firmware. A device firmware update is distributed as a firmware update package. After the firmware update package is on the end-user's system, Windows will use the UEFI UpdateCapsule function to hand-off the device firmware payload to the platform firmware for processing. This process is virtually identical to how Windows hands off system firmware update payload, and is discussed below.
It is recommended that device firmware be updated using a discrete firmware update driver package, but device firmware may also be updated with system firmware as part of a single firmware update driver package.
Note UEFI should not be used to update peripheral devices. UEFI requires devices to be present during reboot to apply a firmware update which cannot be guaranteed with (external, removable) peripheral devices.
Driver-updatable device firmware.
This device firmware can be updated by the device driver during the normal Windows OS runtime. Updating device firmware using normal Windows OS drivers is not covered by this paper.
System Firmware Update Windows 10
System requirements for Windows firmware updates
In order for a system to be compatible with the Windows firmware updating mechanism, it must meet the following requirements:
Find Firmware Version Windows 10
The system must implement UpdateCapsule and QueryCapsuleCapabilities as defined by section 8.5.3 of the UEFI specification 2.8.
UpdateCapsule is used to pass the firmware update payload between Windows and the platform firmware.
Platform firmware must support firmware updates initiated by Windows.
System firmware, and some classes of device firmware, must be updatable using this process. Firmware code recognizes a firmware update payload passed to UpdateCapsule and initiates the update process. The implementation is owned by the partner.
Must specify a Firmware Resource in the EFI System Resource Table (ESRT)
The Firmware Resource allows Windows to surface a device instance with a Hardware ID, which will be used to target the system or device firmware update to appropriate systems and devices. It also describes the current firmware version and provides status for previous updates.
There exists a single entry for system firmware updates. All devices with updateable firmware must have a resource specified in the ESRT, unless a device's firmware is updated as part of a system firmware update.
For more information, see ESRT table definition.