Пропал значок сетевого подключения windows xp

I’ll be d a m n e d — it was indeed corruption introduced into the registry by the SP3 upgrade process itself.

In my case it was located in: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumRootLEGACY_CCPROXY

All the invalid entries ( which for me all began with $%& ) had to be deleted. 

Finding your currupted entries is not easy — but expand all sections in all controlsets with Enum  to find them. Posts in other forums have never produced corruption in the exact same registry tree/keys — so unfortuneatly you will have to «look hard». Also deleting the bogus entries may not be as easy as just «delete». You may need to modify the permisions on each entry.

For a small amount of entries:

1) Rightclick and go to the permissions of the corrupt registry key
2) add new permission for the administrator
3) give the administrator «full control»

4) Reboot into Safe Mode (F8)

5) run regedit and delete the offending keys

For a large amount of entries I chose the following instructions:

1. Download and install SubInACL

http://www.microsoft.com/downloads/details.aspx?FamilyID=E8BA3E56-D8FE-4A91-93CF-ED6985E3927B&displaylang=en

2. Create a blank file named reset.cmd in C:Program FilesWindows Resource
KitsTools folder.

3. Edit the reset.cmd file with the following content.

subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=administrators=f
subinacl /subkeyreg HKEY_CURRENT_USER /grant=administrators=f
subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=administrators=f
subinacl /subdirectories %SystemDrive% /grant=administrators=f

subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=system=f
subinacl /subkeyreg HKEY_CURRENT_USER /grant=system=f
subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=system=f
subinacl /subdirectories %SystemDrive% /grant=system=f

4. Enter into the CMD/Command prompt. CD Change Directory to C:Program FilesWindows Resource KitsTools

5. Run reset.cmd

6. After many minutes of processing by subinacl, the permission will be reset  Ignore any errors.

7. Reboot into Safe Mode (F8)

8. Run regedit and delete the offending keys

These instructions were adapted from many other posters across numerous forums and sites — all credit to the original authors.

Good Luck and Regards,

Doug

9/6/08 Update: As this thread is rather long now — I wanted to bring all of your attention to the following — a «fix» which might end up being easier to implement than my early workaround listed above :

Symantec has posted their own Windows Registry cleaning tool.   It is available at: ftp://ftp.symantec.com/public/english_us_canada/tutorials/SymRegFix.exe

Microsoft has also posted their own registry clean-up tool, fixccs.exe, which needs to be run in Safe Mode.  See:

http://support.microsoft.com/kb/953979

Regards — Doug

As an early reporter of the problem — I would like to clarify a few points:

1st — No problem is exactly the same — no fix/workaround will work for everyone — sorry.

2nd — This problem (registry corruption) was directly introduced by the SP3 upgrade procedure. NO QUESTION !

3rd — Going back to SP2 will not work. The corruption remains.

4th — Waiting for Microsoft to acknowledge or fix this serious problem is foolhearty. If you have this specific reported corruption anywhere in «HKEY_LOCAL_MACHINESYSTEM*ControlSet**» — you will likely have issues with your device manager (and more). It will not be resolved until you remove those entries.

5th — Waiting for a «magic» procedure from Microsoft is not likely. Unfortuneatly, if you have this specific corruption — you will have to do the work — find the entries — and remove them — or live with the fallout — until (and if) — resolved by Microsoft.

Those that have sent me private e-mails on conspiracy theories due to the competitive nature between Symantec and Microsoft — while intersting — I will leave it as:  I was not happy having to spend 16 hours researching this issue — to solve an issue introduced by the SP3 upgrade. An issue that I excpect will be widespread — and likely to be talked about on this forum for a long time.

Good luck to those in my boat — Hope my fix works for you.

Regards,

Doug

Solved for me as well, but I used a much simpler method…

(1) Write down Norton Product Key.

(2) Remove Norton products with the Norton Removal Tool found on Symantec’s Website…http://service1.symantec.com/Support/tsgeninfo.nsf/docid/2005033108162039 (does a better job of removing registry entries)

(3) (May not be necessary) Search for the string «$%&» in regedit, delete the remaining corrupt keys (I found 2 ‘legacy’ keys with several corrupt sub-keys)

(4) (May not be necessary) Delete the «Symantec Shared» folder from C:/Program Files/Common Files

