Hi,
I have done a bit of research on this but not come up with anything much.
Here goes, when I click the Start button in Windows 7 (x64) and choose any
program from the start menu, my Windows Explorer stops responding and a window
pops up saying Explorer is restarting. This happens 95% of the time, sometimes
it starts the programs with no problem and doesnt crash.
It sometimes crashes even if I dont click an icon. IE. If I click the Start
button -> Prgrams then click out of the start menu, say, into my browser that
is open behind, it will crash Explorer.
I have noticed if I hold shift while clicking an icon to load a program, this
keeps the start menu open, I can then back out of the menu and click the start
button again to close the menu and it doesnt crash this way.
I am running version 3.1.0 and Windows 7 x64
I dont use any other taskbar modifier.
Regards,
W
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Try this. Run "ClassicStartMenu.exe -nohook". This is supposed to show the
start menu only once, but without involving Explorer. If it crashes that way
too it will be easier to troubleshoot.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2011-08-07
I am having the same problem. I can consistently crash it by clicking on
START, SETTINGS and choosing the Control Panel. I tried the "-nohook" option
and it performed the above step without crashing.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2011-08-07
I also note that I can also get it to crash just by clicking on START and
selecting any menu option that has a cascading submenu. Once I click out to my
desktop (as if I decided to do nothing in the Classic Start menu) I will
experience the same explorer crash. If I click on START and hover over any
option that does not have a cascading submenu and then click to my desktop, I
do not get a crash.
I hope this helps in troubleshooting the issue.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, I have just started using Classic Shell (version 3.1.0) -- in
preference to a paid-for product "Seven Classic Start" which functions
similarly but has woefully bad performance, sometimes taking tens of seconds
to respond.
Hello Ivo!
I'm also getting the same error (under 64-bit Windows 7). I sent a copy of my
XML file to your e-mail address on 09 August 2011 and hope that this will shed
some light on this annoying problem.
Also, I can confirm that these crashes do not occur when launching Classic
Shell via
C:\Program Files\Classic Shell\classicstartmenu.exe -nohook
What are the prospects that you will determine the cause and deliver a fix
soon? Days or weeks?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think I have identified a problem, which will be fixed in the next version.
It is caused by enabling two options at the same time:
General Behavior -> Enable accessibility
Search Box -> Enable Auto-Complete
Turn off one of the two and let me know if that fixes your problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I have done a bit of research on this but not come up with anything much.
Here goes, when I click the Start button in Windows 7 (x64) and choose any
program from the start menu, my Windows Explorer stops responding and a window
pops up saying Explorer is restarting. This happens 95% of the time, sometimes
it starts the programs with no problem and doesnt crash.
It sometimes crashes even if I dont click an icon. IE. If I click the Start
button -> Prgrams then click out of the start menu, say, into my browser that
is open behind, it will crash Explorer.
I have noticed if I hold shift while clicking an icon to load a program, this
keeps the start menu open, I can then back out of the menu and click the start
button again to close the menu and it doesnt crash this way.
I am running version 3.1.0 and Windows 7 x64
I dont use any other taskbar modifier.
Regards,
W
Try this. Run "ClassicStartMenu.exe -nohook". This is supposed to show the
start menu only once, but without involving Explorer. If it crashes that way
too it will be easier to troubleshoot.
I am having the same problem. I can consistently crash it by clicking on
START, SETTINGS and choosing the Control Panel. I tried the "-nohook" option
and it performed the above step without crashing.
I also note that I can also get it to crash just by clicking on START and
selecting any menu option that has a cascading submenu. Once I click out to my
desktop (as if I decided to do nothing in the Classic Start menu) I will
experience the same explorer crash. If I click on START and hover over any
option that does not have a cascading submenu and then click to my desktop, I
do not get a crash.
I hope this helps in troubleshooting the issue.
Please send an email to classicshell@ibeltchev.com. We can perform some
troubleshooting steps.
ibeltchev... email was sent.
Hello, I have just started using Classic Shell (version 3.1.0) -- in
preference to a paid-for product "Seven Classic Start" which functions
similarly but has woefully bad performance, sometimes taking tens of seconds
to respond.
Hello Ivo!
I'm also getting the same error (under 64-bit Windows 7). I sent a copy of my
XML file to your e-mail address on 09 August 2011 and hope that this will shed
some light on this annoying problem.
Also, I can confirm that these crashes do not occur when launching Classic
Shell via
C:\Program Files\Classic Shell\classicstartmenu.exe -nohook
What are the prospects that you will determine the cause and deliver a fix
soon? Days or weeks?
I think I have identified a problem, which will be fixed in the next version.
It is caused by enabling two options at the same time:
General Behavior -> Enable accessibility
Search Box -> Enable Auto-Complete
Turn off one of the two and let me know if that fixes your problem.
Thanks, Ivo!
I disabled the accessibility option and the error message didn't appear.
-- Cheers, Tony Austin.
The latest version 3.2.0 fixes this problem. It was an incompatibility between
the auto-complete and the accessibility features.