Question: Couldn't find Windows 8.1 recovery environment
Answer: Because of the first mistakes, it was not worth continuing the commands. You will have to enter on a new command
Question: The message "Could not find Windows 8.1 recovery environment"
Answer: There were no errors when executing commands?
Let's look at the partition ID, although in theory it shouldn't affect recovery. We need a screen of the commands:
Off-topic:
Do not worry, as a last resort we will expand the factory image from the flash drive with our hands.
Question: Couldn't find recovery environment (Windows 8.1)
Answer:
Message from olen6
It was not possible to simulate your situation with the appearance of RAW partitions, hidden partitions remain in NTFS as if nothing had happened. It remains to try using DMDE to return the partitions to their previous state. Try to do what is written below with a 352 MB partition, you do not need it and if something does not work out, then it’s not scary (anyway, delete it later).
In Disk Management, select a 352 MB partition and click the "Delete" button. Next, run DMDE> open your HDD> find a 352 MB partition with the inscription free, under this inscription there should be a line with the word "Found", also 352 MB, select it> the "Restore" button> restore the boot sector from a copy (Yes)> red Apply button> write changes to disk (Yes)> focus again on this section with the word Found 352 MB> Insert button> GPT GUID section (OK)> red Apply button> uncheck the box to create backup and click (Yes).
After rebooting the 352 MB partition should become visible and NTFS, try to view its contents, open or not?
I connected the screw to another computer via USB - NTFS file system.
Question: Couldn't find Windows 10 recovery environment
I tried to do as it says here I got to the point, as in the screen, but nothing comes of it ...
Answer: yes, it seems that all the sections are in place
Question: Windows 10 "Couldn't find recovery environment"
Answer: Assembly system?
If the system is NOT a build, you can try to check the integrity of the system files ( sfc / scannow from com.line). If it finds and repairs corrupted files, then you can try again to execute
Question: Couldn't find recovery environment
But this did not help... Somehow I restored the system to a certain restore point.
Now after I want to restore the system it writes: Could not find recovery environment
What to do? How to restore the ability to restore Windows? (Screenshot of the "Disk Management" window in Figure 3).
Answer: Drop8Dead What is the name of your laptop and which windows was preinstalled on it from the factory: 8 or 8.1? Give a screen of the command reagentc / info look. I see you added a letter to the last section, so look for a large wim file (about 10 GB) or several swm files on it. If you find it, then give a screen with the full paths to them.
Question: Windows 8.1 cannot be restored - could not find the recovery environment
Answer: There was a case, I updated it to Tehnical Prewie, but then rolled it back to the drain.
But I solved the problem myself, wrote down the environment on a USB flash drive, made a recovery through it, now everything is in order!
The recovery environment for Windows 8.1 and 10 in the form of a menu with the inscription "Select an action" and, accordingly, with a list of possible actions on a blue background of the screen is an environment for resuscitation of these versions of the operating system, an evolutionary continuation of the menu on a black background of the screen with additional boot options, familiar to many according to Windows 7. The recovery environment is designed to solve problems that arise in the operation of Windows 8.1 and 10, it offers access to some standard tools, the use of which can prevent the use of a radical method - reinstalling the system. In the recovery environment, you can:
The predecessor environment in Windows 7 is started by pressing F8 while the computer device boots. This method is extremely convenient in case of a sudden failure of the system and, as a result, the inability to boot. But with Windows 8.1 and 10, this method does not work. For these purposes, there are Shift + F8 keys, but in practice it will not be possible to apply them in every case due to the quick launch of the last two versions of Windows. The faster launch of versions 8.1 and 10 actually makes it impossible to use this keyboard shortcut, especially on computer devices with SSDs.
How do I get into the recovery environment for the last two versions of Windows? From a running system, this can be done in several ways:
shutdown.exe / r / o / f / t 00
In emergencies, when Windows 8.1 or 10 refuses to boot, you can use either the installation media of one of these versions to enter the recovery environment, or prepared using the system itself. In some cases, if the system undergoes a serious malfunction and cannot boot, the recovery environment itself starts as the only option.
Access to the recovery environment can be organized in another way - by installing two or more Windows on the condition that version 8.1 or 10 is installed last and, accordingly, it is their loader that will offer a choice of operating systems for further launch. Thus, the implemented option to enter the recovery environment will be available all the time when the computer boots. And, accordingly, it can be quickly used in the event of a sudden appearance of system problems without the need to use bootable media. Plus, we will get the advantage of an alternative operating system, which, without being damaged itself, will be able to help reanimate the problem system.
The operating system boot selection menu, implemented by the Windows 8.1 and 10 boot loaders, in addition to the list of the systems themselves, also contains the option to change the boot parameters and some other parameters.
With these other parameters
and is the recovery environment.
In the implementation of the boot menu of several operating systems on UEFI computers, the recovery environment may also have an additional option to select the computer's boot device.
Can the second, third and so on Windows, even in direct implementation, even as an access to the recovery environment in the bootloader menu, become a panacea for all cases of problems with the software part of the computer? If two or more Windows are installed on different partitions of the same hard disk, and they have a common bootloader, then no. Windows bootloaders have an unpleasant feature - they get corrupted. And it is not always possible to reanimate Windows using its standard tools. In this regard, it will be much more useful from. By the way, some of them (based on WinPE), in addition to third-party Windows resuscitation tools, may contain some of its standard features, including launching the recovery environment. Among them is the resuscitation Live-disk, and it, by the way, is another way to access the recovery environment of non-bootable Windows.
Have a great day!
A few weeks ago, I became the owner of an HP Pavilion p170nr laptop with Windows 8.1 preinstalled. Since I am an avid Linux user, it was decided to install the main, working Ubuntu system, but also leave Windows for toys and something whimsical, like updating the BIOS. Greed also played a role - in fact, money was paid for the 8-ku.I had to use some kind of partition manager (I don't remember the exact name and I don't know anymore), which promised that it could work with Windows 8, but, as a result, killed me the system partition. Moreover, completely both it and the section with the image for recovery, although I did not perform any manipulations with it.
Naturally, there was nothing to restore the system with a laptop. As I found out later, HP sells them separately. And I didn't bother to create something like that myself.
SystemRescueCD came to the rescue. I will not describe the hour-long twists and turns with manipulating fdisk and testdisk. But at the output, we managed to get a structure identical to this
All files seemed to be in place. testdisk correctly displayed the contents of all partitions except Windows and MSR. The problem with Windows was, apparently, in a very large partition size (it just fell out with a segmentation fault), and I still did not understand what MSR was. Seems to be just storage for anything even without a filesystem.
However, the system refused to boot. Gave a number error (something like 0x00000025), after trying to run the recovery tool, the message changed to "the file \ windows \ system32 \ winload.efi is damaged or missing."
I had to download the PE image of Windows 8.1 (I found it ready at rutracker.ru) and dive into the study of bootloaders, images and other low-level details. All of the following is the fruit of my research, so I was probably wrong about something.
wim images... .Wim files are widely used in newer versions of Windows. Basically, it is just an archive that is used to deploy the system. It can be split into volumes with the .swm extension. The dism utility is used to work with these images.
Boot loaders are simply efi files that are usually located in the \ EFI \ NAME \ Boot directory. NAME is simply a name, often after the name of the hardware manufacturer. Specifically, I have 2 subdirectories in the \ EFI directory - HP and Microsoft, and the bootloader is configured to \ EFI \ Microsoft \ Boot \ bootmgfw.efi.
The standard Windows boot loader also has its own boot menu. It is contained in the file \ EFI \ Microsoft \ Boot \ BCD. Basically, it's just a list of .fi files that you can run and their startup options. For example, this is where the memory test, the system recovery environment and normal Windows boot start. This file is edited using the bcdedit utility. By the way, this is where I had the problem after restoring the disks. One of the parameters of the boot record defines the working disk for it "device partition =". And the corresponding.efi-file will be loaded from it. But after re-creating the Windows partition, its UUID changed, so the file \ Windows \ System32 \ winboot.efi was not found. But I realized this much later, after reformatting the entire section.
From the recovery environment, in turn, you can deploy the recovery image, which is stored on the appropriate partition in the install.wim file (about 17GB). In addition to it, this section stores .wim files with drivers, manufacturer utilities, as well as scripts for installing all this. My install.wim was split into many .swm files, about 350GB in size.
In the same section, I found the winUCRD.wim file, which is very similar in size and structure to winre.wim, but differs from it in size by a couple of hundred kilobytes and contains several extra files. Perhaps some kind of blank for winre, which is being finalized during the installation process.
On this I decided to end my research. A working laptop was needed by Monday, installing and configuring Ubuntu and everything else took about 5 hours.
P.S. While collecting material for this article, I came across an interesting post explaining why the recovery tool might not start. For it, in the BCD, you need to specify the parameters of the RAM disk and the disk on which the installed WIndows is located, which could also break for me.
P.P.S. Yes, indeed, the point was that the device / osdevice parameter of the BCD recording with loading recovery tools did not indicate a recording with the parameters of the RAM disk, but it was not clear where. You can restore using the following commands ()
Bcdedit / create (ramdiskoptions) / d "Ramdisk options" bcdedit / set (ramdiskoptions) ramdisksdidevice partition = Drive bcdedit / set (ramdiskoptions) ramdisksdipath \ Recovery \ WindowsRE \ boot.sdi
Here: Drive - the drive where the recovery image is stored. It's not a UUID, but just ‘c:’
Now we edit the parameters of the recording of the startup of the recovery environment (you can create it anew):
bcdedit / create / d "Boot from WIM" / application OSLOADER bcdedit / set (GUID) device ramdisk = \ Recovery \ WindowsRE \ winre.wim, (ramdiskoptions) bcdedit / set (GUID) path \ windows \ system32 \ winload.efi bcdedit / set (GUID) osdevice ramdisk = \ Recovery \ WindowsRE \ winre.wim, (ramdiskoptions) bcdedit / set (GUID) systemroot \ windows
Here:
Tags: Add Tags
Due to the presence of viruses, mismatch of drivers or software, the OS may malfunction. If your Windows crashed, don't panic. The situation can be corrected by returning the state of files and programs to the time when the PC was working properly.
Certain errors and problems may occur while running OS Windows 7, 10 or 8. As a result of such failures, a new start of the operating system in operating mode becomes impossible. In this case, it is not at all necessary to do a laborious reinstallation of the OS. It is enough to perform a system restore.
When working, we use the following scheme of actions:
There are several ways you can use to get the OS back up and running. Some of them are based on rolling back to saved parameters. Others simply clear the data.
You can "reanimate" the OS in one of the following ways:
Recovering the operating system using the "reanimation" checkpoints of the system is one of the most affordable, effective and popular options. To apply it, you need to carry out a series of clicks:
Such an operation will fix the problems with the computer, discard the changes and return the system to the operating state that allowed the PC to boot normally. Loss of data, files and documents during such recovery does not occur. All data is saved. The operation is reversible. You can roll back the system to a previous computer state and use a different restore point.
Many people wonder how to independently (manually) make a recovery point in order to select it in the future? To do this, in the same menu "Start" - "System Restore" you can create such a point yourself at any convenient and suitable moment for you. It will be saved with the current date, which can only be remembered.
In computer engineering, there is such a thing as a restore point. These are saved PC parameters. As a rule, saving occurs automatically with each successful boot of the OS. The easiest way to resume Windows 7 is to use this data.
Press F8 while booting your computer. This command will bring up a menu of options for starting the system. Next, you need to select the Last Known Good Configuration option.
Another method can be used. Go to the properties of the My Computer folder. Find the line System protection, by clicking on which you will open the dialog box of the same name. Click Recovery - Next. We set a key date, indicate the disks to be repaired, and confirm the actions. After restarting, the PC should work fine.
You can fix OS problems without restore points. To do this, you need to resort to the LiveCD program. It needs to be downloaded and written to a USB flash drive with the .iso extension.
Further, all actions will take place in the BIOS. It is necessary to configure booting from a USB flash drive. To do this, in the Boot section, select USB-HDD in the First boot device line.
Before proceeding directly to the recovery, copy all the necessary files to a removable disk. The LiveCD program provides a special menu for this purpose.
We will fix the system error using an archive copy. Connect the USB flash drive, open the Windows \ System32 \ config \ folder. Files with the names default, sam, security, software, system must be moved to any other folder. In their place, we transfer similar files from the RegBack folder and restart the computer.
The described method will only help if the problem is related to the registry.
You can resort to "reanimating" Windows 7 from the command line if the PC starts to freeze or work slowly, however, the system boots. Enter the menu "Start" and use the right mouse button to run Command Prompt as administrator. Issue the rstrui.exe command, which will open the System Restore program. Click on "Further"... In the next window, select the desired rollback point and click again "Further"... Upon completion of the process, the PC should work normally.
You can enter the utility in a different way. Go to "Start"... To call the command line, press "Run" and register the CMD command. We click the mouse on the found CMD.exe file and wait for the launch. Next, enter rstrui.exe in the command line and confirm the action with the Enter key on the keyboard.
It is not always possible to play it safe and create OS restore points in advance. There may be problems that block the option of such a "resuscitation" of the PC. Then you can use another, no less effective and easy option - restore the Windows system using the system itself.
We rely on the diagram:
This method is preferred if the usual system boot is impossible. Then after pressing the power button of the PC on the system unit, hold down the F8 key to call Launch menu... One of the "Menu" options is "Safe mode"... Select it and press Enter on your keyboard. As soon as Windows boots up, we perform the same algorithm of actions that we described earlier.
If you were able to start the OS, you can resume Windows 8 via "Options"... Move your cursor over the upper right corner and enter them. Click on "Changing computer settings" – ... Chapter "Recovery" will offer several options:
Decide what exactly needs to be done. Then follow the prompts on the menu.
If you choose the latter method, in the window that opens, click on the diagnostic item. You will be offered the following options:
To resume Windows 8.1 press Win + R and call sysdm.cpl. In the system properties window in the tab "Protection" specify the required system drive. Click on "Restore"... By clicking "Further", you will be able to see a list of rollback points. Select the one you want and click Find Affected Programs... Changes that have been made on the PC since the selected moment will be deleted. End the process by clicking "Ready".
In the case of working with Windows 8, problems may occur, incorrect operation of the Internet, etc. To fix this, you can use the classic recovery method via restore points.
Another option is to roll back the system. To do this, open the menu "Start" - "Control Panel" - Windows Update... Selecting an item "Removing updates"... You can do the same using the command line.
So, in the list of updates that opens, we delete those of them, from the moment of installation of which (we look by date) problems and malfunctions began. We delete unnecessary files and reboot.
In Windows 8.1, you can perform a factory reset. Important files will not be affected by this operation. The method is effective, but for its implementation you need the OS to boot without problems. We use the algorithm:
If you cannot log into the system in the usual way, you must use the disk with the system. We load the installation disk, select "System Restore"... Push the button "Diagnostics", and "Restore".
If you're having problems with Windows 10, press Windows + Pause. Go to "System protection" and press "Restore" – "Further"... Select the required metric and press again "Further"... When done, press "Ready"... The computer will automatically restart and the changes will take effect.
One of the advantages of the "ten" is the ability to return the settings to the factory defaults. This avoids having to install the system first. To reset data go to "Computer settings" – "Update and Security" – "Recovery" – "Reset the computer to its original state"... Click on "Begin".
You can take care of the possibility of rollback in case of failure in advance. You can create resume points yourself or configure them to be automatically created at the desired frequency. To do this, in the settings, in the Update and security item, select Backup service. Specify where to save the copies, click Add Disk. After selecting a device, the function will be activated.
You can restore the Windows 10 system again through the use of restore points. In this case, the system will roll back to the moment when it booted without hindrance and worked without failures. This recovery method is described at the beginning of the article.
If the OS does not boot, then a warning table appears on the screen with the key "Additional recovery options"... Click it and select "Diagnostics" - "System Restore"... We make a choice of a Windows restore point, wait for the system rollback and reboot.
If such operations did not help and the computer continues to work incorrectly, you can roll back to the basic settings. Some programs and utilities, personal PC settings will be reset, and personal data will be deleted.
This technique is used extremely rarely if the other options described above do not help. The algorithm of actions in this case is as follows:
It will then take 40-90 minutes to roll back the system.
One of the radical methods of fixing the error involves using an installation disc. After launching it in BIOS, click System Restore. In the Troubleshooting section, indicate the desired action. Then follow the prompts of the system to complete the process.
Similar posts
The debate about which is better than Windows 10 or Windows 7. This phenomenon is not accidental. Microsoft developers claim that it is better to find nothing than Windows 10, and experienced users say the opposite, they say the system is more reliable than Windows 7 now ...
Computer freezing is a rather annoying problem. This can occur both at the stage of starting the system, and in the middle of the process of its operation. Let's see why this can happen and what to do about it? Why does my computer freeze ...
Sometimes, when installing programs or applications, a message appears on the computer screen stating that error 5 Windows 10 has occurred. This means that the user is denied access. This happens if there are several accounts in the system ...
