Upcoming comic book movies with release dates

This post will guide you in fixing the error 0x80070103 when installing Windows Update. According to users who encountered this problem, Windows Update (WU) fails to install several different updates. This kind of Windows Update error is can mostly be seen in the Windows Update screen inside the update reports although it is also known to occur when a user attempts to install a peripheral driver – only if the Windows Update offers to update the driver through a prompt and when you click Yes. There are several possible causes for this error, it could be that Windows Update is trying to install a particular driver for the second time already which happens when it gets confused by an additional piece of identical hardware like the graphics adapter. Aside from that, the Windows Update might have already installed the driver which is known to occur with unsuitable versions of the already installed driver. In addition, the error could also be due to a third-party program interference like a security program or a utility program that is using the same driver and conflicts with the Windows Update. Here are some suggestions that might help in fixing the Windows Update error 0x80070103.

Option 1 – Install the updates in a Clean Boot State

You might want to try putting your computer in a Clean Boot state and then install Windows Updates again without any trouble. During this state, you can start the system with a minimum number of drivers and startup programs that will surely help you in isolating the root cause of the issue.

• 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 that, try to install the Windows Updates or upgrade again.

Option 2 – Try installing the failing driver without using Windows Update

If installing the updates in a clean boot state didn’t help, you can try a manual approach to yield much better results using the Device Manager or by downloading the driver from the manufacturer’s website manually.

• 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. Look for the device driver you and then select either “Update driver” or “Uninstall device”. And if you find any “Unknown device”, you need to update it as well.
• Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
• If you have chosen to uninstall the driver, follow the screen options to complete the process and then restart your PC.

Note: You also have the option to go directly to the website of your device driver manufacturer and go to the section called Drivers then check if there’s a new available update – if there is, download and install it.

Option 3 – Try to run the Windows Update Troubleshooter

You might also want to run the built-in Windows Update Troubleshooter in Windows that could help you in resolving the Windows Update error 0x80070103. All you have to do is go to Settings > Update& security > Troubleshoot > Windows Update. From there, click on the Run the troubleshooter button and follow the next one-screen instructions that appear. After that, restart your computer and check if the error is now fixed or not by trying to install the update once again.

Error 101 - What is it?

Error 101 is a Google Chrome error. You may experience this error if you browse the internet using Google Chrome. This error results when the existing HTTP connection between Chrome and the website is broken. The error is displayed in the following format: “Error 101 (net::ERR_CONNECTION_RESET): The connection was reset.”

Solution

Error Causes

The cause of Google Chrome error 101 cannot be narrowed down. This error can be triggered on your PC due to multiple reasons. These include:

• The inability of the Google Chrome installer to create a temporary directory on your PC during the installation process
• Enabled DNS Prefetching
• Firewall
• Viral Infection
• Bad Registry Entries
• Poor Internet Connection

Though this error code is not fatal, nonetheless it is advisable to fix it to ensure you are able to browse the internet using Google Chrome.

Further Information and Manual Repair

The good news is that this error is quite easy to resolve. Even if you are not a technical whiz you can still manage to fix it by trying these easy and effective DIY methods we have listed below:

Method 1: Reload the Website link on Chrome or Check Your Internet Connection

Sometimes refreshing the webpage can resolve the issue easily. Try doing it. Reload the link by pressing Ctrl +R. This will refresh the webpage. If it starts working then that’s great but if it doesn’t then it is advisable to check your internet connection. Disable and Enable the connection and then try browsing on Chrome again. If websites are accessible then the problem is resolved. If the error persists then try other methods.

Method 2: Disable DNS Pre-fetching

Sometimes this error may occur due to enabled DNS pre-fetching. To resolve the issue, open Chrome, then click on the wrench key. Go to setting and under the bonnet and Privacy section, look for the DNS perfecting option. If it is enabled, then uncheck it to disable DNS Pre-fetching. Save the changes and then close the browser. Now open it again and try browsing on Chrome. If error 101 does not appear and you are able to access websites then the issue is fixed.

Method 3: Scan for Viruses

Another way to fix this is to download and run a powerful antivirus. Scan and remove viruses to fix the problem.

