Discussion Locked

Persistent folder display on desktop

0 helpful
13 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We use NT 4.0, SP3. We don't use roaming profiles. On some machines, the C:\Program folder opens on the desktop every time a certain user logs in. If you close that window, it still comes back on the next login. If you delete the C:\Program folder, you get an error message saying that it can't be found.

We've determined that the setting is in the Current User registry. It's probably one of the Streams or DesktopStreams settings, but finding which one has been a problem. Has anyone else seen something similar?

13 replies

by denis a. bilas

Try to look into

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

or

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

by rmmcp

Disconnect the network cable. I know Wkstn won't like that, but then power up and use a local logon. If it doen't do this, that will tell you if it's network logon related.

by mrbjh

you say you dont use roaming profiles, so that means you use mandatory profiles if any at all. If this is the case then the profile has that folder in it and is re-downloaded everytime the user logs in and thus keeps comming back. Try editing the profile, removing the folder and re-uploading it.

by robbkester

We don't use mandatory profiles. We just don't store any profile information on the server. Each user gets a workstation-specific copy of the Default User profile on each machine at their first login. Then, on future logins to that machine, they use the local profile. Each user has a separate, unlinked profile on each workstation.

This happens to every user on the machine, so it appears to be at the Local Machine level, not the Current User level.

by valentin

It is maybe that that folder was opened when user logged off - system opens it each time user logs in again. Try to close folder and re-login

by robbkester

We tried that, but the folder keeps coming back. I think that something has become corrupted so the system can't properly record that the window was closed.

This discussion is closed to new replies.