Fix Downloader.dll Not Found Error in Windows

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.

Bluetooth perhaps is slowly becoming an outdated feature but sometimes you can really used it and need it. By default, in Windows 11 Bluetooth is turned OFF so if you need it, you will need to turn it ON first. Luckily turning it ON is easy and we will guide you through the process

Turning Bluetooth using the Quick Settings menu

The easiest and fastest way to turn the Bluetooth ON is using the quick setting menu:

1. Click on indicator icons located left of date and time in Taskbar
2. Click on the Bluetooth icon (if the icon is not displayed, click on the pencil icon, then click on Add and add Bluetooth icon from the list)
3. Right-click on the Bluetooth icon and select go to Settings
4. Go to Adding a Bluetooth Device to Windows 11 section

Switch it ON via Windows Settings

1. Open Windows settings by using ⊞ WINDOWS + I combination
2. Click on Bluetooth & Devices
3. Inside settings turn Switch to ON beside Bluetooth
4. Click + Add Device large button on top
5. Click Bluetooth
6. Select device in the list of found devices (make sure device is turned ON, it has Bluetooth sharing ON, and that it is in pairing mode)
7. If the device needs the password, type it in
8. When the message Your device is ready to go is showed on the screen click on the Done

Advice on Bluetooth devices

Note that the Bluetooth devices you connect to Windows 11 stay linked to your PC unless you pair them with a different PC, smartphone, or tablet later. After a time, most Bluetooth devices power down automatically to save battery life. To continue where you left off, either power the Bluetooth device up (if it has a power button) or press a button on a keyboard or mouse, and it should automatically turn on and reconnect with your PC. If you’re having trouble connecting your Bluetooth device, make sure that Windows 11 is fully updated and that you’ve installed any drivers that came with your device. Make sure that the device is fully charged or that it has a fresh set of batteries. while Windows is searching. You’ll need to remove the device from Windows 11 first and then attempt to pair it with your PC again.

Removing devices

If you need to remove (un-pair) a Bluetooth device, just open Windows Settings and navigate to Bluetooth & Devices. Locate the name of the device that you want to remove, click the three dots button in the corner of its square and select Remove Device.

Code 21 - What is it?

Code 21 is a Device Manager error code that appears when you try to use a hardware device attached to your computer and the Windows prohibits you from using it.

This is due to the Windows experiences problems loading the device driver. This error message is displayed in the following format:

“Windows is removing this device. (Code 21)”

Solution

Error Causes

Error code 21 means that Windows is in the device removal process and the device has not been completely removed. It occurs when you set a device to be removed and then select the same device to run on your system.

Upon your instructions, Windows start to remove that device and when you on the other hand try to use/access the same device that you selected for removal, it kicks up Code 21.

Further Information and Manual Repair

If you are experiencing error code 21 on your PC, it is advisable to resolve it immediately.

Though this error will not damage your system, but will significantly lower the performance of your PC which is definitely something you don’t want especially if you work on your computer daily and use it to perform important time-sensitive errands.

To repair and resolve, try the methods given below:

Method 1 - Wait for a Few Seconds and Then Press F5

This is one of the best and easiest ways to resolve code 15 on your system. Wait for a few seconds, and then press the F5 key. This will update the Device Manager view and the error will most probably go away.

Method 2 - Restart Your PC

Sometimes error codes may pop up due to temporary glitches. To resolve such errors, a simple reboot of your PC is enough. Shut down Windows and then restart your system.

This is most likely to resolve Code 21. However, if the error still persists then this means the underlying problem for code 21 is deeper than you think. Try method 3 to resolve.

Method 3 - Install DriverFIX

As mentioned earlier, the error code 21 may occur if you have selected a device to remove and then you try to reuse it.

To resolve, you may have to install the device again and the driver for that the reinstalled device. To reinstall the driver without any hassle, simply download DriverFIX.

It is a smart, user-friendly, and intuitive software program designed to resolve driver problems. The program is embedded with intelligent device identification technology which:

• Automatically detects all the appropriate system drivers
• Matches them with the latest available versions
• And then updates drivers according to their compatible versions on a regular basis

Furthermore, it enables accurate installation and ensures that your system is running at its optimal speed.

Other features that this program boasts are full backup and restoration, safe USB management, and ejection.

If nothing works, you can try the full backup and restoration feature and restore your PC to its previous state when it was functioning properly before the error occurred.

DriverFIX creates a backup of all your files and data hedging keeps you from disasters like data loss. It restores the system to the time when it was working properly.

Click here to download DriverFIX on your system and resolve error code 21 today.

As you know, Microsoft Edge is the default web browser in Windows 10 operating system. It is a built-in browser that replaced the ancient Internet Explorer for its performance and features. Aside from being the default web browser, it is also set as a default PDF viewer in Windows 10. So if you open a PDF file, it will be automatically opened in the Edge browser even if you have installed a PDF reader on your computer. However, some users recently reported getting an error that says, “Couldn’t open PDF in Edge, Something’s keeping this PDF from the opening” when they tried to open a PDF file or view an internet link that has a downloadable PDF file in the Edge browser. If you are one of these users, read on as this post will help you troubleshoot the problem and fix it. This kind of error mostly occurs if you have installed other PDF viewers on your computer. They could be interrupting Edge while it tries to open the PDF documents. To fix it, check if Microsoft Edge is set as the default PDF viewer or you could also try to clear its browsing cache. In addition, you could also reset or repair Edge. For detailed instructions, refer to the given options below.

Option 1 – Check if Microsoft Edge is set as the default PDF viewer

The first thing you can do is to check if Edge is set as the default PDF viewer. If it’s not, you have to set it as one to fix the problem.

• Open Control Panel and go to Default Programs.
• Then click on the “Associate a file type or protocol with a program” option.
• Next, select the PDF file option and click on Change program.
• After that, select Microsoft Edge in the pop-up window and then select the “Always use this app to open .pdf” option.
• Now click the OK button to set Edge as the default PDF viewer and then check if you can now open the PDF file in the Edge browser.

Option 2 – Clear the browser cache of Microsoft Edge

• Open Microsoft Edge.
• Then click on the three horizontal dots to open the menu.
• From there, click on Settings. And under Settings, click the “Choose what to clear” button under the Clear browsing data section.
• Next, check all the checkboxes and then click the Clear button to clear the browsing data in the Edge browser.
• Restart Edge.

Option 3 – Reset, repair or reinstall Microsoft Edge via Settings

You can reset, repair or reinstall the Edge browser through Settings. If none of it helped, you can try the following:

• Open File Explorer and then go to this path – C:/Users/YourUsername/AppData/Local/Packages

Note: Before you type in the path in the Address bar, make sure that you put your user account name in place with the “YourUsername”.

• Tap Enter to proceed.
• Next, look for the folder named “MicrosoftEdge_8wekyb3d8bbwe” then right-click on it.
• Click on Properties and uncheck the option “Read-only” under the General tab in the Properties window.
• Click on Apply and then OK to save the changes made.
• After that, look for the MicrosoftEdge_8wekyb3d8bbwe folder again and delete it. And if a prompt stating “Folder Access Denied” appears on your screen, just click on the Continue button to proceed – doing so will delete most of the content inside the folder except for the folder named “AC”.
• Restart your PC.
• Now all you have to do is to re-register Microsoft Edge using PowerShell. In the Start Menu, search “Windows PowerShell”.
• Right-click on Windows PowerShell from the search results and select the “Run as administrator” option.
• Type in this command in the PowerShell windows and tap Enter – Cd C:/Users/YourUsername

Note: Once again, make sure that you key in your user account name in place of “YourUsername.

• After that, type in this command and tap Enter – Get-AppXPackage -AllUsers -Name Microsoft.MicrosoftEdge | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml" -Verbose}
• Restart your PC.

There has been recently discovered in the field of malware targeting Android devices. Affecting more than 10 million users of Android phones, the malware GriftHorse is doing its attacks via phishing and premium services scams. A lot of applications have been discovered that are hosts for this malware and many of them are inside the Google store and available for download. According to Zimperium zLabs, this malware that was recently detected has been doing its scams and attacks even in November of 2020 and has thus far accumulated hundreds of thousands of dollars in its scam. On the surface it looks very harmless, asking for typical permissions like internet access, calls, and other related needed functions, and then it waits. After few months the real attack happens when users get charged with premium service they never subscribed to in the first place.

List of Infected Applications that Carry GriftHorse Trojan

Zimperium zLabs listed out some of the apps with this malware. Users are advised to avoid installing them.

