Vista - Windows Explorer start folder problem

Since the last few days, when I start Windows Explorer it starts up in
C:\Windows\System32 instead of my local Documents folder. This is also
breaking Java programs when bringing up a file selection dialog. This starts
in the same folder, and is denied access to list the files in that folder.

I proved this by creating a new user. When running Windows Explorer it
starts up in the user's Documents folder and so does a Java file selection
dialog (successfully).

Please tell me how I can revert this folder on my main user to what it
should be. I hunted through the registry without success.

Jeff

Go to the shortcut that you use to start Windows Explorer. Right click and
select the shortcut tab.

In the Target Line, you can enter the path where you want Windows Explorer
to show when it is opened.

Enter: C:\Users\your username to open with the the user folder selected.
Enter: %systemroot%\explorer.exe /e, to open with 'Computer' selected and
the other drives showing.

You can enter any path to any folder you wish.

--

Ronnie Vernon
Microsoft MVP
Windows Shell/User


"JeffG" <JeffG@xxxxxx> wrote in message
news:98F7F2F2-FCB7-4D96-8217-166B8B659A2A@xxxxxx

Thanks, but I actually knew that already - also it doesn't solve the problem
of breaking other programs that use the same default start folder that
Windows Explorer uses and then don't have privs to list the files in that
folder (system32).

In fact it's treating the symptoms rather than curing the disease. I
actually found the problem and its solution: because I had accidentally
created a file called Documents in my top-level user folder, Vista had
renamed the real Documents folder to Documents.bak behind my back BUT it
refused to tell me that, although I have unchecked the (stupid) option to
suppress file extensions. The only way I found out was when I looked at the
folder's properties, where it showed its type as "File Folder (.bak)".

It was impossible to rename it back from Windows Explorer - I had to do that
in the Command Window. Now I have done that, everything is back to normal and
working as it should.

Why, oh, why, does Microsoft have to make things so DIFFICULT?

"Ronnie Vernon MVP" wrote: