Completely Uninstall and Remove Flash

Google Chrome, Microsoft Edge, Mozilla Firefox are some of the leading browsers commonly used these days and they all include an embedded copy of the Adobe Flash Player. So if you are running a Windows 10 PC then you can have up to 4 copies of Adobe Flash Player; one for Microsoft Edge, one for Internet Explorer, one for Opera, one for Firefox. You might also experience cases wherein two flash players are simultaneously running, i.e. one installed in Chrome as a single plug-in and another one installed in Windows, trying to parse the data. And in such cases, you might consider removing or uninstalling one of the versions of Adobe Flash Player. If you do, then you’ve come to the right place as this post will guide you in disabling the embedded Adobe Flash Player in Windows 10.

Before you get started in removing the Adobe Flash Player in Internet Explorer & Microsoft Edge browser, you need to sign in with your administrative account even if don’t use it or set it as the default browser. After you’ve signed in to your administrative account, follow the steps below.

Step 1: Open your browser, if you are using Edge then open it.

Step 2: After opening your browser, go to its Settings and select Advanced Settings.

Step 3: Next, Move the slider against the “Use Adobe Flash Player” option to off.

Step 4: After that, open File Explorer and navigate to this address, “C:/Windows/servicingPackages” and from there, check on the following entries:

  • Adobe-Flash-For-Windows-Package~31bf3856ad364e35~amd64….(version number of the Flash Player)
  • Adobe-Flash-For-Windows-WOW64-Package~31bf3856ad364e35~amd64….(version number of the Flash player #)
  • Adobe-Flash-For-Windows-onecoreuap-Package~31bf3856ad364e35~amd64…(version number of the Flash Player)

Step 5: Take note of all the listed package names of Adobe Flash Player and tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and hit Enter to open the Registry Editor.

Step 6: Next, right-click on the three keys which have the name of the packages you listed and select “Permissions” one after the other.

Step 7: Then check “Allow” to enable full control for the Administrators account and click OK to save the changes made.

Step 8: Select the three keys one after the other and select Visibility DWORD located on the right side and then right-click on Visibility and change the Value data from 2 to 1.

Step 9: Go over the same procedures again for the other keys. Once you’ve completed then you should now be able to remove packages using the DISM tool.

Step 10: Simply open an elevated Command Prompt and execute the following commands:

  • dism /online /remove-package /packagename:Adobe-Flash-For-Windows-Package~31bf3856ad364e35~amd64-10.0.17134.1
  • dism /online /remove-package /packagename:Adobe-Flash-For-Windows-WOW64-Package~31bf3856ad364e35~amd64-10.0.17134.1
  • dism /online /remove-package /packagename:Adobe-Flash-For-Windows-onecoreuap-Package~31bf3856ad364e35~amd64-10.0.17134.1

Keep in mind that the numbers at the end could be different on your computer due to the difference of version number so you have to use the numbers on your system. After that, reboot your computer.

Do You Need Help with Your Device?

Our Team of Experts May Help
Troubleshoot.Tech Experts are There for You!
Replace damaged files
Restore performance
Free disk space
Remove Malware
Protects WEB browser
Remove Viruses
Stop PC freezing
GET HELP
Troubleshoot.Tech experts work with all versions of Microsoft Windows including Windows 11, with Android, Mac, and more.

Share this article:

You might also like

The device is not ready trying to connect USB
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.
Read More
Fixing To use System Restore you must ...
There are cases when you want to undo some changes you’ve made to your computer and to do that you have to perform the System Restore task. However, if you encounter an error that states “To use System Restore you must specify which Windows installation to restore”, when doing so, read on as this post will help you fix the problem. This kind of error in System Restore could be due to corrupted files in the system. There are also situations where you are not able to boot up once you encounter this error which could be a big problem. On the other hand, this error might have something to do with corrupted BCD files. Whatever the cause is, here are some potential fixes you have to try.

Option 1 – Try to run System File Checker offline

Like pointed out, since the error might be due to corrupted system files, you can try to run System File Checker offline. How? Refer to these steps:
  • You need to go to the Advanced Startup Options and from there select Troubleshoot.
  • Next, select the Advanced Options and then Command Prompt.
  • After opening Command Prompt, type the commands given below and tap Enter right after you type each one of them.
    • Cd /
    • Dir
  • If you can see the “Users” folder, that is your system’s drive. However, if you can’t see it, you can just change the drive-by assigning “D” as its alphabet volume.
  • Then execute this command where “C” is the system drive: sfc /scannow /offbootdir=C: /offwindir=C:Windows
  • Now repeat the given steps sequentially.

Option 2 – Try to run DISM tool

You can also run the DISM tool to repair the potentially corrupted system image. First, you have to check the health of the system like checking the integrity of the system files and Windows services. To run DISM, follow the given steps below sequentially.
  • Open Command Prompt from the Advanced Startup options.
  • After that, execute this command where “C:” is the system volume: DISM /Image:C:Windows /Cleanup-Image /RestoreHealth /Source:C:WindowsWinSxS
  • If you encounter an error after executing the given command, insert the Windows USB or DVD and then execute this next command where “E:” is the USB or DVD drive: DISM /Image:C:Windows /Cleanup-Image /RestoreHealth /Source:esd:E:SourcesInstall.esd:1 /limitaccess
  • In some cases, “install.esd” would be “install.wim” and in such case, you have to modify and execute this command: DISM /Image:C:Windows /Cleanup-Image /RestoreHealth /Source:wim:E:SourcesInstall.wim /limitaccess

Option 3 – Try to repair corrupted BCD

As mentioned, the error could also be due to corruption in BCD, and to fix it, you can use Bootrec.exe – a built-in command-line tool used to troubleshot issues related to boot up and Windows Startup. Before you run this tool, make sure that you have inserted a bootable USB or DVD into your computer. Once you have that covered, follow these steps:
  • You need to go to the Advanced Startup Options.
  • Then click on Troubleshoot.
  • Next, select the Advanced Options and then Command Prompt.
  • Once Command Prompt has been pulled up, enter each one of the following commands and in the sequence that they are given to rebuild BCD files and repair MBR files:
    • Bootrec /Fixmbr
    • Bootrec /FixBoot
  • After you execute the commands given above, you should see a confirmation message that says, “The operation completed successfully”.
  • Now type the “Bootrec /RebuildBCD” command to rebuild BCD.
  • Finally, close Command Prompt and then restart your computer to successfully apply the changes made.

Option 4 – Try to run the Automatic Repair Utility

You might also want to use Automatic Repair in fixing the error. To do so, follow the steps below.
  • You can start by creating and booting from a bootable Windows 10 USB Stick.
  • After that, click on Repair your computer located in the bottom left corner when you are on the initial Windows Startup screen.
  • Next, click on Troubleshoot, and then on the other screen, click the Startup Repair option.
  • Now select the operating system you want to repair. Once you do that, it will start to repair your operating system. Wait until the process is completed and then check if the problem’s now fixed.

Option 5 – Try to use the Windows Recovery Environment

If the four options given above didn’t help fix the problem, you could try running Windows Repair and a Windows bootable USB or DVD.
  • First, insert the bootable USB or DVD and boot into it, and select the “Repair your computer” option.
  • Next, once you see the manufacturer logo on your computer, tap the key to enter into Windows Recovery Environment.
  • After that, change the Boot sequence to DVD drive under the UEFI Firmware settings and restart your computer.
  • Once your computer has restarted, select the boot order and make changes accordingly as displayed in the BIOS.

Option 6 – Try running System Restore in Advanced Startup Options

Since you probably can’t boot into your Windows 10 computer, you can try to run System Restore again in the Advanced Startup Options.
  • Boot your computer into the Advanced Startup Options screen.
  • From there, you will see some options to troubleshoot when you can’t log in to Windows in the usual way.
  • Now select Troubleshoot > Advanced Options > Command Prompt.
  • After that, type “exe /OFFLINE:C:Windows” and hit Enter to execute the command which will start the System Restore process.
Note: You need to replace “C” with the drive where Windows Installation is located.
Read More
Restore, Minimize and Close are not working
Recently, a number of users reported not being able to use the Restore, Minimize and Close buttons on their Windows 10 computers. This kind of issue can be quite annoying as you won’t be able to use your computer properly, especially when you navigate between programs and windows. In such cases, the buttons on the right side of the title bar won’t respond to any inputs which could be caused by a number of factors such as different input modes, corrupted system files, and many more. If you are one of the users who are currently facing this problem, worry not for this post will guide you on what you can do to resolve it. There are several potential fixes you can check out to fix the issue. You can try to check if Tablet Mode is enabled and if it is, you have to disable it. You could also boot your computer in a Clean Boot State to check if a third-party program is the one that’s causing the problem. In addition, you could also reinstall the program where you experience the problem or run built-in utilities like System File Checker and DISM tool.

Option 1 – Make sure that you are not in Tablet Mode

Since Windows 10 is designed to work on both desktop and mobile devices, it could be that your computer has slipped into Tablet Mode which explains why you’re not seeing the Taskbar. To check if your computer is really in Tablet Mode, follow these steps:
  • Go to the Start menu and select Settings.
  • Next, select the System setting and from the left pane select the Tablet Mode.
  • From there, make sure that the buttons next to the options given below are set to the off position:
    • Hide app icons on the taskbar in tablet mode
    • Automatically hide the taskbar in tablet mode

Option 2 – Put your computer in a Clean Boot State

As pointed out, it is possible that some third-party program or service is the one that’s behind the problem. To isolate this possibility and to identify the culprit, you have to put your computer into a Clean Boot State. To do so, follow the steps below.
  • 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.)
  • Once your computer is in a Clean Boot State, try to open the program where the problem occurred.

