Upgrade to 10122 gets error fbl_impressive Professional 10122 - Error

I upgraded to 10074 with no problems but trying to upgrade to 10122 gets error fbl_impressive Professional 10122 - Error 0xd0000225. I'm logged into my Microsoft account, so I don't think that's the problem. I've cleaned up all the files and registry, but still getting the error. Any suggestions?

Hi there

ensure that you have deleted a load of files from your Downloads folder (C:usersusernamedownloads) and clean up the C drive -- delete previous windows installations etc. (File explorer==>C==>properties

Now re-boot and try again.

Cheers
jimbo

Try this:
Launch an elevated command prompt and enter the flowing commands

Dism /Online /Cleanup-Image /RestoreHealth
sfc /scannow

reg query HKLMSYSTEMCurrentControlSetControlLsa > %TEMP%curCtlLSA.txt
exit

Then restart your machine.

DISM repairs the CBS store and SFC makes sure all system files are in the correct place (this might actually be redundant after DISM, but run it anyway)

The reg query writes the key to a file (C:Users<yourLogin>AppDataLocalTempcurCtlLSA.txt) that might provide a clue, but don't change anything yet, just look. If the values are not there, you MIGHT consider adding them if the DISM and SFC don't cure the issue.
Fix : This user wasnt added to this PC. Code: 0xd0000225

There are a few references out there with vastly different solutions. The most prevalent involves MS accounts, but you say that is ok on your machine. Another involves BCD, but neither the BCD or LSA 'fix' seem to apply in your case.

Your best place to start is DISM and SFC.

If there are any errors reported let members know.

DISM ran clean. SFC found two files corrupt and repaired them. Did not correct the problem.
Added the two values to the LSAsecurity packages. No joy.

Is there a log file that would point to the problem?

I tried to upgrade Windows 7 to 10122 and it was a 7 hour nightmare. Finallky worked but was slow as heck. I ended up doing a clean install of this build and it works just fine.

DISM ran clean. SFC found two files corrupt and repaired them. Did not correct the problem.
Added the two values to the LSAsecurity packages. No joy.

Is there a log file that would point to the problem?

I tried to upgrade Windows 7 to 10122 and it was a 7 hour nightmare. Finally worked but was slow as heck. I ended up doing a clean install of this build and it works just fine.

Gary might have the best solution. A clean install. You'll need an ISO for that and to create the ISO you'll need the ESD.

Log files:
Look in Windows - search ext:log
Look in Event viewer
for the SFC and Dism logs, look in WindowsLogsCBSCBS.log
if you want, pack the CBS.log file into a zip folder (send to compressed folder) and attach it to a post.
Someone will get around to looking at.
Screenshots and Files - Upload and Post in windowssh blog - Windows 10 blog