strange '"run as administrator" problem

[Gilles Pion]

Hello all,

I've discovered a very strange problem on my system: the "run as administrator"
context menu just stopped working on shortcuts (.lnk).

Nothing happens, no UAC prompt, no application launched

It continue to works on executables (.exe, .cmd etc...) and strangely for "quick
launch" shortcuts on the taskbar (but *only* if activated via the taskbar,
opening the quicklaunch folder ant selecting one of the shortcuts doesn't work)

Also the "control-shift-enter" on the start menu command/search field has no
effect anymore.

I've created another user account to check if the problem was inside the current
user profile but it made no difference.

I've tried a lot if investigations using SysInternals tools without success.

any help?

 

[Mark L. Ferguson]

Boot to Safe Mode and set the shortcut 'run as admin' in advanced security
Properties.

--
Was this helpful? Then click the Ratings button. Voting helps the web
interface.
http://www.microsoft.com/wn3/locales/help/help_en-us.htm#RateAPost

Mark L. Ferguson

..

 

[Jon]

That is a bit odd. You could compare your lnkfile registry associations to
the following to see if there's any obvious difference......

;------------------------------------
Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\lnkfile]
@="Shortcut"
"EditFlags"=dword:00000001
"FriendlyTypeName"="@shell32.dll,-4153"
"IsShortcut"=""
"NeverShowExt"=""

[HKEY_CLASSES_ROOT\lnkfile\CLSID]
@="{00021401-0000-0000-C000-000000000046}"

[HKEY_CLASSES_ROOT\lnkfile\shellex]

[HKEY_CLASSES_ROOT\lnkfile\shellex\ContextMenuHandlers]

[HKEY_CLASSES_ROOT\lnkfile\shellex\ContextMenuHandlers\OpenContainingFolderMenu]
@="{37ea3a21-7493-4208-a011-7f9ea79ce9f5}"

[HKEY_CLASSES_ROOT\lnkfile\shellex\ContextMenuHandlers\{00021401-0000-0000-C000-000000000046}]
@=""

[HKEY_CLASSES_ROOT\lnkfile\shellex\DropHandler]
@="{00021401-0000-0000-C000-000000000046}"

[HKEY_CLASSES_ROOT\lnkfile\shellex\IconHandler]
@="{00021401-0000-0000-C000-000000000046}"

[HKEY_CLASSES_ROOT\lnkfile\shellex\PropertySheetHandlers]

[HKEY_CLASSES_ROOT\lnkfile\shellex\PropertySheetHandlers\ShimLayer Property
Page]
@="{513D916F-2A8E-4F51-AEAB-0CBC76FB1AF8}"


;------------------------------------

 

[Gilles Pion]

A side by side comparison gives no difference...

I suspect a more complex problem since I have also discovered some oddities in
the users control panel applet: the hyperlink "modify my environment variables"
and "Configure advanced user profile properties" have no effect too"

I've found someone having exactly the same problem:
http://groups.google.fr/group/microsoft.public.windows.vista.general/msg/a56e864f5174e371

Since I've spare time for the upcoming week I'm planning to reinstall, but this
sucks

That is a bit odd. You could compare your lnkfile registry associations to
the following to see if there's any obvious difference......

;------------------------------------
Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\lnkfile]
@="Shortcut"
"EditFlags"=dword:00000001
"FriendlyTypeName"="@shell32.dll,-4153"
"IsShortcut"=""
"NeverShowExt"=""

[HKEY_CLASSES_ROOT\lnkfile\CLSID]
@="{00021401-0000-0000-C000-000000000046}"

[HKEY_CLASSES_ROOT\lnkfile\shellex]

[HKEY_CLASSES_ROOT\lnkfile\shellex\ContextMenuHandlers]

[HKEY_CLASSES_ROOT\lnkfile\shellex\ContextMenuHandlers\OpenContainingFolderMenu]
@="{37ea3a21-7493-4208-a011-7f9ea79ce9f5}"

[HKEY_CLASSES_ROOT\lnkfile\shellex\ContextMenuHandlers\{00021401-0000-0000-C000-000000000046}]
@=""

[HKEY_CLASSES_ROOT\lnkfile\shellex\DropHandler]
@="{00021401-0000-0000-C000-000000000046}"

[HKEY_CLASSES_ROOT\lnkfile\shellex\IconHandler]
@="{00021401-0000-0000-C000-000000000046}"

[HKEY_CLASSES_ROOT\lnkfile\shellex\PropertySheetHandlers]

[HKEY_CLASSES_ROOT\lnkfile\shellex\PropertySheetHandlers\ShimLayer Property
Page]
@="{513D916F-2A8E-4F51-AEAB-0CBC76FB1AF8}"


;------------------------------------

 

[Gilles Pion]

I just built a new pc and did a fresh intall of Vista Home Premium 32bit
and I have the same problem.

Did you ever find a solution?

No, I eventually did what I said in my previous post: reinstall from scratch.
BTW, just after that I discovered what was probably the original source of all
my problems: a defective USB keyboard generating a huge amount of strange
symptoms on all my other USB devices...