Option 3 – Try reinstalling the program

If the first two options didn’t work, then you might want to consider uninstalling the program and then install it back with its latest version. This should resolve the problem.

Option 4 – Try to run 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 to good system files that might be the cause why the Restore, Minimize and Close buttons don’t work. To run the SFC command, follow the steps given below.
  • Type “cmd” in the Start search and then right-click on the appropriate search result.
  • Next, select “Run as administrator” to open Command Prompt with admin privileges.
  • 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.
  • Now restart your computer and see if the problem is fixed or not.

Option 5 – Run the DISM tool

You can try running the Deployment Imaging and Servicing Management or DISM tool to fix the problem. 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
    • 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, restart your computer.
Read More
Fixing 0x00000050 Stop Error – A How to Guide

What Is 0x00000050 Stop Error?

While running your Windows 7/Windows Server 2008 R2, your system suddenly stops responding out of complete randomness and you see an error message popping up which says something like this:

0x00000050 (parameter1, parameter2, parameter3, parameter4)

Solution

Restoro box imageError Causes

The stop error 0x00000050 signifies that there’s a PAGE_FAULT_IN_NONPAGED_AREA problem. If you’ve seen this error on different occasions then you will find the parameters in the message to be varying. That is because they are dependent on your PC’s configuration. Not all Stop errors "0x00000050” occur due to a single issue.

