Delete large System Error Reporting files

If when hovering over the upgrade icon on the taskbar you get:

Your version of Windows 10 would reach the end of service soon, Click to download a newer version of Windows 10 to stay supported. or An unsupported version of Windows will no longer receive software updates from Windows Update. These updates include security updates that can help protect your PC from harmful viruses, spyware, and other malicious software which can steal your personal information. Windows Update also installs the latest software updates to improve the reliability of Windows—such as new drivers for your hardware.

and you are unable to perform updates then this guide is for you. There are several things you can do to fix this issue presented here, it is advisable to follow them in a way how they are presented for best performance and system safety.

1. Run setupdiag

   Download and run Setupdiag from the official MICROSOFT website. SetupDiag is a standalone diagnostic tool that can be used to obtain details about why a Windows 10 upgrade was unsuccessful. It works by examining Windows Setup log files to determine the root cause of a failure to update or upgrade the computer. Once the scan is completed, check the generated log files. The SetupDiagResults.log will be generated and saved in the same folder where you downloaded Setupdiag. Open SetupDiagResults.log using Notepad. You may need to take a look at these folders:
   • \Windows\Panther
   • \$Windows.~bt\sources\panther
   • \$Windows.~bt\Sources\Rollback
   • \Windows\Panther\NewOS
   If there are any issues or conditions that are blocking the upgrade, they will be listed here.

2. Edit TargetReleaseVersionInfo Registry key

   Press ⊞ WINDOWS + R to open the run dialog In run dialog type Regedit and press ENTER Locate: HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate Locate two DWORD files, if they do not exist, create them as: TargetReleaseVersion TargetReleaseVersionInfo Set the value of TargetReleaseVersion to 1 If you are stuck on Windows 10 1909 and want to upgrade to Windows 10 20H2 now, you need to set the value for TargetReleaseVersionInfo to 20H2 Reboot the computer

3. Use Windows 10 update assistant

   Visit Microsoft.com and hit the ‘Update now’ button visible on the page Download tool and run it Click on Update now to start the upgrade process

Error Code 0x80070643 – What is it?

Error Code 0x80070643 or Windows Update error code affects various versions of the Windows operating system, including Windows 10. Error code 0x80070643 usually occurs due to corruption within the .Net Framework. When this occurs, users will be unable to install updates they have downloaded on their PC.

Solution

Error Causes

Error codes within Windows occur for many reasons including corrupt system files, viruses, and lack of space on your PC. In terms of error code 0x80070643 in Windows 10, the cause usually relates to a problem with the .NET framework or errors within one’s registry.

Further Information and Manual Repair

To solve error code 0x80070643 in Windows 10, users will need to employ various manual repair methods. These methods seek to fix core problems that result in the error being present on your device in the first place. Thus, the methods include the use of the .Net Framework Repair tool, resetting Windows Update components, or running a clean boot.

Note that the instructions provided in this article must be followed correctly, as making changes to your computer via these manual repair methods can result in serious problems if mistakes are made. Consider a Windows repair technician if you are unable to complete the steps mentioned in the manual repair methods below. Note, failure to rectify this error might result in other error messages, such as error code 0xc004fc03

Method One: Run the .Net Framework Repair Tool

As error code 0x80070643 may be triggered by issues related to the .Net Framework on your machine, it’s important that you download the .Net Framework Repair tool. This tool, as the name suggests, helps to repair errors it detects within the setup or updates associated with the framework.

The tool is available on the official Windows site. Download the tool and follow the instructions provided. Once you’ve downloaded the .Net Framework Repair tool, run it and wait until it fixes all problems detected within the framework.

Afterward, reboot your computer and check to see if Windows Update is functioning properly. If the error code reoccurs, proceed to another solution by implementing the second manual repair method listed in this article.

Method Two: Reset Windows Update Components

This method is the most technical of all the methods mentioned in this article. It will require that Windows 10 user access Command Prompt and make modifications to the Windows registry – an area of the operating system which stores important information, settings and other details regarding hardware and programs installed on your machine. Follow the steps carefully and be sure to back up the registry before proceeding with this manual repair method.

Step one: Type Command Prompt in the search box near Start, then select Command Prompt (Admin).

