Firmware and Driver updates to get more from your Surface devices


Announcement Worldwide, IT Pros everywhere are adopting Microsoft Surface devices for their organizations. Many of you that have adopted Surface devices have asked to learn more about the driver and firmware updates for them since this helps you be better informed on the improvements and enables you to better support end users.  

So in that spirit, here is the list of improvements included in the January driver and firmware update. You can download these updates here.

Intel(R) HD Graphics Family driver update (v10.18.14.4029)

  • Adds support for the Autodesk Mudbox 2015 paintbrush tool.
  • Ensures that unreadable text does not appear in the Microsoft Outlook calendar pane.
  • Improves performance of video display and zoom features in DirectX applications
  • Adds support for the fast cursor feature when using Miracast adapters, including the Microsoft Wireless Display Adapter. 
  • Ensures there is no flickering/blank display on externally connected monitors, especially when connecting multiple monitors in a daisy-chain configuration
  • Improves compatibility with Samsung U28D590D and Dell 2713H monitors. Some customers reported they saw a change in screen resolution when the device is docked and connected to Dell monitor. This has been addressed in the update.
  • Adds additional support to enable better compatibility with Panasonic and Actiontec Miracast adapters
  • Ensures there is no unexpected battery drain while the Surface device is in Connected Standby mode.
  • Resolves KMODE_Exception_Not_Handled system crash when using Excel PowerMap
  • Resolves some instances of Stop 0x9F and Stop 0x133 system crashes.
  • Resolves system hang that could occur if f.lux was enabled by an application.
  • Resolves system crash that could occur when attaching to external monitors immediately after waking the device from sleep or removing it from the docking station.

Marvell Wireless Network Controller and Bluetooth driver update (v15.68.3073.151)

  • As part of ongoing improvements to Wi-Fi experience on Surface Pro 3 device, customers now have the ability to manually select a preference between 2.4 GHz and 5 GHz connections for their device. We will publish a separate blog to describe this functionality further so more customers can take advantage of this capability.
  • Modifies power management logic to allow the wireless adapter to function properly when the Hyper-V feature is enabled in Windows.
  • For European Union customers, there are specific requirements outlined in EN 300 328 v1.8.1. This update includes capabilities to stay current on these requirements, including an LE switch to better control energy detection and Bluetooth Power setting.
  • Resolves a low throughput scenario when using Cisco 3702 access points in 11ac mode.

Surface Home Button driver update (v2.0.1179.0)

  • Improves compatibility with Surface Hub application.

Surface Integration driver update (v2.0.1182.0)

  • Improves compatibility of Surface Pro 3 with Windows 10.

Microsoft Docking Station Audio Device driver update (v1.31.35.7)

  • Addresses scenario where no sound would play while the device was docked without an external speaker connected.

We strongly recommend downloading these driver updates to get more from the Surface devices in your organization.

Thank you,

The Surface IT Pro Marketing team

