Home network discovery not working after latest W10 Update

If it were me, I'd try DISM before doing a clean install.

Tried DISM and after thrashing around for awhile it comes back with a "Sources" issue. Tried several different versions of W10 boot media but it did not like any of them.

Got a new problem that destroys everything I thought was true. One of the systems that was visible on the network suddenly became invisible. Since this was the other system that I let W10 update rather than do a clean install I decided to test the theory and do a clean install. Nothing but sadness! After a clean install with nothing else done to the system except apply whatever updates W10 Update found, the system is still not Discovered on the network.

I'm tired of screwing around, I guess I will have to learn how to address the two problem systems directly and move on until MS resolves the W10 Discovery issues. It seems every time an update comes along for W10 something changes the Discovery function - at least at my house!

Question is why did you try several different versions of Windows 10??? Only ONE would be the correct version....Type winver in your search window and it should display your Windows 10 version. That would be the only version you need for Dism to read. Then use the ISO from Tech bench.....its looking for the boot.wim file in the ISO.

I'm running W10 Pro V1511 on all seven PC's I'm playing with. That's the Install Boot DVD and/or Boot USB that I tried initially. I only mentioned the other W10 Boot versions because I have a collection of them all of which are obsolete since V1511 was distributed. Is there something special about the ISO version from Tech Bench?

Based on my latest disappointment (fresh install - no Discovery), I suspect that fixing whatever is wrong with the one initially in question probably won't fix the Discovery Problem?! I'm starting to wonder if I got something going on with the network router or switch?

Ken429 said:

I'm running W10 Pro V1511 on all seven PC's I'm playing with. That's the Install Boot DVD and/or Boot USB that I tried initially. I only mentioned the other W10 Boot versions because I have a collection of them all of which are obsolete since V1511 was distributed. Is there something special about the ISO version from Tech Bench?

If you try to use the ISO from Media Creation Tool for running Dism to repair system files it will fail. as the boot.wim is in a different format. If you already have the ISO from Tech Bench, that has the right boot.wim format and if you type in the correct location for this iso then dism will find the needed boot.wim file it needs to repair your Windows 10. Here are the steps for running Dism command.

1- Create a folder on desktop: mount
2- Copy install.wim to desktop from the extracted ISO in the Sources folder.
Open Admin Command prompt, copy each line then run:
Dism /mount-wim /wimFile:%USERPROFILE%\Desktop\install.wim /index:1 /MountDir:%USERPROFILE%\Desktop\mount
Dism /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-Image /RestoreHealth /Source:%USERPROFILE%\Desktop\mount\windows /LimitAccess
Dism /unmount-wim /Mountdir:%USERPROFILE%\Desktop\mount /discard
After done with component store repair, run: sfc /scannow
NOTE: You might have to re-run sfc multiple times until you get a clean message.

OK, I downloaded and burned a DVD of the Windows ISO from Tech Bench. Ran the following in an administrative prompt:

Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:K:\sources\install.wim:1 /limitaccess

DISM said it completed successfully.

Ran from an administrative prompt:

Dism /Online /Cleanup-Image /ScanHealth

DISM said all was well - screen shot attached.

Rebooted system and still have - no Discovery - pretty much as I suspected.

What I did was what Brink said todo in the Tutorial you pointed me to a few posts back. Seemed pretty straight forward after you told me what Windows ISO to use. Where did I go wrong?

Ken429 said:

OK, I downloaded and burned a DVD of the Windows ISO from Tech Bench. Ran the following in an administrative prompt:

Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:K:\sources\install.wim:1 /limitaccess

DISM said it completed successfully.

Ran from an administrative prompt:

Dism /Online /Cleanup-Image /ScanHealth

DISM said all was well - screen shot attached.

Rebooted system and still have - no Discovery - pretty much as I suspected.

What I did was what Brink said todo in the Tutorial you pointed me to a few posts back. Seemed pretty straight forward after you told me what Windows ISO to use. Where did I go wrong?

Well now you got me on that question.....I'll check into more info on your network discovery problem ... BUT in one of your earlier posts you did report that Dism would not run without showing you problems, also you could not run SFC /Scannow and have it not report problems. So Dism is reporting a clean system, no problems found. Have you run SFC /scannow to see what it might report??

Yep, both DISM and Scannow reported problems with the system back up a few posts. So... DISM repaired something and Scannow repaired something (attached screen shot) after DISM did it thing. That's the good news, the bad news is Discovery still does not work on this machine and one other that I mentioned above.

Discovery worked on both of the problem machines prior to various W10 updates. Like I said above, I did a clean install of W10 Pro v1511 on one of the problem systems and it had no effect. The two machines in question have different MB's (Gigabyte and ASRock) and processors (Q9550 and 2600K). I have three other systems with ASRock Z97 MB's and they all work properly when it comes to network Discovery. I also have an ASRock Z77 Extreme 4 MB with a 3770K processor and it too works OK.

Ken429 said:

Yep, both DISM and Scannow reported problems with the system back up a few posts. So... DISM repaired something and Scannow repaired something (attached screen shot) after DISM did it thing. That's the good news, the bad news is Discovery still does not work on this machine and one other that I mentioned above.

Discovery worked on both of the problem machines prior to various W10 updates. Like I said above, I did a clean install of W10 Pro v1511 on one of the problem systems and it had no effect. The two machines in question have different MB's (Gigabyte and ASRock) and processors (Q9550 and 2600K). I have three other systems with ASRock Z97 MB's and they all work properly when it comes to network Discovery. I also have an ASRock Z77 Extreme 4 MB with a 3770K processor and it too works OK.

Well right now your computer has repaired the errors that you did have earlier, so you have repaired those problems at least. If this computer is not reporting any system errors I would not do a clean install like you were thinking about this morning. Only other thing I can think of would be the drivers on your network card. Sometimes Windows update replaces the default drivers from the manufacturer to Windows drivers, during a windows update. If you can find drivers for your network card drivers say from whoever made your motherboard, or even who made your network card, that might be something to try. I've had to replace 3 drivers on my computer because MS replaced them with their own drivers, and that did give me problems. After replacing those drivers, I changed windows update to NOT replace any drivers during a new update. Could be worth a shot.
Bottom line right now thou is....computer has no system errors, which is always good.

Also seeing how your system is error free, you might want to make a image backup of this OS and save it to a 2nd drive which is not on your OS. This way all the work you have done so far won't be wasted!! You could use Macrium Reflect free program to make your image backup. Keep it in a safe place.
https://www.tenforums.com/software-ap...ct-update.html

Trust me I believe in backups! I use four purchased copies of Reflect on the machines I use for good stuff and my home server (daily automatic backup) and the free version on the rest of the systems. Reflect has yet to fail me. I spent 40 years in systems develop so I know what can go wrong will and does. Still can't figure out why MS won't make Discovery work and keep it working on all systems. Never had this kind of problem onW7, W8...W8.1 or even the initial release of W10.