The request failed due to a fatal device hardware error

If the Diagnostic Data level in your Windows 10 computer is configured manually to the non-default security setting of zero and you’ve encountered an error code of 0xc0000005, read on as this post will guide you in fixing the problem with the Remote Access Connection Manager Service. In relation to error 0xc0000005, you might also encounter an error in the Application section of Windows Logs in the Event Viewer, along with the Event ID 1000 which would most likely have a reference of “svchost.exe_RasMan” and “rasman.dll”. Before you troubleshoot the problem, keep in mind that the Remote Access Connection Manager or RasMan service is the one that manages dial-up and VPN connections from the computer to the internet as well as other remote networks. Each time you connect, the Services dials the connection or sends out a request for a VPN connection. However, the error 0xc0000005, only occurs when a VPN profile is configured as “Always On VPN or “AOVPN” connection with or without a device tunnel. There are several options you can check out to resolve this error, you can try to install the KB Update 4505903 or fix it via Group Policy. You could also try to enable Telemetry from the Settings app or enable it via Registry Editor. For more information, make sure to check out the provided options below.

Option 1 – Try installing the KB Update 4505903

The first thing you can do to fix the problem is to make sure that you’ve already installed the KB Update 4505903 in your computer. If not, then you have to go to Settings > Update & Security > Windows Update and from there select the Check for updates link. You need to get the standalone package if you are using the Microsoft Update Catalog to update your computer and for that, you have to the website of the Microsoft Update Catalog. On the other hand, if you are using the Windows Server Update Services or WSUS, then you can just manually import the KB Update 4505903 into WSUS.

Option 2 – Try to enable Telemetry in the Group Policy and run the RASMAN service

The next thing you can do to fix the problem is to enable Telemetry via Group Policy and then run the RASMAN service. To do that, follow these steps:

• Tap the Win + R keys to open the Run dialog box and type “gpedit.msc” in the field and hit Enter to open the Group Policy Editor.
• Next, navigate to Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds > Allow Telemetry.
• After that, open the policy and select one of the security levels like Basic, Enhanced, and Full.
• Then click on the Apply and OK buttons to save the changes made and close the Group Policy Editor.
• Once one, open the Run dialog box again and type “services.msc” in the field, and hit Enter to open the Windows Services Manager.
• From there, look for the Remote Access Connection Manager Service and restart it. And then check if it resolved the problem or not...

Option 3 – Try enabling Telemetry via Settings

• Tap the Win + I keys to open the Settings app.
• Next, go to Privacy > Diagnostics and Feedback and select Basic or Enhanced under the Diagnostic data.
• After that, tap the Win + R keys to launch Run and type “services.msc” in the field, and hit Enter to open the Services Manager.
• From there, look for the Remote Access Connection Manager Service and restart it.

Option 4 – Try to enable Telemetry via Registry Editor

• Launch the Run utility and type “regedit” in the field and tap Enter to open the Registry Editor.
• Then navigate to this path: HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsDataCollection
• From this path, look for “AllowTelemetry” and double click on it.
• Now enter the values, 1, 2, 3 for Basic, Enhanced, Full, respectively.
• If you can’t find AllowTelemetry, then just create a DWORD (32-bit) and name it “AllowTelemetry” and edit its value.
• Once done, exit the Registry Editor and restart the Remote Access Connection Manager Service from the Services Manager.

If you encounter the “We couldn’t install some updates because the PC was turned off” while trying to run Windows Update on your Windows 10 computer, then read on as this post will give you a couple of suggestions you can use as a reference to fix this error. Make sure to follow the options given below carefully.

Option 1 – Perform basic computer troubleshooting

If you get the “We couldn’t install some updates because the PC was turned off” error on your laptop, then it’s recommended that you connect your laptop to a power source and then try clicking the Update button again. In addition, you also have to make sure that your computer stays awake until the Windows Update process is completed. This will ensure that your computer does not go into an idle state and interfere with the process.

Option 2 – Try deleting the files from the SoftwareDistribution folder and resetting the Catroot2 folder

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 3 – Try restarting the Windows Update Services

• Open the Services Manager.
• From there, make sure that you set the following services and Startup types:
  • Background Intelligent Transfer Service: Manual
  • Cryptographic Service: Automatic
  • Windows Update Service: Manual (Triggered)

