Logo

Fix Windows Cannot Find a System Image

If you have encountered the “Windows Cannot Find a System Image on This Computer” error while you are trying to restore a system image, then read on as this post will guide you in resolving this problem.

A system image is basically a backup of your whole data in the system. For instance, it can be the backup data of your hard disk or the whole hard disk itself, or one of the volumes. This is really useful in some cases like when you are not able to get back into your system for some reason or when your system has been corrupted. In such cases, you can utilize this feature and get going safe and sound. However, not all things go the way as expected like when you make a system image of a drive for instance, or use that backup to restore data and you suddenly encounter the “Windows Cannot Find a System Image on This Computer” error. This kind of error occurs due to a number of reasons but worry not for your data is safe and you can fix this error easily.

This error is most likely triggered by changing the name of the “WindowsImageBackup” folder. Renaming this folder will certainly be an issue since it is the one that stores all your data. Aside from renaming the WindowsImageBackup folder, renaming the sub-folders can also cause this error which means that renaming the sub-folders of the WindowsImageBackup folder can trigger the error.

To fix this error, here are some suggestions that might help:

Option 1 – Try putting the WindowsImageBackup folder in the Root directory

Windows will have issues finding the WindowsImageBackup folder if it isn’t in the root directory of the drive so if it is not there, the “Windows Cannot Find a System Image on This Computer” error will pop up. When a folder is in a root directory, it means that it shouldn’t be stored within a folder but in the main directory instead.  Thus, you need to put the WindowsImageBackup folder in the root directory to fix the error.

Option 2 – Don’t add any sub-folders in the WindowsImageBackup folder

Another cause of the error is when you add sub-folders in the WindowsImage Backup folder. Adding any sub-folders in this folder will only trigger the error so you should leave the folder as it is and you must not make any modifications to it. So if you have added sub-folders in it, make sure to remove them right away.

Option 3 – Make sure that there is one system image per USB drive

The error can also appear if you’ve stored multiple images inside a single USB drive as it could confuse Windows and will trigger the “Windows Cannot Find a System Image on This Computer” error. Note that storing system images of different volumes of your hard disk in a single USB will prevent you from restoring your data.

Option 4 – Try renaming the System Image folder

If you’ve just changed the name of the System Image folder after you store it on a USB stick or other external device, then it’s no wonder why you’re getting the “Windows Cannot Find a System Image on This Computer” error. Windows search for the default name, “WindowsImage Backup” folder when restoring your data so if it is not able to find it, it throws up this error instead. To fix the error, you need to change the folder back to its default name which is “WindowsImageBackup”.

Option 5 – Check the WindowsImageBackup sub-folders

As mentioned earlier, renaming sub-folders in the WindowsImageBackup folder can trigger the error so if you have renamed sub-folders in this folder, you need to change them back to their default names so that you can restore your data peacefully.

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

Configure Windows 10 to create Dump Files on Blue Screen of Death
If your Windows PC encounters an error, it will display a Blue Screen of Death or BSOD error which usually comes up for a fraction of second and creates some logs or Dumps Files as what other user prefers to call it and then boots your PC suddenly. This process usually takes place quickly that most users find it hard to get the error code and won’t probably be able to check what really went wrong with their PCs. This is where the dump files come in. They are stored internally in your computer and can only be accessed by an administrator. They are classified into 4 main types and in Windows 10 they are either:
  1. Complete Memory Dump
  2. Kernel Memory Dump
  3. Small Memory Dump (256 KB)
  4. Active Memory Dumps
Dump Files are useful as they could help you in resolving the problem and so you need to configure your Windows 10 PC to create them but first, you need to make a system restore point. This is essential as you are about to modify some system files as well as critical Windows 10 settings. There are two ways you can create Dump files – first is by modifying the settings in the Startup and Recovery and lastly is via the WMIC command line. Refer to the instructions prepared below to be guided on how you can create Dump files after any BSOD error using these options.

