CLR20R3 error while launching an Application

The Microsoft Photos app is a useful tool that allows users to view, edit, as well as create videos on their Windows 10 computers. Although it works just fine most of the time, there are some instances when you might encounter some issues when using it. One of these issues is when you cannot save media from the Photos app after you’ve edited an image. This is most likely related to a permission issue. However, according to some users, they got the error where the edited media file can’t be saved. When you encounter this kind of error, you will see the following error in your Photos app:

“It looks like you don’t have permission to save changes to this file. Try saving a copy instead.”

There are several options you can explore to resolve this error. You can try updating the Microsoft Photos app or verify the ownership of the destination folder. You can also re-register and reinstall the app. For more detailed instructions, make use of the options provided below.

Option 1 – Try to update the Microsoft Photos app

The first thing you can do to fix the problem is to update the Microsoft Photos app.

• Open the Microsoft Store and click on the three horizontal dots for the menu located on the top right portion of the window to see the options.
• Next, select Downloads and updates and then click the Get updates button in the top right. This will install any pending updates for all the apps including the Microsoft Photos app using the Microsoft Store.

Option 2 – Try to verify the ownership of the destination folder

The next thing you can do to fix the error is to verify the ownership of the folder because chances are, the location where you’re trying to save the file might not have enough permissions to read and write the file to the disk. Thus, you need to take ownership of the folder by following these steps:

• Type “command prompt” in the Windows Search bar and then right-click on the relevant search result and select “Run as administrator”.
• After that, if a User Account Control or UAC prompt appears, just click on Yes to proceed.
• Next, type and enter this command: TAKEOWN /F <path>
• Note that the <path> is the location of the folder or file in File Explorer.
• Now type and enter this second command: ICACLS <path> /grant administrators:F
• Finally, once the command has been executed, restart your computer and then see if you can now access the folder or file.

Option 3 – Try resetting the Photos app

If the first option of restarting the background process of the Photos app didn’t work for you, you can try to reset the Photos app so that it will use the default factory settings. Note that this option works when you are experiencing this issue after making a couple of changes in the Photos app.

• To get started in resetting the Photos app, open the Windows 10 Settings.
• Then go to Apps > Apps & features.
• After that, scroll down until you see the Photos app option – click on it and open its Advanced options.
• From there, you will see the Reset button, click on it and click and then click on it once more to confirm.

Note: The process may take a couple of minutes to complete. Once it’s done, open the pictures again using the Photos app.

Option 4 – Try reinstalling the Photos app

If none of the first two options given above worked, then you might want to consider reinstalling the Photos app. Unlike what most users think, it isn’t really that hard reinstalling preinstalled apps as you have the Windows PowerShell for that. To use this program in reinstalling the Photos app, follow these steps:

• Open the Windows PowerShell program with admin privileges and key in the following command:

Set-ExecutionPolicy Unrestricted

• After that, execute this second command to re-register and reinstall the Microsoft Photos app.

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml"}

Note: In the command given, do not forget to replace the “PackageFullName” with the actual package name for the Photos app. After executing the command, it will uninstall the Photos app from your computer so you need to install it again from the Windows Store by simply looking for it. Once you found it, just click on install to start the installation process.

The Windows Subsystem for Linus, also known as WSL, is a useful and excellent tool for developers. However, it isn’t without flaws as users can still encounter some errors when using it. One of these errors is the error code WslRegisterDistribution, 0x8007019e,0x8000000d. Although it seems like the error is have something to do with the installation of WSL, it could be a false positive since some users who’ve installed WSL still encountered the same problem. Here’s the context of the error:

“Installing, this may take a few minutes… WslRegisterDistribution failed with error: 0x8007019e/0x8000000d Error: 0x8007019e/0x8000000d The parameter is incorrect. Press any key to continue.”

