Error: ": : The Add/Remove Software data provider failed to load the user .bak registry hive on computer due to the following error: The process cannot access the file because it is being used by another process."

Email It to Me Print this Page
Symptoms  After each collection you get the following warning:
<timestamp>: <server>: The Add/Remove Software data provider failed to load the user <SID>.bak registry hive on computer <server> due to the following error: The process cannot access the file because it is being used by another process.
 
Cause
Most common reasons:
  • A third-party service holds the registry while the user profile is loaded.
  • The user account is being used by different services that inter-connect with some application during a user logon/logoff process.
  • Antivirus software that does not exclude documents and settings .
  • Registry hive, profile list corruption.
    Resolution
    To resolve the issue, complete the following steps:

    1.First, check the registry permission on the SID and compare with a good user SID in the same machine. Usually Admin, Authenticated Users, Created Owner (special), and System are the permissions set by default. So verify on both profile SIDs and assign permission accordingly.
    2. Check the ProfileImagePath on both.Example:
    SID-2143 and SID-2143.bak
    3. You can see the profile path and the username . In SID-2143.bak , the username is mentioned asUser_name.domain_name . You need to check for SID-2143 and verify the path.
    4. Ideally, when every user logs on to the same server, they get the profile created with the name only, and not as username.domain .
    5. Verify the folder in the profile image path to check the settings and folders on the desktop, and in My Documents to check which is good.
    6. After confirming the good profile SID in the profile list, rename the problematic one to .tmp (the profile that is not having correct information).
    7. Make sure that the good SID profile is without .bak or any extension. It should be just a SID only.
    8.Log off and log in with the user and see the behavior, and then log off and log in again.

    If this does not work, complete the following steps:
    1.Log onto the computer as administrator on the Terminal Server.
    2.Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList .
    3. Navigate to C:\Documents and Settings\UsersName (problem user), and make a note of the profile name of the original profile. This profile should be the original profile that has their settings.
    4. Now go back to regedit and manually edit the duplicate profile (.bak ) location in thevProfileImagePath key to be that of the original.
    Original:
    %SystemDrive%\Documents and Settings\Username (example)
    Duplicate:
    %SystemDrive%\Documents and Settings\Username.domain (example)
    5. Change the duplicate to point to the original profile in profileimagepath and save the change.
    6. Now re-run the data collection process.

    If this does not help we recommend to delete the profile.
    Was this information helpful?