•     Amazing Video Editor
•     Bag X-Ray 100% Scanner
•     Bus – Metrolis 2021
•     Call Recoder Pro
•     Call Blocker-Spam Call Blocker
•     Cinema Hall: Free HD Movies
•     Coupons & Gifts: InstaShop
•     GPS Phone Tracker – Family Locator
•     Fingerprint Changer
•     Fitness Point
•     Free Calls WorldWide
•     Geospot: GPS Location Tracker
•     GPS Phone Tracker – Family Locator
•     Handy Translator Pro
•     Horoscope : Fortune
•     iCare – Find Location
•     iConnected Tracker
•     Instant Speech Translation
•     Lifeel – scan and test
•     My Chat Translator
•     My Locator Plus
•     Plant Camera Identifier
•     Racers Car Driver
•     Safe Lock
•     Screen Mirroring TV Cast
•     Slime Simulator
•     Smart Spot Locator

These are only some of the many infected apps available on the internet. Zimperium zLabs also warned that GriftHorse Trojan exists in over 70 countries worldwide. The infected app quickly changes the language and displays content depending on the user’s IP address.

Recently, several users reported an issue on their Windows 10 computers where the taskbar is not visible when they tried to connect to a computer via Remote Desktop Protocol or RDP. The Remote Desktop Connection feature uses the RDP which allows users to access a computer remotely. This is actually different from the taskbar being hidden automatically until the pointer hovers on it since, in this scenario, the taskbar is completely not accessible which makes using the remote computer entirely difficult, if not impossible. There are several suggestions you can check out to resolve this problem, you can try to restart the process of Windows Explorer via Task Manager or you could clear the cache for multiple processes. You could also try to reinstall the Shell Experience components or show the local taskbar in the Remote desktop. Moreover, you could also try to update, uninstall or roll back the display driver/graphics card driver. For more details, refer to each one of the options given below.

Option 1 – Try to restart the Windows Explorer process

The first option you have to try to fix the problem with the taskbar is to simply restart the Windows Explorer process in the Task Manager.

• Tap the Ctrl + Shift + Esc keys to open the Task Manager.
• Next, go to the Processes tab and find the process of Windows Explorer.
• Once you find it, right-click on it and select Restart to restart its process.
• After that, restart your computer and see if you can now see the Taskbar.

Option 2 – Try clearing the cache of multiple processes

The next thing you can do to resolve the problem is to clear the cache of many processes in your computer. To do so, follow these steps:

• Open the Notepad app and paste the following content in the text area:

@echo off taskkill /f /im explorer.exe taskkill /f /im shellexperiencehost.exe timeout /t 3 /NOBREAK > nul del %localappdata%PackagesMicrosoft.Windows.ShellExperienceHost_cw5n1h2txyewyTempState* /q timeout /t 2 /NOBREAK > nul start explorer @echo on

• After that, tap the Ctrl + S keys to save the changes you’ve made in Notepad and select the “All files” as its file type, and then name it “CacheClearTWC.bat”.
• Next, go to the location where you saved the file using File Explorer and then run it. This will run a couple of batch scripts which will clear the cache of multiple processes in the system.
• Tap the Win + X keys and select the “Windows PowerShell (Admin)” option to open PowerShell as admin.
• Next, execute this command in the command line: Get-appxpackage -all *shellexperience* -packagetype bundle |% {add-appxpackage -register -disabledevelopmentmode ($_.installlocation + “appxmetadataappxbundlemanifest.xml”)}
• After the command has been executed, this will reinstall the Shell Experience components and should fix the problem with the taskbar.

Option 4 – Update, uninstall or rollback the Graphics card drivers

• 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: You also have the option to 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.

What is 0x3D55? As you know, Windows 10 is loaded with various Universal Windows Platform or UWP apps such as the Microsoft News, Weather, Calculator, Windows Mail, and many other applications that are based on the modern UWP platform of Microsoft that was introduced in Windows 10. Each one of these apps has a shared piece of code in the kernel for them to be able to get executed across any device that runs the Windows 10 OS which includes laptops, PCs, 2-in-1 devices, mobile phones, mixed reality headsets, and many more. However, there are times when the runtime information for these apps ends up getting corrupted which causes them not to function as expected and throws errors like the error 0x3D55. This kind of error can be pinned down when the UWP app malfunctions and you can also find an error message in the Event Log that reads, “0x3D55: Package family <App name with ID> runtime information is corrupted”. So if you encounter this error, read on for this post will walk you through fixing it. There are three suggestions you need to check out to fix this error – first, you can try to reset the Microsoft Store cache, second, you can try to re-register or reinstall the problematic app and lastly, run the Windows Store App troubleshooter.

