Windows Logo Key+E doesn't work anymore

[Guest]

My Windows Logo Key+E shortcut has suddenly stopped working. It does not
bring up windows explorer anymore. windows+D, Windows+M, Windows+L all work
just fine. The e key works just fine by itself. I've scanned for viruses
and spyware, with updated patterns. I checked the group policy to make sure
it wasn't disabled. I also checked to make sure I didn't have a Scancode Map
entry in the registry.

I use this key a lot - please help!

 

[RA]

My Windows Logo Key+E shortcut has suddenly stopped working. It does
not bring up windows explorer anymore. windows+D, Windows+M,
Windows+L all work just fine. The e key works just fine by itself.
I've scanned for viruses and spyware, with updated patterns. I
checked the group policy to make sure it wasn't disabled. I also
checked to make sure I didn't have a Scancode Map entry in the
registry.

I use this key a lot - please help!

Have you tried a new keyboard?

 

[Ramesh, MS-MVP]

DDE setting might be the problem. See if the folder association fix helps.

http://www.dougknox.com/xp/file_assoc.htm

 

[Guest]

Thank you Ramesh. This fixed the problem. Upon further investigation, I
compared the old registry entries to the new ones, and found that the
following value had been added:

[HKEY_CLASSES_ROOT\Folder\shellex\ContextMenuHandlers\ShellCmd]
@="{82C62DC5-1A4B-43ac-92C8-571410996B45}"

After looking up that CLSID, I found that it belonged to a COM component
generated by the sample application called ShellCmd (included with visual
studio 2003). \Samples\Technologies\Interop\Applications\ShellCmd

I ran the sample application to see something else, and it put these items
in the registry. Thanks for the help!

 

[Ramesh, MS-MVP]

You're welcome willenbrechtal.

--
Ramesh, Windows XP MVP
http://windowsxp.mvps.org

Thank you Ramesh. This fixed the problem. Upon further investigation, I
compared the old registry entries to the new ones, and found that the
following value had been added:

[HKEY_CLASSES_ROOT\Folder\shellex\ContextMenuHandlers\ShellCmd]
@="{82C62DC5-1A4B-43ac-92C8-571410996B45}"

After looking up that CLSID, I found that it belonged to a COM component
generated by the sample application called ShellCmd (included with visual
studio 2003). \Samples\Technologies\Interop\Applications\ShellCmd

I ran the sample application to see something else, and it put these items
in the registry. Thanks for the help!

DDE setting might be the problem. See if the folder association fix
helps.

http://www.dougknox.com/xp/file_assoc.htm