Applications you should remove from Windows

The screen flickers into black, it comes back and on-screen there is a message Driver stopped responding and has recovered. If you have been through this you are aware that the issue is not serious but it can get pretty annoying fast since you are not aware when will it happen again, and it will happen again. In this guide, we will go through the usual reasons for this error and offer solutions to them. Follow the guide step by step in order to resolve the problem.

1. Clean your PC Dirt and dust are your enemy no1, dirty graphic card can not be properly called and can cause overheating which can result in this particular error, make sure that your PC is clean and tidy in order to eliminate dust and dirt as a cause for malfunction.
2. Turn off multiple applications and try running just one at a time Overburdening GPU can cause this error to appear since the graphic card can not handle all requests it gets from multiple active applications. Try to run just one application at a time for some time period to see if the error will appear again.
3. Update driver Update your GPU driver to the latest version from the manufacturer's website, Display Driver Stopped Responding and Has Recovered Error in Windows 10 can be from outdated drivers not able to handle modern tasks
4. Get newer GPU As hard as this advice is, sometimes the reason is an old graphic card that simply can not keep up with modern games and applications, upgrade it to a more modern GPU and watch errors go away.

It has been some time since the release of Diablo 2 resurrected and overall reception was pretty good. People are enjoying the old classic game in hi-def. resolution and with new and improved visuals. Sadly some server issues are present still until this day and somewhat spoil the experience for players. The greatest lag and server crashes are pinpointed to game-creating events. When a player creates a new online game, the server needs to pull a lot of details from the database and make a game, due to some legacy code present this process takes some time and it is demanding a bit on the server-side, and although code was optimized to cater to more modern approach some legacy code still remains. Another thing that was spotted to affect performance itself is player behavior, to be more specific, modern gamer behavior. Where players find good builds and runs on the internet and then go to farm-specific areas or bosses for loot or experience points, which in return boils down to making plenty and short runs that are made by creating games and after run eliminating them. Now pair that with the previous statement about legacy server and database code and you can add 1 and 1 and see how this might be an issue. A lot of short games over legacy code are placing games in a state it was not designed for back in 2001 and therefore we have issues. Sadly solutions without completely rewriting the whole code are not very promising and they include rate limiting, which will prevent players to create many games in succession in a short period of time and maybe even login queues to drop a load on servers. Blizzard reached to people in the whole company, even old diablo 2 developers to ask for advice and they say that they are working on solutions so they could lift limitations and have everything running fine.

What is Error 1723?

Error Code 1723 is a peculiar error type common in Windows PC. It is related to the Windows Installer package. This error is displayed in the following format:

"Error 1723- There is a problem with this Windows Installer package. A DLL required for this install could not be run. Contact your support personnel or package vendor...”

You are most likely to come across the error code 1723 if the Java installation is not completed successfully. In other words, the error indicates that the installation process has failed.

Solution

Error Causes

The 1723 error may occur due to several reasons, the most common being:

• Corrupted installers
• Files are not extracted successfully
• Registry problems
• Missing DLL files

Further Information and Manual Repair

To resolve this issue on your PC, you don’t always have to hire a professional technician and pay hundreds of dollars to get it fixed. The error code 1723 may not be a common Windows PC error but it is easy to fix. Here we have listed some of the best and easiest DIY ways to resolve this error on your system. These solutions are so easy to perform that even if you are not a computer programmer or technically adept, you can work through them and resolve the error in just a few simple clicks. So, let’s get started:

Solution 1: Install the latest Java Version

If the Java version previously installed on your system is not working properly and showing 1723 error messages then it is advisable to install the latest Java version. However, to do this first you will have to uninstall the old version and then download the latest Java version on your PC from a trusted website to ensure it does not contain malicious viruses and malware.

Solution 2: Ensure the Required Files are extracted in the ‘Temp’ Folder for Installers

