File explorer slow in opening folder with shortcuts

Recently a change occured (after an update?).
I have a folder containing only 6 shortcuts, linking to devices or to drives, connected to devices, in my home network. Opening this folder takes about 30 sec. It has to do with those shortcuts that link to drives, connected to devices, which are off. Apparently, file explorer, when trying to present the shortcuts, also tries to get some info from those drives. After failing, file explorer nevertheless decides to present the shortcut after long waiting time.
This effect has come recently in W10. In most cases, the effect is there, but in a few cases, the map is opening normally.

Additional info:
When the folder is closed for a longer period, then opening gives an instantaneous result.
After closing the folder, and opening again some time after closing, the shortcuts only show up after ca 30 sec.

Hello Piko,

Do you see a green progress bar advancing from left to right at the top of File explorer when it is trying to open the folder? If you do it indicates Windows is searching for files or a pathway to devices/drives.

philc43 said:

Hello Piko,

Do you see a green progress bar advancing from left to right at the top of File explorer when it is trying to open the folder? If you do it indicates Windows is searching for files or a pathway to devices/drives.

No, I donot see this progress bar. I tried several adjustments such as changing attributes or excluding the folder from Windows Defender check, but to no avail. So, when a network device is off and I have a shortcut in a folder, linked to this device, for example \\192.168.2.xx the folder always opens immediately. But if the shortcut links to \\192.168.2.xx\storagefolder, then opening of the shortcut folder either goes immediately or takes about 30 sec. Which choice the file explorer makes, is unpredictable and irreproducible. Apparently, file explorer sometimes forgets its history and sometimes not. Maybe that could be the main question mark, although the file explorer problem only occurs in this case.

It is possible that this has to do with "Master Browser" settings for networked devices. If you Google this you will see that W10 has a problem in finding network PC or devices if it is not the master browser on the network. Whether or not your PC is the Master Browser depends on if it was the first device powered up or if other devices have been turned off that were previously assigned as the Master Browser on the network.

You can check the devices on your network as follows:

1.Open up a command prompt
2.Type net view and hit enter
3.Look at the list of computer names. These are the computers on your LAN. Note that the format is \\COMPUTER-NAME
4.For each name in the list, type the following command: nbtstat -a COMPUTER-NAME

One of the results from the nbtstat commands will show a row with “_MSBROWSE_” in it. That means that this computer is the Master Browser.

When you have problems it would be interesting to know if it is when your PC is NOT the Master Browser. If so it is likely not able to find network folder as quickly.

philc43 said:

It is possible that this has to do with "Master Browser" settings for networked devices. If you Google this you will see that W10 has a problem in finding network PC or devices if it is not the master browser on the network. Whether or not your PC is the Master Browser depends on if it was the first device powered up or if other devices have been turned off that were previously assigned as the Master Browser on the network.

You can check the devices on your network as follows:

1.Open up a command prompt
2.Type net view and hit enter
3.Look at the list of computer names. These are the computers on your LAN. Note that the format is \\COMPUTER-NAME
4.For each name in the list, type the following command: nbtstat -a COMPUTER-NAME

One of the results from the nbtstat commands will show a row with “_MSBROWSE_” in it. That means that this computer is the Master Browser.

When you have problems it would be interesting to know if it is when your PC is NOT the Master Browser. If so it is likely not able to find network folder as quickly.

I found for my PC the row with MSBROWSE

That's good! So if you are still having the problem it must be something else and I was on the wrong track.