Classic Shell: Forum

Good Morning,

My environment is virtual.
(VDI on VMware Horizon 7.2)
Windows 10 Enterprise 2016 LTSB
IE11
Classic Shell 4.3.1
Office 2016 Enterprise plus
Adobe Reader DC, 7Zip, Notepad++, VLC, Pdfcreator and another small tools.

When I start my session, I check with Resmon the threads on "Explorer.exe " and it's 173
After one minute, the explorer is stuck; new check and the threads on "Explorer.exe " is more 812

I restart the process explorer.exe and it's OK.

I don't understand where is the problem.

In my Zip attachment, I have several dump

Thank's in advance for your help.

David

This problem was reported by some other Windows 10 users. Hopefully your dump will help Ivo determine the cause.

_________________
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.

I don't know what is causing this problem. I was hoping some changes to the latest version will make it go away, but obviously not.

Hello Ivo,
Ok I think It's not easy.
I have work today on my vm and I have found maybe 2 ways for a solution. (I send the printscreens on the zip attachement)

1.
When I'm in Group Admin Local with my user, I have not problem. It's run very well.
When I'm in Group User (without rights) with my user, the problem come.

On this website https://msdn.microsoft.com/en-us/library/bb625963.aspx (Table 7 Integrity levels linked to specific SIDs) I read that:


If admin mode explorer.exe run in HIGH Assigned integrity level (Administrators)

If user mode explorer.exe run in MEDIUM Assigned integrity level (Authenticated Users)

2.
When I'm in Group User (without rights) with my user, the problem come.
First time In Process Explorer, the process ClassisStartmenu.exe is under Explorer.exe.
When the stuck coming is restart explorer.exe, the process ClassicStartmenu.exe is alone not under Explorer.exe.
I close my session and I restart my session and I have no problem.

Another information:
In my Virtual environnment, I use VMWare UEM for the userprofile.
Classic Shell use special folder or registry in the user ? Beacause I'ts very important that I capture this settings.

Thank's for your help.

David

We're also running Windows 10 Enterprise LTSB with the latest windows updates. I can also reproduce this problem with domain users which are member of the clients local admin group.

Clicking random folders in explorer increases the thread count in a few minutes to approximately 820. Then explorer crashes and I'll have to restart the explorer.exe process and it starts all over again.
When i remove classic shell in the 'infected' user session (so without restarting windows or logging out and in) and restart explorer.exe i can't reproduce the problem anymore. When i reinstall classic shell in the same user session the problem is back immediately. I tried this multiple times just to be sure that is has something to do with classic shell.

But sometimes if we restart the computer or logout and login again the explorer.exe stays around 100 threads no matter how often we click random folders. So the problem is not consistent.

If the developers are still struggling to reproduce the problem, maybe its an idea that we give the devs remote access to an 'infected' user session?

Has this issue been narrowed down to the Start menu component? Have you tried installing only the Start menu and omitting Classic Explorer and IE components?

_________________
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.

Just did some tests:
Installed Classic Shell with only the Classic Explorer feature. The threads stay low.
Installed Classic Shell with only the Classic Start Menu feature. The threads went up to 820.

So yes, i think it has something to do with the Start menu component.

Thx. for testing!

This sounds pretty similar to my posted problemhttp://www.classicshell.net/forum/viewtopic.php?f=12&t=5954

We narrowed the cause down to roaming profiles in combination with folder redirection.
We started using a powershell script to restart the explorer and started logging the restarts.
For Users with extreme restart counts (20-100 restarts a day) we used to follwing "fix":
Open an Explorer Window, go to the Folder Options, change any option in the "View" tab and apply.
Relog the user or restart the client.
Aslong as the local copy of the roaming profile isnt deleted, the explorer is just fine.