Creating custom Keyboard shortcuts in Windows

The Makecab.exe process that’s running on your Windows 10 computer is a program that compresses the Component-Based Servicing log or CBS log files and they can get really huge if they’re not compressed. As a result, it would utilize important space on your operating system although makecab.exe does not consume high CPU resources in doing so. However, there are times when it recreates thousands of instances of itself and could cause overconsumption of system resources which slows down your computer. So when the makecab.exe process causes high CPU usage in your system, this could mean that there is a failed Windows Update. In addition, the high CPU usage of the makecab.exe process could also mean that your computer is infected with a virus or malware. Whichever the case is, you can check out several possible solutions that are given in this post to resolve the problem.

Option 1 – Try to delete log file using File Explorer

The CBS log files could reach up to 20GB size and so if you delete them, it would help in saving space in your computer and since they’re not much of use, deleting them won’t negatively affect the system at all. To delete the CBS log files, all you have to do is open the File Explorer and then go to C:/Windows/Logs/CBS and from there, open the CBS log files and delete them all. Doing so should ease the load in the makecab.exe process since it no longer has to compress the CBS log files. As a result, the process would be more relaxed. After that, you can restart your computer and check if the problem’s now fixed.

Option 2 – Try deleting the log file via Command Prompt

You can also try to delete the log files using an elevated Command Prompt. Refer to these steps to do so:

• Type “command prompt” in the Windows Search bar and then right-click on the related search result and select the “Run as administrator” option.
• Next, type the following command and hit Enter to execute it:

del /f %windir%logscbs*.log

• Restart your computer afterward once the command has been executed. This should end the high disk usage by makecab.exe, if not, proceed to the next given options below.

Option 3 – Uninstall any suspicious programs you’ve installed recently

If you have recently installed some programs on your Windows 10 computer, and since then you’ve experienced high CPU usage brought on by makecab.exe, then you might want to uninstall those programs.

• Tap the Win + R keys to open the Run dialog box
• Then type “appwiz.cpl” in the field and hit Enter to open the Programs and Features in Control Panel.
• From there, look for the suspicious programs you’ve installed, select them and then click on Uninstall to remove them.
• After that, restart your computer and try to install the latest version of the program again. It should work now. If not, proceed to the next available option below.

Option 4 – Try running Disk Cleanup

You might want to run the Disk Cleanup utility as it is a useful tool that could delete temporary and useless files on your computer.

• Tap the Win + R keys to open the Run dialog box and then type “cleanmgr” in the field and hit Enter to open the Disk Cleanup window.
• After that, select the drive you want to clean.
• Now click OK to clean the disk and restart your computer.

Option 5 – Try to run System File Checker scan

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files and missing files. It replaces bad and corrupted system files to 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.

• Restart your PC.

Option 6 – Try scanning your computer using Windows Defender

As mentioned, the high CPU usage of makecab.exe might be caused by some malware or virus in the system and so to eliminate it, you have to scan your computer using security programs like Windows Defender.

• Tap the Win + I keys to open Update & Security.
• Then click on the Windows Security option and open Windows Defender Security Center.
• Next, click on Virus & threat protection > Run a new advanced scan.
• Now make sure that Full Scan is selected from the menu and then click the Scan Now button to get started.

This post will guide you through fixing the INTERNAL_POWER_ERROR Blue Screen Error on your Windows 10 computer. If you encounter this kind of Blue Screen of Death error, this means that the policy manager experienced a fatal error which in turn means that it can happen because of Drivers or Software or even due to external hardware. And so to resolve the issue, here are some suggestions that might be of help.

Option 1 – Update the Device drivers

As mentioned, the INTERNAL_POWER_ERROR BSOD error might have something to do with the drivers. It could be that the drivers are outdated so you need to update them in order to resolve the issue.

• Tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. If you see a red or yellow sign that shows up against the driver, right-click on the driver’s name and select “Update Driver Software” or “Uninstall”. And if you find any drivers with a label saying, “Unknown device”, you need to update them as well.
• Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
• Restart your PC.

Option 2 – Check the Device performance and health

You can also try checking the device's performance and health in the Windows Defender Security Center.

• Open the Windows Defender Security Center.
• From there, check if there is a yellow exclamation icon in the Device performance and health section.
• After that, click on the View report option and you might see Health Report that points towards Storage Capacity, Device Drivers, or Apps and Software which should give you an idea of what the root cause of the problem really is.

