system32 folder opens every time I start Windows XP Pro

[steel]

Every time I start my PC the "system32" folder opens and
is displayed on my desktop.
I then have to close it each time. There are no error
messages, just the folder opens.

How can I stop this, what is the cause??

 

[Kenrick Fu]

Check out this MS KB article for help:
- System32 Folder Opens When Logging on to Windows
http://support.microsoft.com/default.aspx?id=170086

 

[Rick \Nutcase\ Rogers]

Hi Steel,

Please see:

System32 Folder Opens When Logging on to Windows
http://support.microsoft.com/?kbid=170086

Also, start/run msconfig, and see if there is a line that loads /L:ENG. If
so, disable it. It comes from a SoundBlaster Audigy driver, but should not
affect that hardware. You can also repair the registry entry if you like by
removing the leading space in the string that loads it.

However, it can also be caused by other incorrectly built registry strings.
Could you please export and post the contents of these keys in the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

To do this, start/run regedit, expand the branches to each key (do this one
at a time). Click on the key, then on file/export. Give it any name, then
save to the desktop. Once you have saved both keys, close the registry
editor. Right-click one of the saved files on the desktop, choose edit, it
should open in notepad. Click edit/select all/edit/copy. Open a response to
this post and click in the message text area. Hit ctrl+v to paste the
contents. Repeat for the other saved key, then send the post for
examination.

--
Best of Luck,

Rick Rogers aka "Nutcase" MS-MVP - Win9x
Windows isn't rocket science! That's my other hobby!

Associate Expert - WinXP - Expert Zone

 

[Kelly]

Another cause/reason:

This is a known issue for owners of an SB Audigy 2 sound card. Re-enable
the item in MSConfig.

Then see www.kellys-korner-xp.com/xp_tweaks.htm, Line 260, Left column for a
small utility that will correct this for you. The problem is caused by a
leading space before the /L:ENG. This causes the problem, the script
corrects it.