After installing Windows 10 it does not start correctly. Resolving the error “The computer is not started correctly”

The Windows 10 operating system from Microsoft is quite reliable and I don’t have any particular complaints - you still have to try hard to break it. However, cases are different, and therefore today I want to talk about the main errors when loading Windows 10 and how to fix them. In more than half of the cases, restoring the system boot and normal operation is quite possible - you just need to remain calm and correctly follow the instructions below.

Black screen when starting Windows

This is perhaps the most common Windows 10 boot error, which every third user has encountered at least once. A black screen with no signs of “life” of the operating system may be accompanied by the appearance of a cursor on the display or without it at all. It is pointless to wait longer than 15-20 minutes for the system to start successfully - the desktop will not appear. The most common cause is a failure of some drivers or their incorrect installation. In this case, it is not at all necessary that you did the installation yourself - some programs, as well as the Update Center, can do this.
The solution in this case is to start the OS in Recovery mode, booting from the Windows installation flash drive. Open the section Diagnostics, in the next window click on Additional options and then - System Restore.

After this, you will see a list of available recovery points. Select the closest one in time and click the “Next” button.

Only here in the additional parameters select the “Startup Recovery” section.

If you can’t restore normal operation, try the following advice.

Error “The computer is not started correctly”

In this situation, Windows 10 cannot boot, but at least it does not lose control of the computer and signals to the user that the computer is not running correctly.

You can, of course, click on the “Reboot” button, but as a rule this does not give any result (if sometimes it boots normally and sometimes not, check your hard drive).

To correct the situation, you need to click on “Advanced options”, and then go to the section Troubleshooting > Additional options > Boot Options and here click on the “Restart” button. After this, the following menu should appear:

Press the key 6 or F6 to launch Windows Safe Mode with command line support.
Your PC should restart again and boot into Safe Mode. In this case, there should be a command line window on the screen. Enter the following commands one by one:

Sfc /scannow dism /Online /Cleanup-Image /RestoreHealth shutdown -r

The last command will again lead to a reboot and Windows should still start normally.

Operating system not found

This is the saddest option of all. The computer simply does not get to the point of loading Windows and writes errors like this on a black screen.

First: “Boot failure. Reboot and Select Proper Boot device or insert boot media in selected boot device.”

Second: “An operating system wasn’t found.” Try disconnecting any drives that don’t contain an operating system. Press Ctrl+Alt+Del to restart".. In order to restore it, you will need the installation disk again. Go to the section bootrec /RebuildBcd bootrec /fixMbr bootrec /fixboot

This way we will overwrite the bootloader files. Restart the PC and check the operation of the system.

3. Hard drive damage. Well, this is the saddest, and most importantly, expensive option, since you will have to buy a new hard drive.

Some users are faced with the fact that when they try to start their computer, they are taken to a page that says that the system was not started correctly. There may be several reasons for this. For example, this error often appears due to power failures.

Sometimes, when the computer fails to start several times in a row, Windows activates automatic recovery mode. Also the problem may be Windows fast startup, if the user is able to log into the system, then you can disable this mode. Similar failures can be caused by some automatically installed drivers. To eliminate this problem, you need to go to the equipment manufacturer’s website and download all the utilities from there.

If none of the above methods help, then you can go to recommendations which will be given below.

Error after resetting or updating Windows 10

Sometimes after the update is completed or a system rollback, a BSOD may appear. Then the OS reboots, and a page is launched where you can restore Windows functionality. On it you will need to go to the section “ Additional options", then you need to click on the "Troubleshooting" section, then you will again need to select the additional settings item, and then click on the boot options. In the menu that opens, you will have to restart the device.

After starting, you will need to select safe mode, which supports the command line.

When the console starts, you need to enter the following operators:

• sfc /scannow
• dism /Online /Cleanup-Image /RestoreHealth
• shutdown –r

They can take quite a long time to complete, and some may issue warnings about errors in the process. However, you will need to wait for their work to finish. Then the PC will restart, after which the problems, if they were associated with a rollback or installation of updates, should disappear.

Errors: The system seems to have booted incorrectly or the computer is not starting correctly

The user may receive messages about such failures in cases where some data corruption systems.

This failure also results computer infection malware, using dubious programs to clean the registry. The crash may also occur after removing malware or after interrupting the update process.

In the case where the user has a code available restore points, first of all, you should try to roll back the system to them. In this case, the problem may disappear. To do this, you will need to click on the items marked in the figure.

