My Sony Vaio PCG-SR7K has Win2K and IE6 SP3. When I type in text to
any form field and hit enter or tab, IE6 hangs. When I go to the task
manager, it says Not Responding. I tried clearing my AutoComplete and
Password histories with no success. How do I fix this? |
Request for Question Clarification by
pwizard-ga
on
18 Apr 2003 08:50 PDT
It sounds like to me that your AutoComplete database may be corrupted
somehow. It sounds like you've used the method for clearing both the
forms and passwords from within the Content/AutoComplete options
portions of IE, but there's a couple of other things you can also try:
If you're comfortable using the registry editor, you can try deleting
the key:
HKEY_CURRENT_USER\Software\Microsoft\Internet
Explorer\IntelliForms\SPW
HOWEVER: I highly recommend that you export the key to a file before
deleting it in case something goes wrong and you need to replace it
back into the registry.
have you tried disabling all of the autocomplete functions to see if
the problem goes away at that point? That would let us know if
autocomplete is indeed the culprit.
-PWizard
|
Clarification of Question by
welday007-ga
on
18 Apr 2003 10:14 PDT
Through your suggestion, I disabled the AutoComplete options one at a
time. The forms option was the problem. I deleted the registry key
as you suggested, the contents of which looked corrupted, but it did
not fix the problem. When I turned on the forms option again, I get
the same thing. Is there a way to restore the registry key to a
default value? I would have thought it would have been recreated when
needed.
|
Request for Question Clarification by
pwizard-ga
on
18 Apr 2003 11:12 PDT
I believe that this particular registry key may only hold the
autocomplete information for username/password forms and that is why
there is no result from deleting that key. The default value for the
key is just a key of "default" in the SPW subkey. Once the
autocomplete passwords feature is used, it creates a strange encrypted
looking key in this subkey that holds the data.
Some other resources suggest that your profile could possibly be
corrupted. Do you think that you could logon to the PC under a
different username (where a new profile would be created) and see if
you get the same problem? If the problem is resolved by this method,
you probably just have a corrupted index file or something in your
primary profile. You could copy this new profile to your other user
and it would fix the problem, although you would have to setup your
profile again (user settings, shortcuts, etc).
I've read some other articles that mention there may be a problem with
the Protected Storage area on your computer, but I haven't found a
clear way or correcting that issue on Windows 2000. There's a
Protected Storage key in the registry, but either it's contents are
hidden or there's nothing in it. I would be a little leery about
deleting that one.
If you want, you go ahead and try to new user scenario and we can go
from there. I'll keep looking in the meantime.
-PWizard
|
Clarification of Question by
welday007-ga
on
18 Apr 2003 12:17 PDT
I logged on as administrator which had the same problem. It went away
when I disabled the form option.
Interestingly, one of my logon profiles from before would hang after
the password screen, with just a blue background and a live mouse
cursor. I had to ctrl-alt-del to log off. When I added two other
profiles, the same thing occured. This may be related, but now I am
tempted to run the restoration CDs (what a pain).
|
Request for Question Clarification by
pwizard-ga
on
18 Apr 2003 12:36 PDT
It sounds like your Protected Storage cache is probably corrupted. If
you're planning on using the restore CDs, then you might be willing to
try one more solution, but it involves deleting the Protected Storage
registry key and I'm not sure what effect this may have on other
applications, but according to an article I found, it should be fine
and re-constructed on it's own.
Here's the article I found. I would recommend stopping the Protected
Storage service from control panel before deleting the key. Also,
you'll have to use regedt32 instead of regedit on this one as you'll
have to set permissions.
"The cause of your problems is the Protected Storage Service and the
password cache it creates for your user account. Occasionally, the
Registry data associated with this service becomes corrupted and
requires reinitialization. The good news is that I have a fix for you.
The bad news is that the fix will delete all the passwords residing in
the cache, and you'll have to remind IE and Outlook about the
passwords later.
Use the Control Panel Services applet to stop the Protected Storage
Service. Next, use regedt32 to navigate to the
HKEY_CURRENT_USER\Software\Microsoft\Protected Storage System Provider
Registry key. Double-click this key to display its subkeys. As Screen
1, page 184, shows, at least one subkey has a name that is equivalent
to your Windows NT user account's SID (e.g.,
S-1-5-21-36516332-637091160-1803697834-1001). You need to delete this
subkey, but you don't have permission to do so. Therefore, you need to
add yourself to the Registry key's ACL. Highlight the key that
represents the SID, and select Permissions from the Security menu.
Next, add your user account to the ACL with Full Control rights. Now
you can delete the key and restart the Protected Storage Service in
the Control Panel Services applet."
After restarting the Protected Storage service, then I would probably
reboot and see if the problem is resolved.
Again, I must stress that this is a "try at your own risk" kind of fix
as I can't test it on my own system to let you know the results first
hand. But, if you're going to format and restore the system
regardless, this might be worthwhile.
Please let me know either way what you decide and how it goes.
Thanks,
PWizard
|
Clarification of Question by
welday007-ga
on
18 Apr 2003 13:34 PDT
Thank you for that information. I think I will live without
AutoComplete for a while, since this solution sounds risky. My wife
is talking me into buying a new laptop (believe it?) so I will wait
until I have it up and running before I mess with this one. At least
I can use QuickBooks Online again with this work around.
|
