Fix HIDCLASS.sys failed Blue Screen Error

Windows has a lot of built-in tools that help you fix tons of system-related issues. One of them is the System File Check which is the tool you can use to conveniently replace potentially corrupted or missing system files with good ones. But what happens when it does not work? Well, you’ve come to the right place as in this post, you will be guided on how you can replace a corrupted single Windows system file manually with a known good copy of the file if the System File Checker scan is not working. When you encounter this issue with the System File Checker, it will be unable to replace the corrupted system files and returns an error message instead. And so to fix and replace corrupted system files in your Windows 10 computer without the help of System File Checker, you can refer to the instructions provided below. Step 1: First, you need to open the log files listed below and identify which particular file has been corrupted:

• %userprofile%Desktopsfcdetails.txt
• Log %WinDir%LogsCBSCBS.log

Step 2: You will see all the details on the given log files. Once you find out the name and the path of the file, you have to take ownership of this corrupted system file. Step 3: To take ownership of the corrupted file, you need to pull up Command Prompt by tapping Win + R keys on your keyboard and then type “cmd” and tap Enter. Step 4: After opening Command Prompt, type and enter the command below to execute it:

takeown /f FileNameAndPath

Note: In the given command, “FileNameAndPath” represents the name and the path of the corrupted file. For instance, the corrupted file is named “wuapi.dll”, then you need to type “takeown /f C:/Windows/System32/wuapi.dll” Step 5: Next, you need to grant administrators full access & control to the corrupted file and you can do that via Command Prompt again. Step 6: In the elevated Command Prompt, type and enter the following command to execute it:

icacls FileNameAndPath /GRANT ADMINISTRATORS:F

Note: We’re going to use the wuapi.dll again as an example. So the command should be like this: icacls “C:/Windows/System32/wuapi.dll /grant administrators: F”. Step 7: Now all that’s left to do is replace the corrupted system file with a good copy from a trusted source. Once you have a copy, open an elevated Command Prompt again and execute the following command:

copy NewFileLocation FileNameAndPath

Note: In the command given above, the “NewFileLocation” is the location where you have saved the copy of the file. For instance, if you’ve saved it on your desktop, this is how it should look: “copy C:/Users/<username>/Desktop/wuapi.dll C:/windows/system32/wuapi.dll”

First time when your computer is turned ON and when Windows is booting it will wait 10 seconds before starting your startup applications. This 10 second is used to load all of Windows services so everything is running smoothly. If by any chance you do not want to wait for this startup delay and wish to start applications right away then keep on reading and follow this guide precisely. This guide will require you to play ad tweak with the registry of Windows, it is always recommended to make a registry backup before attempting any tweaks. Also, it is imperative to follow the guide as it is presented step by step. be aware that this guide will eliminate a 10-second delay for all of your starting applications, there is no way currently to remove delay for only one or a few.

1. Press ⊞ WINDOWS + R to open the run dialog
2. In run dialog type Regedit and press ENTER
3. Locate HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Serialize
4. If the key does not exist, make a new one,  Go to HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\, right-click on the explorer and choose new > key. Name it Serialize
5. Right-click on Serialize and choose New > DWORD (32-bit) Value
6. Name the value StartupDelayInMSec
7. Double click on StartupDelayInMSec and locate Value data
8. Set the value to 0
9. Save changes and Exit Registry editor
10. Reboot

If you want to reverse changes and enable delay again, go back to the Registry Editor and delete the StartupDelayInMSec value.

Could not connect to the System Event explanation: Although logging into a Windows 10 computer may seem like a simple process, it’s actually not since the Windows operating system has built a mechanism in a way that any third party or malware intervention would not compromise access to the system. This mechanism is supported by numerous services, functions, and DLL files. And Microsoft has been taking this security to a whole new level with the introduction of Windows Hello. Recently, a number of users reported getting the “Windows could not connect to the System Event Notification Service service. Please consult your system administrator” error when logging into their computers. While some users also reported that although they can log in, they encounter the same error message from the Notification area. There are several options you can check out to resolve the error. You have to check the status of several Windows Services and make sure that they are running. You also have to reset Winsock as well as run the System File Checker scan.