However, the most common problem which is encountered which results in the stop error popping up is due to a pool corruption occurring in the Srvnet.sys file.

This issue might be caused because of software incompatibility or a defective physical memory which resulted in requests for data for a hardware driver or service which was not found in the memory.

If you find the error occurring after you’ve installed a new application or a device driver then you should access Safe Mode and uninstall, disable or remove that application or driver.

Further Information and Manual Repair

In order to fix this issue, you should try booting your computer to the “Last Known-Good Configuration” as listed during startup.

For this you have to follow the below-mentioned steps:

  1. Start your system.
  2. When you see the message which says “For Troubleshooting And Advanced Startup Options For Windows, Press F8” hit F8 and proceed.
  3. Use the up and down arrow keys to highlight “Last Known-Good Configuration” and hit enter (This method will only work if your system boot was not successfully carried out ever since you made any specific changes).
  4. When you are starting the computer, press F12 and proceed with the PSA/32 Bit Diagnostics.
  5. Do the following so that a clean boot can be performed:
  • Go to the Start menu when the Windows 7 desktop shows up.
  • On the search bar, type “msconfig” and hit search.
  • Disable all the applications which are listed on the “Startup” tab.
  • Now head over to the “Services” tab and mark the option which reads "Hide all Microsoft Service".
  • Select the “Disable All Services” option.
  • Apply the changes by clicking on “Apply” then restart your PC. You should now check the performance of your computer. If you don’t see a BSOD then you start re-enabling all the Services and Startup applications one by one until you finally figure out which one is causing the BSOD to appear.