Option 4 – Try to run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the “We couldn’t install some updates because the PC was turned off” 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. After that, follow the next on-screen instructions and you should be good to go.

Option 5 – Try to install the Windows Updates manually

As mentioned, the error might be because Windows missed installing a particular update which is why you are not able to proceed with the current update. So to resolve the issue, you need to install the update that wasn’t installed by downloading it from the Microsoft Update Catalog website. You also have to make sure that you didn’t turn off the Windows update or have it delayed.

Option 6 – Run Microsoft’s online troubleshooter

Running Microsoft’s online troubleshooter might also help you fix the Windows update error. 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.

If you encounter the ERR_SSL_VERSION_INTERFERENCE error on your Google Chrome browser then this means that the browser is trying to load a website with SSL protocol but is not able to do so. This error can occur for many reasons and in this post, you will be given potential fixes that could help you in resolving the problem. But bear in mind that these potential fixes are not that straightforward forward so if you encounter an option you don’t understand much, just skip to the options you have the knowledge of. There is no direct fault in the browser for the ERR_SSL_VERSION_INTERFERENCE error as there are issues with caching the website data locally on your computer. Moreover, this kind of error can also appear when a website is coded incorrectly or if there are conflicting browser extensions installed in the browser that prevents the website to function properly. Refer to the suggestions given below to fix the ERR_SSL_VERSION_INTERFERENCE error in Chrome on Windows 10.

Option 1 – Try clearing browser data

There are times when some data in the browser is conflicting with the loading of the website and triggers errors like ERR_CACHE_MISS. And so you can try to clear your browser’s data. This might be a very basic solution but oftentimes it works in fixing this kind of error in Google Chrome. Follow the steps below to clear the data in your browser.

• Open your Google Chrome browser.
• After that, tap the Ctrl + H keys. Doing so will open a new panel that allows you to delete the browsing history and other data in your browser.
• Now select every checkbox that you see and click on the Clear browsing data button.
• Then restart your Chrome browser and check if you can now open any website or not.

Option 2 – Try disabling TSL 1.3

If clearing the browser data didn’t fix the problem, you can also try to disable TSL 1.3 in Chrome. To do so, refer to these steps:

• Open Google Chrome.
• Next, type in “chrome://flags/#tls13-variant” in the address bar and tap Enter.
• After that, you should see the experimental features page for Google Chrome where you can set TSL 1.3 to disabled.
• After disabling TSL 1.3, restart your computer and check if the problem is fixed or not.

Option 3 – Reset Winsock, TCP/IP & Flush DNS cache

Resetting Winsock, TCP/IP, and flushing DNS might help in resolving the ERR_SSL_VERSION_INTERFERENCE error just follow these steps:

• Right-click on the Start button and click on Command Prompt (administrator) so you can pull up an elevated Command Prompt.
• After that, execute each one of the commands listed below. And after you typed in one after the other, you have to hit Enter.

1. netsh winsock reset – type in this command to reset Winsock
2. netsh int ip reset resettcpip.txt – type in this command to reset TCP/IP
3. ipconfig /flushdns – type in this command to flush the DNS cache

• Next, restart your PC and check if the problem’s fixed.

Option 4 – Get rid of any conflicting browser extensions

• Open Chrome and press Alt + F keys.
• Go to More tools and click Extensions to look for any suspicious browser extensions or toolbars.
• Click the Recycle bin and select Remove.
• Restart Chrome and press Alt + F keys again.
• Proceed to On Startup and mark Open a specific page or set of pages.
• To check if the browser hijacker is still active, click Set pages, if it is active, overwrite the URL.

Option 5 – Reset Google Chrome

Resetting Chrome can also help you get rid of the error. Resetting Chrome will restore its default settings, disabling all the extensions, add-ons, and themes. Aside from that, the content settings will be reset as well and the cookies, cache, and site data will also be deleted. To reset Chrome, here’s what you have to do:

• Open Google Chrome, then tap the Alt + F keys.
• After that, click on Settings.
• Next, scroll down until you see the Advanced option, once you see it, click on it.
• After clicking the Advanced option, go to the “Restore and clean up option and click on the “Restore settings to their original defaults” option to reset Google Chrome.
• Now restart Google Chrome.

