Home
Windows
By
Abhishek Silwal
If you have enabled Windows Boot Manager or use an older Operating System where the UEFI bootloader is not available, you will encounter the error message: “Windows failed to start. A recent hardware or software change might be the cause.” It appears when the Boot Manager can’t access the boot device.
It will also display a possible cause, such as, “A required device isn’t connected or can’t be accessed.” This issue mainly happens because of the corruption of the boot files necessary to start the OS. But it is also possible that the necessary boot device is not connected properly.
Remove External Devices
Depending on your Boot priority order, your system may be trying to boot from another media, such as a USB or a network device. So, before trying other possible solutions, try removing all unnecessary external devices.
This way, only the normal OS storage device or installation media is available as the current boot device.
Check BIOS Settings
Before you begin repairing the potentially corrupt boot files, you need to ensure that your computer is detecting the OS drive and interfacing with it properly. Also, you need to check the boot order list to make sure that the OS drive is the first priority.
- Start your computer and press the BIOS key immediately after you see the logo to get to BIOS.
- Go to Boot or a similar tab and select something like Boot Priority.
- Make sure your OS drive (generally C Drive) is at the top of the list. If the drive does not show up, it is not connected properly, and you need to reinsert it in this scenario.
- If you are trying to boot from a Windows installation media, you have to move the media to the top instead.
- Now, look for the SATA mode option. You can usually find it under Advanced or Storage Controller settings.
- If you are using older operating systems, IDE is the preferred choice. And for newer systems, set it to AHCI. We recommend checking if the computer boots when enabling each option to ensure what mode you need.
- If you still encounter the error regardless of the mode, set the SATA mode to AHCI for now if you are using Windows Vista and later OS. After trying other methods, you can switch the SATA mode and check which works best for you.
Perform Startup Repair Using Windows Installation Media
Windows includes the Startup Repair feature that automatically checks for errors with the boot configuration data or other boot files and attempts to repair them. You will get an option to perform the startup repair whenever you encounter the error.
However, if it can’t solve it, the source file for the repair may have some issues as well. In such cases, you need to use an installation media to use it as the source.
- Create a Windows installation media with the same version as your system on another computer.
- Boot using this installation media. If you have an MBR disk, you need to manually change the Boot order from the BIOS to prioritize the installation media.
For a GPT disk or UEFI system, you should get the choice to boot from the media. Or you may need to press a certain key to access the boot menu. Search official sources for such a key for your motherboard. - Set the language preferences and agree with any license terms.
- Then, on the installation screen, click on Repair your computer.
- On newer Windows OS, go to Troubleshoot > Advanced options > Startup Repair. For older ones, you can directly select Startup Repair.
- Follow the on-screen instructions to finish the repair and then boot again.
- This time, boot using your original OS drive and then check if you still encounter the error.
Manually Repair Boot Files
Sometimes, the automatic startup repair utility can’t repair the boot files. In such cases, you need to manually repair them using the Command Prompt.
- Boot using the proper Windows installation media (see above solution).
- Specify your language preferences and click Next.
- On the Install screen, click Repair your computer.
- Select Command Prompt or Troubleshoot > Advanced options > Command Prompt.
- Type the two commands below to check if you have a GPT partition system in your OS disk and press Enter after each:
diskpartlist disk(here, the Gpt column should show an asterisk (*) sign if you have a GPT partition on the disk)
- Enter the commands below depending on the partition scheme of your system disk:
For GPT,
For MBR,
exit(to exit out of diskpart)bootrec /fixmbrbootrec /fixbootbootrec /rebuildbcd
Re-create Boot Files
If the boot configuration and file repairing commands don’t work, you must recreate these files from scratch using your operating system files.
- Boot using the proper Windows installation media and go to the Command Prompt (see above method).
- Type the two commands below to check if you have a GPT partition system in your OS disk and press Enter after each:
diskpartlist disk(here, the Gpt column should show an asterisk (*) sign if you have a GPT partition on the disk)
- Enter the commands below depending on the partition scheme of your system disk:
For GPT,
select disk #(replace # with the relevant disk number)list volume(check the number of the volume with the FAT32 partition that is hidden)select volume #assign letter = S:(or any unused drive letter)exitcd /d S:\EFI\Microsoft\Boot\(replace S: with the drive letter you used earlier)ren BCD BCD.old(to create a backup to account for unforeseen situations)bcdboot C:\Windows /l en-us /s S: /f all(here, replace C: with the drive letter of the operating system and S: with the letter you assigned earlier.)
bootrec /rebuildbcd(not necessary if you have a Windows version before Windows 10 Version 1709)
For MBR,
select disk #(replace # with the required disk number)list volume(check the number of the volume with where Info says System)select volume #assign letter = S:(or any unused drive letter)exitbootrec /fixmbrbcdboot C:\Windows /s S:(here, replace C: with the drive letter of the operating system and S: with the letter you assigned earlier.)
Clean Install Windows
If you cannot boot into your operating system after repairing the boot files, your final option is to clean install Windows. A clean install removes the partition containing the boot files as well as the OS partition. This way, you can reinstall all such files (but without corruption) to resolve your issue.
Clean installing Windows will delete all the data on the disk (of your non-system drives as well). So, first, try backing the data on the disk by booting with a Linux live disk or Windows-to-go disk.
- Create a Windows installation media of the version you want (using the same as the Windows in your disk is not necessary).
- Boot using this media and specify your language preferences.
- Click on Install now on the Install screen.
- Enter your product key if you have it. If not, select I don’t have a product key as well as the Windows build you want (Home, Pro, etc.)
- Click on Next.
- Agree with the license agreements and select Next.
- Choose Custom: Install Windows only.
- Select all the partitions for your OS disk (Drive 0) and click Delete for each. Confirm your choice as well.
- After you only have the unallocated space for the disk, select it and click Next.
- Ignore the warning as the setup process will automatically create the necessary partitions.
- Click on the partition that says Primary and then Next.
- Follow the on-screen instructions to clean install Windows.
- After restarting, check if you can boot from the OS drive. Then, you will need to go through the initial account and privacy setup.
Use USB 2.0 Port to Install Older Windows
All computers that already have Windows 10+ may not support installing old OS like Windows 7 from USB 3.0 ports or flash drives. If you try doing so, you’ll get the above error while trying to boot from the installation media.
This is mainly because of the lack of USB 3.0 drivers on the installation media. But on some computers, you might still be able to install the OS. Regardless, it’s better to either use USB 2.0 or include USB 3.0 drivers in the Windows image on the installation media. You may also need to enable CSM or Legacy support on your BIOS settings.
Additionally, if you only have USB 3.0 ports, you have to enable USB debug mode on BIOS to use them as USB 2.0 ports.
If you are facing this error, then chances are you may have installed new hardware or software which is causing the issue. Sometimes installing the latest Windows updates seems to cause this issue but you can’t be sure until you troubleshoot the issue. Now as far as software problems are concerned, these might be the possible reasons as to
why you are facing this error:
- Corrupted BCD information
- System File is damaged.
- Loose or faulty SATA/IDE Cable
- Conflicting 3rd party software
- Virus or malware
The error which you will get after a reboot will be:
Error: Windows failed to start. A recent hardware or software change might have caused the issue after you install Windows Updates
The main problem is that you won’t boot into Windows and you will be stuck at this error message screen. In short, you will be inside a reboot loop as every time you restart your PC you will again face the same error message until you fix the issue. So without wasting any time let’s see how actually to Fix “Windows failed to start. A recent hardware or software change might be the cause” with the below-listed troubleshooting steps.
Table of Contents
Method 1: Run Startup/Automatic Repair
1. Insert the Windows 10 bootable installation DVD or Recovery Disc and restart your PC.
2. When prompted to Press any key to boot from CD or DVD, press any key to continue.
3. Select your language preferences, and click Next. Click Repair your computer in the bottom-left.
4. On choose an option screen, click Troubleshoot.
5. On Troubleshoot screen, click the Advanced option.
6. On the Advanced options screen, click Automatic Repair or Startup Repair.
7. Wait till the Windows Automatic/Startup Repairs complete.
8. Restart and you have successfully Fix Windows failed to start. A recent hardware or software change might be the cause, if not, continue.
Also Read: How to fix Automatic Repair couldn’t repair your PC.
Method 2: Boot into Last Known Good Configuration
Before going any further let’s discuss how to Enable Legacy Advanced Boot Menu so that you can easily get Boot Options:
1. Restart your Windows 10.
2. As the system restarts enter into BIOS setup and configure your PC to boot from CD/DVD.
3. Insert the Windows 10 bootable installation DVD and restart your PC.
4. When prompted to Press any key to boot from CD or DVD, press any key to continue.
5. Select your language preferences, and click Next. Click Repair your computer in the bottom-left.
6. On choose an option screen, click Troubleshoot.
7. On Troubleshoot screen, click the Advanced option.
8. On Advanced options screen, click Command Prompt.
9. When the Command Prompt(CMD) open type C: and hit enter.
10. Now type the following command:
BCDEDIT /SET {DEFAULT} BOOTMENUPOLICY LEGACY
11. And hit enter to Enable Legacy Advanced Boot Menu.
12. Close Command Prompt and back on the Choose an option screen, click Continue to restart Windows 10.
13. Finally, don’t forget to eject your Windows 10 installation DVD to get Boot options.
14. On the Boot Options screen, choose “Last Known Good Configuration (Advanced).”
Method 3: Perform a System Restore
1. Put in the Windows installation media or Recovery Drive/System Repair Disc and select your language preferences, and click Next
2. Click Repair your computer at the bottom.
3. Now, choose Troubleshoot and then Advanced Options.
4. Finally, click on “System Restore” and follow on-screen instructions to complete the restore.
5. Restart your PC to save changes and see if you can fix Windows failed to start. A recent hardware or software change might be the cause error.
Method 4: Run SFC and CHKDSK
1. Again go to command prompt using the method 1, click on command prompt in the Advanced options screen.
2. Type the following command in cmd and hit enter after each one:
sfc /scannow /offbootdir=c:\ /offwindir=c:\windows chkdsk C: /f /r /x
Note: Make sure you use the drive letter where Windows is currently installed. Also in the above command C: is the drive on which we want to check disk, /f stands for a flag which chkdsk the permission to fix any errors associated with the drive, /r let chkdsk search for bad sectors and perform recovery and /x instructs the check disk to dismount the drive before beginning the process.
3. Exit the command prompt and restart your PC.
Method 5: Rebuild BCD configuration
1. Using above method open command prompt using Windows installation disk.
2. Now type the following commands one by one and hit enter after each one:
bootrec.exe /FixMbr bootrec.exe /FixBoot bootrec.exe /RebuildBcd
3. If the above command fails, then enter the following commands in cmd:
bcdedit /export C:\BCD_Backup c: cd boot attrib bcd -s -h -r ren c:\boot\bcd bcd.old bootrec /RebuildBcd
4. Finally, exit the cmd and restart your Windows.
5. This method seems to Fix Windows failed to start. A recent hardware or software change might cause the error, but if it doesn’t work for you, then continue.
Method 6: Set Correct Boot Order
1. When your computer starts (Before the boot screen or the error screen), repeatedly press Delete or F1 or F2 key (Depending upon your computer’s manufacturer) to enter BIOS setup.
2. Once you are in BIOS setup, select the Boot tab from the list of options.
3. Now make sure that the computer Hard disk or SSD is set as a top priority in the Boot order. If not, use up or down arrow keys to set hard disk at the top, which means the computer will first boot from it rather than any other source.
4. Finally, press F10 to save this change and exit.
Recommended:
- Fix High CPU Usage By TiWorker.exe
- 10 ways to fix A disk read error occurred
- Fix High CPU Usage by svchost.exe (netsvcs)
- Fix High CPU Usage by RuntimeBroker.exe
That’s it you have successfully Fix Windows failed to start. A recent hardware or software change might be the cause, but if you still have any questions regarding this post, please ask them in the comment’s section.
Are you stuck at the “Windows failed to start. A recent hardware or software change might be the cause. To fix the problem.” screen? If you are at loss now, the fixes mentioned in this guide on MiniTool Website might help you out.
Windows Failed to Start Windows 10/11
Some of you might be unable to start Windows after a hardware or software change. As soon as it occurs, you will be stuck at the following error message screen and cannot boot into Windows.
Windows failed to start. A recent hardware or software change might be the cause. To fix the problem.
- Insert your Windows Installation disk and restart your computer.
- Choose your language setting, and then click “Next”.
- Click “Repair your computer”.
Some possible causes for why you are stuck at this screen might be:
- Corrupted BCD files.
- Damaged System Files.
- Virus and malware infections.
- Incompatible third-party software
- Incorrect boot order.
Suggestion: Back up Your System Before Hand
Now, your computer can boot up without error. To avoid having trouble in starting the computer once more, it is essential to create a backup of your system. When your computer crashes, you can use this backup image to restore your system to an earlier state.
Here, we recommend backing up your system with a piece of free backup software – MiniTool ShadowMaker. It allows you to create a backup for your systems, partitions, disks, folders and files. Meanwhile, this tool is also known for providing a one-click system backup solution for Windows devices, that is to say, you can back up your OS easily. To do so:
Step 1. Launch MiniTool ShadowMaker and go to the Backup page.
MiniTool ShadowMaker TrialClick to Download100%Clean & Safe
Step 2. In this page, you can choose the backup source and destination. As you can see in SOURCE, this program is set to back up your operating system by default, so you just need to choose a destination path for the backup image in DESTINATION (an external drive or USB flash disk is preferred).
Step 3. Click on Back Up Now to start the task immediately.
How to Fix Windows Failed to Start Windows 11/10?
Fix 1: Run Automatic Repair
When your system encounters issues like Windows failed to start Windows 10, you can use the inbuilt Automatic Repair feature. This feature will scan system files, registry settings, & configuration settings and fix the problem on its own.
Step 1. Press the Power button to power off your computer and reboot it several times when you see the Windows logo. Then, you will see the Automatic/Startup Repair screen.
Step 2. Press Advanced options to enter WinRE.
Step 3. Go to Troubleshoot > Advanced options > Automatic/Startup Repair. Then, this feature will start to deal with Windows failed to start Windows 10 for you.
Step 4. Once the process is complete, reboot your computer.
Fix 2: Rebuild BCD
BCD (also known as Boot Configuration Data) contains the files that the bootloader can find to boot Windows. Sometimes, BCD might be corrupted due to some reason, leading to Windows failed to start Windows 10/11. In this is the case, rebuilding BCD might do the trick.
Step 1. First, you need to create a bootable USB disk on another computer that works normally. Insert the Windows bootable recovery disk and reboot your computer.
Step 2. If prompted by Press any key to boot from CD or DVD, hit any key to continue.
Step 3. Choose your language preferences and click on Repair your computer from the lower left corner.
Step 4. Go to Troubleshoot > Advanced options > Command Prompt.
Step 5. Type the following command one by one and don’t forget to hit Enter after each command.
bootrec.exe /FixMbr
bootrec.exe /FixBoot
bootrec.exe /RebuildBcd
Step 6. If these commands fail, run the following command:
bcdedit /export C:\BCD_Backup
c:
cd boot
attrib bcd -s -h -r
ren c:\boot\bcd bcd.old
bootrec /RebuildBcd
Step 7. Quit Command Prompt and reboot your computer to check if Windows failed to start on startup is gone.
Fix 3: Run SFC & CHKDSK
Another method is to run SFC and CHKDSK in Windows Recovery Environment. Follow these steps:
Step 1. Boot your computer from the bootable recovery disk or reboot the computer three times to enter WinRE.
Step 2. Go to Troubleshoot > Advanced options > Command Prompt.
Step 3. Type sfc /scannow and hit Enter.
Step 4. After the process is done, run chkdsk C: /f /r /x.
Fix 4: Set Correct Boot Order
The bootloader will look for a set of files when Windows starts. If it cannot find the corresponding files, Windows will not load and you may be probably stuck on the Windows failed to start a recent hardware or software change might be the cause screen. Therefore, make sure that the OS drive is the first priority. Here’s how to set the correct boot order:
Step 1. Shut down your computer and reboot it. When pressing the power button to restart it, press Delete, F1, or F2 (depending on the manufacturer of your computer) to enter the BIOS setup.
Step 2. Go to the Boot tab > select Boot Device Priority > press Enter.
Step 3. Set the default bootable drive to HDD or SSD.
Step 4. Press F10 to save the changes and exit BIOS.
We Need Your Voice
That’s all the causes and solutions for why Windows failed to start after a recent hardware or software change. For more problems about our products, you can leave a comment below or send an email to [email protected]. Have a nice day!
Readers help support Windows Report. We may get a commission if you buy through our links.
Read our disclosure page to find out how can you help Windows Report sustain the editorial team. Read more
Some of our readers who recently complained about the Windows failed to start a recent hardware or software change might be the cause error need to know that this error is inevitable if there is any hardware or software change to your computer.
This error affects the regular boot process of your computer and, at times, causes data loss. This article will teach you how to fix the error.
Why do I encounter Windows failed to start after hardware or software change?
One of the major reasons could be that you have installed hardware or software which has triggered the error. Below are some other factors reported by some users:
- Corrupted BCD file – If you often experience power outages or there are disk write errors, it can cause your BCD file to become missing or corrupted, producing this issue.
- Corrupted or damaged system files – System file corruption or damage is a common cause of starting failures. Read about how to repair damaged system files here.
- Viruses and malware infections – Some viruses and malware may have affected the system files and triggered the error. Try one of the best antivirus software shortlisted in this article.
- Conflicting third-party programs – Some readers claim the error occurred after installing a program that wasn’t compatible with one of the resident apps. Consider using one of these best uninstaller software to remove them.
- Problems with connected devices – This error can manifest due to a conflict with an attached external device. Disconnect them and then reconnect them individually to know which is causing the issue.
Now that you know some of the potential reasons behind this issue, you can work your way through any of the fixes provided in this article.
What can I do if Windows failed to start due to hardware or software change?
It may be worth a simple fix for you if you consider performing the following preliminary checks:
- Disconnect all peripheral devices such as a printer, scanner, camera, or any other USB devices (if any) except for your mouse and keyboard, which you’ll need for navigation.
- Check the storage drive for any damage or connection problems.
- Boot into Safe Mode. You may try these fixes if Windows refused to boot into Safe Mode.
Having confirmed the above checks and the problem persists, you can explore the advanced solutions provided below.
1. Run the Automatic/Startup Repairs
- Insert Windows bootable installation DVD or Recovery Disc and restart your PC.
- After getting the prompt to Press any key to boot from CD or DVD, click on any key to continue.
- Choose your language preferences and click on Next and then, click on Repair your computer.
- In the next section, choose Troubleshoot.
- Click on Advanced options on the Troubleshoot screen.
- Then, select Automatic Repair or Startup Repair.
- Wait for Windows to complete the Automatic/Startup Repairs.
As soon as the process is complete, restart your PC for the fix to take effect. Now, check if the problem is fixed. If it persists, try the next fix.
2. Rebuild BCD Configuration
- Follow steps 1-5 in the method above and click on Command Prompt while using your Windows installation disk.
- Type the following commands one after the other and press Enter after each:
bootrec.exe /FixMbr
bootrec.exe /FixBoot
bootrec.exe /RebuildBcd
- Then, exit Command Prompt and restart Windows.
Rebuilding BCD has been reported by several users to have proved a potential fix for the Windows failed to start a recent hardware or software change might be the cause error.
- ERROR_CANT_ENABLE_DENY_ONLY: 5 Ways to Fix
- ERROR_REGISTRY_QUOTA_LIMIT: 5 Steps to Fix
- ERROR_NO_CALLBACK_ACTIVE: 6 Tested Fixes
- ERROR_BAD_DLL_ENTRYPOINT: How to Fix It Step-by-Step
3. Run SFC and CHKDSK Scans
- Insert your Windows booting media and restart your PC.
- Choose your language preferences and click on Next and then, click on Repair your computer.
- Select Troubleshoot.
- Click on Advanced options.
- Now select Command Prompt.
- Type the following command line and hit Enter:
sfc /scannow
- Then type the following and hit Enter:
chkdsk C: /f /r /x
- Now, exit the command prompt and restart your PC.
You can try running the SFC and CHKDSK scans, as they will search for bad sectors and perform recovery on them.
Alternatively, you can clearly repair this kind of error on Windows with a dedicated optimizing tool that will scan and fix corrupted files that result in Windows failed to start errors.
4. Perform a System Restore
- Insert Windows bootable installation media and restart your PC.
- After getting the prompt to Press any key to boot from CD or DVD, click on any key to continue.
- Choose your language preferences and click on Next and then, choose the Repair your computer option.
- Click on System Restore and follow the on-screen prompts to complete the restore.
- Restart your PC to effect the changes made.
Another helpful way to fix computer problems is by using the built-in System Restore feature in Windows.
You should be able to fix the issue after working your way through the provided fixes in this article.
Similar to this error is the UNetbootin Windows Failed to Start and Windows didn’t load correctly. You can check how to fix them using our detailed guides.
If you have any questions or suggestions, do not hesitate to use the comments section below.
Vladimir Popescu
Being an artist his entire life while also playing handball at a professional level, Vladimir has also developed a passion for all things computer-related.
With an innate fascination for research and analysis, and realizing many other people share his passion for this subject, he delved into writing Windows-related articles, so other people can also benefit from the acquired information.
When not writing kick-ass articles, Vladimir likes to spend his time doing Crossfit and creating art.
After installing new hardware, drivers, software updates, or Windows upgrades, you might encounter the following error when attempting to boot your computer:
"Windows failed to start. A recent hardware or software change might be the cause."
This is a common startup error that typically occurs on Windows 11/10 and Windows Server computers. When this error appears, your computer will be unable to boot, leaving you stuck with this message. It’s worth noting that this issue can affect laptops from various brands, such as Dell, HP, Lenovo, Asus, and Acer.
If you find yourself facing this error, there’s no need to panic. It is fixable, and you can resolve it by following some troubleshooting steps.
Understanding Windows failed to start. A recent hardware or software change might be the cause.
The above error message usually appears on a blue or black screen before the system startup. Additionally, it may display an 8-digit hexadecimal error code such as 0x000000. This particular error is commonly referred to as the “blue screen of death” or “black screen of death,” and resolving it requires some basic troubleshooting skills.
Cause:
Here is a list of common reasons that can trigger the error mentioned above. Understanding these potential causes will help you identify what might be wrong with your computer:
- Recent Hardware or Software Change: This is one of the most common reasons for encountering the above error. Have you recently installed or made changes to your computer’s hardware, such as RAM, HDD/SSD, Processor, or Motherboard? If yes, the appropriate driver might not have been loaded correctly, leading to the error message.
- Corrupted Master Boot Record: The Master Boot Record (MBR) is a critical file for the Windows operating system. It instructs your computer to verify hardware, software, and drivers before launching the OS. If this file becomes corrupted, Windows may fail to start, triggering the “Windows failed to start” error.
- Corrupted or Missing System Files: Incompatible drivers, software installations, or virus/malware attacks can cause some system files to go missing or become corrupted, preventing your computer from booting up properly.
- Incomplete Installation of Windows Updates/Upgrades: Improperly shutting down your computer during an update installation or Windows upgrade can also lead to the above error.
- Faulty cable connection: If the cable connection between hard drive and motherboard is faulty, you may receive the above error.
These are some of the common causes that can prevent Windows 11/10 from loading correctly, resulting in startup issues. To resolve the “Windows failed to start” error, you can apply the troubleshooting methods mentioned below.
How to Fix “Windows failed to start. A recent hardware or software change might be the cause.”
Prior to resolving any critical error that involves the risk of data loss, it is crucial to follow a safety measure and back up your valuable data, including pictures, videos, files, documents, and emails to a secure location. In the event of a system crash, you can rely on the EaseUS Data Recovery Wizard to recover data from the affected OS.
Important Notice:
Before attempting any critical fixes on your Windows OS, it’s crucial to recover and store your data in a safe place. [icon name=”recycle” prefix=”fas” class=”c-green”] EaseUS Data Recovery Wizard comes to the rescue for recovering data from a crashed PC.
No matter if you’re facing the dreaded blue screen of death, startup failures, or boot problems, this tool enables you to boot up your PC and recover your precious data effortlessly. So, be sure to use EaseUS Data Recovery Wizard to safeguard your files before proceeding with any fixes!
Note: Free Version allows you to recover upto 2GB Data.
Solution 1: Repair corrupted MBR or BCD
Repairing the Master Boot Record (MBR) or Boot Configuration Data (BCD) should be your primary approach when addressing Windows startup issues. The MBR or BCD is a vital file, and its corruption is often the root cause of startup problems. To fix this issue, you will require a Windows installation drive or disk.
For a convenient solution, we recommend using EaseUS Partition Master, which is an excellent tool for repairing a corrupted MBR file. This user-friendly tool conducts comprehensive scans and applies necessary fixes to troubleshoot your Windows startup problems effectively.
Repair MBR/BCD using EaseUS Partition Master
Download EaseUS Partition Manager
Resize/Extend Partition
Clone/Migrate HDD/SSD
Convert between GPT/MBR/NTFS/FAT32
All-in-One Disk Management System
Safe & Secure
65 Million Users
99.7% Success Rate
Excellent Trustpilot Rating
TrustScore:4.7
Review:14.5K
[lightweight-accordion title=”Repair MBR using EaseUS” bordered=true]
Step 1: Create Bootable USB drive using EaseUS. Launch EaseUS Partition Master, and click “Bootable Media” on the toolbar. Select “Create bootable media”.
Step 2: Boot your PC using Bootable USB Drive.
Step 3: Click “Toolkit” and choose “Rebuild MBR”.
[/lightweight-accordion]
Repair MBR/BCD Manually
[lightweight-accordion title=”Manually Repair MBR file – Step by Step” bordered=true]
Step 1: Boot your PC using the Windows Installation media. It will open Windows Installation Wizard. Click Next.
Step 2: Select Repair your computer.
Step 3: It will open the Advanced Startup Option or Windows Recovery Environment. Click on the Troubleshoot.
Step 4: Select Command Prompt.
Step 5: Type the following command and press Enter to execute it.
bootrec /fixmbr
bootrec /fixboot
bootrec /RebuildBcd
Step 6: Now restart your computer, and you will not see the boot time error message Bootmgr is missing.
[/lightweight-accordion]
Solution 2: Run SFC, CHKDSK, and DISM command
These three sets of commands encompass the entire process of repairing your computer.
- First, the SFC (System File Checker) command repairs any corrupted system files.
- Next, the CHKDSK (Check Disk) command identifies and resolves issues with bad sectors and errors on your hard drives.
- Lastly, the DISM (Deployment Image Service and Management Tool) command handles the repair of Windows images.
To tackle a Windows startup issue, you’ll need to run these commands within the Advanced Recovery Environment, ensuring a comprehensive approach to troubleshooting and resolving the problem.
[lightweight-accordion title=”Run SFC, CHKDSK, DISM command” bordered=true]
Step 1: Boot your PC using the Windows Installation media. It will open Windows Installation Wizard. Click Next.
Step 2: Select Repair your computer.
Step 3: It will open the Advanced Startup Option or Windows Recovery Environment. Click on the Troubleshoot.
Step 4: Select Command Prompt.
Step 5: Now run the following commands one by one.
i. System File Checker tool
sfc /scannow
ii. Run Dism command
Dism /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /RestoreHealth
iii. Run Disk checking utility.
chkdsk C: / f / x / r
[/lightweight-accordion]
Solution 3: Revers the Installation of Recent Drivers/Software
If you identify that this error has started to occur after installing a driver or softwares, you need to uninstall the recently installed drivers and softwares. You can do it as follows:
Use Safe Mode
To determine if the issue is caused by third-party software or drivers, try booting your computer in Safe Mode. Safe Mode loads a minimal set of drivers and services, allowing you to isolate the problem.
[lightweight-accordion title=”Open PC in Safe Boot Mode” bordered=true]
Step 1: Boot your PC using the Windows Installation media. It will open Windows Installation Wizard. Click Next.
Step 2: Select Repair your computer.
Step 3: It will open the Advanced Startup Option or Windows Recovery Environment. Go to Troubleshoot
Step 4: Select Advanced options
Step 5: Select Startup Settings
Step 6: Click on Restart button to enable safe mode.
Step 7: Once you boot your computer in Safe mode, uninstall the recently added games, drivers, and softwares.
[/lightweight-accordion]
Fix using EaseUS Partition Master tool
If your computer fails to open in Safe Mode, consider using a reliable professional tool like EaseUS Partition Master. This versatile tool enables you to create a WinPE bootable USB drive, which can be utilized to repair Windows.
Copy OS and data to another HDD/SSD
Convert MBR to GPT for Windows 11 upgrade
Convert to NTFS/FAT32
Repair File System/Windows Startup error
Create/Delete/Resize/Move/Format/Wipe/Extend/Merge Partition
Create WinPE Bootable Disk
65M Users
99% Disk Management
12K Downloads/Day
4.7 TrustPilot Rating
Windows 11/10/8/7 & Server 2022/2019/2016/2012/2008/2003
The WinPE bootable device functions as a lightweight Windows installation tool, enabling you to launch the operating system from the USB drive and perform essential troubleshooting steps to resolve the issue. This approach provides a convenient and effective solution for tackling challenging startup problems.
[lightweight-accordion title=”Create WinPE Bootable Drive using EaseUS Partition Master” bordered=true]
Step 1: Insert 8GB+ USB flash drive to computer.
Step 2: Launch EaseUS Partition Master and go to Toolkit → Win 7/8/10/11 ISO.
Step 3: Browser your ISO file and click Next.
Step 4: Select your USB drive and click on Start button to create Bootable Windows 11/10/8/7 and Windows server USB drive.
[/lightweight-accordion]
Solution 4: Uninstall Recent/Incomplete Windows updates
Let me clarify that an incomplete installation of Windows updates can also lead to the “Windows failed to start” error. To resolve this issue, you must remove the recent Windows updates that may be causing the problem.
[lightweight-accordion title=”Uninstall Updates – Step by Step” bordered=true]
Step 1: Open the Advanced Startup Option or Windows Recovery Environment. Click on Troubleshoot.
Step 2: Go to the Troubleshoot ➜ Advanced options ➜ Uninstall Updates.
Step 3: Select Uninstall the latest quality update.
Step 4: click on the Uninstall quality update button and remove the updates.
[/lightweight-accordion]
Solution 5: System Restore
Another effective approach to fix the “Windows failed to start” error is by performing a System Restore. When you initiate a System Restore, Windows reverts to a previous known good configuration state, undoing recent changes made to your computer. This method serves as an excellent way to reverse any alterations that might have triggered the startup issue, providing a reliable solution to get your system back on track.
[lightweight-accordion title=”System Restore – Steps by Steps” bordered=true]
Step 1: Open the Advanced Startup Option or Windows Recovery Environment. Go to the Troubleshoot ➜ Advanced options ➜ System Restore.
Step 2: Click Next and then Select Date.
Step 3: Click on Finish to start Restoring process.
[/lightweight-accordion]
Summary
Encountering the “Windows failed to start. A recent hardware or software change might be the cause” error is a daunting situation for any Windows user. Resolving this issue may demand step-by-step troubleshooting, and it requires patience. While some fortunate users might fix the error with a single solution, others may need to try multiple approaches to find the right fix. In either case, staying persistent and following a systematic troubleshooting process will eventually lead to resolving the problem and getting your system back up and running smoothly.