How to Fix Windows 10 Error 0x8000222

The Windows Defender program can both scan and monitor almost the entire folder on a Windows 10 computer. So if you have a folder that may have files that could trigger an alarm to Windows Security, then it would be better if you add an exclusion to Windows Security. Note that it is okay to do this as long as you’re certain that the contents of the folder you want to exclude are safe and that Windows Defender is only throwing out warnings for nothing. This way, Windows Defender won’t scan those folders in the future. And besides, there are also some Windows folders and files that you may exclude from the Antivirus scans, especially if you want to save your scan time. This kind of feature also comes in handy when you trust a file type or folder or any process that you believe is safe but the Windows Security considers as malicious. To exclude a folder or a file or process or a file type from the Windows Security scan, here are some steps you can follow. Make sure to do them carefully. Step 1: Search for “Windows Security” in the Search box and then click on it from the search results to open it. Step 2: Next, click on Virus & threat protection > Manage settings > Add or remove exclusions. Step 3: After that, on the next screen, click on Add an exclusion > Folder. It will show you a list that includes File, Folder, File Type, and Process. Step 4: Now click on “+Add and exclusion” on the next window and then select a folder you want to exclude and click OK to add it in the Exclusions list. Step 5: Click on the down arrow button to remove it and then click on the Remove button. Note: If you want to only ignore a few file types, it’s better if you configure your antivirus program to ignore these files with a specific extension. This way, it will ignore all of them no matter what their location is. Also keep in mind that when you select a folder, all the subfolders in it will also be excluded from the scan. Thus, you need to understand what you’re about to do. Once you’re done excluding the folder, it is recommended that you protect the folder using the Controlled Folder Access since this folder is not monitored for threat. The Controlled Folder Access will ensure that an external program does not alter it. This way, you can be sure that even though this folder is not included in the scan, it is still secure.

If you are trying to install or reinstall a program on your Windows 10 computer but encountered an error instead that says, “Fatal error, Installation fails, Installation ended prematurely because of an error”, then you’ve come to the right place as this post will guide you how you can fix it. This kind of error is most likely caused by some files that may have been left behind by the previous installation of the program. Each time a program is uninstalled, it leaves behind its files and if the uninstallation process wasn’t completed properly, then it would result in errors like the

“Fatal error, Installation fails, Installation ended prematurely because of an error”.

Moreover, this kind of error is a generic one that can also occur with any software reinstallation or installation. And to fix this error, there are several suggestions you must check out. You can try to install or reinstall the program in a Clean Boot State or restart the Windows Installer Service. You could also try to re-register the Windows Installer Service or re-register the VBScript.dll file.

Option 1 – Install or reinstall the program in a Clean Boot State

It is possible that there are some third-party applications in your computer that are preventing the program from getting installed and to isolate this possibility, you need to boot your computer in a Clean Boot State and then try installing the program again. Putting your computer in this state can help you identify which program is the culprit and thus isolates the problem. In a Clean Boot state, your computer will start using only the pre-selected minimal set of drivers and startup programs. Note that you have to disable and enable one process at a time.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” 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.)
• After you’ve set your computer into a Clean Boot State, make sure that you’re signed in as administrator and then try to install the program again.

Option 2 – Try to restart the Windows Installer Service

The next thing you can do to fix the problem is to restart the Windows Installer Service. To do this, follow these steps:

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and then hit Enter to open the Windows Services Manager.
• Next, look for the Windows Installer service among the list of services shown.
• Once you found it, right-click on it and open its Properties.
• From there, click on the Stop button and then click on the Start button.
• But if it isn’t running, then just click on the Start button.

Option 3 – Try to unregister and re-register the Windows Installer Module

• Tap the Win + R keys to open the Run dialog box.
• Then type the “msiexec /unregister” command and hit Enter to unregister the Windows Installer Module.
• Next, type the “msiexec /regserver” command and hit Enter to re-register the Windows Installer Module.
• Now restart your computer and see if unregistering and re-registering the Windows Installer Module fixed the problem or not.

