Quoted:
When you say "none of my user accounts have access to these registry
keys." Do you mean there are no user accounts on the computer with
administrative rights or that the permissions changes won't stick? If
you can, open user accounts from control panel and change account
type.
If this won't work try kelly's Change Registered Owner and
Organization
(line 7 right side)
http://www.kellys-korner-xp.com/xp_tweaks.htm
Perhaps that script from kelly's-korner works but I checked it over
and
didn't feel comfortable running it on a machine that is currently
functioning. I decided to try something else after reading your post
and, as you'll see further down, I did fix my problem.
Before I go further here, I should mention that before coming up with
the solution I have posted here, I had my Search Assistant and
VBScript
functioning. What was not working was Windows Script Host reinstall
and/or regsvr32 jscript.dll.
Coming back to your question, my user accounts do have administrator
rights. The problem is that some keys (in HKEY_CLASSES_ROOT) will not
even allow their rights to be changed. Here are some of the
"offending
keys" (see note further on to tell you how to find all the "offending
keys"):
JavaScript
JavaScript1.1
JavaScript1.2
JavaScript1.3
LiveScript Author
ShockwaveFlash.ShockwaveFlash
VBScript
VBScript Author
I was able to change all my offending keys' permissions to allow full
access on the necessary user accounts. The procedure I used was not
as
easy as what I see most people posting. It went something like this:
(1) Start Run Regedit [Enter]
(2) Locate the "offending" key
(3) Right Click Permissions
(4) Advanced Button
(5) Owner Tab
(6) Select your current user account (assuming you have
administrator's
rights) and Click Apply to change ownership.
(7) Click OK
(8) Click on Advanced Button Again
(9) Permissions Tab
(10) Click/Check "Inherit from parent the permission entries that
apply
to child objects. Include these with entries explicitly defined here."
(11) Click Apply (Note: the results here will depend on the parent
permissions. You may need to change your parent permissions to make
this work. That is outside the scope of my explanation.)
(12) Click OK
This changes one key at a time. You will need to press F5 to refresh
screen. Generally this will make some subkeys available, which will
need to their permissions changed also. Attempting to apply changes
to
child keys will always bring error messages and no results.
To find all the "offending keys", I used my down arrow key to scroll
through all the classes listed in HKEY_CLASSES_ROOT. When you come
upon a key that you do not have permission to see, you will get a
modal
popup warning.
After granting proper permissions on all these "offending keys"
jscript.dll registered fine for me.
In truth, I think I may have arrived at the same solution you did.
But
since my case was slightly different it involved keys in
HKEY_CLASSES_ROOT.
I may also mention that the problem seemed to be associated with one
or
more of the following events:
Uninstalling McAffee Antivirus
Installing McAffee Internet Security 7
Installing WindowBlinds
Uninstalling WindowBlinds
Uninstalling McAffee Internet Security 7 (because my subscription
showed to be out of date, even when it was not.)
One of the systems of this problem was that I could not reinstall
McAffee IS 7 because of script errors.
May I mention again for reference of others having the same issue, it
will not help to do an XP Repair. My problem persisted after an XP
Repair.
Quote brand dub:
I just bought new hard drives and reinstalled XP Home. (I just wanted
a
clean slate) so I can show you what the default permissions are if
you
need them.
Thanks, but I don't need this anymore. Also, I probably have my
permissions set different than default but I don't care about security
because of the environment this computer is used in. Full permissions
to all users should not hurt anything.
But, will look into this and post back if I find