Option 3 – Try to run the Chkdsk utility

Running the CHKDSK utility might also help you resolve the INTERNAL_POWER_ERROR Blue Screen error. 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 following command and hit Enter:

chkdsk /f /r

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

Option 4 – Try increasing the size of the Hibernation file

• In the Cortana search box, type “command prompt” in the field, and from the search results that appear, right-click on Command Prompt and select “Run as administrator”.
• Next, type in the following command and hit Enter to execute it:

powercfg /hibernate /size 100

• Note that the default size of the Hibernation file is 75% and after executing the command, it should increase to 100%. Now exit Command Prompt and check if the problem’s now fixed or not.

Option 5 – Try to run the troubleshooters

Blue Screen Troubleshooter:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Performance Troubleshooter:

• Tap the Win + R keys to open the Run dialog box.
• Type “msdt.exe /id PerformanceDiagnostic” in the field and hit Enter to open the Performance troubleshooter.
• Then click on Next to get started. Wait until the process is completed.

System Maintenance Troubleshooter:

• Tap the Win + R keys to open the Run dialog box.
• Type “msdt.exe /id MaintenanceDiagnostic” in the field and hit Enter to open the System Maintenance Troubleshooter.
• After that, click on Next to start troubleshooting the problem and wait until it’s done then check if it fixes the problem or not.

Option 6 – Uninstall the programs you installed recently

Chances are, some programs that you just installed might be the one that’s causing the BSOD error. Thus, you need to uninstall the program to resolve the problem.

• In the search box, type in “control” and then click on Control Panel (desktop app) among the search results.
• After that, select Programs and Features from the list which will give you a list of all the programs installed on your computer.
• From there, look for the concerned program and select it and then uninstall it.

Note: If you have downloaded the app from the Windows Store, you can simply right-click on it from the application list and then uninstall it.

Option 7 – Run Windows Defender offline

You also have the option to run Windows Defender offline and scan your computer to see if any malware has infected the computer and the one that’s causing the INTERNAL_POWER_ERROR Blue Screen Error.

Many Windows 10 users often change the IP addresses of their computers’ network adapter in order to connect to the internet or network they belong to in times when there is no automatic connection for their computers. In most cases, access to modifying this setting is restricted for some odd reason even if you are an administrator. So if you are one of the users whose Windows 10 VPN IPv4 Properties are not working, this post can help you remedy that so that you can open and edit the IPv4 Properties on your Windows 10 PC. The common way to change IP settings is by going to Settings > Network and then to Internet > Change adapter options > Select Network adapter > right click and open Properties. From there, you can select TCP/IP 4 and modify it. If you aren’t able to do this, refer to the instructions laid out below to troubleshoot the problem in accessing the IPv4 Properties.

Option 1 – Try using PowerShell to manually set the IPv4 properties

As you are not able to set it using the interface, you can do so using PowerShell instead. Note that this option will only work for you if you run PowerShell with administrator privileges. After opening PowerShell, according to many users, you have to run the this command – set-DnsClientServerAddress -InterfaceAlias “Ethernet” -ServerAddresses xxx.xx.xxx.xxx,x.x.x.x,xxx.xx.xxx.xxx,x.x.x.x Usually, Ethernet is the name of your network adapter which is set by default. If you want to see the actual name of your network adapter, you can just type this command and tap Enter after doing so – Get-NetAdapter -physical | where status -eq 'up' After entering the given command, you will see a list of active Ethernet adapter in your computer as you can see on the image above. Note that the 4 sets of X like the one on the image below should match with the sequence:

Option 2 – Try editing the rasphone.pbk files

The rasphone.pbk files stores property for the connections and since you are not able to access the IPv4 properties, it is most likely that it has been disabled here. The good thing is that you can open these files and edit them using Notepad. Refer to the steps below to do so.

• Open the Windows Explorer and then enable the show hidden files option.
• After that, look for the files at this location – C:Users <username>AppDataRoamingMicrosoftNetworkConnectionsPbk_hiddenPbkrasphone.pbk
• Then right-click on it and select the “Open with” option and choose the Notepad app.
• After opening the file, look for “IpPrioritizeRemote” from the long list.
• Once you found it, set its value from “1” to “0”.
• After that, look for “IPInterfaceMetric” and set its value to “1” and tap Ctrl + S to save the changes you’ve made, and then exit and try accessing the IPv4 properties again. It should work, but if you’re still unable to access it, try the next option below.