6. Update your Windows with “Windows Updates”.
Read More
How to Fix Runtime Error 339

What is Runtime Error 339?

Runtime Error 339 is a common error code format that appears when a computer overloads with too much data. However, in some cases, it may occur due to the missing registry keys, DLL files, or during installation. It may lead some programs to shut down all of a sudden and may also corrupt files on the system.

Solution

Download Available to Completely Repair Runtime Error 339

Restoro box imageError Causes

This error code is alarming as it is a critical sign of an unstable system followed by improper maintenance of the computer. The potential risks associated with the Runtime Error 339 include:
  • System startup issues
  • Slow PC performance
  • System crash and failure
  • System file corruption
Therefore, to avoid these risks and system failure, it is advisable to fix the runtime error 339 immediately.

Further Information and Manual Repair

If you have a Runtime Error 339 issue on your computer, here is a great way how you can fix it right away:

Scan For Viruses

Improper maintenance of the computer indicates that your system might be exposed to viruses and malware. Viruses can modify the Windows registry and lead to Runtime Error 339. Therefore, first, it is important to scan for viruses on your PC.

Identify Software that Causes Errors

Scanning will help you identify software that produces this error on your PC. Once you identify them, either uninstall them or update the program. To uninstall the program, go to the Control Panel and then click on the Add/Remove program if you have Windows XP, if not then click on the Programs and Features item. Now delete the program from your system.

Obtain the Latest Version of the Installer and Re-install the Deleted Program

Once you get your hands on the latest version of the installer, run it on your system by following the on-screen instructions. Install the program. There is also another way to fix Runtime Error 339 and that is by downloading the Runtime Error tool.

Use a Professional Runtime Error Fixer Tool

To fix the error you can also use a professional Runtime Error fixer tool to scan for viruses on your PC. It is available for free download here. Download the tool and install it on your computer. Simply scan your PC after installation. Click the repair button once the scan is complete. This tool fixes problems in just a few minutes.
Read More
How to Fix Error Code 0x80073afc

Error Code 0x80073afc - What is it?

Error code 0x80073afc deals with an antivirus program first built into Windows 8/8.1 This error occurs when Windows Defender, the built-in anti-virus software in Windows 8/8.1 and higher, does not start automatically and users attempt to manually start the program. During the initialization period of the program start-up, something goes wrong and users get a 0x80073afc Error message. The error message states there was a problem with the initialization of the program. Windows Defender provides protection of your computer and it is advised by the Microsoft Corporation that you ensure it starts up automatically on every start-up.

Solution

Restoro box imageFurther Information and Manual Repair

Users have found several manual repairs that have fixed the problem without needing to contact technicians for extra help. While the methods below should solve your problem easily, if this is the first time you have encountered the issue you may want to do a simple restart. This has fixed the problem for some users and is the easiest first troubleshooting move. If it doesn’t work move on to the methods listed below, which are easily completed without extra help.

Before trying any of these methods, please make sure that you are logged into a profile that is listed as the administrator of the computer of his administrative powers enabled. If this is not the case you will not be able to complete the following methods. Please log out and log back in on the administrator profile.

Method 1:

First, check to see if you have a third-party anti-virus program installed on your computer. Some users believe that the built-in Windows Defender program is not powerful enough to handle the safety of their computer so they usually download a third-party program. However, that program may have caused a conflict with Windows Defender and may not allow it to open. If you do have a third-party program installed, try uninstalling it then manually starting Windows Defender.

Method 2:

If method one does not work, you may be infected by malware or a virus that has tampered with the settings on your computer and will not allow Windows Defender to start automatically or manually.

First, open Run by holding the “Win” key and pressing the “R” key. Then type “Regedit”. The program will ask for permission to follow through with this action. Click on “Yes” and the Open Registry Editor will open.

Find the HKEY_LOCAL_MACHINESoftwareMicrosoftWindows NTCurrentVersionImage File Execution Option and check to see if there are any files similar to MSASCui.exe or MpCmdRun.exe. If there are any file entries that resemble that, you will want to right-click on them before selecting the “Delete” option. If you do not see any entries that match, this is not the issue with your Windows Defender and you will want to try another method.

The Registry on your computer is very important. It helps tell your computer what programs are safe to run, what programs should be run, and what programs should not be run. If it is tampered with by a virus or Malware, multiple system operations can be affected.

