Microsoft today began shipping a fresh set of firmware updates to Surface Pro 3 owners, bringing improvements to system stability and security. Available for devices on the Windows 10 Creators Update (version 1703) and later, the updates also address an issue causing a Device Manager error state.
- Surface Integration – System: 2.0.1630.0 improves system stability and resolve Device Manager error state.
- Marvell AVASTAR Bluetooth Radio Adapter – Bluetooth: 15.68.9125.57 improves system security.
- Marvell AVASTAR Wireless-AC Network Controller – Network adapters: 15.68.9125.57 improves system security.
If you're still running a Surface Pro 3 as your main device, you should be able to snag these updates now via Windows Update.
Has this latest update fixed the type cover not working error that appeared with a recent firmware update.
So I'm not the only one then?!
Definitely not. https://answers.microsoft.com/en-us/surface/forum/surfpro3-surfperf/type... And I've verified this firmware update does not fix the type cover issue.
My Bluetooth adapter hasn't been failing so hopefully they fix it. I'm still mad about the heat causing my screen to crack. Hopefully this update will give me Bluetooth back
I must be one of the handful of people who never upgraded the SP3 to Windows 10. "Available for devices on the Windows 10 Creators Update (version 1703) and later.." Oh well. I probably would at this point (if it was still free) as many of the apps are in Win 8 are dead (though I still prefer that OS for this device.)
A real Tablet oriented OS.
Why the Tablet mode in Windows 10 can't be like Windows 8?
At least without being forced to install firmware updates, your type cover keyboard will stay working, and you need not pay roughly the same price as your original SP3 for a replacement unit.
Windows 10 Pro is working very well with surface pro 3.
Get the best of Windows Central in in your inbox, every day!
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.