Windows 10: KB4087256 Servicing stack update for Windows 10 v1709 - Feb. 13

Source: https://support.microsoft.com/en-us/...bruary-13-2018


Direct download links for KB4087256 MSU file from Microsoft Update Catalog:

*Arrow Download KB4087256 MSU for Windows 10 v1709 32-bit (x86) - 5.9 MB

*Arrow Download KB4087256 MSU for Windows 10 v1709 64-bit (x64) - 13.0 MB

 

I had to look in "Installed Updates" to see if KB4087256 was installed.

*Arrow View Windows Update History in Windows 10 | Windows 10 Tutorials





:)

 

Servicing Stack Update for Windows10 Version 1511 (KB3140741)

Since the recent Servicing Stack Update to Windows 10, KB3140741, I have been unable to connect to the internet via my usb network adaptor from shutdown. When I restart the internet connects normally and holds connection. Also if I unplug the usb adaptor
and reconnect it the internet connects and holds connection.

I have tried adaptor driver update, uninstall and reinstall network adaptor, network troubleshooter ( this sometimes works!), and networking commands in command prompt window as detailed in Windows 10 help(Fix Network Connection Issues). I have also tried
different usb sockets on my computer, and resetting the router.

Thus I am able to use the internet, but it is extremely inconvenient to have to keep restarting to connect as detailed above. Also the adaptor worked flawlessly prior to the update.

Hoping you can provide some help to resolve this problem.

 

2017-09 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4040724) fails to install.

You are welcome. Let us know how it went.

One thing: That article speaks of "servicing stack" update KB4035631. It's not for Win 10, v1703, & it will appropriately refuse to install. Here is the one for
v.1703...

https://support.microsoft.com/en-us...stackupdateforwindows10version1703june13-2017

Servicing stack update for Windows 10 Version 1703: June 13, 2017

 

Thanks Brink, I had to check installed updates through the CP as that was the only place that showed that update. It certainly wasn't showing in update history.