Fix We couldn’t install some updates

Error Code 0x80070005 – What is it?

Error code 0x80070005 is also known as the “Access Denied” error code because it prevents Windows users from accessing updates on their machines. This error code exists due to a lack of permissions on one’s system files or registry, permissions which are necessary for the updates via Windows Update to complete successfully. Error code 0x80070005 affects multiple versions of the Windows operating system including Windows 8, 8.1, and Windows 10.

Solution

Error Causes

The lack of files or registry permissions which result in the presence of error code 0x80070005 on your device may occur based on several reasons. The most common of these relates to the existence of malware programs on your machine. Malware can disrupt and change system files which are required for the update process to occur. Thus, this error code requires a systematic approach to first find missing or corrupt files, as well as cleaning up malware programs that could be preventing your machine from accessing updates.

Further Information and Manual Repair

Windows 10 users can repair error code 0x80070005 by implementing manual repair procedures. These procedures include the installation of tools like SubInACL.exe which enable users to access information about registry keys and files, thus detecting issues that may be preventing them from completing the update process in Windows Update.

These manual repair methods are listed below with clear instructions that even average Windows users can understand and follow. However, if you attempt the procedures and experience any issues that prevent you from successfully fixing error code 0x80070005, contact a Windows repair technician. Also, consider downloading an automated tool since these tools often help users fix PC performance issues that cause error codes to occur within various versions of the Windows operating system.

Method One: Log on as Administrator to Install Updates

By logging on as an administrator, Windows users may be able to access updates via Windows Update and thereby fix error code 0x80070005 in Windows 10. Follow the steps below to complete this manual repair method.

• Step one: Click the Search bar near the Start button
• Step two: Type User Accounts in Search
• Step three: Select User Accounts
• Step four: Click Manage User Accounts, then type in password if prompted to do so

Once you are logged on as an administrator, go to Settings to access Windows Update. You will be given the option to install the latest updates. Select this option and wait for the process to be completed. If error code 0x80070005 reoccurs, however, you will need to proceed to manual repair method two which requires that you scan for malware.

Method Two: Scan for Malware

This method is very simple. As you scan for malware on your machine, you will be able to detect any malicious programs that may be preventing you from installing updates on your device. This will in turn enable Windows users to clean up their system, fix the error code, and prevent others from occurring.

First, be sure you have a viable antimalware program on your machine. Scan for viruses and other harmful programs using this third-party software. Another option is to run Windows Defender on your machine.

Once you’ve completed the scan and error Code 0x80070005 moved any malware that may be present, attempt to install updates via Windows Update. If the problem causing error code 0x80070005 in Windows 10 is resolved, you will be able to install the updates. However, proceed to the next manual repair method if the error code remains on your device after you have scanned and removed malware programs.

Method Three: Install SubInACL Tool

The SubInACL tool enables Windows users to access security details and other information regarding files and registry permissions. Use this tool to fix files and registry permissions by following the instructions below.

• Step one: Download the SubInACL tool via Microsoft’s official website
• Step two: Run program as administrator
• Step three: Restart machine
• Step four: Go to Settings, Update & security, then Windows Update
• Step five: Reattempt installation of updates

Once you’ve been able to run the SubInACL tool and fix files or registry permissions, your machine should be able to access updates. If error code 0x80070005 reoccurs, however, you may need to contact a Windows repair technician to verify if issues unrelated to permissions are causing the error code to occur.

Method Four: Download an Automated Tool

If you wish to always have at your disposal a utility tool to fix these Windows 8 and other related issues when they do arise, download and install a powerful automated tool.

When your computer is slow, you don’t have much choice but to wait until it gets done with a task at its own pace, albeit a slow one. So if you want to switch user accounts on your computer a couple of times daily, then a slow computer can get really irritating. What makes system processes slow is that the accounts have some programs or applications running and resources allocated to them. And besides, if your computer is already low on performance, it will kill the natural fluidic flow of the user. But worry not, for this post will guide you in switching user accounts with the help of some minor tweaks in your Windows 10 computer. To disable or enable Fast User Switching, you have two methods to do that using the Registry Editor and the Group Policy Editor. Either way, refer to the instructions laid out below.

