Classic Shell: Forum

During the nvidia driver update, explorer freezes and needs to be killed and restarted via task manager. The driver installation completes successfully.
I have taken a series of 30 dumps because the nvidia installer takes some time to complete.
I believe the issue is manifesting between dump 20 and 24 as I see the taskbar flashing at that point and then it's frozen. It looks like blocked event loop.
Notice that:
a) I use and have kept Launch folder windows at separate process enabled and taken the dump using the pid.
b) Issue manifests on two systems in my disposal both running 4.3.0 on build 15063.250 but it also happened prior to the Creator's Update.

https://www.dropbox.com/s/7a0a9htxfyk78 ... ze.7z?dl=0

Cheers!

Does this happen if Classic Start Menu is not running? Try that.

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

I am a Windows enthusiast and did Classic Shell's testing and usability/UX feedback.

No it does not. The first thing I tried was uninstalling classic shell to test.

I will also add that both systems are in mint condition. They both pass sfc and dism checks. Specifically the laptop is new and has fresh installation of windows.

This appears to be the dreaded "too many threads get created by COM" problem. As of now I have not been able to repro it and I don't know how to fix it.

This started happening a few months ago, I thought it was related to the nvidia driver and did not investigate any further until I reproduced it in the laptop.

Not sure if you have Nvidia hardware but can you try this reproduction scenario:
Install a previous version of Nvidia driver and install Geforce Experience with it.
Initiate driver update from within Geforce Experience.
After the update finishes explorer should be in this state.

Unfortunately I am not very familiar with the inner workings of explorer but perhaps I could help somehow as I am a software developer.
Is there any way to identify which COM object triggers the thread spam? Or provide better debugging information via VS debugger?