Option 1 – Check for certain Windows Services

• First, you need to tap the Win + R keys on your keyboard to open the Run dialog box.
• Next, type “services.msc” in the field and click OK or tap Enter to open the Windows Services Manager.
• After that, you will see a list of services and from there, look for the following Windows Services:
  • DHCP Client
  • System Event Notification Service
  • Windows Font Cache Service
• Now make sure that the Startup Type of each service is started and running.

Option 2 – Try resetting the Winsock drivers

• In the Start Search, type “command prompt” and right-click on Command Prompt from the search results, and then select the “Run as administrator” option.
• After opening Command Prompt, execute this command: netsh winsock reset

Note: If you are using IPv4, execute the “netsh int ipv4 reset” instead. On the other hand, if you are using IPv6, execute the “netsh int ipv6 reset”

• Now exit Command Prompt and see if the error is now fixed.

Option 3 – Try running System File Checker or SFC scan

You could also run System File Checker or SFC scan to fix the BSOD error. It is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

• Reboot your PC.

Error Code 0x80072efe - What is it?

Error Code 0x80072efe is a fairly common error code that generally occurs in Windows 10. It is most often associated with the process of performing updates using the Windows Update tool.

Common symptoms include:

• Inability to install or complete updates on your Windows machine
• Computer freezing as programs are run or started
• Inability to perform installations of downloaded programs
• Programs crashing or failing to work properly

While Error Code 0x80072efe can cause a number of frustrating issues on your device, the good news is that there are several methods that can be used to fix this error. The two most common methods are actually fairly easy to perform and do not require advanced tools or knowledge. However, if you don’t feel like you will be able to perform the necessary steps on your own, be sure to get in touch with a qualified computer repair technician to help you in the resolution of this particular error.

Solution

Error Causes

Two things are generally behind the appearance of Error Code 0x80072efe on a Windows device. The first is that one or more of your registry keys are not available, have been corrupted, or are not installed properly. The second is that necessary DLL files aren’t working properly within your machine.

However, other things can mimic these causes, which is why the two methods listed below will resolve the issue in most cases.

Further Information and Manual Repair

Fortunately, there are two resolution methods that can be used quickly and easily when Error Code 0x80072efe arises on your Windows computer. Neither of these requires advanced knowledge or skill, but if you don’t feel comfortable with performing these steps on your own, it is recommended that you contact a qualified computer repair technician in order to get assistance.

Here are the best ways to resolve Error Code 0x80072efe on your computer:

Method One:  Check Your Time and Date Settings for Accuracy

If your time or date has been set incorrectly, it can make your system logs appear to have incorrect information, which can lead to the appearance of Error Code 0x80072efe. Because this is the easiest thing to fix if it is indeed the problem that is making the error code appear, this should always be the first thing that you try when this error code arises.

In order to check your time and date settings, follow these simple steps:

• Step One: Make sure that you are logged into your computer as an administrator.
• Step Two: Click on the time and date listed on the lower right edge of your screen. If the settings are not correct, choose the option to change the time and date.

If method one has not successfully resolved Error Code 0x80072efe, you may need to attempt method two.

Method Two:  Check Your Firewall Settings During Updates

In some cases, your firewall can prevent your machine from accessing the information that it needs in order for the installation or update to go through correctly. If that is the case, you can follow a few simple steps to turn off your firewall, just while you install the update, and then turn it back on.

In order to do so, follow these steps:

• Step One: In the Start menu, choose the option to open the Control Panel.
• Step Two: Select the option for System and Security, looking for and clicking on Windows Firewall.
• Step Three: Turn off any private network firewalls.
• Step Four: Reboot your computer to apply the changes that you have made.
• Step Five: Re-attempt to run your Windows Update.

Note that if this method allows you to successfully bypass the error code, you’ll need to make sure to turn the firewall back on when you are finished. Even though it can interfere with the Update process, your firewall is still very important to your computer.

Method Three: Use An Automated Tool

If you wish to always have at your disposal a utility tool to fix these Windows 10 and other related issues when they do arise, download and install a powerful automated tool.

