re: Corrupted Enum keys make a come back
Sunday, February 15, 2009 at 4:00 pm
Windows XP Annoyances Discussion Forum
Posted by Rafael
(1 messages posted)
THANKS !!!
I tool tried the PnP, aproprosfix, permissions and SFC to no avail. then I kept digging
in this forum and found your reply.
My corrupted string started at $%& and everytime an issue or reboot occured it added
a new digit until eventually it was "$%&'()+,-./0123" afterwhich it repeated over
and over and over. Looking at the registry was like the old ASCII Christmas tree
printouts.
So drinking a beer and pressing the delete key alot it was fixed.
Ironically, it was all surrounding Symantec 360 if that helps anyone. You're probably
asking why didn't I just run the clean up tool? Well, I could not run Symantec's
Clean Up tool as this PC belonged to a client who also had Symantec PC Anywhere for
work.
Symantec's clean up tool is know for cleaning all the components of the shared common
files so it would have broken his other apps.
Time for another beer to savory the victory!!!
-Rafael
On Thursday, February 14, 2008 at 1:54 pm, Lyle Campbell wrote:
>I too tried the PnP, aproprosfix, registry permissions fixes, scanned the system
>for malware, ran a registry fix all to no avail. Somewhere in the thread is an
entry
>from someone who noticed corrupt key names in the registry starting with "$%&'()1234".
> I noticed one of these under HKLM, System, (all ControlSets), Enum, USB.
>Then I searched for that string and found hundreds of them, each name incremented
>by one character of the string until the maximum filename size was reached. They
>were all owned by the System so after logging in as administrator I had to first
>change the ownership to the administrator and then was allowed to add the administrator
>with full control permissions. Rather than do this on each of the hundreds of files
>I did it at the USB level and propogated the change downward by checking the box
>next to "change owner on subcontainers..." and "replace ... on child objects...".
> Then you can either delete the keys individually or the folders name "VID....".
>
>After I found and deleted these, then rebooted the system and watched it rediscover
>it's devices the device manager was again filled, the sound worked, the network
properties
>were available, etc. Wahoo!
>
>Bottom line is there are as many ways to break something in Windoze as there are
>to get there but this happened to work for me. Hope it helps you too.
>
>
>
|
All messages in this thread [show all]
 |  | | |  | Solution (Ed C: Mon, Feb 25, 2008, 7:04 pm) |
| | | |  | re: Corrupted Enum keys make a come back (Rafael: Sun, Feb 15, 2009, 4:00 pm) |
| |
| |
Return to the Windows XP Discussion Forum
|
|