Method 4: Check the permission for your temporary folder

As mentioned above, another underlying reason for error 101 can be Google Chrome installer was unable to create a temporary directory on your system during the installation process. To resolve it, check the permission for your temporary folder. Here’s how to do it: First go to the start menu and type Run. Now enter one of the following directories in the text fields 1. Windows XP: %USERPROFILE%Local Settings 2. Windows Vista: %USERPROFILE%AppDataLocal After that press OK. This will open a new window. In the Window that opens, right-click the temp folder. Now select properties and press the security tab to continue. In the group and user names section, select your user profile name. In the permissions, section verify that the checkboxes for READ, WRITE, and READ  & EXECUTE permissions in the DENY column are not selected. After you have verified, click apply and then ok. Now try reinstalling the Google Chrome browser again on your system.

Method 5: Remove Bad Entries by Cleaning the Registry

Bad entries and cookies saved in the registry can also lead to error 101. You can remove them manually but that will take a great deal of time and can be slightly difficult if you are not technically sound. Therefore, it is advisable to download Restoro. This is a user-friendly PC Fixer integrated with a registry cleaner that scans and removes all registry issues in a few clicks. It removes all the bad entries and junk files cluttering the registry and repairs it instantly. Click here to download Restoro.

Intel announced that Pat Gelsinger (CEO) and Dr. Ann Kelleher  (technology Department head) will discuss Intel’s process and packaging innovations on an upcoming webcast that will happen on July 26^th. The spokesman will talk and provide a deeper look at the process and packaging roadmaps for Intel. As we know Intel is planning to expand its production capabilities, outsource some of its technologies and offer foundry services to other chip design companies. The strategy will also include a shift to a 7nm process and Intel’s effort to set itself again as leader of CPU performance by 2024. There is also a chance that we will hear exact plans for Intel in the next three or four years. Intel didn't reveal much else about what Gelsinger and Kelleher plan to discuss during the webcast. The event will be streamed on July 26 at 2 pm PT via the Intel Newsroom; it will also be available to watch on-demand after the stream ends.

As you know, each time you log out of your Windows 10 computer, it will take you to the login screen where you can switch users or log back in. But there are instances where Windows 10 remains stuck on the signing out screen, along with a blue spinning circle and all you can see is the process of your computer signing out, however, it does not progress and only gets stuck there. Thus, in this post, you will be guided on how you can resolve such an issue on your Windows 10 computer. So if you are one of the users who experience the same problem, there are several fixes you can check out if your computer is stuck on the signing out screen with a blue spinning circle. You can try to force shutdown your computer or troubleshoot the problem in a Clean Boot State. You could also try to check the status of the User Profile Service or repair User Profile, as well as run System Restore. For more details, refer to each one of the suggestions provided below. But before you troubleshoot the problem, make sure that you are logged in to your computer as an administrator.

Option 1 – Try to force shutdown your computer

The first thing you can do is to force reboot your computer as this simple fix could help in fixing the problem. This option is quite simple, just make sure that before you do it, you have to save all your work.

• First, turn on your computer and press and hold the power button for at least 30 seconds. You might notice the screen flashing or making any changes, just ignore it.
• After that, plug out and plug in your computer and automatically turn it on.
• Once done, check if the issue is now fixed or not.

Option 2 – Put your computer in a Clean Boot State

It is possible that some third-party application is causing your computer to get stuck in the signing out screen. So you can try putting your computer in a Clean Boot State and see if it fixes the problem.

• 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” checkbox 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” checkbox.
• 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.)
• Once your computer is in a Clean Boot State, you should now be able to sign out or sign in without any problem.

Option 3 – Try checking the status of the User Profile Service

If forcing your computer to shut down or putting your computer in a Clean Boot State didn’t fix the problem, you can try to check the status of the User Profile Service since it is the one responsible for loading and unloading user profiles. Thus, if this service is disabled or stopped, you will no longer be able to sign out or sign in successfully.

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Services Manager.
• From there, look for the User Profile Service and make sure that its Startup Type is set to Automatic and that its status is “Started”.
• Once done, exit the Services Manager and see if the issue is resolved.

Option 4 – Try to repair your corrupted profile via Registry