Option 3 – Enable the Split Tunneling if you use VPN

All data goes back and forth when you are using a VPN service on your computer. And since you are using VPN, it could be that it disables the IPv4 interface. If that’s the case, you need to stay connected with both the local network and VPN and to do so, you have to enable Split Tunneling. How? Follow these steps:

• Open PowerShell with administrator privileges.
• Next, type in “Get-VpnConnection” and tap Enter. After doing so, it will give you the exact name of your VPN.
• After that, type in “Set-VpnConnection -Name “yourVPNName” -SplitTunneling $True” and tap Enter. Once you enter the command, it will free your IPv5 settings so that you can change it to connect with your local network if you prefer it to.

In case you don’t know, Windows contains a feedback mechanism that generates error reports from hardware and software problems. These reports are temporarily stored in the system and send them back to Microsoft so that it can find solutions to the reported problems and fix them in the upcoming updates.  However, as time goes by, these reports actually take a lot of space in your computer which is why end-users like you are free to delete them with the help of the new Free Up Space feature in Windows 10. As useful the Free Up Space feature may be, there are times when you won’t be able to use it for some reason which is why in this post, you will be guided on how to use alternative ways in deleting very large System queued Windows Error Reporting file, some of which may run in Gigabytes. Every time the Windows Error Reporting or WER sends out an error file and looks for a solution, the WER server at Microsoft sends out a solution instantly. And if the solution is under investigation or is unknown, then you will be notified about it right away and will be asked for more details. As mentioned, even though the Free Up Space feature in Settings will be able to clear the error reporting files, there are instances when it won’t be able to delete very large System queued Windows Error Reporting files. Alternatively, there is an option to delete these files using the Disk Cleanup Utility. Feel free to select which option you’d like to use to get rid of Windows Error Reporting Files.

Option 1 – Delete Windows Error Reporting Files via Settings

• Go to Settings.
• From there, go to System > Storage > Free Up Space and then click on it to launch it.
• Afterward, give it some time to populate all the files and folders. Once it’s done, select “System created Windows Error Reporting files” to mark its checkbox while leaving the other options unchecked.
• Next, click on the Remove files button to delete all the Windows Error Reporting files from your computer.

Option 2 – Manually delete the Windows Error Reporting Files

• Tap the Win + E keys to open File Explorer.
• Next, enable the Hidden Files view from the menu.
• Then go to C:/ProgramData/MicrosoftWindowsWER.
• From there, you will see various folders like LocalReportArchive, ReportArchive, ReportQueue, and Temp.
• Open each one of the aforementioned folders and delete the archive files. Note that these files will have names similar to “00c58c1f-b836-4703-9bcf-c699ca24d285”.

Note: If you are not able to delete any of these files, you have to take ownership of the folder. To do so, refer to these steps:

• Right-click on the folder and then select Properties.
• Next, click on the Edit button in the Properties window and click OK to confirm if you got a User Account Control elevation request.
• After that, select user/group from the permission windows or click on the Add button to add another user or group. It would be best if you add “Everyone” to give permission.
• Then check “Full Control” under the “Allow” column to assign full access rights control permissions.
• Now edit the permission to Full Control for “Everyone”.
• Click OK to save the changes made and then exit.

On the other hand, if you do not want to go through all these troubles in deleting the Windows Error Reporting files, you can just disable it especially if it already becomes a daily annoyance as the files generate every day and their sizes are mostly gigabytes. And besides, there are times when these files do not make it to the Microsoft WER server and end up only occupying a lot of space for nothing.

As you know, DLL files in the Windows environment contain all the code needed by programs in order to properly function. And like with most other software, the functions in the DLL file have to be compatible with Windows especially if they are using any built-in service. So if you encounter an error that says, “DLL is either not designed to run on Windows or it contains an error”, when you try to launch a program, then this could be due to a compatibility issue. To fix this error, read on as this post will walk you through doing that. Based on the reports of users who encountered this error, the error pointed to a DLL file that was either designed to run on a different version of Windows. It is also possible that the DLL file itself is the problem. Here’s the complete error message:

“Bad Image – DLL file is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support.”