Another method to resolve the 1723 error code is to check whether the required files are extracted in the temp folder for installers or not. The error may occur if the location is incorrect and the account is not permitted to extract files in the temp folder. In this scenario, the best way to resolve the issue is to change the permissions of the temp folder. This can be done by logging in to your account and opening file explorer or ‘My Computer’. Now copy and paste this link address in the address bar: DL:UsersUSERNAMEAppDataLocal. Please note, here DL is the drive letter of the Windows drive, and in the username insert the username of the account that you are using. Now right-click the ‘temp’ folder. Select properties and click on the Security tab. After that click edit below the list and press add. Again type the username here and click OK. The next step is to select the added account from the list and tick ‘FULL CONTROL’ box under ‘Permissions for Username’. Click OK and then close the properties. Once this process is complete, now try running the installer again. This will most likely resolve the issue. Nonetheless, if the error still persists, then this means the underlying cause of the error is deeper than you think. The error may be related to registry issues. In such situations, try solution 3 to fix the error 1723 on your system.

Solution 3: Download Restoro.

When the error code 1723 is triggered due to registry issues, then it is advisable to scan your PC with Restoro. Registry issues should be resolved immediately because they pose serious threats to your system. It can lead to system failure, crash and valuable data loss. Registry basically saves practically all the information and activities performed on your PC including the unnecessary and obsolete files like junk files, cookies, temporary files, and invalid entries. If these files are not removed they can corrupt the registry, damage dll files and installers thereby generating error codes like 1723 on your system. The easiest way to repair and clean the registry in seconds is to run Restoro on your PC. It is a smart, intuitive, advanced, and multi-functional PC repair tool. It is embedded with multiple powerful utilities and is a one-stop solution for all PC related issues. This software is compatible with all Windows versions. It is deployed with a highly functional registry cleaner that scans and detects all registry issues on your PC and removes them right away. It wipes out the unwanted files, repairs the damaged dll files and restores the registry. Other powerful utilities that are embedded in this software include an antivirus, a system optimizer and Active X controls and class modules. To resolve 1723 error code on your PC today, click here to download Restoro.

What is QTCF.dll Error?

Sometimes you may experience QTCF.dll error on your computer either during installation or while upgrading applications like iTunes and QuickTime. This error indicates that the installation or the upgrading of the desired application was unsuccessful. The QTCF.dll error is recognized by the Apple Support Community and they have provided a solution to fix this error easily.

Solution

Error Causes

QTCF.dll error occurs because the computer overloads with too much data which corrupts and damages registry files. And therefore the desired program fails to download and start on your PC. When this happens you see a pop up on your screen and the QTCF.dll error message that is usually displayed as:

• QTCF.dll not found
• QTCF.dll file is missing

Such message display hinders your ability to use iTunes or QuickTime applications on your PC. Furthermore, it also slows the performance of your system and you may encounter startup and shutdown problems. Therefore, it is advisable to repair the problem and fix the QTCF.dll error right away.

Further Information and Manual Repair

The good news is that you don’t need to go to a professional or be an IT expert in order to fix the QTCF.dll error. Since this error means that the installation or the attempt to upgrade the system was unsuccessful therefore you need to reinstall the fresh copy of the application. Here’s how you can easily fix the problem by yourself and install a fresh copy of the application: Step 1: First close all the applications running on your computer. Step 2: Now uninstall the application that you were trying to install such as iTunes or QuickTime.  To do this, go to the start menu, click on settings, control panel, and programs. Now click on the application you want to remove. Step 3: Once the application is uninstalled and removed from your computer, then restart it again. Step 4: Now download a fresh version of the application (iTunes or QuickTime) from Apple’s official website http://www.apple.com/quicktime/download/. Step 5: Run the installer. If reinstalling doesn’t work, then it is advisable to download the QTCF.dll repair tool. This repair tool will scan your PC for errors in seconds. Once the scanning is complete, click on the ‘fix all’ button to repair your computer. Once the error is fixed, restart your computer and then try reinstalling the desired application one more time.

A Word of Advice

For regular PC users, it is advisable to install an anti-virus and malware scanner and run it every time you use your computer. This helps you keep informed about the viruses or errors that your computer might be exposed to. And you can take timely actions before you experience file corruption and damage.