Option 1 – Enable or disable Fast User Switching via Registry Editor

• Tap the Win + R keys to open the Run dialog box.
• After that, type “Regedit” in the field and tap Enter to open the Registry Editor.
• Next, go to this registry key: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesSystem
• Then right-click on System and select New > DWORD (32-bit) Value and name this newly created DWORD as “HideFastUserSwitching”.
• Now double click on it. If you want to enable Fast User Switching, input “0” as the value, and if you want to disable it, input “1” as its value.
• Restart your PC to successfully apply the changes made.

Option 2 – Enable or disable Fast User Switching via Group Policy Editor

Take note that this option will not work if you are using the Windows 10 Home edition since the Group Policy Editor does not come with Windows 10 Home. Refer to the steps below to enable or disable Fast User Switching using Group Policy Editor.

• Tap the Win + R keys to open the Run dialog box and then type in “gpedit.msc” in the field and hit Enter to open the Group Policy Editor.
• Next, navigate to this path inside the Group Policy Editor: Computer ConfigurationAdministrative TemplatesSystemLogon
• Now double click on the configuration listing labeled as “Hide entry points for Fast User Switching” to open the configuration page.

Note: On the configuration page, you will see the following description:

“This policy setting allows you to hide the Switch User interface in the Logon UI, the Start menu, and the Task Manager. If you enable this policy setting, the Switch User interface is hidden from the user who is attempting to log on or is logged on to the computer that has this policy applied. The locations that the Switch User interface appears in the Logon UI, the Start menu, and the Task Manager. If you disable or do not configure this policy setting, the Switch User interface is accessible to the user in the three locations.”

• From there, you can choose to enable or disable the Fast User Switching depending on your preferences. After you’ve selected, click OK and exit the Group Policy Editor.
• Now restart your PC to apply the changes made successfully.

As of late, many users reported getting an error in Windows Sandbox that has an error code of 0x80070015. According to users, they encountered this error when they tried to start Windows Sandbox. Based on the error code, it seems that there are some problems with the supporting services of Windows Sandbox that trigger the error. It is possible that these services are misconfigured or that they are outdated and have to be updated. Here’s the complete message of the error:

“Windows Sandbox failed to start. Error 0x80070015. The device is not ready. Would you like to submit feedback about this issue?”

If you are one of the users who encountered this kind of error in Windows Sandbox, then you’ve come to the right place as this post will help you sort this problem out. All you have to do is follow each one of the options provided below.

Option 1 – Make sure that all the supporting processes and services of Windows Sandbox are running properly

If running Windows Sandbox as an administrator didn’t fix the error, you have to ensure that all related processes for Windows Sandbox are running properly. To do that, follow these steps:

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• Next, from the list of services, look for the following services in the given order:
  • Network Virtualization Service: (Startup type: Manual)
  • Virtual Disk: (Startup type: Manual)
  • Hyper – V Virtual Machine: (Startup type: Manual)
  • Hyper – V Host Compute Service: (Startup type: Manual)
  • Container Manager Services: (Startup type: Automatic)
• After you find the aforementioned services, restart each one of them.
• Once done, try to open the Windows Sandbox again and see if the error is fixed or not.

Option 2 – Try to install any pending Windows Updates

If the second option still didn’t work, then you might want to check Windows Updates on your computer and see if there are any pending Windows Updates you have to install. All you have to do is go to the Windows 10 Settings app and then go to the Windows Updates section and click on the “Check for updates” button to check if there are any pending updates that are needed to be installed. This could fix the Windows Sandbox Error 0x80070015.

Option 3 – Try to run Windows Sandbox as an admin

• In the Start Menu, scroll down until you see the entry for the Windows Sandbox.
• Then right-click on it and select More and then select the “Run as administrator” option to open it with admin privileges.
• Next, if a User Account Control or UAC prompt pops up, just click on Yes to proceed.
• You should now be able to open the Windows Sandbox without the error. However, if the error persists, proceed to the next given option below.