Error code 0x8007019e or 0x8000000d could be due to the absence of supporting Windows 10 features since the error does not even let one use the WSL-based command line. If you are one of the users facing this problem, then you’ve come to the right place as this post will provide you with a couple of suggestions to fix it. There are two options you can check out to fix the problem, but before you do that, you need to make sure that the Windows Subsystem for Linux feature is enabled. The two options include enabling WSL using the “Turn Windows features on or off” option and using the Windows PowerShell.

Option 1 – Try to enable the WSL using the “Turn Windows features on or off” option

• To get started, search for “Turn Windows Features on or off” in the Start Search and click on the appropriate result to open a dialog box.
• After that, you will see a populated list in the dialog box and from there, look for the “Windows Subsystem for Linux” option.
• Once you find it, select OK. This will search and install the system files needed and ask you to restart your computer.
• Restart your computer. The Linux distro should now work without any trouble.

Option 2 – Try to use Windows PowerShell

The next thing you can do to fix the error code 0x8007019e or 0x8000000d is to use Windows PowerShell.

• Tap the Win + X keys and click on the “Windows PowerShell (Admin)” option to open Windows PowerShell as admin.
• After that, execute this command to enable the Windows Subsystem for Linux feature: Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
• The command you entered will start to search for the required system files and install them.
• If prompted, type “Y” to restart your computer. This should fix the problem.

Error Code 16 - What is it?

Code 16 is a type of Device Manager error code. Windows XP users are most likely to encounter it. This error pops on XP systems that are running legacy or not plug-and-play hardware.

Error code 16 is displayed in the following format:

‘Windows cannot identify all the resources this device uses. (Code 16)’

Solution

Error Causes

Error code 16 occurs when you use a peripheral device such as an external drive or a printer and that device is not properly or completely configured. Though the device may have been recognized before Windows fails to verify its configuration. Simply put, error code 16 appears when devices are partially configured.

In addition to this, another cause of error 16 is outdated or corrupt device drivers. Devices often fail to run successfully because of driver problems.

Device drivers are programs that provide instructions to control different devices attached to the computer system such as audio devices and printers to name a few.

Though error code 16 is not fatal like other PC error codes such as BSoD; however, it may hamper your ability to use certain devices installed on your system and lower your work productivity.

To avoid inconvenience, it is advisable to resolve the error immediately to avoid inconvenience.

Further Information and Manual Repair

PC error codes are often considered technical and difficult to resolve which is why many prefer to hire a professional for the repair job rather than doing it themselves.

Small repair jobs like fixing error code 16 by a professional computer programmer may cost you hundreds of dollars.

So, why incur so much cost when you can repair it easily by yourself even if you are not a technical whiz.

Error code 16 is easy to repair.

Here are some effective DIY methods that you can use for resolving error code 16 on your PC. These methods require no technical background, knowledge or expertise for that matter. Just simply follow the instructions and resolve the error code 16 issue.

Let’s get started…

Method 1 - Setup from the Disk that Came with the Hardware Device

Run setup from the disk that came with the hardware device, or you can simply copy the setup software file to your hard drive/flash drive. Refer to the vendor’s direction to set up.

If for any reason you’re unable to find the directions, simply uninstall the device. Then go to the start menu, Control Panel, and select ‘Add New Hardware’.

Now pick the appropriate hardware and follow the steps that the Wizard suggests. This is most likely to resolve the error code.

Nonetheless, if the error code still persists, then try method 2.

Method 2 - Allocate More PC Resources

Another alternative method to resolve error code 16 is to allocate more PC resources to the device. To specify additional resources:

• Go to the start menu
• Type Device Manager
• Then go to the Device properties and click the resources
• Here specify the device in the Device Manager
• If you see a resource with a question mark, assign that resource to the device
• However, if for any reason the resource is unable to change, then simply click ‘Change Setting’.
• If Change Settings is not available, then click the box to the ‘Use Automatic Settings’ box. This will make the option available.

Method 3 - Install DriverFIX

