P
Phil J
This morning we had a pair of users lose what appeared to
be their .LNK file association (all shortcut icons
appeared blank, prompted for Open Withs. Of course the
users chose something to open with, but that's another
story).
As we played in the registry, we noticed it was more than
just the LNK association. Under CLASSES, there were about
10-15 keys in the immediate area that all errored out when
accessed. "Cannot Open .xxx: Error while opening key" -
could not delete in safe mode + Admin either. So we tried
resetting the permissions using regedt32.exe to allow
everyone access. This gave us access to the keys
temporarily, but if we log back out and in, we still get a
group of keys that error out - not the same group, it
seems to be different each time. Permissions hold, but if
I change them and change them back, we gain access once
again. It goes away upon logging back out.
How can I stop Windows from cannibalizing these keys?
We're running 2K SP3. This just happened out of the blue
as far as I know - no new installs recently on the two
machines, and A/V scans find nothing. Any ideas? Thanks
PJ
be their .LNK file association (all shortcut icons
appeared blank, prompted for Open Withs. Of course the
users chose something to open with, but that's another
story).
As we played in the registry, we noticed it was more than
just the LNK association. Under CLASSES, there were about
10-15 keys in the immediate area that all errored out when
accessed. "Cannot Open .xxx: Error while opening key" -
could not delete in safe mode + Admin either. So we tried
resetting the permissions using regedt32.exe to allow
everyone access. This gave us access to the keys
temporarily, but if we log back out and in, we still get a
group of keys that error out - not the same group, it
seems to be different each time. Permissions hold, but if
I change them and change them back, we gain access once
again. It goes away upon logging back out.
How can I stop Windows from cannibalizing these keys?
We're running 2K SP3. This just happened out of the blue
as far as I know - no new installs recently on the two
machines, and A/V scans find nothing. Any ideas? Thanks
PJ