Hi, Windows 7 creates now and then new roaming user profiles like user.domain.000, user.domain.001, user.domain.002 and so on. Of course, I can delete the new profiles and restore the old ones. Nevertheless, I'd like to know why new profiles are created. I have already googled this issue for several days. Most websites say that a process locks a file or a HKCU registry hive at *logoff*. The profile isn't saved properly and that's why a new one is created at login. I tried to simulate this error in a VM: I saved a virus to the profile documents folder. Avira Antivir blocked access to this file. Nevertheless the profile was written back to the profile share without any error. Logging in was possible after that. Only the virus file was missing on the server. So it seems a locked file can't be the problem. What is causing this behavior? How can I debug this? Userenv logging isn't possible in Windows 7 anymore. Can I log an event when a new profile folder is created? When there are no special settings for the event log, new .00x folders aren't logged separately. Windows just says the profile was copied to a .00x folder. But no reason is noticeable. File and registry access during the login can be logged with procmon/psexec. One gigabyte logfile is easily generated. Since I don't know, when windows generates a new profile, I can't start this debug program in advance. Any help would be much appreciated. Chris

Hi, All the users on this Win 7 have this issue? If it only occurs on one user, did you do any modification on its profile before? Please check the NTFS permission Have you checked Profilelist and deleted the .bak profile and retry login? Any security application is running on the machine? could possiblity hold the registry key You could refer the following post to have a check: http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/b68b1550-6371-47ee-a173-f4248d583363 If the above info doesn't help, we'd collect PROFILE.ETL to further troubleshoot the issue. a. Log onto the machine as an administrator. b. Select the start menu c. Type cmd in "Start Search" d. Right click on cmd under programs e. Select "Run as administrator" f. Enable the User Profile Service Tracing using the following command in the new-opened elevated command prompt at the root of the C drive: logman -start profile -p {eb7428f5-ab1f-4322-a4cc-1f1a9b2c5e98} 255 3 -ets g. Do not Log off as the current user and switch to logon as the user who receives the profile problem (please tell me the user name). h. Once the user experiences profile issue, please switch back as the administrator. i. Stop the User Profile Service Tracing using the following command in an elevated command prompt logman -stop profile -ets j. Gather the profile.etl file in the root of the C drive and upload it to a shared space Thanks, BrianPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, All the users on this Win 7 have this issue? If it only occurs on one user, did you do any modification on its profile before? Please check the NTFS permission Have you checked Profilelist and deleted the .bak profile and retry login? Any security application is running on the machine? could possiblity hold the registry key You could refer the following post to have a check: http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/b68b1550-6371-47ee-a173-f4248d583363 If the above info doesn't help, we'd collect PROFILE.ETL to further troubleshoot the issue. a. Log onto the machine as an administrator. b. Select the start menu c. Type cmd in "Start Search" d. Right click on cmd under programs e. Select "Run as administrator" f. Enable the User Profile Service Tracing using the following command in the new-opened elevated command prompt at the root of the C drive: logman -start profile -p {eb7428f5-ab1f-4322-a4cc-1f1a9b2c5e98} 255 3 -ets g. Do not Log off as the current user and switch to logon as the user who receives the profile problem (please tell me the user name). h. Once the user experiences profile issue, please switch back as the administrator. i. Stop the User Profile Service Tracing using the following command in an elevated command prompt logman -stop profile -ets j. Gather the profile.etl file in the root of the C drive and upload it to a shared space Thanks, BrianPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Dear Brian, thank you for your reply. I'm not able to reproduce this issue. Thanks again. Chris