After which, the following window will open.

In it you can select a point and begin rolling back Windows to its previous state. If there are no points, then you should press cancel and go to the previous screen where you will need to open the command prompt. It will require enter operators:

After this, you can try to start the OS again. Most likely, Windows will start. If this does not happen, you can enter the following statements into the console to undo the changes made:

• cd e:\configbackup\
• copy * e:\windows\system32\config\

If the previous tips did not help, then all that remains is to use automatic reinstallation of the OS.

Sometimes it may happen that when you start the tenth version of Windows, a notification appears on the “Automatic Repair” screen that the computer did not start correctly or the operating system did not load correctly. To fix this problem, you need to know its cause, which will allow you to choose the right solution.

Initially, it is worth noting that if the error pops up after turning off the PC or stopping the Tens update, but is eliminated by simply restarting the computer, and then occurs again, or when the PC does not turn off immediately, after which the recovery is performed in automatic mode, then this instruction won't be useful. In this case, there may be several reasons for this.

The most common reason for this computer behavior is power problems, perhaps even the power supply is acting up. In this case, after several attempts to start the operating system in automatic mode, the restoration of the operating system is activated. The second most popular option is problems with PC shutdown and fast boot mode. Here you should deactivate fast startup.

This can also be caused by driver problems. For example, on laptops with Intel processors, rolling back the Intel Management Engine Interface driver to a previous version may well eliminate this disconnection problem. In addition, you can run a scan and restore the integrity of the “tens” data.

If the problem occurs after a system reset or update

The most common way a notification appears that the PC is loaded incorrectly looks something like this. After resetting the operating system, a blue screen will appear with the INACCESSIBLE_BOOT_DEVICE notification, however, this may indicate more serious problems. In this case, everything is much simpler. After this, the data is reset, as a result of which the “Recovery” window appears with the “Advanced options” button and a reboot is performed. This method can be used in other variants of manifestation of a similar error. This is a completely safe method.

In this window, you need to go to “Advanced options”, where you need to click “Troubleshooting”. On this screen, you need to click on “Advanced Options” again, which contains “Boot Options.” You need to click on them, and then click “Restart”.

In “Boot Options” you need to press F6 to launch safe mode with the ability to work with the command line. If this succeeds, then you need to log in as an administrator.

In the command line that appears, you must execute in a certain sequence
several entries. When entering the first ones, error notifications may pop up or they will take a long time to complete. In that case, you just need to wait.

Initially, you need to enter sfc /scannow. Then you should write dism /Online /Cleanup-Image /RestoreHealth. The last command, shutdown –r, will reboot the computer.
You must wait until the computer boots. Basically, such actions can correct the error and return the operating system to normal startup.

“The computer did not start correctly” or “The system does not seem to boot correctly”

If, after starting a PC or laptop, a notification appears informing you that the computer is being scanned, and behind it a blue screen appears with a notification that the PC is not started correctly and a suggestion to restart it or visit additional settings, this may indicate defects in some system files of the operating system .

This problem can occur after turning off the power during an update, installing an antivirus or removing viruses from a PC, cleaning the registry, or installing unknown
programs.

It is still possible to solve this problem. If a situation occurs in which automatic creation of recovery marks is enabled on the system, then you should try to use this feature. This can be done quite simply.

You need to click “Advanced options”, and in the window that appears, select “Troubleshooting”. Then again you need to click “Advanced options”, where you should find “System Restore”.

In the window that appears, click “Next” and, if a suitable rollback label is found, it must be applied. Most likely, these actions will get rid of the error. If there are no marks, then you need to click “Cancel”. After fixing the problem in another way, it is necessary to activate automatic label creation
rollback

By pressing the “Cancel” button, a blue screen will appear. On it you need to click on “Troubleshooting”.

After this, you can take subsequent steps that may lead to the startup returning. In this case, the command line will be used. You must click on the “Reset PC to its original state” button, which will reset the system, but the ability to save personal data will remain, and all programs will be deleted. If you want to return to the original state, then you need to click “Advanced options”, and then select “Command line”.

It is worth noting that using this method can seriously damage your computer, so you should only undertake it with complete confidence in your actions.

Using command lines, you will sequentially check the integrity of files and system elements, fix them, and restore the registry from a backup copy. Mostly these steps will help fix the problem.