(5) Reinstall Norton Product.

Good Luck!

-Kevin

I posted a workaround/fix all the way back on Page 1 of this thread.  I will repost again. Good Luck !

MRFREEZE61 wrote:

I’ll be ******** — it was indeed corruption introduced into the registry by the SP3 upgrade process itself.

In my case it was located in: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumRootLEGACY_CCPROXY

All the invalid entries ( which for me all began with $%& ) had to be deleted. 

Finding your corrupted entries is not easy — but expand all sections in all controlsets with Enum  to find them. Posts in other forums have never produced corruption in the exact same registry tree/keys — so unfortuneatly you will have to «look hard». Also deleting the bogus entries may not be as easy as just «delete». You may need to modify the permisions on each entry.

For a small amount of entries:

1) Rightclick and go to the permissions of the corrupt registry key
2) add new permission for the administrator
3) give the administrator «full control»

4) Reboot into Safe Mode (F8)

5) run regedit and delete the offending keys

For a large amount of entries I chose the following instructions:

1. Download and install SubInACL

http://www.microsoft.com/downloads/details.aspx?FamilyID=E8BA3E56-D8FE-4A91-93CF-ED6985E3927B&displaylang=en

2. Create a blank file named reset.cmd in C:Program FilesWindows Resource
KitsTools folder.

3. Edit the reset.cmd file with the following content.

subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=administrators=f
subinacl /subkeyreg HKEY_CURRENT_USER /grant=administrators=f
subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=administrators=f
subinacl /subdirectories %SystemDrive% /grant=administrators=f

subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=system=f
subinacl /subkeyreg HKEY_CURRENT_USER /grant=system=f
subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=system=f
subinacl /subdirectories %SystemDrive% /grant=system=f

4. Enter into the CMD/Command prompt. CD Change Directory to C:Program FilesWindows Resource KitsTools

5. Run reset.cmd

6. After many minutes of processing by subinacl, the permission will be reset  Ignore any errors.

7. Reboot into Safe Mode (F8)

8. Run regedit and delete the offending keys

These instructions were adapted from many other posters across numerous forums and sites — all credit to the original authors.

Good Luck and Regards,

Doug

I’ll be d a m n e d — it was indeed corruption introduced into the registry by the SP3 upgrade process itself.

In my case it was located in: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumRootLEGACY_CCPROXY

All the invalid entries ( which for me all began with $%& ) had to be deleted. 

Finding your currupted entries is not easy — but expand all sections in all controlsets with Enum  to find them. Posts in other forums have never produced corruption in the exact same registry tree/keys — so unfortuneatly you will have to «look hard». Also deleting the bogus entries may not be as easy as just «delete». You may need to modify the permisions on each entry.

For a small amount of entries:

1) Rightclick and go to the permissions of the corrupt registry key
2) add new permission for the administrator
3) give the administrator «full control»

4) Reboot into Safe Mode (F8)

5) run regedit and delete the offending keys

For a large amount of entries I chose the following instructions:

1. Download and install SubInACL

http://www.microsoft.com/downloads/details.aspx?FamilyID=E8BA3E56-D8FE-4A91-93CF-ED6985E3927B&displaylang=en

2. Create a blank file named reset.cmd in C:Program FilesWindows Resource
KitsTools folder.

3. Edit the reset.cmd file with the following content.

subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=administrators=f
subinacl /subkeyreg HKEY_CURRENT_USER /grant=administrators=f
subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=administrators=f
subinacl /subdirectories %SystemDrive% /grant=administrators=f

subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=system=f
subinacl /subkeyreg HKEY_CURRENT_USER /grant=system=f
subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=system=f
subinacl /subdirectories %SystemDrive% /grant=system=f

4. Enter into the CMD/Command prompt. CD Change Directory to C:Program FilesWindows Resource KitsTools

5. Run reset.cmd

6. After many minutes of processing by subinacl, the permission will be reset  Ignore any errors.

7. Reboot into Safe Mode (F8)

8. Run regedit and delete the offending keys

These instructions were adapted from many other posters across numerous forums and sites — all credit to the original authors.

Good Luck and Regards,

Doug

9/6/08 Update: As this thread is rather long now — I wanted to bring all of your attention to the following — a «fix» which might end up being easier to implement than my early workaround listed above :

