Classic Shell: Forum

Hi,

I am having some problem using Classic Start Menu on Windows 10.
I have two input languages installed on my system, English (US) and Thai.
The usual way to switch between these two languages is to press the Grave Accent (`) key.

However, I found that pressing the grave accent key would cause Classic Start Menu crash to and restart.
This only happens the Classic Start Menu is in focused, for example typing in the search box, and when typing a file/folder name on Desktop.
What would happen is Classic Start Menu would freeze for about 10 seconds and then it would restart itself again.
When I am on other program I could just use the (`) key to switch language just fine.

I hope that you can fix this bug.
Thank you.

Please capture a crash dump: viewtopic.php?f=12&t=6

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

I am a Windows enthusiast and helped a little with Classic Shell's testing and usability/UX feedback.

I have two explorer processes running.
I've tried to capture a crash dump on one of them but it says "The process has exited. Dump count not reached."
Any advice?

C:\Users\ongarta\Desktop\Procdump>procdump -e 6960

ProcDump v7.1 - Writes process dump files
Copyright (C) 2009-2014 Mark Russinovich
Sysinternals - http://www.sysinternals.com
With contributions from Andrew Richards

Process: explorer.exe (6960)
CPU threshold: n/a
Performance counter: n/a
Commit threshold: n/a
Threshold seconds: 10
Hung window check: Disabled
Log debug strings: Disabled
Exception monitor: Unhandled
Exception filter: *
Terminate monitor: Disabled
Cloning type: Disabled
Concurrent limit: n/a
Avoid outage: n/a
Number of dumps: 1
Dump folder: C:\Users\ongarta\Desktop\Procdump\
Dump filename/mask: PROCESSNAME_YYMMDD_HHMMSS


Press Ctrl-C to end monitoring without terminating the process.

[15:28:38] The process has exited.
[15:28:38] Dump count not reached.


C:\Users\ongarta\Desktop\Procdump>

If you have two Explorer processes, restart Windows and then when you log in, you will have only one Explorer process. Then run procdump immediately (without opening any Explorer windows) and try to make it crash. Then attach the dump file (*.dmp) here so it can be analyzed.

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

I am a Windows enthusiast and helped a little with Classic Shell's testing and usability/UX feedback.

I have restarted, now there is only one explorer.exe process and ran procdump.
It still only shows:
[15:59:01] The process has exited.
[15:59:01] Dump count not reached.

Thanks.

C:\Users\ongarta\Desktop>procdump -e explorer.exe

ProcDump v7.1 - Writes process dump files
Copyright (C) 2009-2014 Mark Russinovich
Sysinternals - www.sysinternals.com
With contributions from Andrew Richards

Process: explorer.exe (4368)
CPU threshold: n/a
Performance counter: n/a
Commit threshold: n/a
Threshold seconds: 10
Hung window check: Disabled
Log debug strings: Disabled
Exception monitor: Unhandled
Exception filter: *
Terminate monitor: Disabled
Cloning type: Disabled
Concurrent limit: n/a
Avoid outage: n/a
Number of dumps: 1
Dump folder: C:\Users\ongarta\Desktop\
Dump filename/mask: PROCESSNAME_YYMMDD_HHMMSS


Press Ctrl-C to end monitoring without terminating the process.

[15:59:01] The process has exited.
[15:59:01] Dump count not reached.

After running procdump -e explorer.exe, you are trying to make the crash happen right? Open the Start Menu and press the ` key (or do whatever makes it crash while procdump is still running). Let it crash, the taskbar will disappear and appear again and only then a dmp file will be created.

Also, you could try this alternate method to capture the crash dump: viewtopic.php?f=12&t=6#p9789

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

I am a Windows enthusiast and helped a little with Classic Shell's testing and usability/UX feedback.

Another thing is that Windows 10 Explorer.exe is very sensitive to slowdowns too. When you press the grave accent key (`), it may be possible that it is just becoming very unresponsive and restarting due to the slowdown. If that is the case (if you are not getting a crash dump at all), try using the command for the slowdown dump: procdump -n 10 -s 1 explorer.exe

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