Option 1 – via Startup and Recovery

  • Type in “control panel” in the Cortana Search box and then click on Control Panel from the search results to open it.
  • After opening Control Panel, you need to make sure that you view the contents by their Category then click on the header link which is labeled “System and Security” or you could also right-click on the This PC icon and then click on Properties.
  • Next, select the Advanced system settings from the left panel. Once you do, a new and small window will pop up.
  • Under the newly opened window, look for the section called Startup and Recovery and then click on the Settings button.
  • And from the System Failure section, you can choose any option from the drop-down for Write debugging information such as:
    • None – this means that there is no dump file created by Windows
    • Small Memory Dump – this means that Windows will create a Minidump file on BSOD
    • Complete Memory Dump – this means that Windows will create a Complete Memory Dump file on BSOD
    • Automatic Memory Dump – this means that Windows will create an Automatic Memory Dump file on BSOD
    • Active Memory Dump – this means that Windows will create an Active Memory Dump file on BSOD
Note: The complete dump needs a page file that is allowed to be the size of the physical memory installed in your PC with a dedicated 1 MB of space for just the page header.
  • Now once you have selected the most suitable option for you, just click on OK/Apply and then exit.
  • Restart your PC to successfully apply the changes made.

Option 2 – via the WMIC command line

  • The first thing you need to do to create Dump files via the WMIC command line is to tap the Win + X keys combination or simply right-click on the Start button and then select the Command Prompt (Admin) option. You could also type in “cmd” in the Cortana search box and then right-click on Command Prompt from the results and select Run as administrator.
  • After that, type in any of the commands given below depending on your preferences so that your Windows 10 PC will be configured to create Dump Files:
    • No dump file: wmic RECOVEROS set DebugInfoType = 0
    • Small Memory Dump: wmic RECOVEROS set DebugInfoType = 3
    • Kernel Memory Dump: wmic RECOVEROS set DebugInfoType = 2
    • Complete Memory Dump: wmic RECOVEROS set DebugInfoType = 1
    • Automatic Memory Dump: wmic RECOVEROS set DebugInfoType = 7
    • Active Memory Dump: wmic RECOVEROS set DebugInfoType = 1
Note: A complete dump has to have a Page file which is allowed to be the size of the physical memory installed on your PC accompanied by a 1 MB space for just the page header.
  • Now type in “exit” in the Command Prompt to exit it.
  • Restart your PC to apply the changes made successfully.
Read More
PrintNightmare returns Microsoft states
PrintNightmareA few days ago we celebrated fixing of months-long PrintNightmare vulnerability by Microsoft, sadly a new bug and issue have been found. Firstly discovered Microsoft stated:
A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged file operations. An attacker who successfully exploited this vulnerability could run arbitrary code with SYSTEM privileges. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
A few days ago, Microsoft officially released a patch that was supposed to finally fix it. As you might recall this vulnerability was present for quite some time, Microsoft's solution after a long struggle was to elevate certain privileges to administrator account only and remove user accounts from managing printers. It complicated things a little bit but it was stated payoff was worth it. The new issue now is that on a system that already had accounts created and set, old accounts still can hijack the system, patch issues address only accounts that are created after the fix is administrated, old ones can still do whatever they want. Once again of course Microsoft has stated that until it is again resolved you should again disable the Print Spooler service as a temporary workaround.
Read More
How to Fix DCOM Error 1084 on Windows
Distributed Component Object Model or DCOM is a module on Windows computers that allows computers to run programs over a network to another computer. It is a software component from Microsoft that allows COM objects to communicate with each other while that program is remotely running over the network. The COM Model is another extension of the DCOM model which both work together in order for the intended task to be executed. To make this module work, there are three components needed such as the Class Identifier or CLSID, the Programmatic Identifier or PROGID, and the Application Identifier or APPID. However, DCOM does not always work as expected as it could still encounter some errors. One of them is error 1084. Because of this error, the execution of programs in a remote computer on the network would be interrupted. So if you encounter the DCOM error 1084 when you try to start a service like running the DISM tool or in other scenarios on your Windows 10 computer, then this post could help you. Refer to the instructions given below to start troubleshooting the problem.

