Classic Shell: Forum

Hi,
I'm using Classic Shell 4.3.0, Windows 10 Home 64 bit.
My windows button doesn't open the menu, well not predictably. Sometimes, usually just after a restart, it'll work... Once... After that it's ignored.
It also stops win+prtsc from working (which is actually more of an inconvenience since I'm very familiar with ctrl-esc for the start menu from old keyboards!)

I saw old posts about checking the MouseClick setting, which I have... It all looks good to me.

<?xml version="1.0"?>
<Settings component="StartMenu" version="4.3.0">
<MouseClick value="ClassicMenu"/>
<AllProgramsMetro value="0"/>
<RecentMetroApps value="0"/>
<SkinW7 value="Windows Aero"/>
<SkinVariationW7 value=""/>
<SkinOptionsW7>
<Line>USER_IMAGE=0</Line>
<Line>SMALL_ICONS=0</Line>
<Line>LARGE_FONT=0</Line>
<Line>ICON_FRAMES=1</Line>
<Line>OPAQUE=0</Line>
</SkinOptionsW7>
<SkipMetro value="1"/>
</Settings>


Please, any ideas?

If other win+key related shortcuts aren't working either, it doesn't sound like classic shell is the cause.
Does win+e open file explorer?

If nothing with the windows key works, it's possible the key was remapped:
http://www.majorgeeks.com/files/details/keytweak.html This tool would allow you map it back to where it belongs if that is the case

Does the mouse click work every time?

Yup, without fail.

I just went through a few tests... Clicked on the desktop (empty bit of wallpaper), windows button doesn't work, clicked on the task bar (empty bit), windows button doesn't work. Used mouse to open start menu (left mouse over the start menu button), windows button still doesn't work. So it's going missing, even when Classic start should have focus.

Win+letters either highlight shortcuts on the desktop beginning with that letter, or chimes if there isn't anything.

Win+E chimes, I don't have any shortcuts starting with "E" to the desktop.

As I said, it doesn't sound like classic shell the behavior you describe on the desktop is the same as if you were just pressing the letters.
This means its either a software issue (try the remapper I linked) Or hardware (try a new keyboard)