The first step is to enter diskpart. Then you need to write list volume. After this, a list of disk volumes should appear. Here you need to find out and remember the letter of the system partition with the operating system. In addition, you must remember the letter of the “System Reserved” volume. After this you need to enter exit.

Next you should write sfc /scannow /offbootdir=C:\ /offwindir=E:\Windows to scan the data integrity. Here C: is a drive with a bootloader, and E: is a disk with an operating system. In this case, a notification may pop up stating that this procedure cannot be performed. Here you need to continue executing commands.
Then you should write E:. After this you need to write md configbackup, then cd Windows\System32\config\. Next you need to run copy * e:\configbackup\.

The next command will be cd Windows\System32\config\regback\. Then you need to enter copy * e:\windows\system32\config\, after which you will be prompted to replace the files. Here you need to press A in the Latin layout and then Enter. These actions will start restoring the registry from a backup copy that is automatically created by the operating system.

After this, you need to exit the command line and in the “Select Action” window you need to click “Continue. Exit and use of Windows 10."

After this, the system should start. If this does not happen, then using the command line you can cancel all adjustments. To do this, you need to sequentially enter cd e:\configbackup\, and then copy * e:\windows\system32\config\, then press A and Enter. If none of this helps, then the only thing left to do is reset Windows 10 to factory settings.

In automatic mode, it usually starts after an incorrect shutdown or exposure to viruses, which causes critical errors. However, quite often you can observe a situation when the message “Preparing automatic recovery” of Windows 10 appears on the screen, and after a reboot, instead of starting the system, only a black screen is visible, or the recovery simply goes in a loop (the same window is displayed at each restart).

The sad thing is that no matter how hard you try, it may be impossible to complete this process. However, if the system itself, not to mention the backup copies, has not been damaged to the most extreme extent, when nothing except re-installation helps, several methods for eliminating this situation can still be proposed.

Preparing automatic recovery for Windows 10: black screen and reasons for the process to loop.

Be that as it may, despite all the statements of the developers that the new system is almost the most stable, alas, it also contains many errors that are constantly being corrected. And system failures are not always eliminated by a simple rollback.

If we talk about the possible reasons for this behavior in Windows 10, it is quite difficult to say for sure what exactly is causing such a failure. However, with a certain degree of probability the following can be distinguished:

• damage to backups;
• lack of system files;
• lack of space to save checkpoints with images;
• incorrect settings of the primary BIOS/UEFI system;
• problems with hard drive and RAM.

Preparing automatic recovery for Windows 10: what to do first?

First, let's look at the standard scheme of actions. If, after a notification appears that automatic recovery of Windows 10 is being prepared, nothing happens after the restart, you can try to use safe mode to start.