Option 1 – Try to reset the Microsoft Store cache

Just like browsers, Microsoft Store also caches as you view apps and games so it is most likely that the cache is no longer valid and must be removed. To do so, follow the steps below.

• Right-click on the start button and click on Command Prompt (administrator).
• Next, type in the command, “wsreset.exe” and tap Enter. Once you do, the command will clear the cache for the Windows Store app.
• Now restart your PC and afterward, try opening Microsoft Store again and then try to install your app or update your computer again.

Option 2 – Run the Microsoft Store Apps troubleshooter

The Microsoft Store Apps Troubleshooter will help you in fixing the error 0x3D55. 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.

1. Tap Win + I keys again to open the Windows Settings panel.
2. Go to Update & Security and then go to Troubleshoot.
3. On your right-hand side, scroll down to find the Windows Store Apps and then click on the Run the troubleshooter option and see if it fixes the problem.

Option 3 – Try to re-register the UWP app via PowerShell

• First, type “command prompt” in the Start Search and right-click on Command Prompt and then select the “Run as administrator” option.
• Next, navigate to this location in the command line utility: C:/Users/<Insert Username>/AppData/Local/Packages
• After that, execute the “DIR” command to view the list of all the directories in the given location.
• Once the list appears, look for the ID of the problematic app and take note of it.
• Now tap the Win + X key combination or right-click on the Start button and click on the Windows PowerShell (Admin) option.
• If a User Account Control or UAC prompt appears, just click on Yes to proceed and open the Windows PowerShell window.
• Next, type in or copy-paste the following command to re-register the Microsoft Store app and tap Enter:

PowerShell -ExecutionPolicy Unrestricted -Command "& {$manifest = (Get-AppxPackage Microsoft.<YOUR APP ID HERE>).InstallLocation + 'AppxManifest.xml' ; Add-AppxPackage -DisableDevelopmentMode -Register $manifest}"

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

As you know, the functioning of the Windows Sandbox feature is supported by various components in the background of the Windows operating system. And the only way for you to enable the Windows Sandbox feature in your computer is through the Turn Windows features on or off utility. This feature will work directly on the basis of Virtualization which is also supported by Hyper-V. However, there are some reports claiming that some computers have the Windows 10 Sandbox item greyed out in the Turn Windows features on or off utility. Thus, in this post, you will be guided on what you can do to resolve such a problem in your Windows 10 computer. In this kind of problem, you should know that this has something to do with the Second Level Address Translation which is one of the important pillars of how the Windows 10 Sandbox feature functions. Thus, if the Second Level Address Translation or SLAT feature in Windows Sandbox is not supported by the CPU of your computer, there is no way for you to use Windows Sandbox on your computer. On the other hand, if SLAT is supported, then there is definitely something you can do to resolve the greyed-out Sandbox item in Windows 10.

To get started, follow the steps provided below.

Step 1: First, you have to boot into the BIOS of your PC. Step 2: After that, make sure that the following options are set to their respective configurations:

• Hyper-V – Enabled
• VM Monitor Mode – Yes
• Virtualization – Enabled
• Second Level Address Translation (VT-d or RVI) – Enabled
• Data Execution Prevention – Enabled

Step 3: Once you’re done, save the configuration and then restart your Windows 10 computer as usual. Step 4: Once your computer has restarted, you should see the same option in the Turn Windows features on or off utility and it should no longer be greyed out. Then you can now enable the feature and follow the onscreen instructions need to use the feature as best as you can.

The Windows 10 operating system utilizes a variety of measures in order to track your app launches so that it can boost both your start and search results. It can personalize the start menu based on the apps that you use the most on the Start menu as well as the search results. This way, the App Launch Tracking is definitely useful especially when you want to access your favorite and frequently used apps quickly in the Start menu and search results on your Windows 10 computer. On the other hand, Windows 10 provides users with the ability to control their privacy settings in order to protect the privacy of users. Windows 10 users can either opt to enable the app launch tracking to improve the start menu and search menu or opt to disable the app launch tracking in order to prevent the Windows operating system from tracking that you open if you really value your privacy that much. Whichever setting you prefer, you need to change the privacy control settings as well as make some tweaks in the Windows Registry in order to turn on or turn off the app launch tracking feature.