There are times when the WMI Repository gets corrupted which results in the Provider Load Failure. To resolve this issue, you need to repair or rebuild the WMI Repository in your Windows 10 computer. In this post, you will be guided on how exactly you can do that. In case you don’t know, the WMI which stands for Windows Management Instrumentation is a set of specifications from Microsoft to consolidate the management of devices and applications in a network. The WMI is a database that stores meta-information and definitions for WMI classes. Using only these, the conditions of the systems can be known. You can find the WMI Repository in %windir%System32WbemRepository. It provides end-users with the status of the local or remote computer system. Keep in mind that you must not use this on the Server 2012 Cluster machine. Although there are command-line tools that can fix or restore the Windows Management Instrumentation repository. However, Microsoft suggests that it’s better if you verify if there is corruption. Here are a list of errors as well as permission issues you might encounter:

• Unable to connect to root default or rootcimv2 namespaces. It fails with the error code “0x80041002” pointing to “WBEM_E_NOT_FOUND.”
• 0x80041010 WBEM_E_INVALID_CLASS
• When you open Computer Management and Right Click on Computer Management (Local) and select Properties, you get the following error: “ WMI: Not Found” or it hangs trying to connect
• Trying to use wbemtest , and it hangs
• Schemas/Objects missing
• Strange connection/operation errors (0x8007054e)

To verify if there is corruption, you can try running the following command in an elevated Command Prompt:

winmgmt /verifyrepository

 After you enter the command, if there is a response saying, “repository is not consistent”, then the repository has an issue. If not, then something else is causing the problem. Since you are certain that corruption exists in the WMI repository, then here are some suggestions you need to check out to repair or rebuild the WMI repository.

Option 1 – Try to reset WMI Repository

• Type “command prompt” in the Start Search and right-click on Command Prompt from the search results and then select “Run as administrator”.
• After opening Command Prompt with admin privileges, type and enter this command: winmmgmt /salvagerepository

The command you entered is used when the winmmgmt command performs a consistency check. So if an inconsistency is detected, it will rebuild the repository.

• Next, execute this command to see if the WMI repository now comes back as consistent: winmgmt /verifyrepository

This command will perform a consistency check on the WMI repository.

• If it states that the WMI repository is not consistent, then you need to type and enter this command: winmgmt /resetrepository

This command is used to reset the repository to its initial state when the operating system was first installed.

Option 2 – Try to force recover the WMI Repository

The WMI Repository comes with a built-in self-recovery process so when the WMI service restarts or detects any corruption, it will automatically trigger the self-recovery procedure. This can happen in two ways:

• AutoRestore: This will use the backup images if the Volume Shadow copy or VSS backup is turned on.
• AutoRecovery: The rebuilding process will generate fresh images of the WMI repository based on the registered MOFs. The MOFs are available in the registry located at HKLMSoftwareMicrosoftWBEMCIMOM: Autorecover MOFs

Note: Autorecover MOFs is a key so double click on it to check its value. On the other hand, if the self-recovery procedure does not work, you can try to use the force-recovery process instead. How? Refer to these steps:

• First, you need to check the reg key value is empty or not under this registry path: HKLMSoftwareMicrosoftWBEMCIMOMAutorecover MOFs
• If the reg key value is empty, you have to copy-paste the reg key value from another computer. Just make sure that it’s from the System which is equivalent to the computer in question.
• Next, type and enter this command: Winmgmt /resetrepository
• After you enter the command, if you get an error that says, “WMI repository reset failed. Error code:0x8007041B. Facility: Win32”, then you have to stop all the Dependency Services on the WMI service by running the following commands:
  • net stop winmgmt /y
  • Winmgmt /resetrepository

This should fix the problem.

The touchscreen feature inside Windows 11 is a pretty good thing but sometimes can be very impractical. The screen can easily and constantly get dirty due to fingers touching it all the time and there are users that do not wish or want to have this feature at all. If you are one of the mentioned users and for any reason, you do not wish to have a touchscreen-enabled then sit back and relax, we have you covered in this tutorial on how to fully disable touchscreen inside Windows 11.