However, if you did find similar file names, and you deleted them, try to start Windows Defender manually. If it does not work again, move on to the next method. 

Method 3:

If the first two methods do not work for your issue, and you are still receiving error code 0x80073afc when attempting to start Windows Defender, this step should solve the problem if you have Restore Point installed on your computer, which you most likely do.

For this method, we will be restoring your computer to a previous Restore Point. First, just like in method two, hold the “Win” key and press the “R” key. This will open run. Next type “Rstrui.exe” and click “ok”. After some time, you will see System Restore Windows. Click “Next” and select the restore point that you would like to go back to. After your computer has restored to the point you selected, check to ensure that Windows Defender has started correctly.

If the above methods aren't able to rectify the issue, you might have to download and install a powerful automated tool to get the job done.

Read More
Windows got stuck on Preparing Windows screen
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
Read More
Repairing or rebuilding the WMI Repository
There are times when the WMI Repository gets corrupted which results in the Provider Load Failure. To resolve this issue, you need to repair or rebuild the WMI Repository in your Windows 10 computer. In this post, you will be guided on how exactly you can do that. In case you don’t know, the WMI which stands for Windows Management Instrumentation is a set of specifications from Microsoft to consolidate the management of devices and applications in a network. The WMI is a database that stores meta-information and definitions for WMI classes. Using only these, the conditions of the systems can be known. You can find the WMI Repository in %windir%System32WbemRepository. It provides end-users with the status of the local or remote computer system. Keep in mind that you must not use this on the Server 2012 Cluster machine. Although there are command-line tools that can fix or restore the Windows Management Instrumentation repository. However, Microsoft suggests that it’s better if you verify if there is corruption. Here are a list of errors as well as permission issues you might encounter:
  • Unable to connect to root default or rootcimv2 namespaces. It fails with the error code “0x80041002” pointing to “WBEM_E_NOT_FOUND.”
  • 0x80041010 WBEM_E_INVALID_CLASS
  • When you open Computer Management and Right Click on Computer Management (Local) and select Properties, you get the following error: “ WMI: Not Found” or it hangs trying to connect
  • Trying to use wbemtest , and it hangs
  • Schemas/Objects missing
  • Strange connection/operation errors (0x8007054e)
To verify if there is corruption, you can try running the following command in an elevated Command Prompt:
winmgmt /verifyrepository
 After you enter the command, if there is a response saying, “repository is not consistent”, then the repository has an issue. If not, then something else is causing the problem. Since you are certain that corruption exists in the WMI repository, then here are some suggestions you need to check out to repair or rebuild the WMI repository.

Option 1 – Try to reset WMI Repository

  • Type “command prompt” in the Start Search and right-click on Command Prompt from the search results and then select “Run as administrator”.
  • After opening Command Prompt with admin privileges, type and enter this command: winmmgmt /salvagerepository
The command you entered is used when the winmmgmt command performs a consistency check. So if an inconsistency is detected, it will rebuild the repository.
  • Next, execute this command to see if the WMI repository now comes back as consistent: winmgmt /verifyrepository
This command will perform a consistency check on the WMI repository.
  • If it states that the WMI repository is not consistent, then you need to type and enter this command: winmgmt /resetrepository
This command is used to reset the repository to its initial state when the operating system was first installed.

Option 2 – Try to force recover the WMI Repository

The WMI Repository comes with a built-in self-recovery process so when the WMI service restarts or detects any corruption, it will automatically trigger the self-recovery procedure. This can happen in two ways:
  • AutoRestore: This will use the backup images if the Volume Shadow copy or VSS backup is turned on.
  • AutoRecovery: The rebuilding process will generate fresh images of the WMI repository based on the registered MOFs. The MOFs are available in the registry located at HKLMSoftwareMicrosoftWBEMCIMOM: Autorecover MOFs
Note: Autorecover MOFs is a key so double click on it to check its value. On the other hand, if the self-recovery procedure does not work, you can try to use the force-recovery process instead. How? Refer to these steps:
  • First, you need to check the reg key value is empty or not under this registry path: HKLMSoftwareMicrosoftWBEMCIMOMAutorecover MOFs
  • If the reg key value is empty, you have to copy-paste the reg key value from another computer. Just make sure that it’s from the System which is equivalent to the computer in question.
  • Next, type and enter this command: Winmgmt /resetrepository
  • After you enter the command, if you get an error that says, “WMI repository reset failed. Error code:0x8007041B. Facility: Win32”, then you have to stop all the Dependency Services on the WMI service by running the following commands:
    • net stop winmgmt /y
    • Winmgmt /resetrepository