Option 4 – Try to re-register the vbscript.dll file

You may have to re-register the vbscript.dll file using the regsvr32.exe before you can successfully install the program and fix the error. The Regsvr32 tool is a command-line utility that can be used to register and un-register the OLE controls like DLL and ActiveX (OCX) control in the Windows operating system. Follow the steps below to use it.

• Open Command Prompt as admin from the WinX menu.
• Next, type regsvr32.exe vbscript.dll in the elevated Command Prompt and hit Enter to execute the command. This will re-register the affected DLL file using the Windows operating system tool, regsvr32.exe.
• You should see a message saying, “DllRegisterServer in vbscript.dll succeeded” if the Regsvr32 tool was able to run successfully. After that, try to install the program again and see if it now works.

If you encounter a Windows Update error with an error code 0x80070652 and an error message saying, “ERROR_INSTALL_ALREADY_RUNNING”, then it indicates that there was a previous Windows Update that was not installed successfully. This kind of Windows Update error typically happens when it gets stuck and so to resolve it, here are some suggestions that might help.

Option 1 – Restart your computer and try installing the Updates again

You can restart your computer and then try installing the updates once again. There are instances when a simple restart resolves Windows Update errors. Thus, after you restart your computer, check for updates once again and see if you’re still getting the error or not.

Option 2 – Try running the Windows Update troubleshooter

You might also want to run the Windows Update Troubleshooter as it could also help in fixing Windows Update error code 0x80070652. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 3 – Try downloading the Windows Update that failed

If the Windows Update that has failed 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.

Option 4 – Try to restart the Background Intelligent Transfer Service

The Background Intelligent Transfer Service or BITS is a part of the Windows Update service and is the one that manages the background download of Windows Update, as well as scans for new updates and so on. And if Windows Update is experiencing some problems, you can try restarting BITS but make sure that you have admin privileges to do so.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “services.msc” in the field and hit Enter to open Windows Services.
• From the list of Services, look for the Background Intelligent Transfer Service and double-click on it to open Properties.
• After that, you need to set the Startup type to “Automatic (Delayed Start) and click on Apply.
• Now click the Stop button to stop BITS and then click the Start button to restart the service.
• Click OK to save the changes made and then restart your PC.

Option 5 – Try to update Windows after a couple of minutes or an hour

There are times when the issue is from Microsoft’s end. It could be that there’s some issue with Microsoft’s server so it would be better if you give it a couple of minutes or an hour or so before trying to run Windows Update again.

The Blue Screen of Death error or BSOD is definitely not an issue to face on your computer. Many users, if not all, have already experienced this headache at least once. One of these BSOD errors is the ATTEMPTED EXECUTE OF NOEXECUTE MEMORY error. The bug check error code for this is 0x000000FC and is usually caused by outdated or faulty drivers. In some cases, it could also be caused by an error in the Random Access Memory or RAM. This kind of error in the RAM might be physical, based on drivers, or even some kind of unwanted malware. So basically there are lots of possibilities why this particular BSOD error pops up. If you are currently facing this BSOD error, read on and carefully follow the suggestions given below but before you do that, make sure to create a System Restore point just in case something goes wrong. This way, you can always undo those changes using the System Restore point. Once you have that covered, proceed to the options given below to fix the ATTEMPTED EXECUTE OF NOEXECUTE MEMORY error.

Option 1 – Try updating Windows 10 with all the security patches and updates

You might be able to fix the ATTEMPTED EXECUTE OF NOEXECUTE MEMORY error by simply updating your Windows 10 computer with all the security patches and updates. To do so, go to Settings then proceed to the Windows Update section > Update & Security > Windows Update, and then click on the Check for Updates option. After you do that, it will automatically find and install all the latest security patches and feature updates from Microsoft.

Option 2 – Try updating all your drivers

From time to time, drivers get corrupted or outdated so it’s no surprise that they conflict with the operating system and cause errors like the ATTEMPTED EXECUTE OF NOEXECUTE MEMORY BSOD error. To fix the problem, you need to update all your drivers. Follow the steps below to update your 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. If you see a red or yellow sign that shows up against the driver, right-click on the driver’s name and select “Update Driver Software” or “Uninstall”. And if you find any “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.
• Restart your PC.