Comments (15)

  1. anonymouscommenter says:

    Hi,

    is there any info about ARM based Surfaces, will they get any update or even Windows 10?

  2. anonymouscommenter says:

    What a great write up on this update! Thanks, and keep them coming!

  3. anonymouscommenter says:

    Thanks for adding details on the new firmwares!! Keep providing surfaces firmwares updates and promoting it,

  4. anonymouscommenter says:

    Nice!!!!

  5. anonymouscommenter says:

    After installing on my Pro 3 i7 and logging on – it shows only a console-window with some technical information.
    Had to perform a hard reset to keep it working again.
    Further there is a issue with the pen since installing the update. Sometime the Pen stop working for a few seconds.

  6. anonymouscommenter says:

    Fantastic work team, thank you so much! We are deploying Surface Pro 3's at my rapidly growing corporation in Rhode Island, US. These fixes, especially WiFi, Hyper-V, and docking station, are much appreciated.

  7. anonymouscommenter says:

    Colour banding issue is still present on SP3.

  8. anonymouscommenter says:

    with new drivers on my SP2 I noticed that Miracast image has big black frames. Old drivers used full image size with no frames. There is a setting for that on my PTV3000 adapter but it looks like Surface is ignoring it. On WiDi driver from intel using
    different computer there is a setting to change image frame. How can I set up image size on Surface using Miracast?

  9. anonymouscommenter says:

    Does this update fix the scaling issue when using an external monitor?

  10. anonymouscommenter says:

    Also. Since installing the latest updates even with a standard external monitor, either direct from the SP3 or the dock, the external monitor is lost when the SP3 screen goes blank. I have to unplug and re-plug the mini Display Port either back into the
    SP3 or the dock. This has crippled my productivity. 21/01/2015

  11. anonymouscommenter says:

    It suppose to help with scaling issue

  12. anonymouscommenter says:

    So my WiFi issue was down to Hyper-V being enabled. Just reporting that that is solved now, thanks!
    Also solved: While Docked in Docking, powering up attached to a High-res HDMI Display, would hang the UEFI bootloader and require an extra powerdown/powerup. Also solved.

    So great stuff. Thanks guys!

  13. anonymouscommenter says:

    Why aren't all of the drivers signed by WHQL?

    dism says that these drivers aren't signed:
    iaLPSS_GPIO.inf
    'iaLPSS_I2C.inf',
    'iaLPSS_SPI.inf',
    'iaLPSS_UART2.inf',
    'ECFirmware.inf',
    'SamFirmware.inf',
    'TouchFirmware.inf',
    'UEFI.inf',
    'SurfaceAccessoryDevice.inf',
    'SurfaceCapacitiveHomeButton.inf',
    'SurfaceCoverAudio.inf',
    'SurfaceCoverTelemetry.inf',
    'SurfaceDisplayCalibration.inf',
    'SurfaceIntegrationDriver.inf',
    'SurfacePciController.inf',
    'SurfacePen.inf',
    'SurfacePenDriver.inf',
    'SurfaceTouchCover.inf',
    'SurfaceTouchCover2FwUpdate.inf',
    'SurfaceTouchCoverFwUpdate.inf',
    'SurfaceTypeCover.inf',
    'SurfaceTypeCover2FwUpdate.inf',
    'SurfaceTypeCoverFwUpdate.inf',
    'SurfaceTypeCoverV3FwUpdate.inf',

    Is this going to cause me a problem with image deployment?

  14. anonymouscommenter says:

    Hi, is there a new Ethernet driver with the Surface Dock, as opposed to the Surface Docking Station? When we PXE boot our corporate SP 3 devices they boot fine and start to install but intermittently drop the network connection, sometimes after 10 mins,
    sometimes after 30 mins. They build fine with a USB Ethernet Dongle directly in the device. If I plug the LAN cable direct in the dock the SCCM task sequence fails intermittently and the client loses it's IP address. I can't find a new driver anywhere – just
    the same ones as linked here.
    https://www.microsoft.com/en-gb/download/details.aspx?id=38826

    Both of which are already in my MDT x64 boot image. Has anybody had similar problems or any suggestions – we can build fine in the older Surface Pro Docking Station. The client installs the Surface Ethernet Adaptor 8.14.704.2014, and the USB Ethernet Adaptor
    uses 8.18.303.2015.

    *UPDATE* – The Surface Dock adaptor on the device does not work AT ALL apart from power when plugged in upside down, I thought it would be adaptable both ways. When plugged in the correct way around it is intermittent as to when it picks it up and shows up
    as 'Unknown USB device' – and the Ethernet Adaptor is therefore not detected. So, in conclusion, it doesn't appear to be drivers because when it does detect it works fine. As the SCCM task sequence has a number of reboots it is likely not redetecting the dock.

    Potentially a faulty dock – we have another one arriving today so I will test it and see if it is better.

    Any advice Microsoft?

    Thanks,
    Michael

  15. anonymouscommenter says:

    Also – when I plug the dock device in it seems to be random how many USB ports it picks up – sometimes it will install 2 instances of the Generic SuperSpeed USB Hub, and 2 instances of the Generic USB Hub, and other times it will install 2 SuperSpeeds,
    and just 1 Generic USB. I am starting to really doubt the effectiveness of the connectors, I will test it with another SP3 and another dock in case this is a localised issue.

    Will post back.

    M

Skip to main content