MASIGNCLEAN104

Could not find the Recovery Environment in Windows 10

iklan banner

If Windows Recovery Environment is non working in addition to y'all have a message Could non notice the Recovery Environment inwards Windows 10, hence this postal service may endure able to help you. Sometimes y'all mightiness confront an number where y'all cannot kick into Windows RE. There tin endure multiple reasons, but accept y'all e'er wondered where Windows RE is available on your computer?

Windows Recovery Environment non working

If Windows Recovery Environment is non working in addition to y'all have a message  Could non notice the Recovery Environment inwards Windows 10

During Windows Setup, Windows initially places Windows RE Image file inwards the installation partition. If y'all accept installed Windows on C drive, it volition endure available at the C:\Windows\System32\Recovery or C:\Recovery folder. It’s a hidden folder. Later, the organization copies this icon file into the recovery tools partition. It makes certain that i tin kick into recovery if in that location is a work alongside the drive-partition.

Could non notice the Recovery Environment

The fault unremarkably happens when either Windows RE is disabled or the Winre.wim file is corrupt. So if y'all dice an fault where the Windows Recovery Environment is non working, hither is how y'all tin railroad train it:

1] Enable Windows RE

If Windows Recovery Environment is non working in addition to y'all have a message  Could non notice the Recovery Environment inwards Windows 10

  1. Open PowerShell or Command Prompt alongside admin privileges.
  2. Type reagentc /info in addition to hitting Enter.
  3. If the output says Status every bit enabled, y'all are all set.

To enable Windows RE, type reagentc /enable and hitting Enter. Influenza A virus subtype H5N1 success message at the terminate volition ensure Windows RE is available.

2] Fix Winre.wim corrupted or missing

If Windows Recovery Environment is non working in addition to y'all have a message  Could non notice the Recovery Environment inwards Windows 10

In either of the case, y'all volition ask a novel re-create of Winre.wim. You tin search on the computer, or y'all tin notice the file on simply about other like reckoner where Windows RE is working. Once y'all locate the file, re-create it from simply about other computer. You ask to laid the icon path to a novel location.

Next, execute the next ascendancy to modify the path of the WIM file to the novel location. The steps should endure used when the file-path of Windows RE file is dissimilar from the park spot.

Reagentc /setreimage /path C:\Recovery\WindowsRE

If the file is corrupted, y'all tin re-create it from simply about other computer. Copy it to the C:\Recovery path in addition to hence laid the path again. Make certain to verify the path alongside reagentc /info command.

The Recovery folder is hidden, in addition to non accessible using Windows File Explorer. Also, the WINRE folder within it is hidden. You volition accept to role PowerShell or Command Prompt to access them. Before copying, brand certain to disable WINRE on that computer, in addition to enable it later.

3] Check & Fix Invalid WinRE Reference inwards Windows Boot Loader

Windows Boot Loader determines if it has to charge Windows RE. It is possible that the loader is pointing to an wrong location.

Open PowerShell alongside admin privileges, in addition to execute this command:

bcdedit /enum all

Look for an entry inwards Windows Boot Loader identifier laid every bit Current.

If Windows Recovery Environment is non working in addition to y'all have a message  Could non notice the Recovery Environment inwards Windows 10

In that section, notice “recoverysequence” in addition to banker's complaint the GUID.

Again, inwards the result, search for Windows Boot Loader identifier laid every bit the noted GUID.

If Windows Recovery Environment is non working in addition to y'all have a message  Could non notice the Recovery Environment inwards Windows 10

Make certain that the device and osdevice items demo the path for the Winre.wim file in addition to they are the same. If not, nosotros volition accept to indicate the electrical current identifier to i which has the same.

Once y'all notice the novel GUID, run the command:

bcdedit /set {current} recoverysequence {GUID_which_has_same_path_of_device_and_device}

See if this resolves the issue.

4] Create a Recovery Media

Download Windows 10 ISO file using the Media Creation Tool. Create a recovery drive in addition to hence the needful. Check if this resolves the issue.

All the best.


Source: https://www.thewindowsclub.com/
Share This :