It is a fact that Blue Screen of Death errors can give you a headache for you will have a hard time fixing it as it is one of the most difficult errors you can encounter on your Windows computer. One of these BSOD errors is the UNEXPECTED KERNEL MODE TRAP error. If you receive this kind of error then it means that the operating system was not able to catch a trap or an exception generated by the CPU. This BSOD error has an error code 0x00000007F and indicates that the Intel CPU generated a trap that the kernel failed to catch. One of the most likely causes is hardware failure due to faulty memory. Aside from this cause, you also have to track down other probable causes for this problem like corrupted system files, incompatible drivers or programs, faulty hardware, and even dusty components, and so on. To fix the UNEXPECTED KERNEL MODE TRAP BSOD error, here are some suggestions that might help.

Option 1 – 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. In addition, you might also want to check the hardware components of your computer that might not support the operating system itself. You can disconnect all the external devices like USB drives, scanners, printers, etc., and then reboot your PC. After that, add the devices again one after the other and check if the BSOD error is now fixed or not. Moreover, you can also perform a clean boot to make things easier for you.

• 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” checkbox 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” checkbox.
• 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.)

Option 2 – Update your device drivers

• 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. Look for the device driver you and then select either “Update driver” or “Uninstall device”. And if you find any “Unknown device”, you need to update it as well.
• Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
• If you have chosen to uninstall the driver, follow the screen options to complete the process and then restart your PC.
• Connect the device and Scan for hardware changes – you can see this option under Device Manager > Action.

Option 3 – Use the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like UNEXPECTED KERNEL MODE TRAP. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:

• 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.

Option 4 – Run the Windows Memory Diagnostic tool

You can use the Memory Diagnostic tool in Windows to check RAM. Before you use this tool, make sure you save all your important work.

• Tap the Win + R keys to open the Run dialog box.
• Next, type in “mdsched.exe” in the field and hit Enter to open Memory Diagnostic.
• After that, the Windows Memory Diagnostic will give out two options such as:

1. Restart now and check for problems (recommended)
2. Check for problems the next time I start my computer

• Select any of the given options. After that, your computer will restart and check for memory-based issues upon the restart. If there are any issues, it will automatically them.

Option 5 – Disable Memory caching in the BIOS

You can also disable memory caching in the BIOS to fix the UNEXPECTED KERNEL MODE TRAP error.

• Open the BIOS Setup screen.
• Next, go to Advanced > Cache Memory and then disable it.
• Tap the F10 key to save the changes made and restart your computer.

Option 6 – Run System File Checker

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow
• Restart your computer once the scan is completed.

Option 7 – Clean your hardware components for dust

Cleaning your computer’s hardware components for dust might also help in resolving the UNEXPECTED KERNEL MODE TRAP error. Make sure to use a soft cloth in cleaning the hardware as well as a small blower. Moreover, ensure that you do not damage any parts with moisture or cause harm to any circuits while you’re at it.

Error Code 38 – What is it?

Error Code 38 is a device driver error that users encounter on any Windows 2000 operating system and its following versions.

It occurs when the peripheral device that you connect to your PC cannot be accessed due to an inability of the Windows system to acknowledge the driver as a previous record of the driver being loaded is found in its memory.

It is a common error that users come across and appears on your PC with the following message:

“Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38)”

Solution

Error Causes

Error Code 38 is prompted when incomplete program files are left in the Windows system which damage or corrupt its files. There are various factors that contribute to this, some of which are:

• An incomplete program installation
• An incomplete program uninstallation
• Hardware is not removed properly
• System recovery from viruses
• An improper system shut down

The above triggers are very likely to create incomplete files within the Windows registry thereby leading to its damage and corruption.

This is especially true in the case of your PC when it has recovered from viruses when using anti-virus software. The anti-virus in its effort to remove the virus also could remove the files which contain them thereby increasing the risk of the error code.

These damaged files can severely impact the health of your PC and are imperative to fix it immediately to prevent further problems.

Further Information and Manual Repair