Step two: Select Yes as soon as the User Account Control box appears.

Step three: Stop Windows Update service, the BITS service, and Cryptographic service by typing the following commands:

net stop bits

net stop wuauserv

net stop appidsvc

net stop cryptsvc

Step four: Be sure to press Enter after typing each command.

Step five: Type the following command, then Enter to delete qmgr*.dat files:

        Del "%ALLUSERSPROFILE%Application DataMicrosoftNetworkDownloaderqmgr*.dat"

Step six: Press enter after typing the following command:

        cd /d %windir%system32

Step seven: Reregister the files for BITS and Windows Update that you stopped in step three. To do this, type the following commands, selecting Enter after each command:

        regsvr32.exe atl.dll

        regsvr32.exe urlmon.dll

        regsvr32.exe mshtml.dll

        regsvr32.exe shdocvw.dll

        regsvr32.exe browseui.dll

        regsvr32.exe jscript.dll

        regsvr32.exe vbscript.dll

        regsvr32.exe scrrun.dll

        regsvr32.exe msxml.dll

        regsvr32.exe msxml3.dll

        regsvr32.exe msxml6.dll

        regsvr32.exe actxprxy.dll

        regsvr32.exe softpub.dll

        regsvr32.exe wintrust.dll

        regsvr32.exe dssenh.dll

        regsvr32.exe rsaenh.dll

        regsvr32.exe gpkcsp.dll

        regsvr32.exe sccbase.dll

        regsvr32.exe slbcsp.dll

        regsvr32.exe cryptdlg.dll

        regsvr32.exe oleaut32.dll

        regsvr32.exe ole32.dll

        regsvr32.exe shell32.dll

        regsvr32.exe initpki.dll

        regsvr32.exe wuapi.dll

        regsvr32.exe wuaueng.dll

        regsvr32.exe wuaueng1.dll

        regsvr32.exe wucltui.dll

        regsvr32.exe wups.dll

        regsvr32.exe wups2.dll

        regsvr32.exe wuweb.dll

        regsvr32.exe qmgr.dll

        regsvr32.exe qmgrprxy.dll

        regsvr32.exe wucltux.dll

        regsvr32.exe muweb.dll

        regsvr32.exe wuwebv.dll

Step eight: Reset Winsock in Command Prompt by typing the following command, then selecting Enter:

      netsh winsock reset

Step nine: Configure proxy settings in Windows 10 with the following command, then press Enter:

     netsh winhttp reset proxy

Step ten: To restart the BITS, Windows Update, and Cryptographic service, type the following commands, then press Enter:

        net start bits

        net start wuauserv

        net start appidsvc

        net start cryptsvc

Step eleven: Install the latest Windows Update Agent.

Step twelve: Restart your machine.

Once you’ve restarted your PC, check Windows Update to verify if the error code is resolved. You should now be able to access the latest updates on your device. However, if a problem has arisen and the error code reoccurs, you will need to proceed with a Clean Boot.

Method Three: 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.

Raptor Lake, a new and upcoming Intel 13th generation CPU will break the 6GHz barrier for the first time ever in normal working mode, overclocked mode in Intel words will go as high as 8GHz. CPU will be 15% faster than Alder lake in single-threaded tasks and a stunning 41% faster in multi-threaded workloads.

The current world record for overclocking is 8.72GHz done with AMD FX-8370 and Intel is aiming at breaking that record with Raptor Lake, of course, this kind of extreme overclocking will require some top-of-the-line nitrogen cooling systems.

Raptor Lake will run on the current LGA 1700 socket, so you will not need to buy another motherboard for CPU and they will also be manufactured on a 10nm process which means that you will need to take care of cooling and power supply if they really go over 6GHz.

Mid-range Intel Core i5-13600K processor will come with 14 cores inside and 20 threads running at a maximum P-core frequency of 5.1GHz, while Core i7-13700K will have 16 cores and 24 threads and run on 5.3GHz max P-core frequency. Best i9-13900K will come packed with 24 cores, 8 of them will be P-cores, and the rest 16 are E-cores, and 32 threads. It will reach 5.4GHz frequency but it was stated it can go to 5.8GHz with Thermal Velocity Boost.