In this second option, you can try to repair the corrupted profile using the Registry but before you proceed, make sure to create a System Restore Point and then follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Then type “regedit” in the field and hit Enter or click OK to open the Registry Editor.
• Next, go to this registry key: ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionProfileList
• Once you’ve opened the registry key, you should see a list of all the user profiles on your computer. Now click on each S-1-5 folder and look for the “ProfileImagePath” entry and double click on it to check which user account it is related to. You will see a path like “CUsersACK” where “ACK” is the username.
• You should know which of the user account is corrupted. Just look for a key named “RefCount” and change its Value data to “0” and click OK. And if it isn’t available, simply right-click on the right pane and create it.
• After that, double click on the key named “State” and make sure that the Value data is “0” and click OK.
• Exit the Registry Editor and restart your computer to apply the changes made and then check if it fixed the problem or not.

Option 5 – Run System Restore

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

What is SYNTP.SYS file? it is a system file created by Synaptics Touchpad drivers that are responsible for all the gestures and tracking users’ touch on the Touchpad. However, what happens when this driver fails? Well, it’s either that your touchpad will partially stop working or it will completely stop working at all. And in such cases, you will encounter the SYNTP.SYS Blue Screen error along with any of the following error codes:

• IRQL_NOT_LESS_EQUAL
• KMODE_EXCEPTION_NOT_HANDLED
• INVALID_PROCESS_ATTACH_ATTEMPT

To resolve the problem, use the instructions given below as a reference.

Option 1 – Run the Memory Diagnostic Tool to check for Memory leaks

• Tap the Win + R keys to open Run and type exe and hit Enter to open the Windows Memory Diagnostic Tool.
• After that, it will give two options such as:
  • Restart now and check for problems (Recommended)
  • Check for problems the next time I start my computer
• Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.

Note: After you select the option, your PC will restart and check for memory-based issues. If it finds any issues, it will automatically fix them and if there’s no issue found, then it’s most likely not a memory-based issue so you should try the other options given below.

Option 2 – Try reinstalling the Synaptics Driver

You might want to reinstall the Synaptics driver to resolve the SYNTP.SYS Blue Screen error.

• Tap the Win + R keys to open the Run dialog box.
• After that, type “appwiz.cpl” in the field and hit Enter to open the Programs and Features section in the Control Panel.
• Next, you have to look for the “Synatics Point Device driver” and right-click on it, and then click on Uninstall to remove it from your computer.
• Restart your PC and then check for updates under the Windows Update section.
• After that, it will find the latest available and stable Synaptics driver and then install it.
• Then click the “Check or Updates” under the Windows update section and it will automatically look for the latest available Synaptic driver and install it for you.
• Now restart your PC and for the changes to take effect.

Option 3 – Try to run a System File Checker scan

You can also try to run a System File Checker or SFC scan in order to scan your computer for corrupted files that might be the cause behind the Error 0x80000003. Once it finds any corrupted system files, it will automatically fix them. To run System File Checker, here’s what you have to do:

• 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 after the scan is completed.

Option 4 – Perform a System Restore

Performing System Restore might help you in fixing the SYNTP.SYS Blue Screen error. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

Option 5 – Try to run the CHKDSK utility

Running the CHKDSK utility might also help you resolve the SYNTP.SYS errors. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.

• Open Command Prompt with admin privileges.
• After opening Command Prompt, execute the following command and hit Enter:

chkdsk /f /r

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

Option 6 – Use the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like SYNTP.SYS Blue Screen error. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Support for Bluetooth hardware has always been included in the Windows 10 operating system for a long time now. And it just keeps getting better especially now with the support for the latest version of Bluetooth 5.0 LE. However, there are still times when Bluetooth experiences a couple of issues one of which is users were not able to turn on or off Bluetooth on their Windows 10 Pc since the option to turn Bluetooth off or on is missing in the Windows 10 settings app and even in the Action Center. So if you are one of the users who experience the same problem, read on as this post will guide you in resolving the issue. To resolve this Bluetooth issue, here are some suggestions that could help:

Option 1 – Try running the Bluetooth Troubleshooter

