I am using Windows 10 version 1511 (OS Build 10586.753). I'm facing a problem in the "Save as" dialog box. It freezes for 15-20 seconds in every software, be it Chrome, Firefox, Microsoft word, photoshop, etc.What must I do to resolve this issue?
When you open a 'Save as..' window from any app you are actually calling Explorer.exe with some custom parameters, the same executable that when run without any parameters gives you File Explorer. A freeze suggests that a folder or device in the view it opens to is not immediately accessible and takes a while to confirm that it's there.
Do you have any mapped network drives, for example? Or an external drive that may need to spin up before it can be seen? Exactly what causes your delay depends on how your system is configured. Does File Explorer freeze in a similar way? If so, find the folder/device that causes the delay there and it should fix it for 'Save as..' too.
No, I don't have any mapped drives. My pc is all alone. File Explorer works flawlessly. Its just the save as dialogue box which is causing trouble.
This problem has been around far longer than Windows 10. It often involves a previously network connection that's no longer available. It can be difficult to track down because (obviously) you won't see a mapping that Windows tries (and fails) to find. It could even be down to Onedrive not being signed in.
"Save As" and "Open" file dialog windows very slow to appear......Only when I disabled my LAN connection did the dialog windows appear instantly...
...After considerable effort on this problem, I finally figured out the solution - in my case, at least. As I mentioned, I had recently changed the names of several of the PCs on my home network. I discovered that Windows (XP and 7) retains the old names in the Registry and tries to search them when you do a Save As or an Open. That causes it to go into a loop for awhile...
I'll check out the link soon. Just to be more clear. I've never mapped my PC or networked it anywhere. It's been all alone since 2006.
I tried this as explained on this web page
https://social.technet.microsoft.com...tpronetworking
sc config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc config mrxsmb20 start= disabled
It hasn't helped me yet.
Changing the name of the PC doesn't help either, neither changing the name of the workgroup.
Quote