[BUG]: Slow file explorer - networked drives

[Pe6r0]

Description

Hey so I have my NAS's networked drives mapped in the pc (I imagine that's the issue) and ran the standard but now the file explorer will take about 20 seconds to start up if they aren't acessible. To top this I also have nordVPN. In the past I've never had an issue having both local lan networked drives and the vpn running, as well as it not taking 20 seconds to startup if they weren't acessible.

I don't want to reinstall my OS or revert everything so is it possible to know which bits I should revert? Thanks

OS

windows 10 pro build 22631.3235

Reproduction steps

Just open the file explorer in the conditions I specified above (a networked drive no longer acessible)

yes.

Scripts

I ran the desktop application, just the normal standard one.

Screenshots

no applicable SS

Additional information

I don't know, lemme know if you need more info, thanks

[Pe6r0]

I don't know if it helps but the error it does give when I do click on them (instead of it being unavailable) is "The local device name is already in use. This connection has not been restored."

[Pe6r0]

If anyone else runs into this: there is some feature of windows that this script disables that has the normal functionality. This can be circumvented by adding split tunneling to the file explorer.

[undergroundwires]

Hi @Pe6r0, happy that you found the root cause and thank you for sharing the insights. Did you figure out which script/missing feature causes this? If we know that, we can remove that script from "Standard" pool and document this side-effect.