Option 1 – Try checking the status of DCOMLAUNCH Service or DCOM Server Process Launcher and its 3 dependencies

The DCOM Server Process Launcher service launches both COM and DCOM servers in response to object activation requests. This is why if this service is stopped or disabled, the programs that are using COM and DCOM won’t properly function. So you need to make sure that the DCOMLAUNCH service is running.
  • In the Cortana search box, type “services” and click on the Services icon to open the Services Manager. Alternatively, you can also tap the Win + R keys to launch the Run prompt and then type “services.msc” in the field and hit Enter to open the Services Manager.
  • Next, check the following services:
    • DCOM Service Process Launcher
    • Background Tasks Infrastructure Service
    • Local Session Manager
    • Remote Procedure Call (RPC)
  • Then right-click on each one of the services and click on their Properties.
  • After that, select Automatic from the drop-down menu of Startup Type and make sure that all the aforementioned services are Running.
  • Now click OK for each one of the services.

Option 2 – Troubleshoot the problem in a Clean Boot State

There are instances that some conflicting programs installed in your computer might be the one that’s causing DCOM error 1084. To identify which program is causing the problem, you need to put your computer in 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.)
  • From there, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

Option 3 – Try to use the DISM tool

You might want to repair potentially corrupted files in your system as having them could also trigger the DCOM error 1084. To repair these corrupted system files, you can run the DISM commands:
  • Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
  • After that, input each one of the commands listed below sequentially to execute them:
    • Dism /Online /Cleanup-Image /CheckHealth
    • Dism /Online /Cleanup-Image /ScanHealth
    • Dism /Online /Cleanup-Image /RestoreHealth
  • Once you’ve executed the commands given above, restart your computer and check if the DCOM error is now fixed.

Option 4 – Reset your computer

  • Tap the Win key or click on the Start button located in the Taskbar.
  • Then click on the Power button at the bottom right portion of the screen.
  • Next, press and hold the Shift key on your keyboard and then click on Restart. This will restart your Pc into the Advanced Startup options.
Note: Once you have access to the Advanced Startup options, you have to go to the setting which allows you to Reset your Windows 10 PC. All you have to do is select Troubleshoot > Reset this PC to reach the following screen Afterward, select either the “Keep my files” option and then proceed to the next on-screen instructions that follow to reset your Windows 10 computer without losing your files.
Read More
Fix Windows Update Error 0x80070103
This post will guide you in fixing the error 0x80070103 when installing Windows Update. According to users who encountered this problem, Windows Update (WU) fails to install several different updates. This kind of Windows Update error is can mostly be seen in the Windows Update screen inside the update reports although it is also known to occur when a user attempts to install a peripheral driver – only if the Windows Update offers to update the driver through a prompt and when you click Yes. There are several possible causes for this error, it could be that Windows Update is trying to install a particular driver for the second time already which happens when it gets confused by an additional piece of identical hardware like the graphics adapter. Aside from that, the Windows Update might have already installed the driver which is known to occur with unsuitable versions of the already installed driver. In addition, the error could also be due to a third-party program interference like a security program or a utility program that is using the same driver and conflicts with the Windows Update. Here are some suggestions that might help in fixing the Windows Update error 0x80070103.

Option 1 – Install the updates in a Clean Boot State

You might want to try putting your computer in a Clean Boot state and then install Windows Updates again without any trouble. During this state, you can start the system with a minimum number of drivers and startup programs that will surely help you in isolating the root cause of the issue.
  • 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 that, try to install the Windows Updates or upgrade again.

Option 2 – Try installing the failing driver without using Windows Update

If installing the updates in a clean boot state didn’t help, you can try a manual approach to yield much better results using the Device Manager or by downloading the driver from the manufacturer’s website manually.
  • Tap the Win + R keys to launch Run.
  • Type in 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.
Note: You also have the option to go directly to the website of your device driver manufacturer and go to the section called Drivers then check if there’s a new available update – if there is, download and install it.

Option 3 – Try to run the Windows Update Troubleshooter