Although this error code may pose serious problems for your PC, thankfully, it is very similar to other PC driver errors and thus is an easy one to get rid of. Here are various methods that you can use to get your PC running smoothly again.

Method 1 – Restart your PC

The easiest method you can use to solve your PC error code is to simply restart your PC. It may be that the error prompted upon connecting the device you have connected is merely a temporary problem, and upon restart, will resume functioning smoothly.

Method 2 – Run the Troubleshooting Wizard

If restarting your PC does not help, you will have to find the exact nature of the problem by running the troubleshooting wizard for the device and then address the problem accordingly. To do this, proceed with the following steps:

1. Run Device Manager on your PC
2. Click on the program under the installed programs that is creating problems for you
3. Click on the ‘General’ Tab
4. Click ‘Troubleshoot’
5. Upon opening, the Troubleshooting Wizard will ask a series of questions regarding the error. Answer the questions and follow its directions for solving the error code.

After following the directions of the Troubleshooting wizard, make sure to restart your PC for the changes to take effect. Now check if your device is still causing problems.

Method 3 – Use System Restore

If the error persists, you can use system restore to eliminate the problem. Here is how to do so:

1. Log in using an Administrator account
2. Click ‘Start’ button and select All Programs > Accessories > System Tools > System Restore
3. Click ‘Restore my computer to an earlier time’ and click ‘Next’
4. Select the last Windows to restore point from the ‘On this list, click a restore point’ list, and click ‘Next’
5. Click ‘Next’ on the confirmation window to proceed
6. Restart your PC after restoration is complete

By restoring the system via a last saved system checkpoint, you can obtain undamaged Windows system files that can help resolve the error code.

Method 4 – Manually uninstall and reinstall the device driver

If using system restore does not work either, you may have to resort to manually uninstalling and then reinstalling the device driver causing the problem.

This would be necessary since the remaining incomplete files due to a partial removal or installation of programs are responsible for the error code. By uninstalling and reinstalling the device driver program, it would lead to the completion of the files.

You can do this by firstly logging in as Administrator and opening Device Manager. Select the device that is causing the problem and double click it; make sure that the peripheral is connected properly to the PC.

Upon opening, click on the ‘Driver’ tab and then select ‘Update Driver’. Make sure to refer to the system documentation that you received with your PC or computer to check for the motherboard details and driver specifics.

Method 5 – Use software to automatically download the driver

Manually uninstalling and reinstalling the driver will do the trick; however, it may be time-consuming especially when you would have to resort to your hardware user manual.

Using a program such as DriverFIX can save you a lot of time and frustration in having your device to work properly on your computer.

DriverFIX, with its user-friendly approach to help you fix your PC issues, comes with an integrated database that detects which drivers you need to reconfigure within just a few seconds and downloads it automatically.

It further ensures that your drivers are installed in their entirety leaving no room for any incomplete files to remain that create Error Code 38, or any other driver-related errors for that matter.

It also has the added advantage of being able to backup and restores your files should there be the slightest possibility of system file damage. DriverFIX is the answer to fixing your PC error codes accurately and quickly.

Click here to download DriverFIX to fix Error Code 38 quickly and effectively!

Error 1032 - What is it?

If you are an iPhone or an iPad user and you sometimes open your email Yahoo Mail account on your phone, then you will most likely experience the MF Message Error Domain: Error 1032. This error may occur when you access your mail account. The MF Message Error Domain: Error 1032 may prevent you from composing new emails and even stop the inbox from loading.

Solution

Error Causes

The error 1032 can be triggered due to multiple reasons such as:

• Overloaded History
• Problems with the account log-in credentials
• Outdated Yahoo Mail app
• Authentication issues

Further Information and Manual Repair

To fix this issue on your iPhone or iPad, here are some methods you can try:

Method 1 - Delink and Re-setup Yahoo Email Account

If the error code 1032 occurs due to problems with the account log-in credentials, then try re-setting up your Yahoo email account. To do this, go to tap settings mail, contacts, and calendar, then remove your email account. Now repeat the process and provide valid log-in credentials to re-setup your Yahoo email account.