There are times when system files get corrupted and if the Windows Update process finds the system’s integrity questionable, chances are, the update, upgrade or the installation may fail and you will only be getting an error code 0x80073712 instead of completing the process. The error code 0x80073712 indicates that a file needed by the Windows setup or the Windows Update is most likely missing or damaged. To resolve the problem, here are some suggestions you can try.

Option 1 – Try running the DISM Tool

Running the DISM Tool helps in repairing the Windows System Image as well as the Windows Component Store in Windows 10. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt as admin.
• Then type in this command: exe /Online /Cleanup-image /Restorehealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

After you run this tool, a log file is created at C:WindowsLogsCBSCBS.log. On the other hand, if the Windows Update client is already broken, you will be prompted to use a running Windows installation as the repair source or use a Windows side-by-side folder from a network share, as the source of the files. Although the chances of this happening are less, if it turns out to be the case, you need to run an advanced command in the DISM tool to repair a broken Windows Update. Just repeat the process above but use the following command instead:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:RepairSourceWindows /LimitAccess

Option 2 – Try running the System File Checker

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files that might be causing the error 0x80073712. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

Option 3 – Try running the Chkdsk utility

You can also try running the Chkdsk utility to resolve the Windows Update error 0x80073712. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the Chkdsk utility comes in. The Chkdsk utility repairs hard drive errors that might be causing the problem.

• Open Command Prompt with admin privileges.
• After opening Command Prompt, execute the commands listed below, and don’t forget to hit Enter right after you type in each one of them and if you have installed Windows to some different directory, you must replace “C” with the name of the drive you’ve installed Windows with.
• chkdsk C: /r /x
• chkdsk C: /f

Note: The Chkdsk function might take a while before it finishes its operations so you need to be patient and wait until the entire process is completed.

Option 4 – Try running the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows Update error 0x80073712. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button.

Option 5 – Try running Microsoft’s online troubleshooter

You also have the option to run Microsoft’s online troubleshooter which could help you fix Windows Update errors.

The latest security vulnerability was discovered inside both Windows 10 and Windows 11 letting any user access admin privileges inside the operating system. This can, of course, be used by a potential attacker to get full control of the system. The problem lies in Microsoft's security rules assigned to the Windows Registry and the Security Account Manager. Both for some reason have reduced restrictions allowing any local user to fully access the files without administrator privileges. The problem is even more amplified if we think about Security Account Manager which includes all account data including the passwords of all users using the same PC. This can provide a potential attacker with all information and let them log on into the administrator account for full control. Microsoft is aware of the matter and is tracking it with code CVE-2021-36934, and includes a complete workaround for the issue, which includes restricting access to  %windir%\system32\config and deleting any restore points or Shadow volumes that were created before that point until the hole is plugged with an official security patch.

Stop 0x0000000A - What is it?

Stop 0x000000A is a type of blue screen of death error associated with Windows XP. It occurs either during or after the installation of Windows XP. In other cases, the stop 0x000000A error may occur when the device driver uses an incorrect memory address, causing an IRQ conflict. The Stop 0x000000A error message means that a process or a driver attempted to access a memory section without permission.  The stop error message is displayed in the following format:

Stop: 0x0000000A (parameter1, parameter2, parameter3, parameter4) IRQL_NOT_LESS_OR_EQUAL *** Address x has base at x - filename

Solution

Error Causes

The stop 0x000000A error is triggered due to multiple reasons. These include:

• Faulty hardware
• The poor device driver installation
• Incompatible device driver
• Viruses and malware attack
• Disk fragmentation

Blue screen of death errors like the stop 0x000000A error code is critical. These errors may pose serious PC threats. When this error occurs the computer screen turns blue, the program running on the system stops and if the error is not fixed in time it may also result in a system crash and failure.

Further Information and Manual Repair

To resolve the Stop 0x000000A error on your PC, here are some solutions that you can try:

1. Roll Back Drivers