This should fix the problem.
Read More
Fix DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
If you suddenly encounter the DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL Blue Screen error on your Windows 10 computer along with the error codes, 0x000000D5, 0xb10BBD9E, 0x0D82DA24, 0Xfecd479D, 0x779827CB then read on as this post will provide you some troubleshooting tips that could help you resolve the BSOD error. Getting this kind of BSOD error means that a driver has referenced memory that was freed earlier and it could also mean that the Driver Verifier Special Pool option has caught the driver accessing memory which was freed earlier. Follow the given options below to fix the DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL BSOD error.

Option 1 – Use the Driver Verifier Manager

The Driver Verifier Manager is another tool in Windows that could help you fix driver-related issues.
  • Type in the keyword “Verifier” in the Cortana search box to search for Verifier in Windows 10.
  • After that, select the option “Create custom settings”.
  • Make sure that you have checked everything except the options “DDI compliance checking” and “Randomized low resources simulation”.
  • Next, select the option “Select driver names from a list” option.
  • Afterward, you have to select all the drivers from any unofficial or third-party provider. To simply put it, you have to select all the drivers that are not supplied by Microsoft.
  • Then click on the Finish button.
  • Open Command Prompt as administrator and execute this command – verifier /querysettings
  • The command you just executed will display the Driver Verifier settings so if you see any of the flags enabled boot your Windows 10 PC into Safe Mode.
  • Open the Command Prompt as admin again and run this command – verifier /reset
  • The command will reset the Driver Verifier. Once the process is done, restart your PC and check.

Option 2 – Try updating SSD firmware

If you have installed SSD on your computer recently and you have started getting the DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL Blue Screen error since then you may have to update the SSD firmware. To fix this, you can download the Intel Solid-State Drive Toolbox from the official website. This toolbox is compatible with Windows 10 and Windows 7 and later versions.

Option 3 – Try running the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL. It can be found in 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 – Try running Microsoft’s online Blue Screen Troubleshooter

If running the built-in Blue Screen Troubleshooter didn’t work, you can also try running Microsoft’s online Blue Screen Troubleshooter. All you have to do is go to Microsoft’s website and from there, you will see a simple wizard that will walk you through the troubleshooting process.

Option 5 – Try to reinstall or update device drivers of recently installed hardware

If the first few options didn’t work for you, then it’s time to either update or roll back the device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.
  • Open the Devices Manager from the Win X Menu.
  • Then locate the device drivers and right-click on them to open the Properties.
  • After that, switch to the Driver tab and click on the Uninstall Device button.
  • Follow the screen option to completely uninstall it.
  • Finally, restart your computer. It will just reinstall the device drivers automatically.
Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 6 – Try disabling Hardware Acceleration

You might want to disable Hardware Acceleration system-wide or for a particular program like Google Chrome and see if it resolves the DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL BSOD error
Read More
Fix Windows Updates and MS Store, 0x80240438
If you were trying to update your Windows 10 computer and failed due to Error Code 0x80240438, then you’ve come to the right place as this post will give you a couple of suggestions you can check out to resolve this error. You can encounter Error Code 0x80240438 not just in Windows Updates but also in Microsoft Store. This is due to the fact that the delivery mechanism for both Windows Updates and Microsoft Store is common and interdependent. This is why a lot of Windows Update and Microsoft Store error codes are similar. And so fixing them won’t be that hard as well since most methods are basically the same. When you encounter this kind of error in Windows Update or Microsoft Store, you will see the following error message on your screen:
“There were some problems installing updates, but we’ll try again later. If you keep seeing this and want to search the web or contact support for information, this may help – (0x80240438).”
To resolve Error Code 0x80240438, here are some potential fixes you need to check out:

Option 1 – Try to run the Windows Update Troubleshooter