Method 2 - Update Yahoo Mail App

Another reason can be the outdated Yahoo Mail App. If this is the cause, then simply update it to the latest version. To do this, simply download the latest version from the iTunes store and run it. This will hopefully resolve the issue.

Method 3 - Manage App Connections to Resolve Authentication issues

If the error 1032 occurs due to authentication issues then there are possibilities of conflicts between account security settings. The best way to resolve the error in such a situation is to learn how to manage app connections. Here’s how it’s done: Use your desktop computer to sign in to your Yahoo account. Now click the menu icon and select account info. Enter your account password and sign in again. Now click manage apps and website connections under Sign-in and security section. A list of all authorized mobile devices and applications will be displayed to you. Remove any existing entries appearing for mobile devices. After this, try logging into your Yahoo account from your iPhone or iPad. You will not receive the error.

Method 4 - Clear History

When the cause of the issue is overloaded history, then the best way to go about it is clearing the clutter in the history. Also clear cache and cookies. The cache is the location where temporary files are saved for speeding up the file retrieval process. But sometimes it can get corrupt and the iOS may fail to retrieve data from corrupt cache contents. To clear history and cache, simply tap Settings, Safari, and then clear history, cookies, and data. The process may take some time depending on the cache file size.

TPM, also known as Trusted Platform Module, is a specialized chip used for security as well as encryption of users’ private data like Fingerprint, Facial data, and many more. TPM also comes with a Management Console and if you are not able to load the Management Console and you got the “Cannot load Management Console” error instead, read on as this post will guide you in fixing the problem. This type of issue usually happens when you clear or disable the TPM using the settings in the BIOS and so when you run the Trusted Platform Module Management console, you encounter the error. To fix the “Cannot load Management Console” error in your Windows 10 computer, here are some options you should check out.

Option 1 – If TPM is cleared in the BIOS:

If the Trusted Platform Module is cleared in the settings of the BIOS, you have to close and restart the TPM Management console or TPM.msc once again. It could be that the TPM Management has to reload the changes again after you’ve made them which is why you encounter the “Cannot load management console” error.

Option 2 – If TPM is disabled in the BIOS:

If you opted to disable TPM using the BIOS settings or you have turned it off by accident, then you have to enable it back and you have two options to do that – you can either enable TPM from the BIOS or using the Windows PowerShell. For more details, refer to the instructions below.

Enabling TPM from the BIOS:

• You need to first reboot your PC and then go to the BIOS.
• From there, look for TPM under the security options and in case the TPM management option has been disabled or greyed out, refer to the sub-steps given below to make it active again
  • Enable the Admin password in the BIOS.
  • Then go back to the TPM settings and check if the TPM management is already available.
• After that, you should now be able to enable TPM. Remember that it’s always a good idea to have an ADMIN password for your BIOS as it makes sure that no one can change the settings in your computer BIOS and Security level options.

Enable TPM via Windows PowerShell:

• This second option is a lot easier compared to the first one if you have admin privileges. So once you’ve opened the Windows PowerShell with admin privileges, you need to run the following command:
  • $tpm = gwmi -n rootcimv2securitymicrosofttpm win32_tpm
  • $tpm.SetPhysicalPresenceRequest(6)
• After you execute the commands given above, you need to restart your computer.
• Now, once your computer has restarted, you need to accept any BIOS prompts and then check if the “Cannot load management console” error is now fixed.

One of the biggest annoyances in Windows 10 is that it’s upgrading from one version to another. Although these upgrades are necessary to fix some bugs or improve user experience, some of them actually bring bugs into the computers instead. And in one of the recent Windows 10 updates, a lot of issues were found especially for users who use Remote Desktop on a daily basis. The error stacks up as Windows 10 Remote Desktop Protocol client is not working or won’t connect and can’t find the computer HOSTNAME generally. Based on the reports by users who experienced this issue, there are two cases around it:

1. Users who try to reach a specific website or folder on the network