After this statement, we can clearly see that the 6GHz breaker CPU will probably be an i9 special KS variant. In other words, specially tested and picked existing i9 running at higher speeds as was with Alder Lake as well where normal i9-12900K ran at 5.2GHz while i9-12900KS was running at 5.5GHz.

You have the option to choose to configure the Network to Private or Public when you set it on Windows 10 PC. On the other hand, if the option to change the Network from Public to Private goes missing in Windows Settings then this post will surely help. You can find this setting under Settings > Network and Internet > Ethernet and appears when you click on it. If you are not able to see the option to change the network profile, then you either can’t open the settings, or the option to change it has been disabled. To resolve this issue, you can either use the Registry Editor or Windows PowerShell. Refer to the options given below for more details.

Option 1 – Change the Network Profile via Registry Editor

Changing the Network Profile can be done using the Registry Editor. But before you proceed, make sure that you create a System Restore Point first just in case. Refer to the steps below to do so.

• Tap the Win + R keys to open the Run dialog box.
• Then type “Regedit” in the field and hit Enter to open the Registry Editor.
• After that, navigate to this key: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionNetworkListProfiles
• Now expand the Profiles key folder located in the left pane to see one or more folders.
• Next, expand each one of these folders and look for the “Description” sub-key which should match the name of your network.
• After you find the Description sub-key, look for another sub-key named “Category” and double click on it to open it.
• Now change its value from “0” to “1” to change the Network Profile from Public to Private.

Option 2 – Change the Network Profile via Windows PowerShell

Aside from the Windows Registry, you can also use Windows PowerShell in changing the Network Profile from Public to Private and so on. Take note that you have to use PowerShell with admin privileges. Just refer to the steps below to do so.

• Tap the Win + X keys and then select the “PowerShell (Admin)” option.
• Next, click on Yes if the User Account Control prompt appears.
• After that, execute the commands listed below. Hit Enter right after you key in each one of them.
  • Get-NetConnectionProfile
  • Set-NetConnectionProfile -InterfaceIndex <index number> -NetworkCategory Private

Note: Since every Network Profile has an index number, you can check the label “Name” to identify the network that you want to change.

If you encountered an error message saying, “We couldn’t find any drives, To get a storage driver, click Load driver” when you try to install Windows in a VirtualBox machine, then you’ve come to the right place as this post will guide you in fixing this error. This error message is displayed on the screen where you have to choose a partition to install the guest operating system. This error is most likely due to the lack of correct settings as well as a corrupted virtual disk. To fix this error, you have to remove existing storage devices, create a new storage device and select the correct ISO file.

For complete instructions, follow the given steps below.

Step_1: The first thing you have to do is remove all the existing Storage devices and since this option is already available in VirtualBox by default, there is no need for you to install any third-party software. Step_2: After that, open VirtualBox and select the virtual machine and then click the Settings button. Step_3: Next, switch to the Storage section and on your right-hand side, you will see “Controller: SATA” and two other sub-labels. From there, select Controller: SATA and then click on the red cross button that says, “Remove selected storage controller”. Step_4: Now click on the Add new storage controller icon and select the “Add SATA Controller” option from the given list. Step_5: Afterwards, click the “Add hard disk” button and select the “Create new disk” option, and then you have to create a new virtual disk for your virtual machine. Step_6: Verify if you have selected Dynamically allocated while you create the virtual hard disk. Once the process is completed, you will get a “.vdi” file in the list. Step_7: Next, click on the “Add optical drive” button and select the “Choose disk” option. Here, you have to select the ISO file and if you can find an ISO file in the given list, select it from there, else, you have to click the Add button and navigate to the folder where the ISO file is located. Step_8: Once you’re done, click the OK button and boot your virtual machine. You should see options instead of the “We couldn’t find any drives, To get a storage driver, click Load driver” error message. If you see the options, you can now create a new partition and start the installation process of the Windows operating system in the VirtualBox machine without any problem.

One of the most useful tools in the Windows 10 operating system is the Windows Media Creation tool. This tool is used to download and install the latest version of Windows 10. However, there are times when you might encounter some issues while using this tool. One of these issues is the Error code 0x80072F76 – 0x20016. If you encounter this error, you will see the following error message during setup:

