April 2018 Windows Update -- Can't see network on all machines.

I have two Dell desktops running Windows 10 Pro and a Lenovo Laptop running Windows 10 Home.  Before the update I could see all computers in the network in Windows Explorer.  After the update I can only view the whole network on the Windows 10 Home machine. 

I tried enabling SMP 1.0 /CIFS File Sharing Support on the desktops (per recommendations from the robot assistant linked to this forum), but that only allows me to see the one of the desktops, not the laptop.  I compared the laptop with the desktop SMP settings, and I notice that the laptop has an "SMP Automatic Removal" setting not present on the desktops. 

Is the "automatic removal" feature what's allowing the laptop to see the entire network?  If so, can it be added to a Windows 10 Pro installation?

This is what Microsoft recommends:

Explorer Network Browsing

The Computer Browser service relies on the SMBv1 protocol to populate the Windows Explorer Network node (also known as "Network Neighborhood"). This legacy protocol is long deprecated, doesn't route, and has limited security. Because the service cannot function without SMBv1, it is removed at the same time.

However, if you still have to use the Explorer Network in home and small business workgroup environments to locate Windows-based computers, you can follow these steps on your Windows-based computers that no longer use SMBv1:
Start the "Function Discovery Provider Host" and "Function Discovery Resource Publication" services, and then set them to Automatic (Delayed Start). When you open Explorer Network, enable network discovery when you are prompted.

All Windows devices within that subnet that have these settings will now appear in Network for browsing. This uses the WS-DISCOVERY protocol. Contact your other vendors and manufacturers if their devices still don't appear in this browse list after the Windows devices appear. It is possible they have this protocol disabled or that they support only SMBv1.

https://support.microsoft.com/en-us/help/403431...
Best,
Andre
twitter/adacosta
groovypost.com

5 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I'm not sure this applies, because I'm not using a legacy machine.  It's a two year old Dell XPS

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Well, you can try one of two things:

uninstall the April Update:

Press Windows key + R
Type: appwiz.cpl
Hit Enter
Click View installed updates

If the following KBs are are installed, right click KB4093105 then click uninstall

or

Upgrade to Windows 10 1803 to see if the problem is fixed.

Please be advised some users are reporting issues with the Windows 10 1803 update. Make sure you backup before attempting to upgrade:

http://answers.microsoft.com/en-us/windows/wiki...

How to block it if you don't want to upgrade:
https://www.groovypost.com/howto/block-windows-...

What is the make and model of your computer?

Have you checked the manufacturers website to determine compatibility?
Check this List to Determine if Your Computer is Compatible with the Windows 10 Fall Creators Update 1803
https://answers.microsoft.com/en-us/windows/wik...

perform the following tasks:
12 Things You Should Do Before Installing Windows 10 Creators Update (Version 1803)
https://www.groovypost.com/howto/prepare-comput...


How to download official Windows 10 ISO files
http://answers.microsoft.com/en-us/windows/wiki...

How to Upgrade to Windows 10 Creators Update version 1803 using ISO File from Versions 1507, 1511, 1607, 1703 or 1709
https://answers.microsoft.com/en-us/windows/wik...
Best,
Andre
twitter/adacosta
groovypost.com

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Thanks for the tips Andre.

My network has three computers:

1) Dell XPS 8900 desktop running Win 10 Pro April 2018 update 1803 (~2 years old)

2) Dell StudioXPS 435T Desktop running Win10 Pro April 2018 update 1803 (~9 years old)

3) Lenovo Flex3 1580 Laptop running Win10 Home April 2018 1803 update  (~ 2 years old)

I removed the 1803 update on the XPS 8900, but it re-installed itself. After the reinstall, I can see both the Flex3 and the 435T from the XPS 8900 with full read and write privileges.  I can see the 435T from the Flex 3, but can't see any the XPS8900 from either the 435T or the Flex3.  The XPS 8900 to Flex 3 communication is critical to me, and I can live with it the way it is now, but it would be much more convenient to be able to push files from the Flex 3 to the XPS 8900.  Should I be able to do that?

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Do this on the computer giving problems.

Open Start > Settings > Update & security > Troubleshoot
Scroll down
Click Network adapters
Click Run the Troubleshooter

When complete, restart to see if the problem is resolved.

If not, press Windows key + X
Click Device Manager
Expand Network adapters

Right click your adapter
Click Uninstall

Exit Device Manager, restart. Windows 10 should detect the network adapter then reinstall it. Check if you can connect and browse.

also try:

Open Start > Settings > Network & Internet > Status

Scroll to the bottom then click Network reset.

Disable Energy Efficient Ethernet in "Client for Microsoft Networks"
Best,
Andre
twitter/adacosta
groovypost.com

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Basic Question:

Should I be able to see and access all the computers logged in to my (private) network from any computer on the network no matter which computer boots first? I'd like to use all three computers as terminals so that I can copy files from one machine to the other.  All machines are used in different locations with different software.

One desktop and the laptop are connected by wifi.  One desktop is hard wired.  As it is now, the first computer I boot sees and has read/write privileges to the whole network.   The other wifi and hard wired computers can't see the computer that booted first.  This was confusing at first because the network owner moved from machine to machine, depending on boot sequence.  It also means that the first computer  booted (network owner) is the only one with Read/Write permissions.

Would it matter that I use the same log on with all three machines?

If I made my network public, but my router is password protected and only three computers have the password, would any other machines be able to access my network?

I have image files of all three computers.  Am I correct in assuming that I won't be able to get an ISO for the version of Windows prior to the April 2018 update 1803?  Am I correct in assuming that after May 10, I won't be able to revert to an earlier version of Windows without using those image files?

Follow up to the Andre's email immediately proceeding.

When I get to "Client for Microsoft Networks" the property box is visible but can't be clicked.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info


Last updated February 14, 2020 Views 3,567 Applies to: