Windows 2000 (service pack 2) explorer corrupts current foldersetting when try to access a different

  • Thread starter Thread starter Gerd
  • Start date Start date
G

Gerd

Dear all,

I just can't believe that there is no solution for the following
problem other than switching to Windows XP or at least to some
replacement for Explorer.EXE:

If I open the Windows explorer with its standard setting (tree view in
the left pane shows all the folders) and let it open, I experience the
following problem after the Explorer has been idle for some minutes:

When I return to
explorer and attempt to click on another folder or a file in another
folder I get the message

"C:\Documents and Settings\Username\Desktop\desktop\[]\tmp is not
accessible. The filename, directory name, or volume label syntax is
incorrect".

It seems that explorer replaces the current directory drive letter
with "C:\Documents and Settings\Username\Desktop\desktop\[]". The
created
folder name has an imbedded control character displayed as a square
symbol. This is an invalid path and results in the access violation.
Explorer must be terminated at this point because it becomes
completely unusable.

In addition, some of the folder icons in the treeview are destroyed
(either replaced by wrong icons or not shown at all).

Here's a screenshot (unfortunately, german version of Windows 2000,
but I hope it gives a clue):

http://img512.imageshack.us/img512/1313/explorermackeip6.png

I just can't believe that there is really NO fix for that! There were
some hints referring to memory (RAM) and filesystem issues but they
are not applicable here. The RAM installed in this computer is error-
free, and chkdsk did not find any problems in the filesystems
whatsoever.

Please help!

Thank you very much in advance and kind regards,

Gerd
 
Any particular reason why you still are on SP2? The latest Service Pack
for Windows 2000 is SP4, I am not saying that SP4 will fix your problem
but there are all kinds of fixes in every service pack and the bug you
have may have been addressed in a later service pack.

John
 
Dear John,

Any particular reason why you still are on SP2?  The latest Service Pack
forWindows2000is SP4, I am not saying that SP4 will fix your problem
but there are all kinds of fixes in every service pack and the bug you
have may have been addressed in a later service pack.
Click to expand...

Oops, a typo. Of course, I am on SP4 and all updates available from
Windows Update for Windows 2000 are installed, too.

There was somebody in the far past who already had this problem when
SP2 was the most recent one but it seems that SP4 doesn't fix it
anyway. In very rare cases, I have been told, this problem can also
occur on Windows XP.

Please accept my sincere apologies for confusing you,

Gerd
 
Gerd said:
Dear John,




Oops, a typo. Of course, I am on SP4 and all updates available from
Windows Update for Windows 2000 are installed, too.

There was somebody in the far past who already had this problem when
SP2 was the most recent one but it seems that SP4 doesn't fix it
anyway. In very rare cases, I have been told, this problem can also
occur on Windows XP.

Please accept my sincere apologies for confusing you,
Click to expand...
I have had SP4 for years and have never experienced your problem. It
sounds like you may have a corrupt version of Win2k. You may also have
some other drives installed which you have not mentioned that could be
causing issues.
 
Back
Top