Depending on the Windows version, you can access the automatic system repair from here in different ways:. If the current version of Windows cannot be repaired manually or automatically, your next option is to restore your operating system to an earlier state when everything was still working. By restoring your system in this way, your personal files remain completely untouched, unlike when the system is re-installed. The prerequisite, however, is that a corresponding system image is available.
Unless you have disabled this feature on your own, Windows automatically creates these images at regular intervals, or whenever something fundamental changes the system flow — such as installing drivers, replacing a hardware component, or performing an update. On the internet there are numerous external tools that can automate the backup of system images. However, this automatic backup operation only includes the system disk that is usually located on the C: drive.
If you also want to consider all other partitions, you must proceed manually. From Windows 7 onwards, it has been possible to create system images using self-explanatory, on-board tools. You will then need to select the desired partitions and a recovery disk , such as an external hard disk. Saving your system image can take from a few minutes to hours, depending on the amount of data and performance of your computer.
This can happen, for example, due to a computer virus. In this case, you must reinstall or repair the boot manager. This task is also performed by the automatic system repair see above. In the command line, enter the following three cmd commands one after the other and confirm them with the [Enter] key :.
When entering commands, pay attention to the space between the two terms. If nothing else helps, the most radical method is always to completely rebuild your operating system. For this you need your installation data carrier again. However, you should have saved your personal data beforehand.
This should be done at regular intervals, just like saving your system image, so that you are always prepared in case a problem arises. This is often the case if you have installed a new hard disk in your PC that does not yet have an operating system.
But first check if you have not changed the boot order and the hard disk might not be recognized for this reason. Otherwise, you may be reinstalling for nothing. Now you know what you can do if your Windows operating system no longer boots. But what if, after switching on the computer, the dreaded bluescreen of death appears or the screen remains completely black?
The graphics card may not be properly connected, there may be dust on the memory contacts, or the newly installed processor may not be compatible with the old motherboard. To do this, reinstall your old processor and search for the appropriate update files on the mainboard manufacturer's website.
So be sure to make a backup first. If the problem still isn't solved, you'll have to resort to the exclusion method : Remove all newly installed and connected hardware including peripheral devices such as printers and headphones and restart your computer. If your computer and Windows boot successfully again, start by reconnecting the remote hardware one by one and restarting the computer until you find the culprit.
Unfortunately, Windows Update can break Fast Boot compatibility. The two other keys that might work are F2 and Escape. If you don't see any Fast Boot entry, your computer was made before as they did not include a Fast Boot option. They're useful for recovery because they work even when Windows doesn't. Accessing these settings requires launching your computer in BIOS mode.
Once in BIOS mode, check the following settings:. Secure Boot on the wrong setting can cause your computer not to start. Furthermore, disabling Secure Boot may stop you from upgrading to Windows The reason Secure Boot causes problems is that it's designed to protect computers against malware. Because it checks the drivers and hardware loaded by Windows at startup, any driver or hardware component not recognized by the system will generate an error at boot. Secure Boot settings are located under Boot options.
You can turn it on or off. Malware is a major cause of an unbootable computer. The best method for dealing with malware is a bootable antimalware rescue disk. I prefer Kaspersky's free disk as it only requires downloading the image and using Etcher to image a flash drive or other writable disk. Etcher works in Windows, macOS, and Linux. You can then boot into the afflicted computer using the rescue disk and remove malware preventing the computer from booting.
Download: Kaspersky Rescue Disk Free. It might still be possible to boot into the Command Prompt. Using this interface, you can perform more troubleshooting procedures. You'll need to have Windows 10 on a bootable disk or USB drive to perform the procedure, so use another computer to set that up before you get started. To boot to the Command prompt, start your computer. While it's initializing, watch out for details of a combination of keys that will allow you to enter the BIOS.
This information is typically delivered alongside the vendor logo. Your choice here will depend on where your copy of Windows 10 is located. Again, the specifics of this process may vary from one system to another, so consult the on-screen instructions. Next, insert the disk or drive containing Windows 10 into your system, save your configuration, and restart your PC.
Enter the requested language, currency, and input preferences, then select Repair your computer on the next screen. If you're already booting Windows 10 from a disk or drive, it's well worth utilizing a couple of utilities that are available as part of the process. Once you've booted from the drive as detailed above, you'll get access to options that can get your PC back on track.
System Restore is a utility that allows you to return to a previous Restore Point when your computer was working normally. It can remedy boot problems caused by a change you made rather than a hardware failure.
Startup Repair is a general-purpose troubleshooter for issues that prevent Windows from starting up. If you're struggling to find the source of your boot issues, it's a good idea to run the utility in case it can find a solution.
A system with more than one drive installed can cause boot issues for Windows 10 users if their operating system OS volume has its drive letter unintentionally unassigned. However, you can fix this problem with a minimum of fuss by booting to the command prompt interface. The Startup Repair tool automatically fixes many common problems. The tool also lets you quickly diagnose and repair more complex startup problems. When the computer detects a startup problem, the computer starts the Startup Repair tool.
When the tool starts, it performs diagnostics. These diagnostics include analyzing startup log files to determine the cause of the problem. When the Startup Repair tool determines the cause, the tool tries to fix the problem automatically. Start the system to the installation media for the installed version of Windows. For more information, see Create installation media for Windows. The Startup Repair tool generates a log file to help you understand the startup problems and the repairs that were made.
You can find the log file in the following location:. For more information, see A Stop error occurs, or the computer stops responding when you try to start Windows Vista or Windows 7. If the corruption in the MBR affects the partition table, running Fixmbr may not fix the problem. If methods 1, 2 and 3 do not fix the problem, replace the Bootmgr file from drive C to the System Reserved partition.
To do this, follow these steps:. If Windows cannot load the system registry hive into memory, you must restore the system hive. If the problem persists, you may want to restore the system state backup to an alternative location, and then retrieve the registry hives to be replaced. Starting in Windows 10, version , Windows no longer automatically backs up the system registry to the RegBack folder. This change is by design, and is intended to help reduce the overall disk footprint size of Windows.
To recover a system with a corrupt registry hive, Microsoft recommends that you use a system restore point. For more details, check this article. If the system gets stuck during the kernel phase, you experience multiple symptoms or receive multiple error messages.
These include, but are not limited to, the following:. For example, "0xC2" , "0xB" , "inaccessible boot device" and so on. The screen is stuck at the "spinning wheel" rolling dots "system busy" icon. If either of these options works, use Event Viewer to help identify and diagnose the cause of the boot problem. To view events that are recorded in the event logs, follow these steps:. In the console tree, expand Event Viewer, and then click the log that you want to view. For example, click System log or Application log.
On the Edit menu, click Copy , open a new document in the program in which you want to paste the event for example, Microsoft Word , and then click Paste.
0コメント