Classic Shell: Forum

(I searched the forum but didn't find a similar thread in which this bug (is it a bug ??) was brought forward.)

- When I run a program called "Tweaking's Windows Repair" (http://www.tweaking.com) on my Win 7 SP 1 system then in one repair ("Repair Icons") the process "Explorer.exe" is killed and restarted. Running this repair is needed to make Windows re-generate the (corrupted) Windows thumbnail caches. After Explorer is restarted "Classic Shell" (CS) doesn't work anymore, then (among others) the default Windows "Start" button is back again. (Although the process "ClassicMenu.exe" keeps running). I have to restart my system to get CS working again.

- I know that when Explorer.exe is re-started then it sends out a socalled "Explorer started" Event to inform other programs that "Explorer.exe" has been restarted. Does CS reply to this Event at all ? Or is this Event "lost" or "absorbed" somewhere by other program that is running ? I ask because some other programs also fail to respond to this Event.

- Is there a work-around, a fix for this problem ? To be fixed in the next version ? (Should this thread be moved to the "Requests" subforum ??).

(Still love the program, though).

Probably that program runs as admin, and then it restarts Explorer as admin too. Try restarting Explorer yourself from Task Manager.

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

(Didn't have time too reply earlier)

- Did some testing. And the results are interesting & revealing. "Windows Repair" (WR) (See above) "breaks" Classic Shell (CS). WR stops the process "Explorer.exe", deletes the iconcaches and then re-starts Explorer.exe. But then CS doesn't show up anymore. Then the CS "Start" button reverts to the default button. These actions were done under a user account, not the administrator account.
- However, when I then kill & re-start Explorer.exe (using Task Manager) then CS re-emerges without a hiccup, in its former glory.
- So, WR seems to be the cause of this odd behaviour of CS.