Windows 10: Can't see Win10 PC on network after KB4041676 Cumulative Update

Windows 10 installed the KB4041676 cumulative update to 1703 build 15063.674 on my Toshiba notebook last night. Now the 3 other PCs on my home network can't see the Toshiba anymore. But the Toshiba sees them and connects to the Internet via my Netgear router. Systems on the network:

* Desktop running Windows 7 64 bit
* Desktop running Windows 10 32 bit
* Notebook running Windows 7 32 bit
* Notebook running Windows 10 64 bit

Options in Advanced sharing settings 'Private (current profile)' haven't changed:

[x] Turn on network discovery
. . [x} Turn on automatic setup of network connected devices
[x} Turn on file and printer sharing.

Under 'Settings > Update & security >Troubleshoot' I ran the 'Incoming Connections Troubleshooter > What are you trying to do > Share files and folders'. That reported, "Problems found - Windows requires more information to diagnose the problem. - Not fixed." I have yet to get any troubleshooters in Windows to fix these sorts of issues.

I don't use the Homegroup for sharing, preferring to share individual folders on various systems. So I have turned on password protected sharing on each system and have created user accounts on all systems for the same 4 users on all 4 systems.

Any suggestions on what may have caused this, and how to fix it?

Thanks for any thoughts on all this. *Smile

Edit: Also ran these troubleshooters with no success:
* HomeGroup
* Internet Connections
* Network Adapter

Have also tried disabling antivirus
Disabled the Windows 10 Firewall.
Network properties on Toshiba shows IPv4 & IPv6 connections made in both Wifi & Ethernet individually.
I am able to ping the Toshiba from the other systems.

:)

 

Windows 10 Update KB4041676

1. Did you ever "reinstall" Windows 8.1 before (or after) you upgraded to Win10?

2. When (approx.) date did you replaced the HDD with a SSD and then do a "clean install" of Win10?

3. What installation media did you use to do the "clean install" of Win10?

4a. How did you "reinstall" Win10 three (3) days ago?

4b, Why did you "reinstall" Win10 three (3) days ago?

5. Had KB4041676 been installed before you "reinstalled" Win10 three (3) days ago and if so, was the mouse working then?

6. How old is the mouse? Has bloody.com Support confirmed that it's fully-compatible with Windows 10 Version 1703 OS Build 15063.674 - as well as Windows 10
Version 1709?

7. Do you see the same behavior when using a different (e.g., wired or wireless; newer) mouse?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

COMMENTS:

Mouses are fairly inexpensive these days. If a newer/different mouse works OK with KB4041676 and Windows 10 1709 installed, is troubleshooting the problem worth it?

There is a way to "block" KB4041676 but chances are you'll see the same behavior after installing the next cumulative update for Win10 1703 - as well as after upgrading to Win10 1709.

If the behavior's caused by a driver update which Windows Update installed, you can rollback (or reinstall) the driver & "block" it from installing again. Then you can configure your system such that no further driver update of any kind are ever install
via Windows Update again.

 

2017-10 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4041676)

Hello I can't install 2017-10 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4041676

ho do I solve this issue

 

Can't count the number of times I rebooted the systems the other day... always my #1 goto action to resolve this issue. But today after booting them up, the problem was gone. Maybe I just wasn't believing in fairies enough the other day Tinkerbell *Wink

 

Glad its working for you now, the only thing from your OP to check would have been your Security Settings on your shares

 

Ah yes... Security Settings on shares. I forgot about that @Clintlgm. Thanks for mentioning that. I'll add it to my checklist for future reference.

 

Yes I'll be looking out for that after this FCU update, the CU did change my setting and it took me awhile to figure it out.