Isn’t it annoying when you get an error message pop up stating ‘Cannot find propsys.dll” or “propsys.dll not found” when you start your computer or open a particular program? The propsys.dll file is crucial to the Windows operating system. This file is located in one of the following locations: "C:\Windows", C:\Program Files, C:\WINDOWS\system32, or C:\Program Files\Common Files". And the propsys.dll error indicates that the propsys digital library file is damaged and corrupt. The propsys.dll error may lead to a very unstable operating system. It may also hamper your ability to access many programs on your computer, lead to program and system crash and slow down the system’s performance. Therefore, to avoid these system threats, it is advisable to fix the error immediately.

Solution

Error Causes

The common causes of propsys.dll file error are:

• Registry problem
• The propsys.dll file is damaged due to a virus or spyware
• Improper software removal
• Hardware Failure

The propsys.dll error message is displayed in either of the following forms:

• Propsys.dll not found
• Cannot find [Path]propsys.dll
• This application failed to start because propsys.dll was not found. Reinstalling the application may fix this problem
• The propsys.dll file is missing

Further Information and Manual Repair

There are many ways to fix the propsys.dll error. However, for optimum results from the fix, you must first identify the cause of the error and then choose the solution accordingly.

• Recommended Solution for Registry Issue

If you use your system daily the resulting wasted/invalid/junk entries may dilate the registries. This can result in registry malfunctioning which may result in a propsys.dll error on your screen. When this happens, it is advisable to use a registry cleaner to fix the problem. Registry cleaner helps clean up the junk entries and repairing the corrupted registries. For this, you will first have to download a registry cleaner repair tool. Download and install the software on your computer. After downloading it, click the start scan button to run. This helps scan and diagnose system errors on your computer in seconds. Once the scanning is complete, click on the fix button to repair the registry problem.

• Recommended Solution for File Damage and Corruption

Use the ‘System Restore’ option to restore corrupt and damaged files.  The ‘System Restore’ function will help you get a fresh copy back and simultaneously help fix the error. Here’s how to use and access the ‘System Restore’ function on your computer: Simply go to the start menu and in the search box type restore. Once you type, it will show you the system restore option. Now select ‘choose a different restore point’. After this, you will be presented with a list of restore points. Choose a point that you believe happened before the propsys.dll error. Confirm your selection and restart. Another alternative solution for file damage is to run a virus scan of your entire system; the damage could be related to a virus or malware infection.

• Recommended Solution for Hardware Failure

If a propsys.dll error occurs due to hardware failure, then it is advisable to update the drivers for hardware devices that you think are related to propsys.dll. For example, if you receive the propsys.dll error when you play a 3D video game, then try updating the driver for your video card.

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.

RocketDock is one of the most popular app launchers as it has been used excessively back in several windows versions. This was modeled based on the Mac OS X launch bar and offers an animated response when you hover the mouse over the apps gathered on the Dock. This is perched at the top of your screen, and you can easily drag your favorite app icons to have them in one place. The dock keeps all your most favorite shortcuts intact for faster and easy access. Like other apps, you can easily customize the dock with skins and other add-ons. If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

Pinned Windows 10 Taskbar Items. One of the most used interfaces in the Windows environment is the Taskbar. It is where users like to pin their most-used programs as well as shortcuts with extra privileges and automated tasks. In fact, it’s a lot better than the Start Menu. So if any Windows Update messes up with your computer, or if you’ve just switched to a different computer, setting up the Taskbar with the very same set of programs you used to have is definitely not an easy task. But worry not as this post will guide you on how you can backup and restore the items on your Taskbar either manually or automatically.

Manual Backup:

• Tap the Win + R keys to open the Run prompt.
• Then type “%AppData%MicrosoftInternet ExplorerQuick LaunchUser PinnedTaskBar” in the field and hit Enter to open the folder where you can see all the shortcuts or pinned items in the Taskbar.
• After that, copy all the files in the folder and paste them somewhere else as a backup. For instance, E:\Pinned Items Backuppinnedshortcuts.
• Next, tap the Win + R keys to open the Run prompt once more, and then type “Regedit” in the field and hit Enter to open the Registry Editor. When the User Account Control dialog box appears, click Yes.
• After opening the Registry Editor, navigate to this key – HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionExplorerTaskband
• Then right-click on the Taskbar folder and select Export.
• Now save the file with the .reg extension to another location like the E:\Pinned Items Backup folder and then name it.
• Close the Registry Editor.

