Share via

Process1_Initialization_Failed Error During Rollback from Windows 11 back to 10

Anonymous
2021-08-06T18:45:33+00:00

I'm attempting to Rollback to Windows 10 from Windows 11 preview. When I attempt to, however, I get the "Black Screen of Death" and the error: PROCESS1_INITIALIZATION_FAILED. How can I resolve this?

Update, I accidentally marked this inquiry as resolved. Its not. I selected answered accidentally. Lets continue to troubleshoot and share until we fix this rollback/reset garbage.

Windows Insider program | Windows Insider preview | Security, privacy, and accounts

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

26 answers

Sort by: Most helpful
  1. Anonymous
    2021-08-07T23:52:43+00:00

    So after speaking with an agent, its known that one cannot rollback or reset once this specific preview has been installed. The only solution to rollback is to clean install Windows 10 from a USB flash drive. I think I'll do that, sell my laptop and get a MacBook.

    Whatever makes you happy. 😉

    I never use rollback.

    I save Windows Image Backups in case I want to go back to a working system.

    I only keep the system on a 512GB SSD, all my data is on separate HDDs.

    It is quick to make a System Image Backup and restore it when needed.

    Why do you even install a Beta build if you are not willing to see bugs ?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-08-07T23:18:11+00:00

    So after speaking with an agent, its known that one cannot rollback or reset once this specific preview has been installed. The only solution to rollback is to clean install Windows 10 from a USB flash drive. I think I'll do that, sell my laptop and get a MacBook.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-08-07T22:52:32+00:00

    Sorry for marking it as answered. Yes, it only resolved the security/windows defender issue. I was absolutely exhausted when I marked it as if the initial inquiry had been answered. In the Windows defender link fix video, he typed in Powershell into the search, right clicked and chose run as administrator. When Power Shell popped up he entered: Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} and pressed enter. Let the commands run and when they stop, type exit and then restart your computer. When you're back in Windows security features will be accessible. Now we just have to figure out this darn rollback and reset issue.

    OK, I did not need to use that command after all it worked by simply resetting that single app.

    Get-AppxPackage Microsoft.SecHealthUI -AllUsers | Reset-AppxPackage
    

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2021-08-07T21:32:14+00:00

    Sorry for marking it as answered. Yes, it only resolved the security/windows defender issue. I was absolutely exhausted when I marked it as if the initial inquiry had been answered. In the Windows defender link fix video, he typed in Powershell into the search, right clicked and chose run as administrator. When Power Shell popped up he entered: Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} and pressed enter. Let the commands run and when they stop, type exit and then restart your computer. When you're back in Windows security features will be accessible. Now we just have to figure out this darn rollback and reset issue.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2021-08-07T18:51:53+00:00

    hmmm..., the post marked as answer does not fix the issue in the header of this thread.

    Not sure why they marked as answer. It was just for the second issue, but I cannot see from the video what he actually did to find the missing app.

    The Process1_Initialization_Failed is unresolved at this point, we'll see what happens on next update. :-(.

    The owner of the thread marked it, not sure why? the issues are not related.

    btw: I don't have the problem with Windows Security link.

    The security problem shows if you update from 21h1 19043.1151 to 22000.120.

    You don't see it on clean install or update from 22000.100.

    Was this answer helpful?

    0 comments No comments