A practical step-by-step guide to fixing the “Could not find the recovery environment” error when Reset this PC, Advanced startup, or Windows recovery options no longer work.
The message “Could not find the recovery environment” usually appears when you try to use Reset this PC, Advanced startup, or another recovery option in Windows 10. Instead of opening the Windows Recovery Environment, Windows tells you to insert installation or recovery media.
Windows Recovery Environment, often shortened to WinRE, is a special recovery system stored separately from the main Windows installation. It provides tools such as Startup Repair, System Restore, Command Prompt, Uninstall Updates, System Image Recovery, and Reset this PC.
The error is almost always related to one of the following WinRE configuration problems. Understanding the cause helps you choose the right fix instead of randomly changing partitions.
The recovery environment exists, but Windows has it turned off. This is the easiest case to repair.
The recovery image file was deleted, moved, or not copied correctly during a Windows upgrade or disk clone.
The partition may have the wrong ID, no longer contain WinRE, or be too small after partition editing.
Windows points to a location that no longer exists, often after cloning an SSD or changing partition layout.
Most fixes below are safe, but recovery partitions are sensitive. Before changing anything, complete this short checklist.
To open an elevated command window, press Win + X and select Windows PowerShell (Admin), Command Prompt (Admin), or Terminal (Admin), depending on your Windows 10 build.
Windows includes a built-in command-line utility named reagentc. It shows whether WinRE is enabled and where Windows expects the recovery image to be stored.
reagentc /info
Look for these lines in the output:
Enabled.If the status is Disabled, start with the next section. If the status is enabled but recovery still fails, the path or recovery image file may be broken.
If WinRE is disabled, enabling it may immediately solve the “Could not find the recovery environment” error.
Even if WinRE already appears disabled, run the disable command first. This clears the current registration state.
reagentc /disable
Now ask Windows to register and enable the recovery environment again.
reagentc /enable
Check the status one more time.
reagentc /info
If the output shows Windows RE status: Enabled, restart your PC and try Reset this PC or Advanced startup again.
If reagentc /enable fails or the WinRE location is blank, Windows may not know where the recovery image is located. You can manually register the recovery folder.
First, check whether the standard recovery folder exists:
dir C:\Windows\System32\Recovery
If you see Winre.wim in that folder, register it with this command:
reagentc /setreimage /path C:\Windows\System32\Recovery
reagentc /enable
reagentc /info
C:\Windows\System32\Recovery, you need to assign a temporary drive letter to that partition and point reagentc to the correct folder.
The file Winre.wim is the recovery image used by Windows Recovery Environment. If this file is missing, WinRE cannot start even if the recovery partition exists.
dir /a C:\Windows\System32\Recovery\Winre.wim
If the file is not found, you can restore it from Windows 10 installation media.
D:.Check whether the source file is install.wim or install.esd:
dir D:\sources\install.*
Create a temporary folder and mount the Windows image:
mkdir C:\Mount
DISM /Mount-Wim /WimFile:D:\sources\install.wim /Index:1 /MountDir:C:\Mount /ReadOnly
mkdir C:\Mount
DISM /Mount-Wim /WimFile:D:\sources\install.esd /Index:1 /MountDir:C:\Mount /ReadOnly
Copy the WinRE image to the standard recovery folder:
mkdir C:\Windows\System32\Recovery
copy C:\Mount\Windows\System32\Recovery\Winre.wim C:\Windows\System32\Recovery\
Unmount the image and register WinRE again:
DISM /Unmount-Wim /MountDir:C:\Mount /Discard
reagentc /setreimage /path C:\Windows\System32\Recovery
reagentc /enable
reagentc /info
DISM /Get-WimInfo.
If the problem started after cloning Windows to a new SSD, deleting partitions, expanding the C: drive, or converting the disk layout, the recovery partition may no longer be registered correctly.
diskpart
list disk
select disk 0
list partition
Look for a small partition labeled Recovery, usually several hundred megabytes to a few gigabytes in size. The exact size varies depending on the Windows build and update history.
Replace 4 with the number of your recovery partition:
select partition 4
assign letter=R
exit
Check whether the recovery image exists on that partition:
dir /a R:\Recovery\WindowsRE
If Winre.wim is present, register it:
reagentc /setreimage /path R:\Recovery\WindowsRE
reagentc /enable
reagentc /info
After confirming that WinRE is enabled, remove the temporary drive letter:
diskpart
select disk 0
select partition 4
remove letter=R
exit
If Windows cannot find the recovery environment and you need to reset or repair the PC urgently, you can use Windows 10 installation media instead of the local recovery environment.
You can also perform an in-place repair install from inside Windows if the system still boots. This keeps personal files and installed apps while refreshing Windows system files.
Once WinRE is working again, take a few minutes to protect it. Many WinRE problems happen after aggressive disk cleanup, incorrect partition resizing, or low-quality cloning.
reagentc /info and confirm WinRE is still enabled.Use this command set as a compact checklist. Run each command in an elevated Command Prompt.
reagentc /info
reagentc /disable
reagentc /enable
reagentc /info
reagentc /setreimage /path C:\Windows\System32\Recovery
reagentc /enable
reagentc /info
dir /a C:\Windows\System32\Recovery\Winre.wim
reagentc /disable, setting the correct WinRE path, and running reagentc /enable usually fixes it.
C:\Windows\System32\Recovery. A separate partition is safer because recovery files remain available even if the Windows partition has problems.
The fastest way to fix “Could not find the recovery environment” in Windows 10 is to run reagentc /info, then disable and re-enable WinRE. If that fails, check whether Winre.wim exists and manually register the correct recovery folder.
If the recovery partition is damaged or missing, do not rush to delete partitions. Use Windows 10 installation media as a safe fallback, repair WinRE when possible, and keep a bootable USB drive for future emergencies.