Note: You also have the option to go directly to the website of your graphics card manufacturer and check if there’s a new update – if there is, download it.

Option 3 – Try running a Memory Check using Windows Memory Diagnostic

As mentioned, this error might be caused by some issues in the memory. To resolve it, you need to run the Memory Check on your Windows 10 PC. Refer to these steps to do so.

• Tap the Win + R keys to open the Run dialog box.
• Then type “mdsched.exe” in the field and hit Enter to open the Windows 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 4 – Try using the System File Checker via Command Prompt

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files that might be causing the ATTEMPTED EXECUTE OF NOEXECUTE MEMORY BSOD error. 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.

Mapping network drive has many benefits in terms of speed and ease of access of files via network. It lets you access the hard drive over the whole network like it was the hard drive inside your PC case. In order to easily and quickly map a folder as a network drive follow the guide below.

1. Open File Explorer
2. Click on the three dots icon in the Toolbar
3. Select Map Network Drive
4. Click the Drive drop-down menu
5. Select a driver letter that you wish to assign as a network drive
6. In the folder field enter network device and share name (click on browse to see all devices on local network)
7. Check the box beside Reconnect at sign-in if you wish to automatically connect to a network drive on Windows startup
8. Check Connect Using Different Credentials if you wish to connect to a network drive using different credentials that one used to login into Windows.
9. Click Finish

After finishing setting Windows 11 will try to connect to the network drive and if successful drive icon will appear inside File Explorer and the drive will open up to see its content. If for any reason it cannot connect try checking user credentials, cables, network adapters, etc.

If you always use Google Chrome when browsing the internet, then you might have come across an error saying, “This webpage is not available, DNS PROBE FINISHED BAD CONFIG”. If you do, then this problem certainly has something to do with the DNS since any error code which has “DNS” in it points out a network issue in the computer. Getting the DNS_PROBE_FINISHED_BAD_CONFIG error indicates that your computer is not able to connect the website because the Domain Name Server or DNS wasn’t able to resolve the website name into IP address or it is not available at all. So in this guide, we’ll help you sort out this issue in Chrome on your Windows 10 PC.

Option 1 – Check the Network Cables and restart your router then reconnect

The most obvious thing you can do first is to try checking if the network cables connected to your computer or router are properly connected or not. If it turns out that some network cables are not connected properly, then it’s probably why you’re getting the DNS_PROBE_FINISHED_BAD_CONFIG error in Chrome. And if your computer is connected via Wi-Fi, you need to make sure to restart your router once. In addition, you can also forget the Wi-Fi your computer is currently connected to and then try reconnecting again to see if it would work.

Option 2 – Flush the DNS and reset TCP/IP

Flushing the DNS and reset TCP/IP could also help in fixing the DNS_PROBE_FINISHED_BAD_CONFIG error in Chrome. To do so, refer to these steps:

• Click the Start button and type in “command prompt” in the field.
• From the search results that appear, right-click on Command Prompt and select the “Run as administrator” option.
• After opening Command Prompt, you have to type each one of the commands listed below. Just make sure that after you type each command, you hit Enter
  • ipconfig /release
  • ipconfig /all
  • ipconfig /flushdns
  • ipconfig /renew
  • netsh int ip set dns
  • netsh winsock reset

After you key in the commands listed above, the DNS cache will be flushed and the Winsock, as well as the TCP/IP, will reset.

Option 3 – Try to remove the Proxy

You can also try to remove the Proxy as it might also help you in fixing the DNS_PROBE_FINISHED_BAD_CONFIG error. Here’s how you can do it:

• 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 – Change the DNS

Try to use the Google Public DNS If the first option didn’t work, you can try to use the Public DNS by Google and see if it can help fix the DNS error. You have to modify the DNS settings in your system explicitly and use the DNS IP addresses.