Turn off touchscreen via device manager

1. Click on the Windows Search icon in the taskbar
2. Type Device Manager
3. Click on Device Manager from the list of results
4. Inside locate Human Interface Devices and click on the right arrow
5. In the list, find HID-Compliant Touch Screen and select Disable Device
6. Click on Yes to confirm

Disable it via Windows Terminal

1. Right-click on the Windows icon in the taskbar
2. Click on Windows Terminal (admin)
3. Inside run this command: Get-PnpDevice | Where-Object {$_.FriendlyName -like '*touch screen*'} | Disable-PnpDevice -Confirm:$false

Conclusion

No matter which method you prefer, both of them will disable the touch screen inside Windows 11. Thank you for reading trough article and I hope to see you again. Take care.

If you are frequently experiencing slow loading of folders in your Windows 10 computer, Downloads folder for instance, then you’ve come to the right place as this post will help you resolve such issue. Slow loading of folders is a common problem faced by many users even when they are using the latest hardware like SSDs. So if you experience the same thing, be it with the Downloads folder or other folders on your computer, there is a way to resolve that issue and make the folder load faster. Slow-loading means when you attempt to open the folder, it takes a couple of seconds before it displays its contents. In such cases, you’ll see a green loading address bar that says “Working on it” which can get quite annoying especially if you are in a hurry. And if you notice that this only happens in the Downloads folder, there certainly is something wrong. This kind of problem can occur on SSDs and normal hard drives. The main reason behind the occurrence of this problem is that the folder may have been optimized for viewing photos or other media formats which is why it takes quite longer than usual to load all the files and their thumbnails. However, since the Downloads folder usually contains all kinds of files like documents, zip files, audio/video files, etc. there is no need to optimize this folder for media files only because doing so is only going to make the Windows File Explorer slow in loading the folder’s contents and thumbnails which does not exist for many files.

Option 1 – Configure the Downloads folder

• Right-click on the Downloads folder or the folder you’re having trouble opening.
• Then click on Properties and go to the Customize tab.
• After that, click on the “Optimize this folder for” option in the drop-down menu.
• Next, select General items from the drop-down which might have been set by default to Pictures or Video.
• You also have the option to apply this template to all the subfolders, that is if your folder has any subfolders.
• Now apply the settings and restart Windows Explorer.

Note: Once you’ve completed the steps above, it should now make the folder content display a lot faster than before. Now try to open the Downloads folder which would not take much time as you will see the changes right away.

Option 2 – Run CHKDSK to check your disk for errors

When it comes to some issues concerning the hard drive or removable devices, there is a utility in Windows that might help which is called “chkdsk”. This error check utility can help with several issues in the system including File System Error -2147219196.

• Tap the Win + S keys to open the Search box.
• Then type “command prompt” in the field and from the search results that appear, right-click on Command Prompt and select “Run as administrator”.
• After opening an elevated command prompt, copy and paste the following command and hit Enter:

chkdsk /r /f

• Now if you are prompted to run CHKDSK after your reboot your PC, just tap Y and reboot your PC.
• If CHKDSK is not able to find any errors, tap the Win + E keys and navigate the access window. From there, right-click on the concerned drive and click on Properties.
• After opening Properties, click on the tab Tools and then click on the “Check” button under the Error-checking section.
• Wait until the process is completed and then restart your computer.
• Once your computer has restarted, try accessing the file and check if the error persists.

If you were trying to install a program on your Windows 10 computer but encounter an error instead that says, “Error 1310, Error writing to file: <PATH>, Verify that you have access to that directory” then read on as this post will guide you on how you can fix it. This kind is a fairly common type of error encountered by many Windows users. You can get this error when you try to install certain programs like Excel, AutoCAD, Adobe Photoshop, and some other Adobe products on Windows. One of the most likely causes for this error is that the required files or location is already used by some other software which means that Windows finds that you are trying to overwrite a software that is already installed. Aside from that, it could also occur if the program installer does not have access to write to that directory. To fix Error 1310, here are some potential fixes that could help.

