Classic Shell: Forum

Just letting you know on windows 10 pro, I'm using ts plus to terminal services my way into this machine. After some time roughly 10min or so, a message will come up from cortana saying classic shell has crashed and the computer needs to log out. I can restart my remote session and everything will work again for 10min.


Please fix?


Thanks for such an awesome free product

What is the exact error message? A screenshot of the error would be helpful.

I was kind of in a rush to clear up the issue, sorry. Is there an event log I can perhaps read and relay to you? I ended up removing the program for the time being.

Cortana has nothing to do with Classic Shell. That's why I need to see the exact message. I don't know of any log that is relevant.

I'm searching thru the event logs now and found this with keywords: classic



The description for Event ID 56 from source Application Popup cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

ACPI
5

the message resource is present but the message is not found in the string/message table

I believe in windows 10 cortana just appears with just about any "windows related" error. The dialog box just says "cortana" on it.

Also just found this:


The program explorer.exe version 10.0.10240.16431 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 860
Start Time: 01d105168b927741
Termination Time: 0
Application Path: C:\Windows\explorer.exe
Report Id: aac3d26e-710a-11e5-9bd2-408d5c1c5a45
Faulting package full name:
Faulting package-relative application ID:

You can use these instructions to capture a crash dump in Explorer: http://www.classicshell.net/forum/viewt ... p?f=12&t=6

It doesn't create a crash dump. In fact I can continue to work indefinitely just fine, except the entire bar at the bottom and start menu are completely frozen and unusable until I log out of my session and log back in.

"stopped interacting with Windows" means the process froze for a long time. You can capture a dump of the frozen process as well. It will show what it was doing at the time.

Well it looks like it may not be classic shell. I've removed classic shell and restarted the PC, and now I'm getting "start menu" rather than "classic shell"..... perhaps its a tsplus issue then. haha oh what fun...

Are you certain the old message did say "Classic Shell" and not "Start menu"? Busted start menu is a common problem with Windows 10 and I am not aware of a fix. I just know it is not related to Classic Shell.