• The first thing you have to do is right-click on the network icon in the Taskbar and select Network and Sharing Center.
• Next, click on the “Change Adapter Settings” option.
• After that, search for the network connection that you are using to connect to the internet. Note that the option might be “Wireless Connection” or “Local Area Connection”.
• Right-click on your network connection and click on Properties.
• Then select the new window to choose the “Internet Protocol 4 (TCP/IPv4)” option.
• After that, click on the Properties button and click the checkbox in the new window for the option “Use the following DNS server addresses”.
• Type in “8.8.8” and “8.8.4.4” and click OK and exit.

Option 5 – Clear Chrome’s browsing data

If your browsing data in Chrome hasn’t been cleared for some time now then that might be the reason why you’re suddenly getting the DNS_PROBE_FINISHED_BAD_CONFIG error when you browse the web. To fix this error, you need to clear your web browsing data. Refer to the following steps to do so.

• Tap the Ctrl + Shift + Delete buttons to go to the Clear browsing data section in Chrome.
• Next, set the time range to “All time” and tick all the boxes and then click on the Clear data button.
• After that, restart the Chrome browser and try to open the website you were trying to open earlier.

Option 6 – Try running the Chrome Cleanup tool

In case you don’t know, there is actually a built-in malware scanner and cleanup tool in Chrome that helps you get rid of any unwanted ads, pop-ups, and even malware, as well as unusual startup pages, toolbars, and other things that could affect the performance of the browser.

STOP 0x00000000 Error Code - What is it?

Stop 0x00000000 error code is a type of a Stop error popularly known as a blue screen of death error code. This is a critical error. It can pop up while loading or using the Windows program on your PC. When this error occurs, the computer screen turns blue and you, the user, get locked out of the program. Furthermore, it can also result in sudden system shut down or system freeze. If not fixed timely, the error may start to pop up more and more frequently which then may lead to complete system corruption and system crash.

Solution

Error Causes

The two most common causes for the STOP 0x00000000 error code are:

• Malware infection
• Registry corruption

This is a fatal system error and must be resolved immediately. Delay may lead to system crashes and data loss. And recovering lost data is not easy.

Further Information and Manual Repair

Though this is a fatal error the good news is that it is easy to resolve. To repair the STOP 0x00000000 error on your system, here are some methods that you can try:

Method 1 - Use System Restore to Bring Your Computer Back to its Previous State

To resolve this error on your system, try using the System Restore tool. Use this tool to bring your computer back to its previous state. The Windows System Restore utility is one of the most valuable recovery tools. To use it, simply type System Restore in the search box. Once you find it, click on it and select a restore point to bring your PC back to its normal state. To activate changes, reboot the PC.

Method 2 - Scan for Viruses

If the underlying cause of the Stop 0x00000000 error code is related to malware infection, then you must download a powerful antivirus to resolve it. Run it to scan your entire PC. Make sure you remove all types of malware including adware, spyware, viruses, and Trojan. Once your PC is malware-free, the error will be fixed in no time.

Method 3 - Clean and Repair the Registry

The registry is an important part of the PC. It stores practically all the activities you perform on your system. It saves all the files including both important and unnecessary files such as junk files, cookies, internet history, bad and invalid entries. If these obsolete and unnecessary files are not deleted frequently and keep on accumulating it takes up all the registry space and corrupts it. This results in registry errors like runtime and BSoD errors and sometimes may also lead to disk fragmentation. To resolve it is advisable to repair the registry. This can be done manually but that will take too much time and also require technical expertise. However, another way to resolve it is to download Restoro. This is a user-friendly PC Fixer with a powerful registry cleaner. It removes all obsolete and unnecessary files, cleans the registry and repairs the damaged files, thereby removing the error right away. Click here to download Restoro and resolve Stop 0x00000000 today!

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.

Sysdata.xml Error Code - What is it?