As previously stated above, device manager error codes like error code 16 may also occur due to driver problems. If this is the underlying reason for error code 16 on your system, then the best way to resolve it is to install DriverFIX.

DriverFIX is user-friendly, advanced, and feature-filled software deployed with an intelligent programming system, which detects all problematic device drivers automatically in seconds.

It matches these drivers with their latest versions and updates them smoothly without any hassle, resolving error code 16 right away.

And furthermore, once you install this software on your PC, you don’t have to worry about driver problems anymore typically because it updates drivers on a regular basis with compatible and new versions, ensuring that your computer functions properly. It is easy to install and is compatible with all Windows versions.

Click here to download DriverFIX to repair error code 16

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.

There are various components that take part during a Windows Upgrade process such as the CPU, Disk, Network, and many more. This is why the process of upgrading your Windows 10 computer can be quite complex and due to its complexity, there are times when you might encounter some errors like the Windows Upgrade error 0x800701E3. If you encounter this kind of error then it has something to do with the “disk” part of the whole upgrade process which could be due to a conflict with the storage of your Windows 10 computer. When you receive this error, you will see the following error message on your screen:

“Windows cannot install required files. Make sure all files required for installation are available and restart the installation. Error code: 0x800701e3.”

To fix this Windows Upgrade error, here are some suggestions that might help.

Option 1 – Delete Files from Software Distribution Folder & Catroot2 folders

The downloaded Windows Updates are placed in a folder called “SoftwareDistribution”. The files downloaded in this folder are automatically deleted once the installation is completed. However, if the files are not clean up or if the installation is still pending, you can delete all the files in this folder after you pause the Windows Update service. For complete instructions, refer to the steps below.

• 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 resetting 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 – Try running the DISM tool

You can try running the Deployment Imaging and Servicing Management or DISM tool to fix the Windows Upgrade problem. 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
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Option 3 – Run the System File Checker Scan

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

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

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

• Restart your computer.

Option 4 – Try running the ChkDsk utility

You can also run the ChkDsk utility to fix the Windows Upgrade error 0x800701E3.

• First, open This PC and right-click on your operating system partition for Windows.
• Next, click on Properties and navigate to the Tools tab.
• Then click on Check under the Error Checking section.
• After that, a new mini window will be opened and from there click on Scan drive and let it scan your disk drive partition for any errors and then restart your computer.

Option 5 – Run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter is one of the things you can first check out as it is known to automatically resolve any Windows Update or upgrade errors like error code 0x800701E3. 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 Upgrade error code 0x800701E3. 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.

In case you don’t know, Windows contains a feedback mechanism that generates error reports from hardware and software problems. These reports are temporarily stored in the system and send them back to Microsoft so that it can find solutions to the reported problems and fix them in the upcoming updates.  However, as time goes by, these reports actually take a lot of space in your computer which is why end-users like you are free to delete them with the help of the new Free Up Space feature in Windows 10. As useful the Free Up Space feature may be, there are times when you won’t be able to use it for some reason which is why in this post, you will be guided on how to use alternative ways in deleting very large System queued Windows Error Reporting file, some of which may run in Gigabytes. Every time the Windows Error Reporting or WER sends out an error file and looks for a solution, the WER server at Microsoft sends out a solution instantly. And if the solution is under investigation or is unknown, then you will be notified about it right away and will be asked for more details. As mentioned, even though the Free Up Space feature in Settings will be able to clear the error reporting files, there are instances when it won’t be able to delete very large System queued Windows Error Reporting files. Alternatively, there is an option to delete these files using the Disk Cleanup Utility. Feel free to select which option you’d like to use to get rid of Windows Error Reporting Files.

Option 1 – Delete Windows Error Reporting Files via Settings

