Re: Open With.. functionality doesn't fully work <XPSP1>
- From: "Bluescreens" <bluescreens@xxxxxxxxx>
- Date: 4 May 2005 14:32:50 -0700
>Is the regvalue that you posted from the machine that "doesn't work" ?
BTW,
>the value is correctly set.
Yes, the regvalue I posted is from a machine that doesn't work. In
other words, logged in as admin, everything works, but logged in as
user, it does not work. I cannot change the menu that results from
selecting Open With ... and Choose Programs.
> Are you're referring to the dynamic Open-with list (cascading menu)
or the
>"Choose Programs" dialog?
The "Choose Programs" dialog, a fairly large menu listing half a dozen,
or more, applications that could concievably open the .txt file I'm
selecting.
>HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Applications\555.exe\shell\open\command
There is no such key. Under Applications I do not see a 555.exe key
while logged in as an administrator. If I log in as admin and then
make the change (add 555.exe to the Choose Programs menu), that key
still is not present, so I question the validity of that key in
determining what appears in Choose Programs.
>HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Applications\555.exe
Does not exist, as noted.
>HKEY_CURRENT_USER\SOFTWARE\Classes\Applications\555.exe (may not
exist)
It *does* exist here!
Here's some interesting data:
On the bad machine, here's HKCU....\Applications perms in the registry:
Administrators (Full)
RESTRICTED (Read)
S-1-5-21-299502267-.... (A long SID) - (Full)
System (Full)
On a 'good' machine, here's Applications perms in the registry:
Administrators (full)
RESTRICTED (Read)
(the currently logged in user) - (Full)
System (Full)
So, for some reason, the current user's account's SID isn't resolving
correctly, and so it's not working. The Admin account isn't being hit
by this since it's a part of Local Administrators group, which has full
permissions anyway, so the SID issue isn't an issue for that account -
only for the user account, which has no special permissions other than
that given straight to his own SID....which doesn't seem to resolve
correctly to a real user account.
So....why would, on some machines (and bear in mind it's not just one)
is this happening? Why are perms on that key messed up?
Thanks for all of your help in pinpointing that key, Ramesh!
.
- Follow-Ups:
- Re: Open With.. functionality doesn't fully work <XPSP1>
- From: Ramesh, MS-MVP
- Re: Open With.. functionality doesn't fully work <XPSP1>
- References:
- Open With.. functionality doesn't fully work <XPSP1>
- From: Bluescreens
- Re: Open With.. functionality doesn't fully work <XPSP1>
- From: Ramesh, MS-MVP
- Re: Open With.. functionality doesn't fully work <XPSP1>
- From: Bluescreens
- Re: Open With.. functionality doesn't fully work <XPSP1>
- From: Ramesh, MS-MVP
- Open With.. functionality doesn't fully work <XPSP1>
- Prev by Date: Cant take away my searches on the internet.
- Next by Date: shell32.dll Icon Index
- Previous by thread: Re: Open With.. functionality doesn't fully work <XPSP1>
- Next by thread: Re: Open With.. functionality doesn't fully work <XPSP1>
- Index(es):
Relevant Pages
|