"The server process could not be started because the configured identity is incorrect. Check the Username and Password."

Hi,

Thanks for posting your query on Microsoft Community.

This issue might occur, when some of the system files got corrupted.

I would suggest you to try perform System File Checker (sfc) scan and check if it helps.

System File Checker is a utility in Windows that allows users to scan for corruptions in Windows system files and restore corrupted files.

To perform SFC Scan, refer to the below link:

https://support.microsoft.com/en-us/kb/929833

Note: Steps mentioned for Windows 8/8.1, will work fine with Windows 10.

Hope it helps, reply to us with the status of your issue. We will be happy to assist you.

I just started to get this error on one machine today.

I ran the sfc.exe utility in an Administrator cmd window, but I get "Windows Resource Protection could not start the repair service" and another thing that says "the server process could not be started because the configured identity is incorrect for Windows 10".

Hey guys,

I thought I'd reply because I've had this issue on a Windows 10 v1511 x64 PC and I've managed to fix it.

First I read this thread: Server process could not be started because the configured identity is incorrect (massive Windows 7 failure)

Their suggestions didn't work for me but I thought I'd share them here in case that helps someone else, since there are no other suggestions here. Read the original thread, or see my summary versions below:

Suggested fix one

"To fix this issue, it is a single registry key that causes it and that needs be tweaked.

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{CDCBCFCA-3CDC-436f-A4E2-0E02075250C2}
The RunAs REG_SZ value needs to be set to "Interactive User" [without the quotes of course].

It can also be caused by the permissions on the key and by the ownership as well.  If you look at the permissions on the key compared to a working box, and look at the ownership comparatively as well.

Ownership is suppsoed to be TrustedInstaller, but it can be other things as well.  If it is not set to that, sometimes it can cause issues as well. 
1) If it is already set to trusted installer, take ownership as administrator and see if then opening explorer works.  *NOTE*  You will have to close all open explorer processes and start them up again before you will notice any effect.

2) If the ownership is set to administrator, set it back to TrustedInstaller using 'NTAuthority\TrustedInstaller' as the other user to set as owner.
If it is still failing after all this, I can try to post a REG dump of that key as a re-import can fix that issue as well."

Didn't work for me, but worth a try as its quite quick and painless.

Suggested fix two

"I also ran into this problem after running sysprep.  I forgot that there are different versions of sysprep.  Make sure you run the correct version for your OS.  You can access files from your HD via the Start --> Run interface.  Type c: and it will pop up with available folders.

All you have to do is to run the correct version of sysprep for the operating system. I used an ERD to access the file structure of the computer. I went to C:\Windows\System32\Sysprep and copied sysprep to the desktop of the Administrator user. I then rebooted the computer logged on as administrator and ran that sysprep exe file that I copied earlier. The sysprep utility will open, leave everything as default and click on the Ok button. The sysprep will eventually reboot your computer. The computer will now need to be configured as if it just came out of the box. Answer all questions as requested and you should now have normal access to your computer."

I didn't try this, even though I had syspreped the PC, because it sounded quite drastic. So it might work, who knows.

Suggested fix three

"I solved this on my system by opening the msconfig and then boot options then selecting active directory repair. 

It would seem to be a configuration issue in the boot loader.
Using grub 2 might fix this issue also."

I didn't try this as I was remotely looking at the PC so I didn't want it in a safe mode where I couldn't remotely access it. Might work, who knows.

Suggested fix four

"in my case I found that the key registry HKLM\SYSTEM\SETUP\SystemSetupInProgress, was set to 1.
Setting it back to 0 solved it."

I tried that, didn't work, it was already set to 0.

My fix that worked for me

I thought the PC hadn't been shut down correctly, I could see improper shutdown events in event viewer. Its not my PC so I wasn't sure. But I thought I might as well try scan disk before wiping it, and that fixed it for me. Because I couldn't get into explorer/my computer on the desktop, I had to run scan disk from command line. Here are the steps to do this:

1. I held down the windows key and pressed R to open the run window.

2. I typed: CMD

3. Make sure it runs as administrator.

4. Once command prompt is open, I typed: chkdsk /x /f /r"

5. It then asked if I wanted to schedule the scan disk at next reboot, so I said yes (by pressing Y).

6. I repeated steps 4 and 5 three times to make sure it was scheduled.

7. I then typed: shutdown -r -t 1

8. The PC should then reboot and scan the hard drive, and once it finished, it was fixed.

Hope this post helps some people, it was a confusing issue and I hope doesn't come back...

How can I run as administrator?

I typed chkdsk /x /f /r in the CMD and they said "access denied as you do not have sufficient privileges. You have to invoke this utility in elevated mode."

I have no idea how to do this.

re the username and passwhi, no it doesn't work as in my version of this problem, the start icon is not working, icons to control panel get the same message,  icons to files get the same message, there is nothing in the taskbar to go to file explorer.

tell me why I shouldn't just restore to the system prior to the update that was forced on me last week.  I didn't want it I didn't ask for it,  and now my computer is comprimised.

so i do a run a system repair file when I can't get to the systsem repair file?