• Go to Settings.
• From there, go to System > Storage > Free Up Space and then click on it to launch it.
• Afterward, give it some time to populate all the files and folders. Once it’s done, select “System created Windows Error Reporting files” to mark its checkbox while leaving the other options unchecked.
• Next, click on the Remove files button to delete all the Windows Error Reporting files from your computer.

Option 2 – Manually delete the Windows Error Reporting Files

• Tap the Win + E keys to open File Explorer.
• Next, enable the Hidden Files view from the menu.
• Then go to C:/ProgramData/MicrosoftWindowsWER.
• From there, you will see various folders like LocalReportArchive, ReportArchive, ReportQueue, and Temp.
• Open each one of the aforementioned folders and delete the archive files. Note that these files will have names similar to “00c58c1f-b836-4703-9bcf-c699ca24d285”.

Note: If you are not able to delete any of these files, you have to take ownership of the folder. To do so, refer to these steps:

• Right-click on the folder and 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.

On the other hand, if you do not want to go through all these troubles in deleting the Windows Error Reporting files, you can just disable it especially if it already becomes a daily annoyance as the files generate every day and their sizes are mostly gigabytes. And besides, there are times when these files do not make it to the Microsoft WER server and end up only occupying a lot of space for nothing.

FLoC is Google’s alternative to third-party cookies and is based on machine learning. This will allow the browser, any browser, to anonymously study how users are browsing and then group them into ‘cohorts’. Following this, you will be served ads based on your cohort and not on your individual data. So, you are still going to be targeted with ads but in a more anonymous manner. Google claims that this will improve user privacy since this “federated learning” happens on the user’s device and artificial intelligence-based learning involves sharing lesser users than what happens with third-party cookies. If something like this gets widely adopted by ad companies and services, it should “protect users” from tracking methods that are more intrusive than third-party cookies, like browser fingerprinting.

Who is against it?

Privacy-focused browsers DuckDuckGo, Brave, and Vivaldi have all warned users against FLoC and have said that they are going to block it on their end. Brave says that Google FLoC has a design that does not respect the customer’s privacy and consent. It has been designed to provide browsing behavior and interest data with any website that users may interact with, and this process does not involve fully informed consent. Vivaldi, another popular Chromium-based web browser, has also made its stance clear regarding the status of FLoC. The company said in a Reddit thread that the FLoC experiment does not work in Vivaldi. It happens because for FLoC to work, some features need to be enabled under the hood, but Vivaldi does not provide those options. The company also added that it plans to stop the entire FLoC component from being a part of the browser, regardless of how Google may implement it. Considering that Brave and Vivaldi have been privacy-focused browsers since their beginnings, the decision to stay away from FLoC is not surprising.

One of the most useful utilities for advanced users in Windows is the Windows command line or Command Prompt. It is efficient in fixing system files, checking the disk for errors as well as other intensive tasks that are made convenient using this. One of the tasks you can carry out using Command Prompt is repairing the Windows bootup process if it encounters any issues. However, if you tried running the “bootrec/fixboot” command and you receive an error message saying, “Element not found”, read on as this post will guide you in fixing this error. This kind of error in the command line could be due to a damaged BCD or MBE, inactive system partition, or it could also be that there is no drive letter being assigned to the EFI partition. Whichever the case is, here are some possible fixes that should help you resolve the problem.

Option 1 – Try to repair BCD

As mentioned the error could be caused by a damaged BCD and so to fix the problem, you need to repair BCD by following these steps:

• First, make sure that you have a bootable Windows 10 USB drive with you and use it to boot your computer.
• Once you’re on the Welcome Screen, click on Next.
• After that, click on Repair your computer located at the bottom-left portion of the window.
• Then select Troubleshoot > Advanced Options > Command Prompt.
• After you open the Command Prompt window, execute the following command:

bootrec /fixboot

• Afterward, enter the next command below to rename the BCD file:

ren BCD BCD.bak

• Next, type the following command and make sure to replace “b:” with the letter of your bootable drive attached to your computer.

bcdboot c:Windows /l en-us /s b: /f ALL