Option 1 – Turn off or turn on app launch tracking via Settings

• Go to Settings and click on Privacy.
• After that, toggle On the “Let Windows track app launches to improve Start and search results” option on the right side of the page under the General Settings to enable the app launch tracking feature.
• And of course, if you wish to disable the app launch tracking feature, simply toggle Off the “Let Windows track app launches to improve Start and search results” option on the very same page under General Settings.
• After that, close the Settings window.

Note: Keep in mind that when you disable the app launch tracking feature, the “Show most used app” setting will either be grayed out or labeled as “Disable” on your Windows 10 computer. Thus, if you want to keep viewing the most used apps, just re-enable the app launch tracking feature if you have disabled it.

Option 2 – Turn off or turn on app launch tracking via Windows Registry

Before you proceed, make sure to create a System Restore point

• 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, navigate to the following path:

HKEY_CURRENT_USERSOFTWAREMicrosoftWindowsCurrentVersionExplorerAdvanced

• After that, right-click on the Advanced folder and then click on New to create a new 32-bit DWORD value.
• Name the newly created DWORD as “Start TrackProgs” and set its value to “1” to enable the app launch tracking feature.
• If you want to disable the app launch feature, set “0” as the value instead of 1.
• Now click OK and restart your computer.

Take note that you still have to create a 32-bit DWORD value even if you are using a 64-bit Windows computer.

Each time you execute a command on your computer, it takes into account a number of files and space for the code in the background for the command to be executed. Thus, executing the command is not that easy which is why you could encounter some errors along the way due to various limitations or poor allocation of memory, and so on. One of the errors you might encounter when executing a command on Windows 10 and Windows Server is the “Not enough storage is available to process this command”. There are several potential fixes you can check out to fix this error. To fix this error, you can try to delete the temporary files in your computer, run the DISM tool or apply some registry tweaks. For more details, refer to each one of the given options below.

Option 1 – Try to delete the temporary files

The error could be caused by some temporary or junk files in your computer and so you need to clear them up to fix the problem. You can achieve that using the Storage Sense feature.

• Open Setting > System > Storage from the WinX Menu.
• From there, you will see a list of all the local and connected storage devices along with the details on the free space. Make sure that Storage Sense is on.
• Next, find a link that says “Free Up Space” and click it to open.
• After that, a screen which is the built-in program in Windows 10 will appear and will scan your computer for the following junk files so you can free up disk space:
  • Windows Upgrade Log Files
  • System created Windows Error Reporting Files
  • Thumbnails
  • Temporary Internet Files
  • Previous Windows Installation Files
  • Delivery Optimisation Files
  • DirectX Shader Cache
• Choose the files you want to get rid of and then click on the remove files option. Note that you’ll have an idea of the total size as you select any of the junk files listed above.
• Now go to the “Free Up Space Now” section and click the Clean now button. This will get rid of all the temporary or junk files in your computer and should hopefully fix Error 1310.

Option 2 – Run the DISM tool

You can also run the DISM Tool as it could also help in fixing the “Not enough storage is available to process this command” error in Windows 10. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth” that could help in fixing error 0x80246019.

• You can run the DISM tool via Advanced Startup Options or you could boot your computer into a Clean Boot State and then select Command Prompt.
• 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 and try again. If it didn’t work, you can try to use the “/StartComponentCleanup” parameter: Dism /Online /Cleanup-Image /StartComponentCleanup

Option 3 – Try to use the Registry Editor

The memory range allocated for the tasks and commands to be executed is associated with the IRPStackSize DWORD. Thus, to fix the error, you need to extend the range by applying some registry tweak. Before you proceed, make sure that you create a System Restore point first. Once you’re done, follow these steps:

• Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and tap Enter to open the Registry Editor.
• Next, navigate to this registry key: ComputerHKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesLanmanServerParameters
• From there, look for the DWORD named “IRPStackSize” and right-click on it. If you can’t find this DWORD, just right-click on any empty space and select New > DWORD (32-bit) Value.
• Input “IRPStackSize” as the DWORD name and double click on it and set its Value data to be greater than its default value. Note that the maximum value allowed is “0xc” and the range starts from “0x1”.
• Now click on OK and exit the Registry Editor and then restart your computer and see if the error is fixed.