To do this, click on the start button and go to the control panel. Then double click the system icon and locate the ‘System Properties’ window. After that click on the ‘hardware’ tab and then click the ‘Device Manager’ button. Here locate the device that you recently updated which could be causing the IRQ conflict. Now double click the device recently updated and click the driver tab. Then click on the ‘Roll Back Driver' button. Wait for the process to finish and then simply reboot your system.

2. Specify the Hardware Abstraction Layer (HAL)

Another method to resolve the Stop 0x000000A error on your system is to specify the hardware abstraction layer (HAL). This can be done during Windows XP installation startup. Simply press the F5 button on your keyboard while the “Setup is inspecting your computer’s hardware configuration’. When prompted, make sure that you specify the correct computer type and HAL (the Hardware Abstraction Layer). Most computers use a single processor, if your computer also has a single processor then simply select ‘Standard PC HAL’ computer type from the menu. Now reboot your PC and then reinstall the Windows XP operating system. If the error is still not resolved then try turning off features in CMOS settings

3. Turn off Features in CMOS Settings

Turn off all the following features in the CMOS settings:

• All caching, including L2, BIOS, internal/external, and write back caching on disk controllers
• Plug and Play
• All shadowing
• Any BIOS-based virus protection feature

After turning off these features, try reinstalling Windows XP again. If this works, then that’s great! However, if it doesn’t, then try method 4; maybe the cause of the stop 0x000000A is associated with incompatible drivers.

4. Install Windows XP compatible Drivers

Sometimes device driver compatibility can also shoot up the stop 0x000000A error message. First, remove the drivers that are incompatible with Windows XP. Now obtain and install new Windows XP compatible drivers. To do this, go to the start menu and the control panel. Now double click on Add or Remove Programs icon. Select the drivers that are incompatible with Windows XP and click on the remove button. After that restart PC and install Windows XP, compatible drivers, for the hardware devices on your system.

5. Scan for Viruses and Repair the Registry

If all the methods discussed above do not resolve the stop 0x000000A error on your PC, then it means either your computer is affected by an infection virus or the problem is associated with the registry like disk fragmentation and invalid entries. To scan for both viruses and registry issues simultaneously in seconds, it is advisable to download Restoro. Restoro is an advanced and multi-functional PC repair tool integrated with powerful utilities including a registry cleaner, antivirus, and a system optimizer. It also scans for Active X controls and class ID errors. The registry cleaning utility scans your entire PC for all possible registry issues triggering different error codes including the stop 0x000000A error. It wipes out all the unnecessary files cluttering and damaging the registry including cookies, temporary files, junk files, and invalid entries. It repairs the fragmented disk and the registry thereby resolving the stop 0x000000A error on your system. The privacy error utility functions like an antivirus. It detects all kinds of malicious software on your system including malware, adware, spyware, and viruses. These are removed immediately thus making your PC error-free. Restoro is safe, efficient, and user-friendly. It is compatible with all Windows versions including XP.  It has a sophisticated interface and a neat layout which makes it quite easy to operate and workaround. Click here to download Restoro and repair your PC and resolve the stop 0x000000A error code now!

As you know, each one of the Windows 10 versions is priced differently and one of the considered more expensive compared to the Windows 10 Home version is the Windows10 Pro. The good thing is, Microsoft allows its users to upgrade from the Windows 10 Home version to the Windows 10 Pro version at a reasonable cost instead of buying the entire license again. However, upgrading your Windows 10 computer is not always that easy and you might encounter some errors along the way. One of the reported errors you could encounter is an error message that says, “Something happened, and we couldn’t start the upgrade”. This kind of problem is due to the problems with the Microsoft Store or the key authorization and to fix it, there are several options you can check out. You can try to run the built-in troubleshooters such as the Windows Update troubleshooter, Windows Store Apps troubleshooter, or Microsoft Accounts troubleshooter. You could also try to reset the Windows Store cache or re-register the Windows Store app. For more details, refer to each one of the given options below.

Option 1 – Try to run the Microsoft Accounts troubleshooter

Since the Microsoft Accounts troubleshooter is not built-in into the Windows operating system, you can download this troubleshooter by clicking on this link.