I am a Windows enthusiast and helped a little with Classic Shell's testing and usability/UX feedback.

So I tried the slowdown dump.
I managed to get 6 dumps before explorer.exe exited.
Here is the link to the dump files: https://www.dropbox.com/s/4m0ulhf5y7v4e ... p.zip?dl=0
Thanks.

Here is the command:

C:\Users\ongarta\Desktop\Procdump>procdump -n 10 -s 1 explorer.exe

ProcDump v7.1 - Writes process dump files
Copyright (C) 2009-2014 Mark Russinovich
Sysinternals - http://www.sysinternals.com
With contributions from Andrew Richards

Process: explorer.exe (4980)
CPU threshold: n/a
Performance counter: n/a
Commit threshold: n/a
Threshold seconds: n/a
Hung window check: Disabled
Log debug strings: Disabled
Exception monitor: Disabled
Exception filter: *
Terminate monitor: Disabled
Cloning type: Disabled
Concurrent limit: n/a
Avoid outage: n/a
Number of dumps: 10
Dump folder: C:\Users\ongarta\Desktop\Procdump\
Dump filename/mask: PROCESSNAME_YYMMDD_HHMMSS


Press Ctrl-C to end monitoring without terminating the process.

[17:39:54] Timed: 1s (Trigger)
[17:39:54] Dump 1 initiated: C:\Users\ongarta\Desktop\Procdump\explorer.exe_580910_173954.dmp
[17:39:57] Dump 1 complete: 10 MB written in 3.5 seconds
[17:39:58] Timed: 1s (Trigger)
[17:39:58] Dump 2 initiated: C:\Users\ongarta\Desktop\Procdump\explorer.exe_580910_173958.dmp
[17:39:59] Dump 2 complete: 10 MB written in 0.5 seconds
[17:40:00] Timed: 1s (Trigger)
[17:40:00] Dump 3 initiated: C:\Users\ongarta\Desktop\Procdump\explorer.exe_580910_174000.dmp
[17:40:00] Dump 3 complete: 10 MB written in 0.6 seconds
[17:40:01] Timed: 1s (Trigger)
[17:40:01] Dump 4 initiated: C:\Users\ongarta\Desktop\Procdump\explorer.exe_580910_174001.dmp
[17:40:02] Dump 4 complete: 10 MB written in 0.9 seconds
[17:40:03] Timed: 1s (Trigger)
[17:40:03] Dump 5 initiated: C:\Users\ongarta\Desktop\Procdump\explorer.exe_580910_174003.dmp
[17:40:04] Dump 5 complete: 10 MB written in 0.6 seconds
[17:40:05] Timed: 1s (Trigger)
[17:40:05] Dump 6 initiated: C:\Users\ongarta\Desktop\Procdump\explorer.exe_580910_174005.dmp
[17:40:06] Dump 6 complete: 10 MB written in 0.5 seconds
[17:40:07] The process has exited.
[17:40:07] Dump count not reached.


C:\Users\ongarta\Desktop\Procdump>

Yes, the edit box seems to get stuck switching languages. However it is not clear why from the dump.
Can you try a different key combination, like Alt+Shift?

I tried on Windows 10 with multiple languages and using the grave accent (`) key to switch languages but couldn't reproduce any slowdown or crashes.

Btw, Microsoft introduced a new visual way of switching languages in Windows 10 (and 8) with Win key+Space.

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

I am a Windows enthusiast and helped a little with Classic Shell's testing and usability/UX feedback.

Using other key combinations to switch language does not cause the restart.
I have tried Alt+Shift, Ctrl+Shift, Win + Space, and clicking on the language bar.

The grave accent (`) key is the standard to switch language in Thailand.
I will find another Windows 10 PC and see if I can replicate the problem on other Windows 10 PC with Classic Start Menu.