You might also want to run the built-in Windows Update Troubleshooter in Windows that could help you in resolving the Windows Update error 0x80070103. All you have to do is go to Settings > Update& security > Troubleshoot > Windows Update. From there, click on the Run the troubleshooter button and follow the next one-screen instructions that appear. After that, restart your computer and check if the error is now fixed or not by trying to install the update once again.
Read More
Fix Error 0x8024a11a or 0x8024a112
What is Error 0x8024a11a or 0x8024a112 ? If you are trying to update your Windows 10 computer and just when you were done downloading the feature update and about to install it, you encounter an error message saying:
“We’re having trouble restarting to finish the install, Error 0x8024a11a, 0x8024a112, 0x80070005 or 0x80070032”
And so to fix this problem, this post will give you a couple of possible solutions. Refer to the options given below to get started.

Option 1 – Restart your computer many times

This is the first thing you can try since there are instances when the Windows Update process gets stuck for a minor thing and restarting the computer usually helps in resolving the issue. All you have to do is click the Restart now button. However, if it does not work, you can use the Power buttons from the Start Menu or WinX Menu. Aside from that, you can also use your power buttons such as Alt + Ctrl + Del to restart your computer. And during the boot process, it is recommended that you restart your computer in Safe Mode or even in a Clean Boot State. After that, you can restart your computer in normal mode. This will make sure that no third-party processes will be able to interfere with the Windows Update process. To put your PC in a Clean Boot State, here’s what you have to do:
  • 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 that, try to install the Windows Updates or upgrade again.

Option 2 – Try running the Windows Module Installer

The Windows Module Installer is a built-in service in the Windows operating system that could help you resolve the Windows update error 0x8024a11a or 0x8024a112. You need to make sure that this service is Started and that its Startup type is set to Automatic – you can do this via Services Manager or by executing the command given below in an elevated Command Prompt.
  • Tap the Win + R keys to open the Run dialog box.
  • Then type “command prompt” in the field and hit Enter to open Command Prompt.
  • And in the elevated Command Prompt type in the following command and hit Enter:
SC config trustedinstaller start=auto
  • After executing the command successfully, you should see the “[SC] ChangeServiceConfig SUCCESS” message on the Command Prompt window.

Option 3 – Run the DISM tool

You can also run the DISM Tool as it helps in repairing the Windows System Image as well as the Windows Component Store in Windows 10. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth” which could help in fixing the Windows update error 0x8024a11a or 0x8024a112.
  • 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.

Option 4 – Run 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 to good system files that might be the cause why you’re getting the errors 0x8024a11a and 0x8024a112. 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 5 – Run the Windows Update Troubleshooter

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

Option 6 – Run Microsoft’s online troubleshooter

Running Microsoft’s online troubleshooter might also help you fix the Windows update error 0x8024a11a or 0x8024a112. This online troubleshooter is known to help in fixing Windows Update errors, it scans your computer for issues that might be causing the problem and then fixes them automatically.
Read More
Fix Something went wrong with the projection
As you know, Windows 10 is created with the goal of developing an operating system that caters to users’ needs and enhances productivity. That’s why modern computers that are running the Windows 10 OS have the capabilities to project their screen to an external display wirelessly. That said, Microsoft has a dedicated and pre-installed app called Connect which helps another device to project their screen on the computer. However, this feature is kind of delicate and won’t work unless it’s properly configured. So if some configuration does not work out well, it will throw an error message that says
“Something went wrong with the projection”.
This kind of error is caused by some issues with the Display driver, hardware, corrupted or damaged system files, and so on. And to fix it, there are several methods you can check out. You can try to update, roll back or reinstall the Display drivers. You could also run the Network Adapter troubleshooter or the Video Playback troubleshooter as well as run System Restore to undo any recent changes that might have triggered the error or reset your Windows 10 computer without deleting any files. For more details, refer to each one of the options provided below.

Option 1 – Try to update or rollback the Graphics driver