According to security experts, the DLL files that are known to trigger this kind of error message are msvcr100.dll, msvcr110.dll, msvcp140.dll, lmirfsclientnp.dll, and so on. To fix this problem, you can try to update or reinstall the program that’s throwing the error to its latest version. You could also ask the vendor for the latest version of the DLL as well as run a System File Checker scan.

Option 1 – Try to update or reinstall the program to its latest version

The first thing you can do to fix the problem is to update or reinstall the program that’s throwing the error. It is possible that the version of DLL might be using a system call that is deprecated. So if you had updated your Windows 10 computer recently, you might want to check for an update of the software or you could also try to reinstall its latest version.

Option 2 – Try asking the vendor for the latest version of the DLL

The next thing you can do to fix the error is to ask for the latest version of DLL from the vendor. There are times when the software uses an open-source version of DLL so it is better if you ask the vendor if there is a DLL file that has to be updated. If there is, then you need to make sure to register the DLL once you have it.

Option 3 – Try to re-register the problematic DLL file

You can also try to re-register the DLL to resolve the problem. The Regsvr32 tool is a command-line utility that can be used to register and unregister OLE controls like DLL and ActiveX (OCX) controls in the Windows operating system. Follow the steps below to use it.

• Open Command Prompt as admin from the WinX menu.
• Next, type the following commands in the elevated Command Prompt and hit Enter to execute the command. This will re-register the affected DLL file using the Windows operating system tool, regsvr32.exe.
  • exe /[DLL file]
  • exe [DLL file]

Note: Replace “[DLL file]” with the name of the DLL file that was pointed out in the error.

• After you execute the given commands, you should see a message saying, “DllRegisterServer in vbscript.dll succeeded” if the Regsvr32 tool was able to run successfully. After that, try to install the program again and see if it now works.

Option 4 – Try to replace the DLL file from a trusted source

• First, you need to get the new DLL file from another computer with preferably the same file version number.
• After that, you need to boot your PC into Safe Mode and navigate to the paths listed below and then replace the file using a USB drive or other external storage devices.
  • x86: This PC > C:/Windows/System32
  • x64: This PC > C:/Windows/SysWOW64
• Next, type “cmd” in the Cortana search box and right-click on Command Prompt, and select “Run as administrator” to open it with administrator privileges.
• Now type the “regsvr32 ntdll.dll” command and hit Enter.
• Restart your PC and check if the error is now fixed.

Option 5 – Run System File Checker scan

If reinstalling the program didn’t work, you can also try running the System File Checker or SFC scan to fix the error. System File Checker is a command utility built into your computer that helps restore corrupted files and missing files. Refer to the following steps to run it:

• Hit the Win + R keys 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 computer.

Option 6 – Troubleshoot the isDone.dll error in a Clean Boot State

You can also troubleshoot the “DLL is either not designed to run on Windows or it contains an error” in a Clean Boot state. It could be that there are some third-party applications in your computer that are preventing the application from getting installed and to isolate this possibility, you need to boot your computer in a Clean Boot State and then try installing the program again. Putting your computer in this state can help you identify which program is the culprit and thus isolates the problem. In a Clean Boot state, your computer will start using only the pre-selected minimal set of drivers and startup programs. Note that you have to disable and enable one process at a time.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• After you’ve set your computer into a Clean Boot State, make sure that you’re signed in as administrator and then try to install the application again.

Option 7 – Try scanning your computer using Windows Defender

The DLL file might also be infected with malware or virus and to eliminate it which could explain why you’re getting the “DLL is either not designed to run on Windows or it contains an error”. Thus, you have to scan your computer using security programs like Windows Defender.

• Tap the Win + I keys to open Update & Security.
• Then click on the Windows Security option and open Windows Defender Security Center.
• Next, click on Virus & threat protection > Run a new advanced scan.
• Now make sure that Full Scan is selected from the menu and then click the Scan Now button to get started.

We have gathered and want to share with you all of the Windows 11 wallpapers if you would like to place them on your desktop now and now wait for the official W11 release. Hope that you will like some of them and I hope to see you again on errortools.com Download Windows 11 Wallpapers here!

And here is the preview of them

There are not many applications for creating mind maps, even fewer that are completely free, so it is with great pleasure to present you with Freeplane. Freeplane is mind mapping, Knowledge Management, and Project Management software completely free and open source. You can it here: https://sourceforge.net/projects/freeplane/files/latest/download

And from developers git page and I quote:

Freeplane is a free and open-source software application that supports thinking, sharing information, and getting things done at work, in school, and at home. The core of the software is tools for mind mapping (also known as concept mapping or information mapping) and using mapped information. Freeplane is written in Java using OSGi and Java Swing. It runs on any operating system that has a current version of Java installed. It can be run locally or portably from removable storage like a USB drive. We use Github only as of the main code repository, all other project parts are hosted at the source forge. So all bugs and feature requests are managed in a separate issue tracker. There is a drop-down box for selecting different types of issues. Other sources of inspiration are our new forum and old forum. Some users write their ideas there. Every contributor and every team member freely decides what task he is going to work on, but for making the best decision we can communicate our self-set goals in the above forum. It is supposed to enable early discussions and community feedback and also to motivate you and other people.

How to start hacking and contributing

People new to the project can start with implementing a new small feature or doing some refactoring or documentation and not with the bug fixing. Not all bug reports seem to be equally important, and if there are important bugs they usually get fixed by people who broke the functionality. I think you should first get there :). For internal developer discussions, there is a private mailing list. It is held private to avoid spam mails. If you want to be subscribed let us know what mail address you are going to use with it. This list is the preferred way to ask all code-related questions because they usually get answered soon and by the most competent team member. Some documentation for new developers is available in Freeplane wiki https://www.freeplane.org/wiki/index.php/How_to_build_Freeplane and also here and here. It is written for new guys and should also be maintained by the new guys to stay up to date. Looking forward to any questions and contributions, Freeplane development team

As you know, the Start Menu in Windows 10 is quite a stable experience. However, there are times when it can encounter some issues as well like getting corrupted. If your computer is going through the same problem, you’ve come to the right place as this post will guide you on how you can fix the “Tile Data is corrupt” error. This kind of problem is actually quite common among a lot of Windows 10 users. This kind of problem prevents the Start Menu from working properly and no amount of clicking the keyboard keys or mouse will resolve the issue. Fixing it is important since the Start Menu is required for the operating system to function properly and even though there are several ways to get around in using the Start Menu, it can get quite problematic. Even if you manage to open the Start Menu, the ability to click on apps to open them is out of the question and you need to fix the problem. Worry not for the potential fixes provided in this post are not hard to follow. You can try to run the Start Menu troubleshooter or run the DISM tool. You could also reset the folder for Tile Database or re-register the Windows 10 Start Menu. For more details, refer to each one of the options provided below.

Option 1 – Try running the Start Menu troubleshooter

The first and basic thing you can do to fix the problem is to run the Start Menu troubleshooter as it can help you fix the problem automatically. Since this is not a built-in troubleshooter, you can download it from the official website of Microsoft. After you download it, run it and wait until it’s done identifying the problem and automatically fixing it.

Option 2 – Try running the DISM tool

You can run the DISM tool as well to help fix the “Tile Database is corrupt” error. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt with admin privileges.
• Then type in the following commands and make sure to hit Enter right after you type each one of them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • Dism(.)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.
• Once it’s done, check if it was able to fix the corrupted Start Menu or not.

Option 3 – Try to reset the Tile Database folder

• First, you need to restart your computer and log into another user account where the Start Menu works.
• Next, navigate to this folder location, C:/Users/<userX>/AppData/Local/Tile/DataLayer.
• From there, copy the “TdlData.xml” file and save it to another drive.
• Once done, restart your computer and log into the user account where the Start Menu is corrupted.
• After that, navigate to this folder location, C:/Users/<userY>/AppData/Local/Tile/DataLayer.
• Now paste the TdlData.xml file you copied earlier and navigate to this location, %LocalAppData%MicrosoftWindowsShell.
• Afterward, copy the DefaultLayouts.xml file from the user account that’s working fine to the user account where the Start Menu is corrupted.

Option 4 – Try to re-register the Windows 10 Start Menu

