Author Topic: Can't login after restoring registry from Registry Backup  (Read 3400 times)

0 Members and 1 Guest are viewing this topic.

Offline LarsErikOsterud

  • Newbie
  • *
  • Join Date: Feb 2016
  • Posts: 2
  • Karma: 0
    • View Profile
Can't login after restoring registry from Registry Backup
« on: August 28, 2018, 04:18:54 pm »
No matter what user I select I get "Failed login for User Profile service".
And now I'm locked out from my PC. Nice backup program :-(
Why does this happend and what good is a registry backup then.
And since I can't login with any user I can revert anything eihter :-(

(I tried restoring a backup from MS regisrty backup, but that always
ends up with a "restore failed" so that isn't any good either).

I the only way to be safe to backup the whole disk nowadays :-(

Anyway. How do I get passed the mess Regisrty Backup make?
I have just spent days reinstalling Windows after a failed update.
Now I'm locked out again after a simple restore. What do I do?

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 10182
  • Location: UK
  • Karma: 122
    • View Profile
Re: Can't login after restoring registry from Registry Backup
« Reply #1 on: August 29, 2018, 01:18:11 am »
I'm assuming you are using Win 10 ?

If so, this article should help - https://www.easeus.com/todo-backup-resource/fix-user-profile-service-failed-the-sign-in.html

Else, you can create a new user account by following the steps in this article, but ignore any suggestion to install Reimage.

https://appuals.com/add-a-user-using-command-line/

Once you are back up and running, run a command prompt as an administrator and enter chkdsk /f then follow the prompts.

You can view its log in Event Viewer when after it has read the data, expand Windows Logs - click on Application - Action/Find then type chkdsk or wininit into the Find box and press enter.

Cancel the Find box and read the log in the scrollable window - primarily you are looking for any KBs reported for bad sectors.

If that is okay, run another cmd prompt as an admin and enter sfc /scannow to see what that reports.
« Last Edit: August 29, 2018, 01:31:36 am by Boggin »