Skip to main content
Druva Documentation

Backup fails due to Windows profile corruption

This article applies to:

  • OS: Windows 7 and 10
  • Product edition: All supported versions of inSync Client

Problem description

Backup fails with an internal error for the device in which the Windows Login Profile of the user is corrupt.

Traceback

The following internal error is logged:

[2019-03-28 13:39:22,002] [WARNING] Backup failed. Error: Internal error. (#100000001)

Log Name: Application
Source: Microsoft-Windows-User Profiles Service
Date: 26-02-2019 11:34:08 AM
Event ID: 1505
Task Category: None
Level: Error
Keywords:
User: S-1-5-21-1020481581-356934737-452798024-211747
Computer: <SAMPLENAME12345.sample.samp.le>
Description:
Windows cannot load the user's profile but has logged you on with the default profile for the system.

DETAIL - Only part of a ReadProcessMemory or WriteProcessMemory request was completed.

Log Name: Application
Source: Microsoft-Windows-User Profiles Service
Date: 26-02-2019 11:33:55 AM
Event ID: 1511
Task Category: None
Level: Error
Keywords:
User: S-1-5-21-1020481581-356934737-452798024-211747
Computer: <SAMPLENAME12345.sample.samp.le>
Description:
Windows cannot find the local profile and is logging you on with a temporary profile. Changes you make to this profile will be lost when you log off.

Resolution

  1. Uninstall the inSync Client from the device.
  2. Back up the Windows user profile.
  3. Copy all the required data for the user from the current user profile.
  4. Delete the User Profile (Windows User Profile) and create a New User Profile.
  5. Delete the Windows user profile and create a new profile.
  6. Copy the backed up user data to the new user profile.
  7. Install and activate the inSync Client.

Verification

Verify whether inSync backups are working well.

See also

To resolve this error without creating a new profile, refer the Method 1 and Method 3 mentioned in the below knowledge article from Microsoft:

You receive a "The User Profile Service failed the logon” error message