You can try to update your Graphics card driver using the Device Manager in your computer to resolve the blank dialog boxes problem or you can also go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it. To update your Graphics driver via Device Manager, refer to these steps:
  • First, boot your computer into Safe Mode.
  • After that, tap the Win + R keys to launch Run.
  • Type in 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. From there, look for the Display Adapters and click on them.
  • After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
  • Now restart your computer.
  • After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.
Note: If updating the Graphics driver didn’t fix the problem, you can also try to roll back to its previous version and see if that helps or you could also try to roll back, update or reinstall the Network Adapter drivers.

Option 2 – Try to run the Network Adapter troubleshooter

To run the Network Troubleshooter, refer to these steps:
  • Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
  • Next, scroll down and select the “Network Adapter” option from the right pane.
  • Then click on the Run Troubleshooter” button.
  • After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.
  • Restart your computer.

Option 3 – Try to run the Video Playback troubleshooter

If the Network Adapter troubleshooter didn’t work in fixing the problem, you can try to run the Video Playback troubleshooter instead. To run it, simply go to Settings > Update & security > Troubleshoot. From there, scroll down until you see the Video Playback option and then click on the “Run the troubleshooter” button to get started. This troubleshooter will detect and automatically fix any problems related to video playback so it should help fix the error.

Option 4 – Try performing a System Restore

You might also want to perform a System Restore that might help you in fixing the error. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.
  • Tap the Win + R keys to open the Run dialog box.
  • After that, type in “sysdm.cpl” in the field and tap Enter.
  • Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
  • After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

Option 5 – Reset your computer

  • Tap the Win key or click on the Start button located in the Taskbar.
  • Then click on the Power button at the bottom right portion of the screen.
  • Next, press and hold the Shift key on your keyboard and then click on Restart. This will restart your Pc into the Advanced Startup options.
Note: Once you have access to the Advanced Startup options, you have to go to the setting which allows you to Reset your Windows 10 PC. All you have to do is select Troubleshoot > Reset this PC to reach the following screen Afterward, select either the “Keep my files” option and then proceed to the next on-screen instructions that follow to reset your Windows 10 computer without losing your files.
Read More
Fix AMD driver crashing Windows 10
Graphic cards are essential to our computers but from time to time in the race to make better GPU and to grab a large portion of the market bad drivers get released and can create really unwanted and unpleasant experiences, from Windows freezes to the black screen of death, to AMD driver Windows crashing down and many more. This article will cover basic troubleshooting with AMD drivers and offer you solutions on how to fix them.
  1. Rollback the previous version of the driver.

    Installing the new driver version is the reason for this particular error, so naturally rolling back the previous version which was stable and did not cause issues will solve the problem. To roll back the previous version of drivers follow the next steps: Open Start menu and click on settings, go to system and choose Apps and features Find: AMD Catalyst Install Manager, right-click on it, and choose to uninstall Go to AMD official website and download the previous driver version, install it on your computer Turn off automatic driver updates and reboot your system
  2. Reinstall the driver

    Sometimes it is not a bug in the released driver, it is a corruption of files because of file transfer or any other specific reason. The reinstalling driver will fix an issue if this is the case. To reinstall the driver Press ⊞ WINDOWS + X and choose Device Manager Expand Display adapters, right-click on AMD device and choose to uninstall Go to the official AMD website, download the latest driver and install it Reboot your system
  3. Disable browser extensions

    Some users have reported that error occurs only when they are watching videos online, if this is your case, go to your browser options and disable extensions to see if this will remove the problem.
  4. Remove Lucid Virty MVP

    If by any chance have this relic installed on your system, go to Applications and remove it. It is an old program shipped with old drivers and it is usually present in your Windows that was upgraded from 8.1 to 10. Uninstall it and see if this fixes your issue.
  5. Clean your graphic card

    Sometimes this error can happen due to excessive dust on your GPU, if you have the expertise, clean it or take it somewhere to be cleaned.