“We’re not sure what happened, but we’re unable to run this tool on your PC. If you continue experiencing problems, reference the error code when contacting customer support – Error code: 0x80072F76 – 0x20016.”

This kind of error in the Media Creation tool could be due to an interrupted download or unstable internet connection, and many more. To fix it, you can run the Windows Update troubleshooter or try using another browser to download the tool to another location. You can also try changing the DNS or the ISP connection or use the Windows 10 Update Assistant as well as delete the $Windows.~BT & $Windows.~WS folders. Check out the given suggestions below to fix the Media Creation Tool Error code 0x80072F76 – 0x20016 in your Windows 10 computer.

Option 1 – Try to run the Windows Update troubleshooter

Windows 10 have various troubleshooters that can help you resolve many system issues. So if you’re dealing with Windows Update errors like Error Code 0x80072f76 – 0x20016, you can run the Windows Update troubleshooter to resolve it. To run the Windows Update troubleshooter, 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 2 – Try using a different browser to download the tool to another location

You could also use another browser in downloading the tool and place it in a different location on your computer but if you do not have another browser, you can just install one and then download the same tool to another location like the Desktop.

Option 3 – Try to change the DNS

• 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 and then check if the Media Creation tool error is fixed.

Note: If you are using a third-party proxy service, you have to disable it.

Option 4 – Try to change the ISP connection

There are times when the connection to the Microsoft servers is interrupted due to some glitch or it could also be blocked by your Internet Service Provider or ISP. To rule out this possibility, you can try to change your computer’s internet connection and then see if it fixes the problem.

Option 5 – Try to use the Windows 10 Update Assistant

There’s another tool you can use as an alternative to the Media Creation tool. It is called the Windows 10 Update Assistant. This tool can also help you download and install Windows updates seamlessly.

Option 6 – Try to delete the $Windows.~BT and $Windows.~WS folders

From time to time, the Windows Update files also get corrupted which can cause some problems and conflicts when downloading and installing a Windows Update. To fix this, you need to delete the $Windows.~BT & $Windows.~WS folders in your computer.

Updating your Windows 10 computer isn’t always as easy as it should be since there are times when you might encounter some errors along the way. One of these errors is the error code 0x80246017 that comes with the error message “WU_E_DM_UNAUTHORIZED_LOCAL_USER”. According to Microsoft, the cause of this particular Windows Update error is that “The download failed because the local user was denied authorization to download the content”. So if you got this error when you tried updating your computer, read on as this post will provide you some suggestions on how you can fix it. Before you troubleshoot the problem using the options given below, make sure that you are logged in as administrator. If you are already logged in as an administrator, follow each one of the options carefully.

Option 1 – Try to check the status of some Windows Update Services

• Tap the Win + R keys to open the Run dialog box.
• Next, type “services.msc” in the field and hit Enter or click OK to open Services.
• From the list of Services, look for the following services and make sure that their Startup type is as follows:
  • Windows Update – Manual (Triggered)
  • Background Intelligent Transfer Service – Manual
• After that, check if the Service status of the listed services above is set to Running. If they’re not, click on the Start button to start these services and then check if you can now enable the Windows Update service or not.

Option 2 – Try to grant Full Control of the System Volume Information directory

• First, tap the Win + X key combination and then select Command Prompt (Admin) from the given menu.
• After opening Command Prompt with admin privileges, type the following command and tap Enter to execute it:

c md.exe /c takeown /f "C:System Volume Information*" /R /D Y && icacls "C:System Volume Information*" /grant:R SYSTEM:F /T /C /L

• Once the command is executed, it will run a batch of tasks and will show each one of their statuses on the command line window and once they’re done, exit Command Prompt.
• Now restart your computer and see if it fixed the problem or not.

Option 3 – Try to disable your antivirus program or Firewall

Disabling the antivirus program or Firewall or any other security software installed in your computer is always a good idea you can try when the Windows Update process does not go smoothly. So before you try updating your computer again, make sure to disable the antivirus or security program and once the Windows Update is done, don’t forget to enable the antivirus program back again.

Option 4 – Try running the DISM tool

