Classic Shell: Forum

Greetings.

How do you end the ClassicStartMenu.exe in Task Manager? Because "end task" using Task Manager does not end it. It remains running even though it disappears from the Task Manager list.

Or any method other than right clicking the Start button and clicking "Exit"?

I'm trying to build a script for use with AutoHotKey that exits Class Start Menu with a hotkey, and without using a mouse driven or click method.

Sure. ClassicStartMenu.exe -exit

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

Where would one use that command? It doesn't work at command prompt, and it doesn't work within a AutoHotkey script.

And how do you end Classic Start Menu within Task Manager? I'm confused because "Classic Start Menu" is listed under "Processes" within Task Manager but when you click "End task" it disappears from the list but the software remains running. And there doesn't seem to be any other process in Task Manager to end. I don't understand how a software can have its process ended and still remain functioning.

You have to enter it on the command line. Of course you have to be in the Classic Shell directory, where ClassicStartMenu.exe is.
The start menu is not in that process. The start menu is in the explorer process. The ClassicStartMenu process is there to inject the start menu into explorer and to watch in case explorer restarts for some reason.

Thanks. I figured it out.

I used the following on the command line:
>"C:\Program Files\Classic Shell\ClassicStartMenu.exe" -exit

And thanks for explanation about the process and why "End task" in the Task Manager does not kill it. Now I get it.

Given that people do need to exit CSM and restart it, why not App Paths? . It's a harmless improvement and users need to exit the menu for *some* changes definitely. In fact, while adding to App Paths, it can be shortened to CSM instead of "ClassicStartMenu.exe". It's easier for scripts too since one may choose to install Classic Shell in D:\Program Files instead of C:\. Most users aren't aware of App Paths to add it themselves.

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

ClassicStartMenu.exe is not a commonly started program. No need to pollute the App Paths with it. If a script needs the path, it can be found in HKLM\Software\IvoSoft\ClassicShell