As you know, Windows 10 has various troubleshooters with user-friendly interfaces where you can utilize them to fix issues in your PC. And since you’re dealing with some Bluetooth problem, you have to run the Bluetooth Troubleshooter.

• Open the Windows 10 Settings.
• Then go to Update & Security > Troubleshoot.
• You should find the option for Bluetooth on your right-hand side – click on it then click on the “Run the troubleshooter” option.
• Now follow the next screen options.

Option 2 – Try to reinstall or update the Bluetooth driver

The issue might have something to do with the Bluetooth drivers. It could be that it is outdated and needs to be updated or that you recently updated it and since then you have trouble removing the Bluetooth devices and so to fix the issue, you can update, roll back or uninstall the Bluetooth drivers. How? Follow the steps below.

• Tap the Win + X keys to open the Device Manager.
• Next, look for the Bluetooth device and right-click on it.
• Select the option “Update driver”.
• After that, a new popup window will appear. In there, select the option, “Search automatically for updated driver software”.

Note: Checking the update may take a few minutes so you’ll have to wait until it finishes. If it is able to find an update, you must install it. And if you want to reinstall the Bluetooth driver, just select the “Uninstall driver” option and follow the next on-screen instructions that follow.

Option 3 – Configure the Bluetooth Services

If the first two options didn’t work, the next thing you can do is configure Bluetooth Services. How? Simply follow these steps:

• Tap the Win + R key combination to open the Run dialog box.
• After that, type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• You will then see a list of services and from there, look for the following services and make sure that their default values are set as follows:
  • Bluetooth Handsfree Service – Manual (Triggered)
  • Bluetooth Audio Gateway Service – Manual (Triggered)
  • Bluetooth Support Service – Manual (Triggered)
  • Bluetooth User Support Service – Manual (Triggered)
• Now click on the Start button to start all the aforementioned services and then check if you can now see the option to turn Bluetooth on or on.

Booting Windows 10 in safe mode can solve many issues with your computer since Windows will boot just in its basic core and you can safely maintain it, find a solution for issues, etc. Before, entering safe mode was easy and pretty straightforward, during Windows evolution, entering safe mode was somewhat complicated and not being made so directly like once it was but do not worry. Starting Windows in safe mode today is even maybe easier than it was before, it is just not so obvious as it once was. In this article, we will go through several ways how you can boot up Windows in safe mode in order to solve whatever issue is troubling you.

1. Start safe mode from settings

   Open Settings by pressing the ⊞ WINDOWS + I or by just clicking on the Start button and clicking Settings. Go to Update & Security, then Recovery. In Advanced startup, click Restart now. Once your PC reboots, click Troubleshoot, then Advanced options. Select Startup Settings then Restart.

2. Go to safe screen from Sign-in screen

   Click the Shift on your keyboard while clicking on the Power button on the bottom right corner of the screen. Once your PC restarts, click on Troubleshoot, then Advanced options. Select Startup Settings then Restart. After the reboot, select 4 or the F4 on your keyboard to run in Safe Mode. If you choose to use Safe Mode with Networking, select 5 or F5.

3. Start Windows recovery Environment

   Go to the Windows Recovery Environment by doing the following steps: Press on the power button to turn off your device. Press on the button again to turn it on. Once Windows starts, press the power button again for 10 seconds to turn it off. Then press it on again. Upon the reboot, hold on to the power button for 10 seconds to turn it off, then turn it on again. Because you've repeatedly turned on and off your PC, you will be redirected to Windows Recovery Environment. On the pop-up window, click on Troubleshoot, then Advanced options. Select Startup Settings, then Restart. After the reboot, select 4 or the F4 on your keyboard to run in Safe Mode. If you choose to use Safe Mode with Networking, select 5 or F5.

4. Hold SHIFT while pressing RESTART on the start menu

   On the Windows 10 sign-in screen, hold on the SHIFT on your keyboard. While pressing on the key, click on the Power button, then choose Restart on the pop-up menu. Once your PC restarts, click on Troubleshoot, then Advanced options. Select Startup Settings then Restart. After the reboot, select 4 or the F4 on your keyboard to run in Safe Mode. If you choose to use Safe Mode with Networking, select 5 or F5