You can try running the Deployment Imaging and Servicing Management or DISM tool to fix the Windows Update error. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt with admin privileges.
• Then type in the following commands and make sure to hit Enter right after you type each one of them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • exe /Online /Cleanup-image /Restorehealth
• After that, wait until the process is finished and do not close the window as the process will probably take a couple of minutes.
• Once it’s done, restart your computer.

Option 5– Run the Windows Update Troubleshooter

If the DISM tool didn’t work in fixing the error, you could also try running the Windows Update Troubleshooter as it could also help in fixing any issues related to Windows Update including the Windows Update error code 0x80246017. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 6 – Run Microsoft’s online troubleshooter

Running Microsoft’s online troubleshooter might also help you fix the Windows Update error code 0x80246017. This online troubleshooter is known to help in fixing Windows Update errors, it scans your computer for issues that might be causing the problem and then fixes them automatically.

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.

Valve has officially announced that Steam Deck will be compatible with Windows 11 despite TPM 2.0 Microsoft requirements. From the beginning, Deck was announced like a mini handheld PC device. Powered with new Steam OS 3.0 based on Linux. However, besides out-of-the-box OS it was also stated that Deck will be a personal device meaning that other PC-based operating systems could be installed on it and even run your typical applications in it. Since Microsoft announced Windows 11 hardware requirements, specifically the TPM 2.0 requirement many users voiced concern that Steam Deck will not be able to connect to Windows 11 TPM 2.0 is something that Microsoft requires for every internal and hardware component that is to connect on a Windows 11 device. This is to ensure that only trusted devices would be included in the array of a PC setup and avoid any problems like malicious hardware injecting software into a system. This would also minimize the compromise Windows would have, as unverified or untrusted devices connect to a Windows PC. However, Valve and AMD are ensuring us that Deck will not have any issue connecting to a PC running Windows 11 or even if you wish to transform Deck itself into a Device running Windows 11.

If you were trying to open File Explorer but it suddenly stopped working and you encounter an error message that states, “An attempt was made to reference a token that does not exist”, read on as this post will guide you in fixing this problem. This problem was initially reported after the April Update and Microsoft was able to fix it right after correcting the build. However, this effort seems futile for some users as recently, some reported getting the same error when they try to open not just Windows File Explorer but also with utilities like Microsoft Management Console or MMC, Visual Studio, Task Manager, Printer, Recycle Bin, etc. Two of the most likely causes of this error are a troublesome Windows Update and corrupted system files. Whatever the cause is, here are some suggestions you can follow to fix the “An attempt was made to reference a token that does not exist” error.

Option 1 – Try to re-register the problematic DLL file

You may have to re-register the ntdll.dll file using the regsvr32.exe before you can successfully install the program and fix the ntdll.dll file crash error. The Regsvr32 tool is a command-line utility that can be used to register and unregister 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 the following commands 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.
  • exe /[DLL file]
  • exe [DLL file]

Note: Replace “[DLL file]” with the name of the DLL file that was pointed out in the error.

• After you execute the given commands, 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.

Option 2 – Replace the DLL file from a trusted source

• First, you need to get the new DLL file from another computer with preferably the same file version number.
• After that, you need to boot your PC into Safe Mode and navigate to the paths listed below and then replace the file using a USB drive or other external storage devices.
  • x86: This PC > C:/Windows/System32
  • x64: This PC > C:/Windows/SysWOW64
• Next, type “cmd” in the Cortana search box and right-click on Command Prompt, and select “Run as administrator” to open it with administrator privileges.
• Now type the “regsvr32 ntdll.dll” command and hit Enter.
• Restart your PC and check if the error is now fixed.

Option 3 – Perform a System File Checker scan

The System File Checker or SFC scan could detect and automatically repair damaged system files that could be causing the “An attempt was made to reference a token that does not exist” error to pop up. 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. 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 and hit Enter.

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

Option 4 – Try reverting back to the previous build of Windows

This kind of error might have something to do with a Feature Update so you can try to revert your computer to a previous build of Windows 10 as it could help you fix the problem. In this case, it would better if you refrain from updating your Windows 10 computer until this problem is completely resolved by Microsoft.