

Solution to the blue screen prompt that the recovery environment cannot be found when booting the Win11 system
Recently, some users are using the Win11 system. Due to a Win11 system reset error, the computer starts with a blue screen and the system prompts that the recovery environment cannot be found. So how should you solve this situation? Let's take a look at how the editor operates. I hope the following tutorials will be helpful to you.
Try to reinstall. After restarting, it prompts ‘Windows cannot complete the installation’ with error code 0x80070002-0x2009. Even the one-click recovery that comes with the system cannot be used. What's happening here? How to reinstall? Can the file not be retained? ”
If you try to boot your computer into recovery mode, you will find that there are no options to choose from in Troubleshooter. Under normal circumstances, there are many repair functions available under "Advanced Options" in "Troubleshooter". At this time, you cannot use these repair functions without connecting the Windows installation or recovery media. Typically, the main reason for the inability to recover the environment is disabling or accidentally deleting the Windows recovery environment.
Possible reasons for the prompt “Recovery environment not found”
Generally speaking, the main reason is that the Windows recovery environment is disabled or accidentally deleted. Of course, there are other reasons too
1. The Winre.wim file is damaged or missing
2. There is no recovery mode in BCD
3. There is an error in the Windows RE configuration file ReAgent.xml
4. There is a problem or damage to the Windows registry
Solution
Method 1: Enable Windows Recovery Environment
In the command prompt window, enter and press Enter to execute the reagentc /info command. If the prompt is disabled, enter and press Enter to execute the reagentc /enable command to re-enable it
Note: If the status of the recovery environment is enabled, but it still prompts that the recovery environment cannot be found, you should check whether the Winre.wim file is damaged or missing
Method 2: Repair damaged or missing Winre.wim file
1. Enter in the command prompt and press Enter to execute the dir /a /s c:winre.wim command
Please note: Under certain circumstances, the Winre.wim file may be stored in a location other than the C drive. You need to change c: in this command to the corresponding drive letter
2. After finding the Winre.wim file, enter the following command in the command prompt to copy the file to the default location
attrib -h -s c:Recovery3b09be7c-2b1f-11e0-b06a-be7a471d71d6winre.wim xcopy /h c:Recovery3b09be7c-2b1f-11e0-b06a-be7a471d71d6winre.wim c:WindowsSystem32Recovery
3. Replace the Winre.wim file path with the default configured path. Please enter the following command:
reagentc /setreimage /path C:windowssystem32recovery
4. Enable the recovery environment and check its status. Please enter the following command:
reagentc /enable reagentc /info
If the Winre.wim file is damaged, you can extract the Winre.wim file from another computer and then copy it to the correct location on your computer. Or if you have the Install.esd file on your computer, you can unzip the file and then put the Winre.wim file inside to the correct location. Then use the reagentc /setreimage /path C:RecoveryWindowsRE command to configure WinRE.wim as the system default recovery environment boot image.
Method 3: Using installation or recovery media
If you perform improper operations when resetting your computer, it may also cause the computer to not be able to find the recovery environment. So what should you do if you can't find the recovery environment when restoring the computer to factory settings? If you have a Windows 10/11 installation disc or recovery media, you can use it to reset or restore Windows 10/11 without fixing this error.
Create an installation CD on a Windows 10/11 computer that can run the same version normally.
Connect the CD to the computer with the problem and set it as the priority startup item.
Select "Next" in the pop-up window.
Click "Repair your computer" and then select "Troubleshoot".
Click "Advanced Options" and then select the recovery tool to fix the "Recovery Environment Not Found" problem.
At the end, if the problem cannot be solved, you can only reinstall the system!
The above is the detailed content of Solution to the blue screen prompt that the recovery environment cannot be found when booting the Win11 system. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











Troubleshooting and solutions to the company's security software that causes some applications to not function properly. Many companies will deploy security software in order to ensure internal network security. ...

Permissions issues and solutions for MinIO installation under CentOS system When deploying MinIO in CentOS environment, permission issues are common problems. This article will introduce several common permission problems and their solutions to help you complete the installation and configuration of MinIO smoothly. Modify the default account and password: You can modify the default username and password by setting the environment variables MINIO_ROOT_USER and MINIO_ROOT_PASSWORD. After modification, restarting the MinIO service will take effect. Configure bucket access permissions: Setting the bucket to public will cause the directory to be traversed, which poses a security risk. It is recommended to customize the bucket access policy. You can use MinIO

phpMyAdmin can be used to create databases in PHP projects. The specific steps are as follows: Log in to phpMyAdmin and click the "New" button. Enter the name of the database you want to create, and note that it complies with the MySQL naming rules. Set character sets, such as UTF-8, to avoid garbled problems.

Redis memory soaring includes: too large data volume, improper data structure selection, configuration problems (such as maxmemory settings too small), and memory leaks. Solutions include: deletion of expired data, use compression technology, selecting appropriate structures, adjusting configuration parameters, checking for memory leaks in the code, and regularly monitoring memory usage.

The following steps can be used to resolve the problem that Navicat cannot connect to the database: Check the server connection, make sure the server is running, address and port correctly, and the firewall allows connections. Verify the login information and confirm that the user name, password and permissions are correct. Check network connections and troubleshoot network problems such as router or firewall failures. Disable SSL connections, which may not be supported by some servers. Check the database version to make sure the Navicat version is compatible with the target database. Adjust the connection timeout, and for remote or slower connections, increase the connection timeout timeout. Other workarounds, if the above steps are not working, you can try restarting the software, using a different connection driver, or consulting the database administrator or official Navicat support.

Common problems and solutions for Hadoop Distributed File System (HDFS) configuration under CentOS When building a HadoopHDFS cluster on CentOS, some common misconfigurations may lead to performance degradation, data loss and even the cluster cannot start. This article summarizes these common problems and their solutions to help you avoid these pitfalls and ensure the stability and efficient operation of your HDFS cluster. Rack-aware configuration error: Problem: Rack-aware information is not configured correctly, resulting in uneven distribution of data block replicas and increasing network load. Solution: Double check the rack-aware configuration in the hdfs-site.xml file and use hdfsdfsadmin-printTopo

Redis memory fragmentation refers to the existence of small free areas in the allocated memory that cannot be reassigned. Coping strategies include: Restart Redis: completely clear the memory, but interrupt service. Optimize data structures: Use a structure that is more suitable for Redis to reduce the number of memory allocations and releases. Adjust configuration parameters: Use the policy to eliminate the least recently used key-value pairs. Use persistence mechanism: Back up data regularly and restart Redis to clean up fragments. Monitor memory usage: Discover problems in a timely manner and take measures.

VS Code can run on Windows 8, but the experience may not be great. First make sure the system has been updated to the latest patch, then download the VS Code installation package that matches the system architecture and install it as prompted. After installation, be aware that some extensions may be incompatible with Windows 8 and need to look for alternative extensions or use newer Windows systems in a virtual machine. Install the necessary extensions to check whether they work properly. Although VS Code is feasible on Windows 8, it is recommended to upgrade to a newer Windows system for a better development experience and security.