If the user has activated the assignment of the F8 key to call the start menu, the standard option is to select safe mode with loading network drivers. If the use of this key is not provided, which is most often the case, it is quite possible that at the boot stage a window will appear with a choice of either booting the system or diagnostic tools (if there are Anniversary and Creators upgrades.

If the system somehow boots, you can try to rollback manually:

1. To do this, you should not use the standard “Recovery Center”; it is better to use the command console, in which you enter the line rstrui.exe.
2. In the rollback window, you must select the point that preceded the occurrence of such a situation. Please note that it will not be possible to stop this process, nor will it be possible to undo changes made during the rollback process.

Sometimes, if the network drivers are loaded and there is an active Internet connection, you can try to perform an online repair using the DISM tool. It may very well be that such a solution will be much more effective.

Using installation media

If a message appears on the screen again stating that an automatic recovery is being prepared and this process is going in cycles, to start you need to use the installation disk or USB drive, having previously set it first in the list of boot devices in the BIOS.

• In the initial window with the installation offer, you must select the hyperlink to system recovery in the lower left corner.
• Go to the diagnostics section, then apply a rollback.

But you should not use startup recovery, since in most cases you will receive a message stating that the computer could not be returned to its original state.

After selecting normal recovery, the standard rollback procedure starts. It is quite possible that this method will produce results.

Expansion of reserved space

Another point when the Windows 10 “Preparing automatic recovery” screen appears, but then the system does not show any signs of life, is due to the fact that you need to increase the disk space allocated for saving backup copies. Again, this only applies to situations where Windows can be booted in Safe Mode.

In this case, the best option would be to use a small and fairly simple Partition Wizard program from MiniTool or a similar development with a built-in bootloader, which is much preferable for cases when the system does not start at all. In it you just need to increase the required space to at least 250 MB (it is better to set a slightly higher value), and then try to boot the system in normal mode.

BIOS/UEFI Settings

Finally, the loopiness of the “Preparing automatic recovery” process in Windows 10 may be associated with the settings of the primary system, which involve deactivating the system of protection against hacker attacks at the hardware level (prohibiting the execution of executable codes). The loop appears for this reason.

Thus, to correct the situation, you need to:

1. When you turn on your computer or laptop, enter the above parameters.
2. Find a line like No-Execute Memory Protect or XD-bit and set it to Enabled.
3. After this, you need to save the changes (F10) and restart the computer device.

Hard drives and RAM

If the problem is in the computer hardware, it may well be that first you should check the disk by booting from removable media using the command line, in which the command chkdsk /x/f/r is written, and at the same time use a check of the main system components (sfc /scannow).

If it is possible to make a safe start, the Victoria (for hard drive) and Memtest+ (for RAM) utilities are perfect for checking. In some cases, if the hard drive has begun to, as they say, “crumble,” as stated, a magnetization reversal program can provide invaluable assistance. It is difficult to say how effective this application is, but judging by the reviews, some hard drives can sometimes be restored in this way.

Conclusion

As you can already see, it is sometimes possible to remove the constant cyclical appearance of a message indicating that automatic recovery of Windows 10 is being prepared. True, in some cases you shouldn’t really count on system tools. But if none of the above helps at all, the system will have to be reinstalled (and in some cases even the hardware changed).

In general, based on purely practical considerations, the first thing to do is to try to boot with a safe start and perform further actions in a somewhat working system. But booting with network drivers is mandatory.

In the event that this option turns out to be completely unworkable, you will have to boot from removable media and try to restore it in this way.

All Windows operating systems, including the most stable seventh or the newest tenth version, are characterized by failures when the system does not boot in normal mode and informs the user that the computer is not running correctly. What is the reason and how to deal with it, see below.

The computer does not start correctly (Windows 8.1, 8, 10): the main causes of failures

As for the reasons that cause this behavior of the system, there can be quite a lot of them. According to statistics, most often such failures occur due to improper shutdown of the computer, forced stop of certain processes (for example, updates), damage to system files or even the bootloader itself.

The most common are failures with error descriptions like INACCESSIBLE_BOOT_DEVICE (inaccessible boot device), CRITICAL_PROCESS_DIED (critical process interrupted), or something like that.

Very often, notifications that the computer is not started correctly and because of this Windows cannot start in normal mode can be encountered during voltage surges, when the terminal spontaneously disconnects from the network when there is no uninterruptible power supply or stabilizer, etc. We should also pay attention to the functionality of all hardware components. But these are minor things. Situations look much worse when the system contains viruses that disrupt the operation of Windows, or for some reason the components responsible for loading the system fail. Let's look at several common cases of such problems and the main methods for eliminating them, without touching on problems with hardware.

What to do first?

So, if suddenly a situation occurs when the computer is not started correctly and the system cannot start, it may very well be that this is a fleeting failure. In this case, first you should reboot the system or simply turn off the terminal using the usual programmatic method from the Start menu.

If this is not possible, you will have to force a shutdown by long pressing the power button on the system unit or on the laptop panel.

As a rule, after such a procedure, upon startup, the system initiates a check of the system disk for errors, after which it can boot in normal mode. Visual verification can be observed in Windows 7 and below. In later versions it is done in the background.

Virus check

No less important if a message appears that the computer is not running correctly is to diagnose the system for the presence of virus threats. If the system does not start at all, this is quite problematic.

Therefore, it is recommended to use special utilities like Kaspersky Rescue Disk, from which the download is performed even before Windows starts. In the utility itself, to make the task easier, you can use its own graphical interface, and it works much better than stationary scanners, allowing you to identify many threats even in RAM or boot sectors.

Automatic recovery. The computer does not start correctly (Windows 10 and below)

In general, almost all recent Windows systems are characterized by the presence of a special self-healing module after critical failures. This is the so-called automatic recovery. The computer does not start correctly, the system does not boot, although there are signs of operability. In this situation, system recovery should start automatically.

A corresponding notification appears on the screen about the start of analysis to restore the system. But this only works if Windows has a fixed rollback point. If the user cleaned or deleted previously created ones before the failure occurred, nothing will work. There is simply no copy in the reserve from which you can roll back to a previous state.

In the seventh version of the operating system and below, fixing this situation looks much easier. When starting the system at the boot stage, you should use the F8 key, which is used to select a safe boot mode, but in the menu that appears, you need to select loading the last working configuration (again, if possible). By the way, in the tenth version it is also possible to use the F8 key to call such a menu.

Boot in safe mode with system file integrity check

The situation is somewhat more complicated with damage to the system components of the system with the impossibility of restoring them automatically (at startup or reboot after a notification appears that the computer has not started correctly). What to do in this case?

To begin with, you can try to boot into safe mode, and then use the command line called from the Run console (Win + R). If for some reason this boot option is not possible, you should set Safe Mode with confirmation on the command line to determine the component on which the boot stops. In this situation, the command line will have to be called from the installation disk.

In both cases, enter sfc /scannow on the command line, after which the system will automatically check and repair faulty components. But this does not always help.

Disabling driver signature verification

Now let's look at the situation when the computer does not start correctly (Windows 10 on board). In the tenth version, getting to safe mode is quite problematic. Here you will need an installation or recovery disk, when booting from which in the recovery section you need to select additional settings and go to diagnostics, and then use the boot options menu.

In the menu that appears, there is a line to disable checking the digital signature of drivers, numbered seven. You need to move to it and press the enter key (you can do this faster by pressing the number 7 on the keyboard).

This problem is very often associated with the oem-drc64.sys driver. If disabling signature verification worked, you need to enter the registry editor in the system (regedit in the Run menu) and go down the HKLM branch through the SYSTEM section to the CurrentControlSet directory, which contains the Services directory. Here you should find the driver folder and delete it.

Restoring a system from an image

It is believed that the best option for restoring system functionality after a message appears that the computer is not running correctly (Windows 10 is used or any other version) is to restore from a previously recorded system image.

Not everyone, however, thinks about such things in advance, however, the process of putting Windows in order in this case turns out to be the fastest and easiest.

Using the command line when an update is incomplete or interrupted

There are also situations when problems with the computer starting incorrectly (8.1, 8, 7 or 10th modification on board) are associated with an incomplete or interrupted system update. You can also deal with these failures.

We call the command line at boot, as shown earlier, and enter the command shown below there:

Force recovery commands

If this option does not help, the computer does not start correctly and the system does not boot, you can try to perform a forced recovery.

To do this, first write three commands on the command line:

• diskpart;
• list volume;
• exit.

Be sure to remember the system partition letter, since in most cases it will differ from the generally accepted value of “c” (most often the system partition “e” will appear).

After entering each command, press the enter key. In theory, this method provides an almost 100% guarantee of restoring Windows functionality.

Bootloader recovery

Finally, if your computer doesn't start properly, Windows of all versions offers another universal solution to repair a bootloader that may be damaged.

To do this, in the same Shell, you need to first use the chkdsk c: /f /r check command, and then directly the recovery directives, as shown below:

After this you can reboot. The system, if the failure was associated with the bootloader, will work like clockwork.

If all else fails

Finally, about one more situation when none of the above helps. You'll have to reinstall Windows. But, in order not to “destroy” the entire system, when booting from the installation disk in the diagnostics section, you need to select the option to return the computer to the so-called original state.

This approach provides the option of saving user files, after which it will be possible to perform a “clean” installation of Windows, which in most cases allows you to get rid of software failures much better than all checks combined. But this, as is already clear, should be done only in the most extreme case, when all other means have proven powerless.

Instead of a total

Finally, it remains to add that the situation when the computer does not start correctly or the system does not start can be associated specifically with the hardware. In particular, problems with the graphics chip or hard drive when it begins to “crumble” can have a particularly strong impact on system loading. If these are truly physical problems, nothing can be done about it. But to accurately identify faults, additional ones should be used. Only if the cause of the failure and the failing component are correctly identified, the correct solution to eliminate such consequences can be determined.

As for all other cases, it is believed that at least one of the above proposed methods will work. So all that remains is to advise using options for troubleshooting, moving from simple to more complex methods. But in any case, to prevent such incidents from happening in the future, it is better to take care in advance of creating a system image or recovery disk, recording anti-virus utilities, etc. This is quite easy to do, even using Windows’ own tools. Any user should have such tools at hand, as they say, in the most unforeseen case, because none of the currently used Windows systems are immune from failures.