Option 1 – Clear up temporary or junk 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
  • The 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 – Reinstall the program in a Clean Boot State

You can also troubleshoot Error 1310 in a Clean Boot state. It could be that there are some third-party applications in your computer that's 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” 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 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 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 un-registering and re-registering the Windows Installer Module fixed the problem or not.

Option 4 – Take ownership of the location where you want to install the app

The next thing you can try to do is to take ownership of the particular folder as this worked for some users who experienced the same problem. But before you do that, you have to create a System Restore Point first, once that’s done, proceed to the given steps below.

• First, locate the concerned folder and right-click on it then select Properties.
• Next, click on the Edit button in the Properties window and click OK to confirm if you got a User Account Control elevation request.
• After that, select user/group from the permission windows or click on the Add button to add another user or group. It would be best if you add “Everyone” to give permission.
• Then check “Full Control” under the “Allow” column to assign full access rights control permissions.
• Now edit the permission to Full Control for “Everyone”.
• Click OK to save the changes made and then exit.
• Finally, try to install the application again.

There are several kinds of errors you could encounter when you are running Windows 10 on a virtual machine. The Windows OS knows the difference between booting up in a standalone computer or in a virtual machine. This is why some specific drivers and system capabilities are used while emulating the Windows OS on software and during this phase, there are times when the System Preparation may throw up an error that says, “A fatal error occurred while trying to sysprep the machine”. This kind of error arises due to a race condition wherein the Sysprep command tries to stop the Microsoft Distributed Transaction Coordinator or MSDTC service and the VMware tool tries to start the MSDTC service. You may also see the following messages logged in the Setuperr.log file:

• [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing ‘C:Windowssystem32msdtcprx.dll,SysPrepDtcCleanup’, returned error code -2146434815[gle=0x000000b7]
• [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = -2146434815[gle=0x000000b7]
• [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep cleanup providers; hr = 0x80100101[gle=0x000000b7]

To fix the 0x0f0082, 0x0f0070, 0x0f00a8 Sysprep errors, you can check out two potential fixes. First, you have to check the status of the MSDTC service and the second one is to check the settings in the Windows Registry. Note that these fixes are proven to be effective on many users and apply to several versions of Windows, including Windows 10.

Option 1 – Check the status of the MSDTC service via Command Prompt

As mentioned, the error could be caused by the malfunctioning of the MSDTC service or it. Thus, you have to uninstall and reinstall the MSDTC service to resolve the problem and you can do that using Command Prompt. Follow the steps below.

• In the Start Search, type “command prompt” and from the results, right-click on Command Prompt and then select the “Run as administrator” option to open it with admin privileges.
• If a User Account Control or UAC prompt appears, just click on Yes to proceed.
• Once you’ve opened Command Prompt, execute this command: msdtc –uninstall
• The command you just entered will uninstall the MSDTC service. After that, you need to execute this second command to reinstall the service: msdtc –install
• Now exit Command Prompt and check if the error is now fixed.

Option 2 – Check the Registry settings

• Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and click OK or hit Enter to open the Registry Editor.
• After opening the Registry Editor, navigate to this registry path: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionSoftwareProtectionPlatform
• From there, look for a DWORD value that’s named “SkipRearm” and double click on it.
• Then change its value data to “1”.
• Restart your computer to apply successfully apply the changes made and check if it was able to fix the error.

Recently, a lot of users reported getting several error messages when they upgraded their Windows 10 computers. One of these error messages users encountered during a Windows 10 upgrade is the Error 0x8007002C-0x4001E. if you are one of the users who is facing this error, read on as this post will help you fix it. When you encounter this error, you will see the following error message on your screen:

“We couldn’t install Windows 10 We’ve set your PC back to the way it was before you started installing Windows 10 0x8007002C-0x4001E, The installation failed in the SECOND_BOOT phase with an error during PRE_OOBE operation.”

To resolve the 0x8007002C-0x4001E, The installation failed in the SECOND_BOOT phase error, here are some suggestions that might help.

Option 1 – Try flushing the SoftwareDistribution and Catroot2 folders

You have to stop a couple of services such as BITS, Cryptographic, MSI Installer, and Windows Update Services. And to do that, you need to flush the contents in the SoftwareDistribution folder. The Software Distribution folder in the Windows operating system is a folder that can be found in the Windows directory and is used to store files temporarily which might be required to install the Windows Update on your PC. Thus, it is required by the Windows Update and maintained by WUAgent. Aside from that, it also contains all the Windows Update History files and once you delete them, you will most likely lose the Update history. As a result, the next time you run the Windows Update, it may result in a longer detection time.

• Open the WinX Menu.
• From there, open Command Prompt as admin.
• Then type in the following command – don’t forget to hit Enter right after typing each one of them.

net stop wuauserv net start cryptSvc net start bits net start msiserver

• After entering these commands, it will stop the Windows Update Service, Background Intelligent Transfer Service (BITS), Cryptographic, and the MSI Installer
• Next, go to the C:\Windows\SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.

After flushing the SoftwareDistribution folder, you need to reset the Catroot2 folder to restart the services you just stopped. To do that, follow these steps:

• Type each one of the following commands.

net start wuauserv net start cryptSvc net start bits net start msiserver

• After that, exit Command Prompt and restart your computer, and then try to run Windows Update once more.

Option 2 – Select the Keep your files option

You can also select the option to perform an in-place upgrade and opt for the “Keep my files” option during an installation as it might make the process a lot smoother and if you need to perform a clean install, you can do so once the setup is completed.

Option 3 – Try to run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the 0x8007002C-0x4001E, The installation failed in the SECOND_BOOT phase error. 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.

Option 4 – Try to run Microsoft’s online troubleshooter

Aside from the Windows Update Troubleshooter, you can also run the online troubleshooter of Microsoft as it can help you with Windows 10 upgrade errors.

Option 5 – Perform a clean install

If none of the options worked, you can try to clean install Windows 10. Just make sure that you have the ISO from the official Microsoft Website and then a bootable USB drive to install Windows 10 again. Take note that this will delete all the data from your drive where Windows 10 was installed previously.

Oobesttings error is the blue screen of death error caused by some faulty settings inside the Windows registry. The good news is that this is not a hard error to fix and if by any chance you are one of the unfortunate people getting this dreaded annoying error, please do keep reading because we have several things that you can do in order to eliminate this issue from your computer.

Reboot your system

This is the easiest and straightforward solution and can work sometimes since if the system has not been properly rebooted in a while memory could be filled with various processes and it can trigger oobesettings error. A simple restart of the system can solve the issue by decluttering files and emptying memory.

Scan and repair with SFC

If rebooting the system was not helpful and sadly you still receive an error then let's scan and repair system files by using Windows built-in tool SFC. In order to use this, we will have to run the command prompt in elevated administrator mode. Follow instructions closely. First click on the search icon on the taskbar and type in CMD The command prompt will show as a search result, on the right side click on Run as administrator. Once it opens type in following command: sfc /scannow and press ENTER Wait for the process to finish completely and restart your device after.

Repair the system registry

If the SFC scan has not repaired the issue then we will move to the next solution that involves repairing the system registry itself. Please note that you need to follow step-by-step for provided instructions since playing with the system registry can cause some serious issues if not done properly and can even render the system unstable. That being said, let's begin: Press ⊞ WINDOWS + R to open Windows run dialog Type inside regedit and press ENTER Inside registry editor locate the following key: HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Session Manager/ Memory Management. and click on it to see properties Inside the properties right-click on CommitLimit value and choose delete. Confirm with yes. Close registry editor and reboot your computer.

Reset Windows 11

If even clearing key inside the registry editor has not helped next step would be to reset the system itself. Press ⊞ WINDOWS + I to open Windows settings and click on System on the left. Inside on the right part click on Recovery In recovery click on the button next to Reset this PC that says Reset PC Choose between keep my files and remove everything (a better option is remove everything, but be sure that you have all your files on a separate drive backed up) Choose between Cloud Download or Local reinstall. Click on next to confirm choices and after that on Reset to start the reset process. Follow onscreen instructions until it is fully done.