• Tap the Win + X and select the “Windows PowerShell (Admin” option from the menu.
• After opening PowerShell, execute this command: Get-AppXPackage -AllUsers |Foreach{Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml"}
• Wait until the command is executed and then see if it fixed the problem with the Start Menu or not.

The GDI32.DLL is a DLL (Dynamic Link Library) file that was developed by Microsoft. It is an essential file of the Windows OS as it contains instructions and information for exe files to follow. These DLL files also use to store the various procedures and codes for the Windows programs. It is considered an essential component of Windows because it ensures that all the programs on Windows are operating properly. So, if the gdi32.dll not found on your computer, then it can negatively impact your computer and the associated programs. Though DLL files used to be so efficient and convenient, they are extremely vulnerable to errors and issues.

1. Perform SFC scan

   Press ⊞ WINDOWS + X to open the Windows menu From the menu choose command prompt (admin) In command prompt type sfc /scannow and press ENTER Leave the computer for the operation to be completed and Reboot your computer

2. Run DISM

   Press ⊞ WINDOWS + X to open the Windows menu From the menu choose command prompt (admin) in command prompt type: DISM.exe /Online /Cleanup-image /Restorehealth and press ENTER wait for the process to be finished and Reboot your computer

3. Update device driver

   Go to your manufacturer's website and update drivers for your components with the latest versions.

4. Update Windows

   If you have an update ready for Windows, update it and see if this will remove the error

5. Scan computer for malware

   Perform a full PC scan for malware to see if this is causing issues with the GDI32.DLL error.

6. Download file

   One solution is to download a file from the official site and place it in the corresponding folder.

7. Perform System restore

   Rollback system restore before the issue happened and your Windows will be working as intended

External hard drives have become essentials as they store data. However, they are also prone to issues and one of them is the “The device is not ready”. You could encounter this error when you try to access your connected hard drive. This error won’t allow you to access the contents of your hard drive so unless you fix it, you won’t be able to access any of the files on your hard drive. One of the most likely causes of this error is a hardware defect. Aside from that, it could also be due to loose connections, obsolete device drivers, as well as compatibility issues between the operating system and the hard drive. Before you start troubleshooting the problem, you need to determine if you were able to access your hard drive before you encountered the error or not. If not, you need to check the compatibility of the device with your operating system as it could be the reason why you’re getting the error. There are several potential fixes you can check out to fix this error. You can try to check the hardware connections, run the built-in Hardware and Devices troubleshooter, as well as the USB troubleshooter. You could also run the CHKDSK utility or update the drivers of the device or the USB drivers.

Option 1 – Try checking the hardware connections

The first thing you have to do before you further troubleshoot the problem is to check the hardware connections of your computer and see if there are damaged ones, just like with USB ports, it would also affect the overall connectivity of the device with the computer. So if you notice some irregularities in the connecting cable physically, you might have to buy another one and replace it and then see if it fixes the problem or not.

Option 2 – Run the Hardware and Devices Troubleshooters

• The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
• After opening Settings, look for the Update and Security option and select it.
• From there, go to the Troubleshoot option located on the left-hand side of the list.
• Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
• After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.

Note: You could also try to run the USB troubleshooter as it could also resolve the problem.

Option 3 – Run the CHKDSK utility

As you know, the CHKDSK utility can help you in identifying the bad sectors in a drive and fix them automatically. Thus, you can run it to fix the “The device is not ready” error when you connect your USB drive to your computer.

• Open Command Prompt with admin privileges.
• Next, type and enter this command to execute it: chkdsk /f <drive>
• Now, wait until the process is completed and exit Command Prompt.
• Restart your computer and try connecting the USB drive again and see if the error is fixed.

Option 4 – Try to update the drivers of the device

Although you can always update the device drivers using the Device Manager, you might want to try downloading the latest set of drivers directly from the manufacturer’s website. Once you’ve downloaded them, install them right away and then correct the external hard drive.

Option 5 – Update or reinstall the Universal Serial Bus Controller driver

If updating the drivers of the device did not fix the “The device is not ready” error, you can try to update or reinstall the Universal Serial Bus Controller drivers instead of using the Device Manager. Refer to the following steps:

• First, click the Start button and type “device manager”.
• Then click on the “Device Manager” from the search results to open it.
• From there, look for the “Universal Serial Bus controllers” option and then right-click on each one of the USB drivers and select the Update Driver from the menu.

Note: If it is a regular USB drive, then it will be listed as a USB Mass Storage Device but if you have a USB 3.0 device, then look for a USB 3.0 Extensible Host Controller.

• Restart your PC and then click the “Search automatically for updated driver software” option.

Note: If updating the USB Controller drivers didn’t work, you can try to reinstall them instead.

Option 6 – Restart your computer in a Clean Boot State

If the first three given options didn’t work and you still see the error when you connect external devices, you can try putting your computer in a Clean Boot State and then try connecting them again.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• Now try to connect the external devices and check if the error is now gone.