Read More
Firewall is preventing or blocking connections
As you know, the Windows Firewall is designed not just to protect your computer from viruses and malware, and other security threats but it’s also designed to block any program from accessing the internet. Users are given the option to block both inbound and outbound traffic for any apps on their computers. However, this kind of option can often lead to not being able to access the internet. In such cases, when you try to run the Windows Firewall Troubleshooter or the Windows Network Diagnostic troubleshooter, it will throw an error message that says, “Windows Firewall is preventing connections to your computer. The Windows Firewall rule HSS DNS Leak Rule may be blocking your connection”. If you are in this kind of scenario, then you’ve come to the right place as this post will guide you on how exactly you can fix this error. When you encounter this kind of error, there are several options you can check out to fix it. You can try to allow an app or feature through the Windows Firewall or uncheck the HSS DNS leak rule in both private and public. For more details, refer to the suggestions provided below.

Option 1 – Try to allow an app or feature through Windows Firewall

The first thing you can do to get rid of the error is to allow a feature or app through the Windows Firewall. To do this, follow these steps:
  • Open the Windows Defender Security Center.
  • From there, select the Firewall and Network Protection option.
  • Next, click on the “Allow an app through firewall” option and then click on the “Change Settings” button and make sure that you have administrative privileges.
  • After that, select the app or feature you want to allow through the Firewall from the menu. You also have the option to manually add the app by using the “Add an App” option.
  • Then select the between the type of network an app can access such as:
    • Private Network will allow the app to connect to the internet only at home or work.
    • Public Network will allow the app to connect to the internet from anywhere, including Public WiFi hotspots.
  • Once done, restart your computer and see if it fixed the error or not.

Option 2 – Try to uncheck the HSS DNS leak rule in both private and public

The next thing you can do to fix the error is to uncheck the HSS DNS leak rule in both private and public. You can do this by following these steps:
  • Open the Windows Defender Security Center.
  • From there, select the Firewall and Network Protection option.
  • After that, click on the “Allow an app through firewall” option and then click on the “Change Settings” button and make sure that you have administrative privileges.
  • Next, scroll down until you see the HSS DNS leak rule in both private and public option and then uncheck it.
  • Now restart your computer and check if the error is now gone.
Read More
How to Fix Task Scheduler Error 0x80070057
One of the important functions in the Windows operating system is the Task Scheduler. It can automatically run various tasks at a certain time where you’ll have to add a task that needs to be executed and then choose the time it has to run at. So when that time comes, the Task Scheduler will run the task automatically. However, some users reported getting an Error 0x80070057 where the Task Scheduler fails to start. This kind of error may be due to a disabled service that prevents the service from running. It is also possible that the antivirus program interfered with the task – it could be that the Task Scheduler is somewhat in the block list since the antivirus adds it to the list automatically when it’s installed. On the other hand, it could be that you lack administrator-level privilege which is why the Task Scheduler was not able to carry out the task. To fix this issue, here are some suggestions you can try.

Option 1 – Try to restart the Task Scheduler service

As mentioned, it is possible that the Task Scheduler service could be disabled. You could have disabled it when trying to enhance your computer’s performance and whatnot. Thus, you need to verify if it’s running or not and then restart it.
  • First, you need to tap the Win + R keys on your keyboard to open the Run dialog box.
  • Next, type “services.msc” in the field and click OK or tap Enter to open the Windows Services Manager.
  • You will see a list of Services and from there, look for the Task Scheduler service and double click on it.
  • After that, go to the General tab and click on the Startup Type options and then select “Automatically” from the given list.
  • Click on the “RUN” option and select the “Restart the Service” option.
  • And click on the “After Second Failure” option and then select the “Restart-Service” option again.
  • Now click on the “After Subsequent Failures” tab and select the “Restart the Service” option.
  • Finally, click on the Apply and OK buttons and then run the Task Scheduler and see if the issue is now fixed.

Option 2 – Try to temporarily disable the anti-virus program

As mentioned, the error could be due to the antivirus program or the Windows Defender Firewall installed in your computer. Thus, disabling them or any security software installed on 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 the Task Scheduler Error 0x80070057 due to interference of antivirus or security programs. Thus, you have to disable both your antivirus program for the meantime and check if it fixes the error or not.

Option 3 – Run the Task Scheduler with an administrator account

