locked
NTUSER.Dat attempts to save to \\Server$NOCSC$\ instead of just \\Server$ RRS feed

  • Question

  • We have 40-50 systems on our domain that all use roaming profiles but this one system started having problems this week.  When the profile is logged off it isn't able to update the profile completely and the event log says the NTUSER.Dat is trying to save to \\server$NOCSC$\User\NTUSER.DAT but does not have permission to the directory.  But that is because that directory is not the correct one it does not exist.  It is supposed to be \\server$\user\profile.V2\NTUSER.DAT.  The file is there but has not been updated in a while.

     Why would the profile change where this is saved to a location that does not exist?


    • Edited by rmtech83 Wednesday, December 9, 2015 3:55 PM
    Wednesday, December 9, 2015 3:43 PM

Answers

  • Hi,

    As we know, Ntuser.dat file is a Windows Operating System registry file that contains preferences and settings for each user account on a computer. While roaming profile would update when user log off, Ntuser.dat file updates during user worked.

    Based on your description, the reason for roaming profile update failed is NTUSER.Dat file try to upload to an incorrect location, isn’t it?

    If so, please confirm with us that what you operated before this issue occurred, it will be helpful to diagnose problem.

    The most general reason for roaming profile update is security permission. In your scenario, we should check that whether the correct permissions has been set on the user's roaming profile folders which are stored on the server.

    Please try modify path into correct location, then test the result. What’s more, we could log in another account on this computer, test whether other roaming profile can update normally, maybe this client or this profile has trouble.

    Hope my clarification is clear.


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Friday, December 11, 2015 1:48 PM
  • Not sure if this will help but give it a try:

    On the problem computer, open Regedit and navigate to HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

    Then walk the subkeys until you find the SID related to the user having the problem.

    Perhaps the ProfileImagePath values is corrupt? If so, type in the correct value.


    Ha®®y


    Tuesday, December 22, 2015 3:44 PM

All replies

  • Hi,

    As we know, Ntuser.dat file is a Windows Operating System registry file that contains preferences and settings for each user account on a computer. While roaming profile would update when user log off, Ntuser.dat file updates during user worked.

    Based on your description, the reason for roaming profile update failed is NTUSER.Dat file try to upload to an incorrect location, isn’t it?

    If so, please confirm with us that what you operated before this issue occurred, it will be helpful to diagnose problem.

    The most general reason for roaming profile update is security permission. In your scenario, we should check that whether the correct permissions has been set on the user's roaming profile folders which are stored on the server.

    Please try modify path into correct location, then test the result. What’s more, we could log in another account on this computer, test whether other roaming profile can update normally, maybe this client or this profile has trouble.

    Hope my clarification is clear.


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Friday, December 11, 2015 1:48 PM
  • Not sure if this will help but give it a try:

    On the problem computer, open Regedit and navigate to HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

    Then walk the subkeys until you find the SID related to the user having the problem.

    Perhaps the ProfileImagePath values is corrupt? If so, type in the correct value.


    Ha®®y


    Tuesday, December 22, 2015 3:44 PM