Manual Restore:

Make sure to copy all the files to one of the drives if you are using another computer and then refer to the following steps.

• Tap the Win + R keys to open the Run prompt.
• Then type “%AppData%MicrosoftInternet ExplorerQuick LaunchUser PinnedTaskBar” in the field and hit Enter to open the same folder where you just copied all the shortcuts. Make sure to keep it open.
• Then open the backup folder where you saved all the pinned items and copy all the files there.
• Next, go to the Taskbar folder (%AppData%MicrosoftInternet ExplorerQuick LaunchUser PinnedTaskBar) and then paste your files in there. If you encounter a problem while doing so, just replace it with your own set of files.
• After that, go to E:\Pinned Items Backuppinnedshortcuts and then double click on tb-pinned-items.reg. If a User Account Control prompt appears, click Yes. This will add the registry file into the main registry hub. You will also get a dialog box that will confirm that data has been added to the registry successfully. Click OK.
• You should now see the items on the Taskbar. You have to restart Windows Explorer. To do so, end its process in the Task Manager.

Automatic Backup:

Backing up and restoring the pinned Taskbar items in your Windows 10 computer can be done automatically as well. But before you get started on the process, you need to understand what’s going on behind the hood first. First, you need to create two bat files and name them “Backup Pinned Taskbar Items” and “Restore Pinned Taskbar Items”. After you have that covered, refer to the following steps:

• Open the Notepad app and paste the following details and save it as “Backup Pinned Taskbar Items.bat.

REG EXPORT HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionExplorerTaskband “E:\Pinned Items Backuptb-pinned-items.reg” xcopy “%AppData%MicrosoftInternet ExplorerQuick LaunchUser PinnedTaskBar” “E:\Pinned Items Backuppinnedshortcuts” /E /C /H /R /K /Y

• After that, run the newly created bat file with admin privileges.

Automatic Restore:

• Open the Notepad app and paste the following details and save it as “Restore Pinned Taskbar Items.bat”.

REGEDIT /S “E:Pinned Items Backuptb-pinned-items.reg” xcopy “E:Pinned Items Backuppinnedshortcuts” “%AppData%MicrosoftInternet ExplorerQuick LaunchUser PinnedTaskBar” /E /C /H /R /K /Y

• After that, run the bat file with admin privileges.

Note: Just so you know, there is a drawback to this process as we’ve noticed that any pinned apps that were downloaded from the Windows Store don’t appear in these places and any items downloaded and installed separately from the internet and then pinned.

KMODE_EXCEPTION_NOT_HANDLED – What is it?

Some users installing or upgrading to Windows 10 experienced the theKMODE_EXCEPTION_NOT_HANDLED Blue Screen of Death (or commonly known as BSOD) error. This error can be due to different types of things, ranging from software to driver issues. When you experience this BSOD error while trying to install Windows 10, it will prompt you to restart your computer every single time you experience it. In most cases, you will also not be able to proceed with the Windows 10 set-up.

Solution

Error Causes

The “KMODE_EXCEPTION_NOT_HANDLED” error is normally caused by:

• Hardware incompatibility
• A faulty device driver or system service

Further Information and Manual Repair

You won’t be able to successfully upgrade or set up Windows 10 if you continue to encounter this BSOD error. Note that this error will always prompt your computer to restart every time it happens, preventing you from completing the Windows 10 set-up.

If you’re not tech-savvy or not capable of debugging this issue, it’s highly advisable to proceed with the basic troubleshooting techniques available in this link.

After troubleshooting, below you’ll find a few solutions to rectify the issue.

Method 1 – Check The Cause of The BSOD Error

Two common causes of the KMODE_EXCEPTION_NOT_HANDLED issue are hardware incompatibility and faulty device driver or system service.

If you experience this error, check first if any of your newly installed hardware is compatible with Windows 10. You can find the required hardware for Windows 10 from this link. 

If all your hardware is compatible with Windows 10, you might need to check the device driver or system service. Review the bug check message. If any of the drivers you have is listed in the message, either disable or uninstall them before upgrading or setting up Windows 10.

