Windows 10: Upgraded to Windows 11, Now Stuck in Recovery Environment

HelloI recently upgraded to windows 11, it seems to work for a day.The next day after restart, it did mention the "sign in" was not succesful and I would have to restart to try again.This did not work several time.After this I mad a change in msconfig to "normal system start".Now I'm stuck in the Windows Recvery Environment. I do not have the advanced options available. I can access my C:\windows folder after entering bit locker key via the command line. If I try to make a restore / recovery, it says it cannot find an image or the windows installation.Although the folder c:\windows is accesibl

:)

 

Missing Recovery Environment

Hi Alan,

Here is a link containing several useful suggestions to help you recover Windows 10. Since the error message that you got tells you to insert your Windows installation or recovery media. We suggest the perform the steps listed under
Use a recovery drive to restore or reset your PC or you can also follow the steps under
Use installation media to restore or reset your PC. Please see the link below for more details:

Recovery options in Windows 10.

Regards.

 

Unable to access Windows Recovery Environment normally

Some entries in the bcd for the recovery environment is either corrupted or missing. To fix the problem, you;d need to rebuild the entries for the recovery environment.
Here's the steps:

1. Turn on folder options to show hidden files/folders. Open admin command then type: reagentc /disable
   - This will move 2 files from the recovery partition reagent.xml and winre.wim to C:\windows\system32\recovery
2. If you have the Windows 10 ISO, double click on it to mount to a virtual cd/dvd else If you have the Windows 10 USB then navigate to Sources folder and look for install.esd or install.wim.
3. Use 7-ZIP to open install.esd or install.wim, select and index. eg. 6 then navigate to Windows\system32\recovery. You'd see 2 files: Winre.wim and reagent.xml.
4. Remove everything from C:\windows\system32\recovery (ie. your current winre.win and reagent.xml)
5. Copy the new winre.wim and reagent.xml from the install.esd/install.wim to C:\windows\system32\Recovery
6. From admin command, type: ReAgentc /enable

Reboot to recovery. This will also fix the problem with shutdown /r /o

 

stuck in recovery

Hi Alexander,

Thank you for posting your query in Microsoft Community.

I understand that your computer is stuck in Automatic repair loop. In this case, I would suggest you to try the following methods:

Disconnect all external devices connected to the computer except essential devices like keyboard and mouse and then boot the computer and check. Sometimes, issues with external devices could cause issues with Windows startup. If the issue still persists,
try the following methods.

Method 1: Run SFC/SCANNOW command in Windows 10:

• 
  Left click on Start button.
  
• 
  Right click on Command Prompt (Admin) option which will let you run
  'Run as administrator’.
  
• 
  Command Prompt Window pops up.
  
• 
  Type: SFC /SCANNOW and hit Enter.
  

You can also follow the link below for reference:

http://support.microsoft.com/kb/929833

Try the following steps to run DISM scan to check and restore system file corruption:

• 
  Open command prompt by pressing Windows key + X and selecting “Command prompt admin”.
  
• 
  In command prompt, type the following commands and press Enter after each command:
  
  DISM.exe /Online /Cleanup-image /Scanhealth
  
  DISM.exe /Online /Cleanup-image /Restorehealth
  

Check to see if the issue is resolved. If not, restart the PC.

Method 2: If the above steps didn’t fix the issue, then I would suggest you to perform a system restore to an earlier date prior to this issue. Refer to these steps to perform a system restore from within the Windows recovery
environment:

• When you enter the blue screen with advanced options (Windows recovery environment), click on ‘Troubleshoot’.
• Now, click on ‘Advanced options’ and then click on ‘System Restore’.
• Follow the prompts and choose a restore point created before this issue started.

Please let us know how it goes. We will be happy to assist you further.

Thank you.