Some users encounter this error when they try to run the Network Troubleshooter. Even when they add the server name inside it, it still won’t identify the problem, and unpredictably, the driver seems to appear and disappear every now and then. And even after connecting, the network commands don’t work at all. This is really troublesome for users who have lots of PCs and all the other systems do not appear on the network.

2. Remote Desktop isn’t able to find the computer HOSTNAME

Some other users reported that the error appeared when they use the classic remote desktop software. It keeps on failing and throwing the error message, “Remote Desktop can’t find the computer “HOSTNAME”. If this is the same scenario you are having, it means that “HOSTNAME” does not belong to the specified network. So you need to verify the computer name and domain where you are trying to connect to. There are times when it used to work after some users tried connecting to the domain a couple of times. However, when users try to use the UWP version of Remote Desktop, it seems to connect most of the time. This kind of problem is definitely a DNS issue. It could be that there are two different records on the DNS server which is why it connects and other times it doesn’t. When it is able to resolve the correct address, the drives connect to the PC however, after a couple of minutes, they will suddenly go missing. Using “nslookup” for the hostname, multiple times, you can check this and see if you’ll get identical results all the time.

nslookup [–SubCommand …] [{ComputerToFind| [–Server]}]

If you’ve determined that the drives disappear each time, you may have to change the DNS server or ask your admin to resolve the problem for you. Alternatively, you can also check out another option that has worked for a lot of users. This second option is disabling the IPv6 on the network adapter. In case you don’t know, Windows 10 prefers IPv6 over IPv4 so if you now have issues using IPv6 to connect to the servers, you can change your computer’s settings so that it’ll only use IPv4 instead of IPv6. To do so, follow these instructions:

• Open Settings > Network and Internet > Ethernet > Change Adapter options.
• From there, right-click on the adapter for where you want to disable it and then select Properties.
• Next, look for the checkbox labeled, “Internet Protocol Version 6 (TCP/IPv6)” then uncheck it.
• Now click on OK and restart your PC to save the changes made.

You might have experienced a situation when you restarted your Windows 10 PC after an upgrade and you tried logging into your account but only a screen with a message saying, “Preparing Windows”. If the screen only stays that way, this indicates that Windows 10 is trying to complete the upgrade or waiting for some files to load up so that you can use your account. Some users also reported that when they tried logging into their accounts, they also get the same message on their screens. To resolve this issue, read on as this post will show you what you can do if your Windows 10 PC is stuck on the “Preparing Windows” screen. A lot of users have tried logging back into their account once more but to no avail as the same screen still greets them. And even when they tried the Ctrl + Alt + Del combo, it still didn’t work. This only goes to show that your account might somehow be corrupted.

Option 1 – Try booting your PC into Safe Mode

The first thing you can do to resolve the issue is to try booting your computer into Safe Mode and then log in using an Admin account. If it seems like your admin account has caused the problem, you need to create an admin account first and then log in after you reboot into the account and then log off. After that, restart your PC normally and check if the problem’s resolved or not. If not, refer to the next given option below.

Option 2 – Try to repair your corrupted profile via Registry

In this second option, you can try to repair the corrupted profile using the Registry but before you proceed, make sure to create a System Restore Point and then follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Then type “regedit” in the field and hit Enter or click OK to open the Registry Editor.
• Next, go to this registry key: ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionProfileList
• Once you’ve opened the registry key, you should see a list of all the user profiles on your computer. Now click on each S-1-5 folder and look for the “ProfileImagePath” entry and double-click on it to check which user account it is related to. You will see a path like “CUsersACK” where “ACK” is the username.
• You should know which among the user account is corrupted. Just look for a key named “RefCount” and change its Value data to “0” and click OK. And if it isn’t available, simply right-click on the right pane and create it.
• After that, double click on the key named “State” and make sure that the Value data is “0” and click OK.
• Exit the Registry Editor and restart your computer to apply the changes made.

Option 3 – 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 the cause why your screen is stuck at “Preparing Windows”. 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 4 – Try to repair hard disk errors using the Chkdsk utility

You can also run the Chkdsk utility to resolve the problem. 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.
• chkntfs /t
• chkntfs /t:10