Option 2 – Try running the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the “Something happened, and we couldn’t start the upgrade” error. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 3 – Run the Windows Store App troubleshooter

The Windows 10 Store Apps Troubleshooter will help you in fixing the problem in Microsoft Store. This is a great built-in tool from Microsoft that helps users fix any app issues. To use the Windows Store Apps Troubleshooter, follow the steps below.

• Tap Win + I keys again to open the Windows Settings panel.
• Go to Update & Security and then go to Troubleshoot.
• Under the Troubleshoot section, on your left-hand side, scroll down to find Window Store Apps.
• Then click on the Run the troubleshooter option and follow the on-screen instructions and then see if it fixes the problem.

Option 4 – Try to reset the Microsoft Store cache

As you know, like any other apps, Microsoft Store also caches as you view apps and games so it is most likely that the cache is no longer valid and must be removed. To do so, follow the steps below.

• Right-click on the start button and click on Command Prompt (administrator).
• Next, type in the command, “wsreset.exe” and tap Enter. Once you do, the command will clear the cache for the Windows Store app.
• Now restart your PC and afterward, try opening Microsoft Store again and then try to install your app or update your computer again.

Option 5 – Try to re-register the Microsoft Store app via Windows PowerShell

• Tap the Win + X key combination or right-click on the Start button and click on the Windows PowerShell (Admin) option.
• If a User Account Control or UAC prompt appears, just click on Yes to proceed and open the Windows PowerShell window.
• Next, type in or copy-paste the following command to re-register the Microsoft Store app and tap Enter:

powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRootWinStoreAppxManifest.xml

• Wait for the process to be completed and then restart your computer.

Option 6 – Try contacting Microsoft

If none of the options worked, you might also want to contact Microsoft for further assistance in fixing the error.

Kernel_Data_Inpage_Error - What is it?

Kernel_Data_Inpage_Error is a BSOD (blue screen of death) error. Also, know as a 0x0000007A Stop error. This bug check indicates that the requested page of kernel data from the paging file failed to be read into memory. In simple words, this means that Windows has trouble reading from the memory. This can apply to both kinds of memory: stored memory on your hard drive and also the dynamic memory in your RAM. The Kernel_Data_Inpage_Error turns your computer screen all blue, stops the program being executed, and sometimes even leads to abrupt system shut down.

Error Causes

Kernel_Data_Inpage_Error may occur due to numerous reasons. The exact cause of this error can easily be found by going through the code displayed in the parameter of 0x00000007A. Let’s take a look at Kernel_Data_Inpage_Error parameter codes and the underlying causes of its occurrence:

• 0xC0000009A- This parameter code triggers missing nonpaged pool resources
• 0xC0000009C- This represents the installed hard disk drive has bad sectors.
• 0xC0000000E- This indicates a hardware failure or an incorrect drive configuration

Further Information and Manual Repair

No matter what the cause for Kernel_Data_Inpage_Error may be, it is advisable to fix it immediately as blue screen of death error codes are considered to be critical PC errors that can cause serious damages and even result in valuable data loss. Here are a couple of ways to repair this issue on your system:

1. Call the ‘Chkdsk’ (check disk) command on your system.

Windows XP, Vista, and 7 users can call this command, by pressing Windows Key +F and type in ‘chkdsk’ and run. However, you can’t run it while actively using Windows but you can always schedule it to start automatically the next time your computer turns on. Wrap up what you need and then reboot. Chkdsk disk checking process can take a long time, especially on large and slow hard drives. To run this command on Windows 8, open Windows search by pressing Windows Key+ F and then type ‘cmd’. Then right-click on the command prompt and choose the option ‘Run as Administrator’. To continue with the disk checking process, here you will be prompted to provide your administrator authentication. Once you insert the administrator authentication, type the command ‘Chkdsk C:/f/r/x” where the letter ‘C’ indicates the drive you want to examine and repair. Run it to scan for Kernel_Data_Inpage_Errors on your system. Chkdsk command will detect and repair errors on the hard drive and then automatically reboot.

Limitations to this Solution:

‘Chkdsk’ is a value-adding inbuilt disk checking tool in PC new Window versions; nonetheless, this command has certain limitations. It is time-consuming. You may have to wait for a long time for it to scan your system. Also when disk check is running, you will have to stop all other activities on your system. Furthermore, Chkdsk does not scan and fix all registry errors and other PC-related errors. So, you can’t be 100% sure that it will resolve all the Kernel_Data_Inpage_Errors on your PC.

Today we will be solving the Device not found 3F0 error which is a common error, especially among HP (HP Pavilion G6), Lenovo, Acer, and Dell laptops/desktops. This error occurs when the computer is turned ON and when the system is about to boot. It can happen on windows 7,  8, or 10. When a mentioned error occurs one of the following messages will be displayed on your screen:

• “No bootable device – insert boot disk and press any key”
• “No Boot Device Found. Press any key to reboot the machine”
• “Boot Device Not Found. Please install an operating system on your hard disk. Hard Disk (3FO)”
• “No boot device is available”

The most common reasons for 3F0 error to occur is:

• Using the unbootable device or disk to boot from.
• If the bootable hard drive you are using might have corrupted or damaged somehow.
• MBR or boot sector is damaged on the bootable hard drive.
• If your system has gone through a virus or malware attack.
• The wrong boot order in the BIOS.
• Hard disk connection problem.
• System files or boot files unknowingly damaged.
• Corrupt hard drive partitions.

This is well, the most simple solution and the easiest one, try to change the boot sequence in the BIOS settings of your motherboard. Sometimes most easier solutions can provide great results and solve our problems. If sadly this fails and the issue persists move to the next solution.

2: Perform a Hard Reset

---

Performing hard reset can often solve issues, to perform a hard reset do the following:

• Turn off the computer and unplug the power adapter. If there is a removable battery, it should also be removed.
• Then disconnect all peripherals, including the removable hard drive, etc.

then

• Press and hold the power button for 15 seconds to drain all remaining power.
• Insert the battery, and then re-plug the AC adapter into the laptop.
• Press the power button to turn on the computer.
• Once the computer starts up properly and the startup menu appears, use the arrow keys to select “Start Windows normally” and then press Enter.

Reconnect everything back of your peripherals. If by any chance problem still persists follow the next step:

3: Test Hard Drive Using HP Diagnostic Tool

---

Use the built-in tool in the Hp device to solve the issue:

• Turn on your computer and keep pressing the Esc key until the menu appears on the screen.
• Next, press the F2 key.
• Choose the Components Tests option from the HP PC Hardware Diagnostics menu.
• Select Hard Drive from the Component Tests menu.
• Click on the Quick Test, then click on the Run once button.
• If there are still any issues with your hard drive, then run the Extensive Test.

4: Restore BIOS Default Settings

---

• Press the Power button to start the computer, and immediately after this, repeatedly press the F10 key to enter the BIOS setup menu.
• To load and restore BIOS Setup Default settings, press F9 on the BIOS setup menu.
• Once loaded, press F10 to Save and Exit.
• Select yes, and then press Enter when it says Exit Saving Changes.

5: Reconnect Your Hard Drive

---

• Turn the computer off and remove the power cable.
• If you have a removable battery, take it out
• Disconnect your hard drive and then connect it back.
• Reassemble your computer and turn the computer on to see if it fixed the issue.

6: Fix and Rebuild Damaged MBR

---

• Boot from the original installation DVD (or the recovery USB)
• At the Welcome screen, click Repair your computer.
• Choose Troubleshoot.
• Choose Command Prompt.
• When the Command Prompt loads, type the following commands: bootrec /FixMbr bootrec /FixBoot bootrec /ScanOs bootrec /RebuildBcd.

7: Fix Operating System

---

• Prepare a Windows installation disc, CD/DVD or USB flash drive and connect it to your PC.
• During the installation process, launch Command Prompt.
• In Windows 7, under the System Recovery Options tab, click Startup Repair.
• In Windows 8 and Windows 10, click Repair your computer, then select Troubleshoot > Advanced options > Automatic Repair (Windows 8) or Startup Repair (Windows 10).

8: Replace the Hard Disk