5. Boot from installation media and choose it in the command prompt

   Create a Windows 10 bootable installation media on any external storage media. Once you do this step, wait for the installation to load. Select your preferred language and click on Next. Click on Repair your computer at the bottom left of the menu. Click on Troubleshoot, then Advanced options. Select Command Prompt - Use the Command Prompt for advanced troubleshooting options. Type in the following command on the prompt: bcdedit /set {default} safeboot minimal Hit Enter and wait for it to tell you that "The operation completed successfully". Exit Command Prompt and click on Continue.

6. Use system configuration tool

   In the Search bar, type in msconfig. Select the Boot tab and under the Boot options, put a check beside Safe boot. Click OK. Reboot PC

7. Press SHIFT + F8

   Press SHIFT + F8 when turning on Windows. This redirects you to Advanced Boot Options Window, then choose to run Windows on Safe Mode

There you have it, 7 different ways to enter safe mode in Windows 10, we hope that any of these tips proved helpful and that you managed to enter the safe mode and fix your Windows issues.

For a while now, Microsoft has been working hard to add various built-in troubleshooters in Windows 10. In fact, there is a troubleshooter for almost every standard or common error in Windows 10. And now with the newly released Windows 10 v1903, Microsoft has added the Recommended Troubleshooting which allows Windows 10 to automatically fix a lot of critical issues on your computer, and in this post, you will be guided on how you can turn on or off the Recommended Troubleshooting in Windows 10. The Microsoft Diagnostic & Feedback data only provides two settings – Basic and Full. So if you want to turn off the Recommended Troubleshooting for some reason, the only way to do so is to stop it from collecting complete data from your PC. And to turn it on or off, you can choose to switch between them. To do that, navigate to Settings > Privacy > Diagnostics & feedback and from there, select Basic under the Diagnostic Data section. After that, go back to Settings and go to Update & security > Troubleshoot. Once you’re there, you should see a warning message saying, “Share Full Diagnostic data to get additional troubleshooting recommendations”. Based on the message, Microsoft will only offer the recommended troubleshooting based on the Full Diagnostic data which it collects from your computer. On the other hand, if you know how to navigate and use the Windows Registry, then you can enable or disable the Recommended Troubleshooting via Registry Editor but before you proceed, make sure that you create a System Restore point. Once that’s covered, follow these steps:

• Tap the Win + R keys to open the Run dialog box and type “regedit” in the field and tap Enter to open the Registry Editor.
• Next, navigate to this registry path: HKEY_LOCAL_MACHINESOFTWAREMicrosoft
• From there, look for the key named “WindowsMigration”. If you can’t find it, just right-click on the left pane and create a new key and then name it “WindowsMigration”.
• After that, create a DWORD “UserPreference” and double click on it to set its value to “0” if you want to turn it off or “1” if you want to turn it on.
• Exit the Registry Editor and restart your computer to apply the changes made.

Note: The Recommended Troubleshooting functionality can look into the error logs sent back to the Microsoft team and use an algorithm to set up a solution for you and they’re nothing but Diagnostics and Feedback data that Windows collects and sends back to Microsoft. Moreover, the recommendations are only visible if you are connected to the internet, else it will show the same message.

Stop C00002lA Fatal System Error- What is it?

C00002lA Fatal System Error is a blue screen of death error that may occur when you start your Windows NT 4.0 based computer. This error causes the screen to turn blue and the system also shuts down. The stop C000021A error message is displayed in the following format:

Stop c000021a {Fatal System Error} The session manager initialization system process terminated unexpectedly with a status of 0xc0000017 (0x00000000, 0x0000000) The system has been shut down.

Error Causes

The stop C000021A error occurs when either Crsrss.exe or Winlogon.exe fails. When the Windows NT kernel identifies that either of these processes has failed, it stops and the error code stop C000021A appears on the computer screen. Here are some of the underlying causes for the stop C0000021A error:

• The incompatible third-party program
• Hard disk issues
• Service pack installation has failed
• Mismatched system files have been installed
• Bad and invalid registry keys

Further Information and Manual Repair

To resolve the stop C000021A Fatal System Error on your PC try the following solutions:

• Remove Incompatible Third Party Programs

If the error occurred after you recently installed a new program, then it is advisable to remove that program. The error occurs due to the incompatibility of the program. To remove the program go to the start menu and click on the control panel. Now click on Add/Remove Program tab and double click on the program name that you recently installed and remove it from the list. Once removed, not reboot your PC. Reinstall a compatible program and run it. It is most likely to resolve the issue. However, if the stop C000021A error still occurs, then it means the problem is critical. It is related to the registry.

• Repair and Restore the Registry

This procedure is slightly long and tricky. To try it, you need to be technically sound. Here’s what you have to do: first create a parallel installation of Windows NT. Start your PC to the parallel installation and then open the Registry Editor. On the Registry Editor’s Windows menu click HKEY_LOCAL_MACHINE on Local Machine and then click Load Hive. Now type the path %systemroot%system32configsystem into the System hive of the prior installation. Then click open. Here you will be prompted to enter the name of the key, type TEST. Note the setting for the current DWord value in the preceding registry key. This is 0x1 and is denoted by CURRENT:Reg_Dword: 0x1. This value indicated that the Current Control Set for your original Windows NT installation corresponds to ControlSet001 in this window. Now if the value is 2, it indicated that the Current Control Set corresponds to ControlSet002. Now locate the following registry key: HKEY_LOCAL_MACHINETESTControlSetXXXControlSession Manager. XXX is the Current Control Set Value. And delete any pending file rename operation entries. Then click TEST hive and then click Unload Hive. After that again repeat the process, open the registry menu and click load hive, here type the path %systemroot%system32configSoftware to the Software hive of the prior installation and then click open. Now you type TEST 2 when you are prompted for the name of the key. Remove any pending file rename operations entries in the following registry keys: HKEY_LOCAL_MACHINETEST2MicrosoftWindowsCurrentVersionRunOnce HKEY_LOCAL_MACHINETEST2MicrosoftWindowsCurrentVersionRunOnceEx Now click TEST2 hive and then click unload hive. Quit the Registry Editor and then restart your original installation. This will resolve the stop C000021A error.

Windows defender error 0x800700AA, service can not be started comes when the user is trying to run Windows defender scan on their system. This kind of behavior happens for two reasons mostly, third-party application conflict or corrupted system files. In this article, we will tackle both scenarios and provide you with solutions in both cases.

Third-party application conflict

In this rare scenario when Windows defender can not start scan due to conflict with installed service or application in the system solution is quite simple. Restart your PC into safe mode and run the scan from there. In a safe mode environment, minimum drivers and services are only loaded eliminating any conflicts that might occur when everything is booted. If Windows defender can not run the scan in safe mode and you get the same 0x800700AA error then you can eliminate application conflict as a reason and move to the next solution which will tackle corrupted system files. If you, however, managed to run a scan then you have a rare third-party application conflict, you can boot normally into windows and try to eliminate one by one to see which one is causing the issue. The safest bet would be to start with security software because most of the time that is what causes conflicts in running services and applications.

Corrupted system files

If the previous solution has not provided you with results then you have system file corruption that needs to be fixed. Move from one solution to another as presented below:

1. Run SFC scan

   SFC scan is a built-in Windows tool for solving corrupted system files issues, it is fully automated and does not require from the user any kind of knowledge or information. To run it and scan the system do the following: Press ⊞ WINDOWS + X to open the secret menu Left-click on the command prompt (admin) In command prompt type SFC /SCANNOW and press ENTER Wait for the process to finish, do not interrupt it and once it is done, restart your computer

2. Run DISM scan

   DISM scan is similar to SFC scan but it tackles different types of system file corruption and it is recommended to run it also after SFC has been completed. Please note that for DISM scan to be successful you will need a stable internet connection since DISM will replace corrupted files with new ones downloaded from Microsoft. To run it do the following: Press ⊞ WINDOWS + X to open the secret menu Left-click on the command prompt (admin) inside command prompt type: exe /online /cleanup-image /scanhealth followed by ENTER, then type: Dism.exe /online /cleanup-image /restorehealth also followed with ENTER. Leave scan to finish and reboot your PC