• Now, wait until the process is completed and restart your computer to successfully apply the changes made.

Option 2 – Try assigning the drive letter to the EFI partition

• Tap the Win + X keys or right-click on the Start button and click on Command Prompt (Admin) to open Command Prompt with admin privileges.
• Then type the following command to start the Diskpart utility:

diskpart

• After that, if you receive a UAC prompt, just click on Yes to proceed.
• Next, type the following command to list all the volumes created on your PC including both types of partitions that are visible to a normal user in the File Explorer as well as the ones created by Windows 10 by default which helps it in storing the boot files and other important system files:

list volume

• Now type the following command to select the desired volume:

select volume number

• Then type the following command to assign a letter to the selected volume:

assign letter=<LETTER>

Note: Make sure to replace “<LETTER>” with the letter you want to allocate to that partition. Afterward, it will assign a letter to the selected volume.

• Reboot your PC to apply the changes made.

Option 3 – Try setting the System Partition to Active

Like the first given option, you also have to make sure that you have a bootable Windows 10 USB drive before you proceed to set the System Partition to Active. Once you have it covered, refer to these steps:

• Boot your computer using the bootable Windows 10 USB drive.
• Next, click Next when you get to the Welcome Screen.
• Then click on Repair your computer located at the bottom left part of the window and select Troubleshoot > Advanced Options > Command Prompt.
• After opening Command Prompt, type the following command and hit Enter to start the Diskpart utility. It is a command line-based utility just like Command Prompt but has a UAC prompt once you provoke it. So if you encounter a UAC prompt, just click on Yes to proceed.

diskpart

• Now type the following command:

list disk

• From there, select your primary disk by typing the following command:

select disk number

• After that, list all the partitions on the selected disk by entering the following command:

list partition

• The command you just entered will list all the partitions created on your PC including both types of partitions that are visible to a normal user in the File Explorer as well as the ones created by Windows 10 by default which helps it in storing the boot files and other important system files.
• Now type the following command to select the partition that is usually around 100 MB in size:

select partition number

• Finally, type the following command to mark the partition active:

active

• Then type the “exit” command to exit the disk part utility.

What is Mapi32.dll Outlook Error?

Mapi32.dll is a Windows Messaging Application Programming Interface that enables Windows to perform various email functions and launch messaging programs like Microsoft Outlook and Microsoft Office. The inability of the interface to execute email functions properly results in the Mapi32.dll Outlook Error. This error occurs mostly when you are attempting to upgrade the operating system to a new version.

Solution

Error Causes

The common causes of the Mapi32.dll Outlook Error during the OS upgrade are:

• Damaged or Corrupt Outlook user profile
• The software is overwritten by some other program
• Outlook PST file corruption

The Mapi32.dll Outlook Error message is displayed in either of the following forms:

• Mapi32.dll is missing
• Cannot start Microsoft Office Outlook. Mapi32.dll is corrupt or the wrong version.
• Mapi32.dll was not found
• Mail is not installed

Further Information and Manual Repair

So, what if you experience this issue and how do you fix it? Well, first there is no need to panic as Microsoft has recognized this issue and provided adequate solutions to fix this problem in no time. However, to ensure the Mapi32.dll Outlook error is a quick fix, you must first understand the cause of the issue and the message displayed on the screen.

1. Let’s say the errors occur because your Outlook profile is corrupt. In this scenario, the best solution is to create a new Outlook profile. Regardless of whether you have Windows Vista or XP, to create your new Outlook profile, first, you will have to click on the Control Panel, then User Account, and then Mail. Once you click on the Mail tab, the mail set up dialog box will open. In this dialog box there will be a ‘Show Profiles’ tab, click and then click the Add tab that appears next. Now type the name for your new Outlook profile and then click ‘OK’. After that, add an email account to go with the profile.
2. If Mapi32.dll is missing or corrupt, you will have to run ‘Fixmapi.exe’ to resolve the problem. It is located in the System32 folder inside the Windows directory in Windows Explorer.