You might also find it useful to check the System Log available in the Event Viewer for other error messages that can help you figure out the driver or device that’s causing the error. Running hardware diagnostics can also be useful.

Method 2 – Disable (or preferably uninstall) Software Before Upgrading

If you’re upgrading Windows 10 from Windows 7 or Windows 8.1, you might need to disable or uninstall the software first. First, try uninstalling your Antivirus utility before starting the upgrade. Restart a few times before starting the Windows 10 installation. If you’re upgrading using the Windows 10 update, make sure that you disconnect from your Wi-Fi or Internet LAN (Ethernet) connection as soon as the download reaches 100% before attempting to start the set-up. Other users also reported that the cause of the KMODE_EXCEPTION_NOT_HANDLED issue is BitDefender. If this is what happened in your case, it will show in the error message such as KMODE_EXCEPTION_NOT_HANDLED (bdselfpr.sys). Users reported that a common solution for this is renaming the file. In the case of BitDefender, try renaming it to bdselfpr.s__. However, make sure to do this cautiously. Sometimes, renaming a file will even do more damage than good.

Method 3 – Disable/Disconnect From Hardware

If you’re connected to any general USB devices (such a smart card reader), disable it. If your computer is connected to other external devices, disconnect all of them. Examples of this include gaming controllers, printers, external hard disk, USB keys, and other non-essential devices).

Method 4 – Other Troubleshooting Steps

Other troubleshooting steps include:

• Upgrade using an .ISO file, instead of directly upgrading from Windows Update. When you do this, make sure you’re disconnected from the Internet during installation. If the process started and you forgot to disconnected, it’s best to restart the installation.
• If you’re connected to a domain while trying to set up Windows 10, disconnect and use a local account.
• If you’re using a SCSI hard disk, connect a thumb drive with the drivers for your storage device. While Windows 10 is setting up, click on the Custom Advanced Option. Using the thumb drive, use the Load Driver command to load the SCSI drive.
• Another possible cause of this error is due to BIOS incompatibility. BIOS issues can be solved by upgrading your version of your system BIOS. If you don’t know how to do this, refer to your BIOS manufacturer’s website.

Method 5 – Use A Trusted Automated Tool

If you still experience the error after doing the methods above, you might want to try a powerful and trusted automated tool to fix the job.

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.

One of the selling points of Windows 11 was the ability to run Android apps natively in it without the need for any third-party software. It is not a big surprise that even after its release Microsoft is evolving and expanding Windows 11 and its features.

Microsoft is now rolling out an update for the Windows Subsystem for Android on the Dev Channel of the Windows Insiders program. The new version upgrades the core operating system from Android 11 to Android 12.1 (also known as Android 12L), which means the new system and app features in Android 12 and 12.1 are now available on Windows for the first time. However, not the new features in those updates apply to the modified version that runs on top of Windows. For example, one of the main improvements in 12.1 was a dual-pane notification panel for larger screens, but Android app notifications on Windows just show up in the Windows notification panel.

The upgrade also improves how Android apps integrate into Windows. The Windows taskbar will now show which Android apps are currently using the microphone, location, and other system services — similar to many native Windows applications. Toasts messages (the small popups that some apps use for temporary messages) are now displayed as Windows notifications, and the titlebar on Android apps will use the current activity name for the title.

Full changelog

• Windows Subsystem for Android updated to Android 12.1
• Advanced networking on by default for newer x64 Windows builds
• Updated Windows Subsystem for Android Settings app: redesigned UX and diagnostics data viewer added
• Simpleperf CPU profiler recording now works with Windows Subsystem for Android
• Windows taskbar now shows which Android apps are using microphone and location
• Improvements to Android app notifications appearing as Windows notifications
• Reduced flicker when apps are restored from minimized state
• Apps are not restarted when devices come out of connected standby on recent Windows builds
• New video hardware decoding (VP8 and VP9)
• Fixes for on-screen keyboard in apps
• Fixes for full-screen Android apps and auto-hidden Windows taskbar
• Windows Subsystem for Android updated with Chromium WebView 100
• Added support for Android NetworkLocationProvider in addition to GpsLocationProvider
• Improved general stability, performance, and reliability

The new update is limited to Windows Insiders for now, but once Microsoft fixes all the bugs, it should start rolling out to everyone on Windows 11 that has the Android Subsystem enabled.