The Windows 10 Store Apps Troubleshooter will help you in fixing the Error Code 0x80240438. This is a great built-in tool from Microsoft that helps users fix any app installation issues. So this is worth a try to solve the problem. This built-in tool also helps you fix the Windows 10 Store if it isn’t working. To use the Windows Store 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 Windows Update and then click on Run the troubleshooter option and follow the on-screen instructions and then see if it fixes the problem.

Option 2 – Try to temporarily disable anti-virus and Windows Defender Firewall

As mentioned, the error could be due to the antivirus program or the Windows Defender Firewall installed on your computer. Thus, disabling them or any security software installed in your computer is always a good idea you can try when you’re not able to access the shared drive on your computer. There are times when you encounter problems like Error Code 0x80240438 due to interference of antivirus or security programs. Thus, you have to disable both your antivirus program and Windows Defender Firewall for the meantime and check if it fixes the error or not.

Option 3 – Disable the Proxy server

You can also try to disable the Proxy server for your LAN to fix Error Code 0x80240438 especially if your computer was attacked by some malware or adware recently. In such cases, there is a chance that the malware or adware has changed your network settings in order to generate intrusive advertisements. Thus, you have to disable the proxy server and you can do that by following these steps:
  • Tap the Win + R keys to open the Run dialog box.
  • Then type “inetcpl.cpl” in the field and hit Enter to pull up the Internet Properties.
  • After that, go to the Connections tab and select the LAN settings.
  • From there. Uncheck the “Use a Proxy Server” option for your LAN and then make sure that the “Automatically detect settings” option is checked.
  • Now click the OK and the Apply buttons.
  • Restart your PC.
Note: If you are using a third-party proxy service, you have to disable it.

Option 4 – Try modifying the “Remove access to use all the Windows Update features” Policy

  • Start by tapping the Win + R key combination to open the Run utility.
  • Then type “gpedit.msc” in the field and tap Enter to open the Group Policy Editor.
  • Once you’ve pulled up the Group Policy Editor, navigate to this setting: User Configuration > Administrative Templates > Windows Components > Windows Update
  • Next, double click on the “Remove access to use all the Windows Update features” policy and set its radio button to “Not Configured”. As you can see, this policy setting has the following description:
“This setting allows you to remove access to Windows Update. If you enable this setting, all Windows Update features are removed. This includes blocking access to the Windows Update Web site at http://windowsupdate.microsoft.com, from the Windows Update hyperlink on the Start menu, and also on the Tools menu in Internet Explorer. Windows automatic updating is also disabled; you will neither be notified about nor will you receive critical updates from Windows Update. This setting also prevents Device Manager from automatically installing driver updates from the Windows Update Web site.”
If you enable this policy setting, you can configure one of the following notification options:
  • 0 = Do not show any notifications: This setting will remove all access to Windows Update features, and no notifications will be shown.
  • 1 = Show restart required notifications – This setting will show notifications about restarts that are required to complete an installation.
  • Now you need to exit the Group Policy Editor and restart your computer for the changes to take effect.

Option 5 – Try resetting the Windows Update folders

Resetting the Windows Update folders can also help in fixing the error in both Windows Update and Microsoft Store. All you have to do is delete the contents in both the SoftwareDistribution folder and reset the Catroot2 folder as well.

Option 6 – Try downloading and installing the Windows Updates manually

Error Code 0x80240438 might be due to a Windows Update that has failed. So if it is not a feature update and only a cumulative update, you can download the Windows Update and install it manually. But first, you need to find out which update has failed, and to do so, refer to the following steps:
  • Go to Settings and from there go to Update and Security > View Update History.
  • Next, check which particular update has failed. Note that Updates that have failed to install will be displayed under the Status column which has a label of “Failed”.
  • After that, go to the Microsoft Download Center and look for that update using its KB number and once you find it, download and then install it manually.
Note: You can also use the Microsoft Update Catalog, a service from Microsoft that provides a list of software updates that can be distributed over a corporate network. With the help of this service, it can be easier for you to find Microsoft software updates, drivers as well as fixes.
Read More
1 2 3 171
Logo
Copyright © 2023, ErrorTools. All Rights Reserved
Trademark: Microsoft Windows logos are registered trademarks of Microsoft. Disclaimer: ErrorTools.com is not affiliated with Microsoft, nor claims direct affiliation.
The information on this page is provided for information purposes only.
DMCA.com Protection Status