Symantec has posted their own Windows Registry cleaning tool.   It is available at: ftp://ftp.symantec.com/public/english_us_canada/tutorials/SymRegFix.exe

Microsoft has also posted their own registry clean-up tool, fixccs.exe, which needs to be run in Safe Mode.  See:

http://support.microsoft.com/kb/953979

Regards — Doug

As an early reporter of the problem — I would like to clarify a few points:

1st — No problem is exactly the same — no fix/workaround will work for everyone — sorry.

2nd — This problem (registry corruption) was directly introduced by the SP3 upgrade procedure. NO QUESTION !

3rd — Going back to SP2 will not work. The corruption remains.

4th — Waiting for Microsoft to acknowledge or fix this serious problem is foolhearty. If you have this specific reported corruption anywhere in «HKEY_LOCAL_MACHINESYSTEM*ControlSet**» — you will likely have issues with your device manager (and more). It will not be resolved until you remove those entries.

5th — Waiting for a «magic» procedure from Microsoft is not likely. Unfortuneatly, if you have this specific corruption — you will have to do the work — find the entries — and remove them — or live with the fallout — until (and if) — resolved by Microsoft.

Those that have sent me private e-mails on conspiracy theories due to the competitive nature between Symantec and Microsoft — while intersting — I will leave it as:  I was not happy having to spend 16 hours researching this issue — to solve an issue introduced by the SP3 upgrade. An issue that I excpect will be widespread — and likely to be talked about on this forum for a long time.

Good luck to those in my boat — Hope my fix works for you.

Regards,

Doug

Solved for me as well, but I used a much simpler method…

(1) Write down Norton Product Key.

(2) Remove Norton products with the Norton Removal Tool found on Symantec’s Website…http://service1.symantec.com/Support/tsgeninfo.nsf/docid/2005033108162039 (does a better job of removing registry entries)

(3) (May not be necessary) Search for the string «$%&» in regedit, delete the remaining corrupt keys (I found 2 ‘legacy’ keys with several corrupt sub-keys)

(4) (May not be necessary) Delete the «Symantec Shared» folder from C:/Program Files/Common Files

(5) Reinstall Norton Product.

Good Luck!

-Kevin

I posted a workaround/fix all the way back on Page 1 of this thread.  I will repost again. Good Luck !

MRFREEZE61 wrote:

I’ll be ******** — it was indeed corruption introduced into the registry by the SP3 upgrade process itself.

In my case it was located in: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumRootLEGACY_CCPROXY

All the invalid entries ( which for me all began with $%& ) had to be deleted. 

Finding your corrupted entries is not easy — but expand all sections in all controlsets with Enum  to find them. Posts in other forums have never produced corruption in the exact same registry tree/keys — so unfortuneatly you will have to «look hard». Also deleting the bogus entries may not be as easy as just «delete». You may need to modify the permisions on each entry.

For a small amount of entries:

1) Rightclick and go to the permissions of the corrupt registry key
2) add new permission for the administrator
3) give the administrator «full control»

4) Reboot into Safe Mode (F8)

5) run regedit and delete the offending keys

For a large amount of entries I chose the following instructions:

1. Download and install SubInACL

http://www.microsoft.com/downloads/details.aspx?FamilyID=E8BA3E56-D8FE-4A91-93CF-ED6985E3927B&displaylang=en

2. Create a blank file named reset.cmd in C:Program FilesWindows Resource
KitsTools folder.

3. Edit the reset.cmd file with the following content.

subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=administrators=f
subinacl /subkeyreg HKEY_CURRENT_USER /grant=administrators=f
subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=administrators=f
subinacl /subdirectories %SystemDrive% /grant=administrators=f

subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=system=f
subinacl /subkeyreg HKEY_CURRENT_USER /grant=system=f
subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=system=f
subinacl /subdirectories %SystemDrive% /grant=system=f

4. Enter into the CMD/Command prompt. CD Change Directory to C:Program FilesWindows Resource KitsTools

5. Run reset.cmd

6. After many minutes of processing by subinacl, the permission will be reset  Ignore any errors.

7. Reboot into Safe Mode (F8)

8. Run regedit and delete the offending keys

These instructions were adapted from many other posters across numerous forums and sites — all credit to the original authors.

Good Luck and Regards,

Doug