Like pointed out, the Task Scheduler Error 0x80070057 may be due to the lack of admin privileges. Thus, you have to log in to an administrator account and try running the Task Scheduler again. It is also recommended that the administrator account you’re going to use as a password when logging in.

Option 4 – Repair the Task Scheduler by deleting corrupted tasks

Note that a single corrupted file can cause big problems so this option is quite important. And for you to delete a corrupted task or any task from the Task Scheduler, you have to use the Registry Editor if you are not able to use the Task Scheduler interface. To do so, follow these steps:
  • Tap the Win + R keys to open the dialog box for Run.
  • Next, type in Regedit and click on OK or tap Enter to open the Registry Editor.
  • Then navigate to this path: ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheTree
Note: In this path, you can see all the tasks that are currently set in the Task Scheduler. And since it would be hard to tell which one of them is corrupted, you have to delete the latest one in Task Scheduler last. But before you do so, make sure that you take note of the ID of the tasks. And for you to get the ID, you have to select the task you wish to delete and double click on the ID string located on your right-hand side, and then copy it in the Notepad.
  • Right-click on the task name and then delete it.
  • After that, delete the very same GUID which you have copied earlier from these folders:
  • ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheBoot
  • ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheLogon
  • ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheMaintenance
  • ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCachePlain
  • ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheTasks
Note: You might not see the same GUID from these folders but if you see it, delete it right away.
  • Next, navigate to this location: C:/Windows/System32/Tasks
  • Delete the very same tasks you just deleted from the Registry Editor.
  • Restart your PC and check if the Task Scheduler is back to its normal state or not.
Read More
Fix Windows is still setting up ... Code 56
If your internet suddenly stops working on your Windows 10 computer and you get an error message saying, “Windows is still setting up the class configuration for this device (Code 56)”, then read on as this post will show you what you can do to resolve it. This kind of issue has something to do with the Network Adapter and you can see this error message in the Properties menu of the corresponding Network Adapter under the Device Manager. This kind of issue could be caused by many things. For one, it could be caused by your VPN connection if you are using one or it could also be due to an outdated driver. Whatever the cause may be, here are some suggestions you have to check out to fix the error.

Option 1 – Check your VPN

When you install a virtual machine or VPN software on your computer, a new setup will be added in the Network Connection settings and helps your computer in using that adapter setting each time the VPN is turned on. Assuming that you are using an Ethernet connection but your system is trying to use another adapter or settings, that’s when issues occur and one of them is the “Windows is still setting up the class configuration for this device” error. To fix it, you can try to disable your VPN temporarily and see if the error is resolved or not and if turns out that your VPN is the culprit, you have to uninstall it and install a new one or its latest version. To uninstall it, follow the steps below.
  • 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 VPN service you are using, select it and then click on Uninstall to remove it.
  • 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 2 – Try to update or rollback or uninstall the Network Adapter drivers

You might also want to update, roll back or disable your Network drivers to fix the “This operation failed as no adapter is in the state permissible for this operation” error.
  • Tap the Win + R keys to launch the Run window and then type in the “devmgmt.msc” command and hit Enter to open the Device Manager window.
  • Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand it.
  • Then right-click on each one of the Network drivers and depending on your preference, you can either select “Update driver”, “Disable device” or “Uninstall device”.
  • After that, restart your PC and see if it helped in fixing the netio.sys Blue Screen error.

Option 3 – Try to run the Network Adapter troubleshooter

To run the Network Troubleshooter, refer to these steps:
  • Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
  • Next, scroll down and select the “Network Adapter” option from the right pane.
  • Then click on the Run Troubleshooter” button.
  • After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.
  • Restart your computer.

Option 4 – Try to reset the Network

You might perform a Network Reset to resolve the problem if none of the three given options above worked. This will reset the entire network configuration including your IP address. To perform Network Reset, follow these steps:
  • Tap the Win + I keys to open Settings.
  • From there, go to the Network and Internet section.
  • Next, scroll down and look for “Network Reset” under the status pane.
  • After that, click on Network Reset and then on Reset now to start resetting the network configuration. Once done, check if it is able to fix the error or not.
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