• Therefore, first start Windows Explorer and then locate the following folder on your computer: C: /Program Files/Common Files/System/Msmapi1033
• Now find Fixmapi.exe and double click it
• After that locate the Mapi32.dll file and rename it to MSmapi32.old and press enter.
• Restart your computer when finished.

A word of advice for computer users is to scan for viruses with an antivirus program or a registry cleaner regularly to prevent the Mapi32.dll Outlook error from occurring in the first place. Viruses often latch onto .dll files and corrupt them. It’s always best to have a forward-looking approach.

Over the years, the Windows 10 updates have smoothened but that does not mean that it no longer encounter some issues. One of these issues is when it gets stuck. As you know, Windows automatically checking for updates regularly or when you click the “Check for updates” button. However, if the Windows 10 update is taking forever and seems to be stuck, then you’ve come to the right place as this post will guide you on what you can do to resolve the problem. This kind of scenario in Windows Updates can be quite confusing especially since there is no response or any indication of what is really happening since you don’t know if the update is still downloading or if it’s already getting installed. To resolve this problem, there are several options you can check out. You can try to exit settings and restart your computer. You could also try to restart the services related to Windows Update or clear both the Software Distribution and Catroot2 folders, as well as run a System File Checker scan. For more details follow each one of the given steps below.

Option 1 – Restart your computer

The most basic thing you can do to fix the problem is to restart your computer. It usually works in fixing common issues like the Windows Update getting stuck at the “Checking for updates” screen. However, if it didn’t work, proceed to the next given options below.

Option 2 – Reset Windows Update components

If the first two options did not work then you might want to reset the Windows Update components manually. Follow the steps below to reset them.

• Open Command Prompt with admin privileges.
• After that, type each one of the following commands and hit Enter after you key in one after the other.
  • net stop wuauserv
  • net stop cryptsvc
  • net stop bits
  • net stop msiserver

Note: The commands you entered will stop the Windows Update components such as Windows Update service, Cryptographic services, BITS, and MSI Installer.

• After disabling WU components, you need to rename both the SoftwareDistribution and Catroot2 folders. To do that, type each one of the following commands below, and don’t forget to hit Enter after you type one command after the other.
  • ren C:WindowsSoftwareDistribution SoftwareDistribution.old
  • ren C:WindowsSystem32catroot2 Catroot2.old
• Next, restart the services you’ve stopped by entering another series of commands. Don’t forget to hit Enter after you key in one command after the other.
  • net start wuauserv
  • net start cryptsvc
  • net start bits
  • net start msiserver
• Close Command Prompt and reboot your PC.

Option 3 – Try checking Services Dependencies

Dependencies of a Windows Service in Windows 10 are when windows services depend on other services. Such is the case with the Windows Update service – it also depends on three different services such as the Remote Procedure Call or RPC service, DCOM Server Process Launcher, and the RPC Endpoint Mapper. Meaning to say, if two of these services are not working as expected, then the dependent service will also be affected. This could be the reason why the Windows Update service could not start.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “services.msc” in the field and hit Enter to open Windows Services.
• From the list of Services, look for the following services:
  • Remote Procedure Call (RPC) Service
  • DCOM Server Process Launcher
  • RPC Endpoint Mapper
• After you find these services, double click on each one of them and check whether the Startup type for all is set to Automatic and the Service status is set to Running or not.
• If the service status is not running, then click the Start button. Afterward, check if you can now run the Windows Update service.

Option 4 – Check the Background Intelligent Service and the Cryptographic Service

• 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:
  • Background Intelligent Transfer Service – Manual
  • Cryptographic Service ­– Automatic
• 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 5 – Try running the System File Checker

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files that might be the cause why your screen is stuck at “Checking for updates”. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

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

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

• Restart your computer.