To develop a good understanding of the Sysdata.xml error code, it is first important to learn what is sysdata.xml file and its function. Sysdata.xml is a type of XML file. The .XML file extension is an Extensible Markup Language file. XML-based formats have now become the default for many office productivity tools including Microsoft Office and LibreOffice. Furthermore, it has also come into common use for the interchange of data over the internet. Sysdata.xml error code usually pops up when .XML based applications are unable to run and crash while loading. This is a type of BSoD (Blue Screen of Death) error code. Common symptoms include:

• System freeze
• The screen turns blue
• Sudden system shut down

Solution

Error Causes

The Sysdata.xml error code is triggered due to multiple reasons such as:

• Faulty hardware
• Malware or viral infection
• Registry issues

No matter what the reason may be, it is advisable to fix this error code right away without any delays. This is a fatal error and can result in a system crash and loss of data. And recovering valuable lost data is the hardest.

Further Information and Manual Repair

Here are some of the effective and easy do it yourself methods to resolve this error on your system:

Method 1: Fix Faulty Hardware

Hardware issues may arise due to many reasons like manufacturing issues or voltage fluctuations. Electrical storms can cause power surges which may affect the hardware causing it to fail. The best way to resolve this is to download the latest drivers for the problematic devices or alter the device configuration in the BIOS setup program.

• To reconfigure the BIOS simply restart your PC and before Windows starts, press Del Key to access your BIOS.
• Now find the factory reset option.
• Select the option and press the button to load your factory defaults.
• After that save changes and confirm your selection.
• Reboot your PC to activate the changes.

Method 2: Scan for Viruses

Sometimes viruses and malware can disguise themselves in the .XML files which can cause them to get corrupted. To resolve the issue, it is advisable to download a powerful antivirus and scan your entire PC for viruses. Remove the detected viruses to resolve the Sysdata.xml error on your system.

Method 3: Repair the Registry

If the registry is not cleaned frequently, it loads with unnecessary and obsolete files like the junk files and cookies. These files clutter and damage the registry and eventually corrupt it and the important files like .XML files stored in it. To resolve the issue it is recommended to download Restoro. It is a user-friendly and powerful PC Fixer embedded with a registry cleaner. It scans your entire PC for registry-related errors and removes them immediately. It cleans the cluttered registry and restores the damaged files thereby repairing the issue right away. Click here to download Restoro.

Although the UWP platform is still new, it is working efficiently and significantly and it’s apparent that Microsoft is betting big on it. It helps developers in building applications for Windows 10 that are more modern and beautiful as well as responsive with the help of the .NET Core and XAML. However, all things considered, it still isn’t perfect and it could still encounter some errors. One of these errors is the Windows.UI.Xaml.Markup.XamlParseException UWP app error. This particular error can occur to any Universal Windows Platform or UWP application and according to security experts, it is due to some XAML parsing error. To fix this error, you can try to reinstall the faulty program or check its privacy settings. You can also run both the Program Compatibility and Windows Store Apps troubleshooters as well as run System Restore. For more information, check out the given options below.

Option 1 – Try to reinstall the faulty application

If you encounter this error in an application that is not a system-related one, then you can just uninstall it from the Windows 10 Settings app and then reinstall it again from the Microsoft Store. On the other hand, if it is a system application like the Camera or Calculator app, you can just uninstall and reinstall it using a PowerShell script.

Option 2 – Try to check the Privacy Settings of the concerned app

You might also want to check if all the Privacy Settings required for a certain application are configured properly as it could also cause issues like the Windows.UI.Xaml.Markup.XamlParseException UWP app error.

Option 3 – Try to run the Program Compatibility Troubleshooter

You might also want to run the Program Compatibility Troubleshooter. This built-in troubleshooter is available in the Windows Update & Security section. From there, select Troubleshoot. This will find a list of programs for you and since you have already downloaded the driver files, just click on Not Listed located at the top of the program list. After that, browse and select the driver files and then let the program do its job. In addition, you can try to run the Windows Store apps troubleshooter as it can also help you resolve the problem.

Option 4 – Run System Restore

If you have recently made changes in your computer’s settings, you could also run System Restore to fix the Windows.UI.Xaml.Markup.XamlParseException UWP app error. How? Refer to these steps:

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