How To Fix the D3dx9_43.dll Error Code

Error Code C0000135- What is it?

C0000135 is a blue screen of death error code (BSoD) also referred to as the ‘Stop’ error. This error code usually pops up on the screen at startup. The system stops and displays the error code:

Stop: c0000135 {Unable to Locate DLL} The dynamic link library FILE_NAME could not be found in the specified path Default Load Path

Solution

Error Causes

There are multiple reasons behind the error code C0000135 BSoD such as:

• Missing and damaged .DLL files which is linked to registry corruption
• Malware attack
• Viral infection

When this error code pops, the computer screen turns blue and hampers your ability to use Windows successfully. Nonetheless, if the error C0000135 is not repaired timely this error can cause a great deal of damage to your PC. It puts you at risk of:

• Data Loss with possibly no chances of recovery
• System Failure and crash
• Cybercrime if malware is the underlying cause of the occurrence of the error code C0000135

To avoid serious PC damages and inconvenience it is advisable to repair this error immediately.

Further Information and Manual Repair

There are two ways to fix the error code C0000135:

1. Hire a Professional
2. Download Error Tools PC Repair

Hire a Technician

Hiring a professional can be costly. You may have to pay hundreds of dollars to the technician to resolve this issue. However, the latter option is not only money-saving but also time-saving, convenient, and simple. In fact, it is so easy that even if you have no technical knowledge you can still work your way around it and repair the error in seconds.

Download Restoro

Restoro is a top-quality, efficient, and multi-functional PC fixer. It is integrated with cutting-edge technology. It has a comprehensive suite of advanced utilities like an intuitive registry cleaner, powerful anti-virus, and a smart system stability detector. All of these exciting and highly functional features are combined together in one. With this helper, you don’t need to search for the underlying cause of the error. When you experience the BSoD error code C0000135 on your system all you have to do is run it for a scan and its intuitive in-built technology will detect the issues and causes in no time and display them to you in the form of a comprehensive scan report. Once the scan is complete, you just have to hit the repair tab to resolve it. It’s that easy and fast! Restoro is powered by a highly functional registry cleaner. This cleaner helps detect all the errors related to the registry. It cleans the unnecessary files cluttering and damaging the hard disk including the junk files, invalid registry entries, internet history, and the files from the programs that you have uninstalled on your PC. These files acquire a lot of disk space and damage .dll files as well. Overloaded registry also slows down the system and the CPU and RAM then require more power to start and function. The registry cleaner embedded in the Restoro removes and wipes out all this unnecessary clutter, clears up the disk space and repairs the damaged files, and corrupted registry, and thus resolves the error code C0000135 on your system. Restoro also serves as a system optimizer. And when you repair issues on your PC with this helper, you’ll see a massive difference in the speed and performance of your computer. It will run smoothly and boot efficiently. Restoro is safe to use. It is bug-free and used widely by PC users experiencing different types of PC-related issues including the error code C0000135. It has easy navigation and a user-friendly interface. You can download and run Restoro on all Windows versions. Click here to download Restoro today!

Have you ever deleted a file by mistake? Do not feel bad, we all have, but what if you deleted the file by mistake and then you went to Recycle bin to restore it only to find out that the bin is empty? If you experienced this kind of issue then you know how unpleasant and frustrating it is but do not worry, we are here to help and provide you with solutions to this problem and hopefully get your file back. Follow the next steps from first to last since they are organized in a way to minimalize the permanent deletion of lost files.

1. Refresh Recycle bin view

   If you spend any amount of time on this site reading through articles, you know I am a big fan of simple and effective solutions and there is nothing simpler than a single press of a button. Open your recycle bin and press F5 to refresh view or right-click anywhere inside and choose refresh. If your file does not appear with this method go to the next step.

2. Set Windows to show hidden system files

   In order for this to work first, you will need to open File Explorer by pressing ⊞ WINDOWS + E When File Explorer opens go to VIEW > OPTIONS. Inside options select “Show hidden files, folders, and drives”, uncheck “Hide protected operating system files (Recommended)”, and click APPLY > OK Go to the recycle bin and check to see if files have managed to show up.

3. Check if Don't move the file to the recycle bin is enabled

   Right-click on recycle bin and choose properties, under properties, there is the option that says Don’t move files to the Recycle Bin, Remove files immediately when deleted. This option is not selected by default, but it could be turned on by someone else or by mistake. If you see that this option is enabled sadly your file is gone and you will have to get the file back by using some third-party undelete application, uncheck this option to prevent future deletion of files by mistake.

4. Increase recycle bin size

   This will not help you to get your file back sadly but it will help you in storing more files in recycle bin. This is helpful since if you reach your recycle bin limit all further files will be permanently deleted and not been able to get them back. So by increasing bin size you will have more space for deleted files to be saved. To do that, right-click on Recycle Bin, select Properties. Now, increase the Maximum size from the Custom size option, and click Apply and OK.

5. Reset recycle bin

   To reset and fix corrupted recycle bin do the following: Press ⊞ WINDOWS + X to open the secret Windows menu and click on command prompt (admin) In the command prompt type in the following: rd /s /q C:\$Recycle.bin Reboot your system

The GDI32.DLL is a DLL (Dynamic Link Library) file that was developed by Microsoft. It is an essential file of the Windows OS as it contains instructions and information for exe files to follow. These DLL files also use to store the various procedures and codes for the Windows programs. It is considered an essential component of Windows because it ensures that all the programs on Windows are operating properly. So, if the gdi32.dll not found on your computer, then it can negatively impact your computer and the associated programs. Though DLL files used to be so efficient and convenient, they are extremely vulnerable to errors and issues.

1. Perform SFC scan

   Press ⊞ WINDOWS + X to open the Windows menu From the menu choose command prompt (admin) In command prompt type sfc /scannow and press ENTER Leave the computer for the operation to be completed and Reboot your computer

2. Run DISM

   Press ⊞ WINDOWS + X to open the Windows menu From the menu choose command prompt (admin) in command prompt type: DISM.exe /Online /Cleanup-image /Restorehealth and press ENTER wait for the process to be finished and Reboot your computer

3. Update device driver

   Go to your manufacturer's website and update drivers for your components with the latest versions.

4. Update Windows

   If you have an update ready for Windows, update it and see if this will remove the error

5. Scan computer for malware

   Perform a full PC scan for malware to see if this is causing issues with the GDI32.DLL error.

6. Download file

   One solution is to download a file from the official site and place it in the corresponding folder.

7. Perform System restore

   Rollback system restore before the issue happened and your Windows will be working as intended

If you encounter the BAD_SYSTEM_CONFIG_INFO Blue Screen error in your Windows 10 PC, then read on as this post will guide you in fixing this issue. Usually, this kind of Blue Screen error is caused by some issues with the Boot Configuration Data file. The main issue inside of the Boot Configuration Data file is that either some boot order files or older files might be in conflict with the newer ones or the stable ones and thus triggering the BAD SYSTEM CONFIG INFO Blue Screen error. This kind of Stop error also indicates that there is an error in the Windows Registry which is why you need to update potential culprit drivers as well as edit some entries in the Registry if need be. But before you get started, make sure that you create a System Restore Point first. After creating a System Restore Point, try to boot your computer into Safe Mode and then restart your computer normally. However, if it doesn’t work, proceed to the given options below.

Option 1 – Run System Restore

Performing System Restore might help you in fixing the BAD SYSTEM CONFIG INFO 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 2 – Update or rollback your device drivers

If the first option didn’t work for you, then it’s time to either update or roll back the device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Open the Devices Manager from the Win X Menu.
• Then locate the device drivers and right-click on them to open the Properties.
• After that, switch to the Driver tab and click on the Uninstall Device button.
• Follow the screen option to completely uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically.

Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 3 – Try fixing the Windows Registry files

In order to fix the Windows Registry files, you need to make a bootable Windows 10 USB drive and then boot your PC using it. To do so, refer to the steps below.

• Once you see the Welcome Screen, click on Next.
• Then click on the “Repair your computer” option located on the bottom-left section of the window.
• Next, click on Troubleshoot > Advanced Options > Command Prompt.
• After opening Command Prompt, execute each one of the commands listed below in the sequence that they are given:
  • CD C:WindowsSystem32config
  • ren C:WindowsSystem32configDEFAULT DEFAULT.old
  • ren C:WindowsSystem32configSAM SAM.old
  • ren C:WindowsSystem32configSECURITY SECURITY.old
  • ren C:WindowsSystem32configSOFTWARE SOFTWARE.old
  • ren C:WindowsSystem32configSYSTEM SYSTEM.old
• After executing the commands given above, type in the next ones below and make sure to execute them in the given sequence below.
  • copy C:WindowsSystem32configRegBackDEFAULT C:WindowsSystem32config
  • copy C:WindowsSystem32configRegBackSAM C:WindowsSystem32config
  • copy C:WindowsSystem32configRegBackSECURITY C:WindowsSystem32config
  • copy C:WindowsSystem32configRegBackSYSTEM C:WindowsSystem32config
  • copy C:WindowsSystem32configRegBackSOFTWARE C:WindowsSystem32config
• Now type “exit” to close Command Prompt.
• Restart your PC for the changes to take effect.

Option 4 – Run a Memory Check to test RAM

On the other hand, you can also fix the BAD SYSTEM CONFIG INFO Blue Screen error by running a Memory Check using the Windows Memory Diagnostic. Refer to these steps to do so.

• Tap the Win + R keys to open the Run dialog box.
• Then type “mdsched.exe” in the field and hit Enter to open the Windows Memory Diagnostic.
• After that, the Windows Memory Diagnostic will give out two options such as:

1. Restart now and check for problems (recommended)
2. Check for problems the next time I start my computer

• Select any of the given options. After that, your computer will restart and check for memory-based issues upon the restart. If there are any issues, it will automatically them.

Option 5 – Rebuild BCD files and repair MBR files

Like what you did on the third option above, you also have to make a bootable Windows 10 USB drive for this option and then boot your Windows 10 PC using it.

• Once you get to the Welcome Screen part, click on Next.
• Afterward, click on the Repair your computer option located on the bottom-left part of the window.
• Then click on Troubleshoot.
• Next, select the Advanced Options and then Command Prompt.
• Once Command Prompt has been pulled up, enter each one of the following commands and in the sequence that they are given to rebuild BCD files and repair MBR files:
  • bootrec /repairbcd
  • bootrec /osscan
  • bootrec /repairmbr

• Now type “exit” to close Command Prompt and then restart your computer to successfully apply the changes made.

As you know, Windows Updates are essential for your operating system as it keeps it protected from potential threats, fixes bugs and improves your experience in using Windows 10. However, there are instances when Windows Updates also cause errors and one of them is the Windows Update Error 0x8024000B. One of the causes of this particular Windows Update error is that Windows was not able to read the Update Manifest file which is needed to install the Windows Updates. This means that the operation was canceled by either the service or the user. On the other hand, this error could also occur if you are not able to filter the results. When you encounter this error, you will see an error message that says, “WU_E_CALL_CANCELLED: Operation was canceled”. This indicates that the operation was canceled by the operating system itself. To resolve the Windows Update Error 0x8024000B, here are some suggestions you need to check out.

Option 1 – Try to run the Cleanup (Decline) Superseded updates PowerShell script

The first thing you can do to fix the Windows Update Error 0x8024000B is to run the Cleanup (Decline) Superseded updates PowerShell script. This is actually an easy fix since all you have to do is download and run it from the Microsoft Technet site. Once you’re done downloading and running the file, restart your computer and see if the error is fixed or not.

Option 2 – Try to rename the Spupdsvc.exe file

If the first option didn’t work, you can try renaming the Spupdsvc.exe file which is one of the reasons why you’re getting the Windows Update Error 0x8024000B.

• First, tap the Win + R keys to launch the Run utility.
• Next, type the following command and hit Enter to execute it in cmd:

 /c ren %systemroot%System32Spupdsvc.exe Spupdsvc.old

• The command you entered will rename the troublesome “Spupdsvc(.)exe” file to “Spupdsvc(.)old”.
• Now restart your computer after the command has been executed.

Option 3 – Try to restart various Windows Update-related services and components

You could also try to restart some Windows Update-related services to resolve the Windows Update error. Refer to the following steps to do so:

• Tap the Win + X key combination and select Command Prompt (Admin) to open Command Prompt with admin privileges.
• After opening Command Prompt, copy and paste each one of the commands listed below one by one and tap Enter right after you enter each command.
  • net stop wuauserv
  • net stop bits
  • net stop appidsvc
  • ren %systemroot%SoftwareDistribution SoftwareDistribution.bak
  • ren %systemroot%system32catroot2 catroot2.bak
• Once you’ve entered all the commands given above, they will stop all the Windows Update services that are running on your computer as well as clear the SoftwareDistribution folder, and reset the Catroot2 folder. Now you have to start all these Windows Update services you’ve just stopped by executing the following commands:
  • net start wuauserv
  • net start bits
  • net start appidsvc
  • net start cryptsvc
• After that, restart your computer and try to run the setup again, and see if the error is now fixed.

Option 4 – Try to run the Windows Update Troubleshooter

You should also try to run the built-in Windows Update troubleshooter as it could help you resolve the Windows Update Error 0x8024000B. To run it refer to these steps:

• Go to Settings and then click on Windows Update from the given menu.
• Next, click on the Troubleshoot option and select Windows Update from the given options to run the Windows Update troubleshooter.
• After that, follow the next on-screen instructions and wait until the process is completed, and check if the Windows Update Error 0x8024000B is fixed or not.

This post will help you fix the ATTEMPTED_WRITE_TO_READONLY_MEMORY Blue Screen issue with an error code 0x000000BE. If you encounter this kind of BSOD error when you try to boot into your Windows 10 computer, note that there are various possible causes for this error. It could be caused by an error with a device driver, hardware issues, or some error in the BIOS of your computer. The ATTEMPTED_WRITE_TO_READONLY_MEMORY Blue Screen error with a bug check of 0x000000BE appears when a driver tries to write a read-only memory segment. You’ll be able to see the name of the driver in the Blue Screen error if the driver that’s causing the error can be identified. You can also see it in memory at the location (PUNICODE_STRING) KiBugCheckDriver. In most cases, this kind of error is usually caused by various files such as iusb3hub.sys, ntkrnlpa exe or vhdmp.sys, ntoskrnl.exe, ntfs.sys, dxgkrnl.sys, tcpip.sys, atikmdag.sys, and win32k.sys. There are several possible fixes you can try to fix this issue but the main issue lies within booting into Windows since the error occurs as soon as you boot into your Windows 10 computer. Refer to each one of the options provided below to resolve the ATTEMPTED_WRITE_TO_READONLY_MEMORY Blue Screen error.

Option 1 – Try to rollback, update or disable drivers

The first thing you can do to fix the ATTEMPTED_WRITE_TO_READONLY_MEMORY Stop error is to roll back, or update, or disable device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Open the Devices Manager from the Win X Menu.
• Then locate the device drivers and right-click on them to open the Properties.
• After that, switch to the Driver tab and click on the Uninstall Device button.
• Follow the screen option to completely uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically.

Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 2 – Try running the Memory Diagnostic Tool

The Memory Diagnostic tool in windows can help resolve the ATTEMPTED_WRITE_TO_READONLY_MEMORY Blue Screen error by checking and automatically fixing any memory-based issues. To run it, refer to these steps:

• 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 your preferred option, your computer 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 3 – Try to update the BIOS

Updating the BIOS can help you fix the ATTEMPTED_WRITE_TO_READONLY_MEMORY BSOD error but as you know, BIOS is a sensitive part of a computer. Even though it is a software component, the functioning of the hardware depends on it largely. Thus, you must be careful when modifying something in the BIOS. So if you don’t know much about it, it’s best if you skip on this option and try the other ones instead. However, if you are well-versed in navigating the BIOS, then follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “msinfo32” in the field and press Enter to open System Information.
• From there, you should find a search field on the bottom where you have to search for the BIOS version and then press Enter.
• After that, you should see the developer and version of the BIOS installed on your PC.
• Go to your manufacturer’s website and then download the latest version of BIOS on your computer.
• If you are using a laptop, make sure that you keep it plugged in until you have updated the BIOS.
• Now double click on the downloaded file and install the new BIOS version on your computer.
• Now restart your computer to apply the changes made.

Option 4 – Try disabling BIOS Memory Options

Disabling the BIOS Memory options such as Caching and Shadowing can help you in fixing the ATTEMPTED_WRITE_TO_READONLY_MEMORY Stop error. All you have to do is enter the BIOS first and then use the Arrow and Enter keys to select your choices. And if you can’t seem to find it, look for specific instructions from your OEM or you could also look out for instructions from the manufacturer of your motherboard.

Option 5 – Try running the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like ATTEMPTED_WRITE_TO_READONLY_MEMORY. 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.

Ehshell.exe Application Error - What is it?

Ehshell.exe is a type of .exe (executable file). This file functions as an essential component of the Microsoft Media Center.  By default, it is located in a subfolder of C:\Windows. Ehshell.exe application error is an error code that pops up when tasks in the Media Center freezes. The Ehshell.exe application error is usually displayed on the screen in the following format:

“ehshell.exe – Common Language Runtime Debugging Services Application has generated an exception that could not be handled. Process id=0xa18 (2584), Thread id=0xa24 (2596).”

Solution

Error Causes

Ehshell.exe application error is triggered when PC users perform repetitive tasks in Media Center on a Windows XP Media Center Edition. The computer stops to respond and the error message is displayed. This error occurs if users perform one or more of the following repetitive tasks in the Media Center:

• Repeated resize, restore and minimize the Media Center Window
• Schedule TV shows to record
• Repeatedly change the channel while Media Center is in a window
• Ehshell.exe file corruption due to malware infection or registry issues

Though this is not a fatal error, to avoid any kind of inconvenience, it is advisable to fix the error right away.

Further Information and Manual Repair

To fix the ehshell.exe application error on your system, you don’t have to hire a professional and spend hundreds of dollars on repair. Here are some of the best and most effective do-it-yourself methods that you can try to resolve this issue on your PC immediately.

Method 1 - Install the Latest Service Pack for Microsoft Windows

To repair the issue, install the latest Windows service pack. A service pack is basically a Windows update, often combines previously released updates that help make Windows more reliable. These are offered free of charge on Microsoft’s official website.  To get started, simply log on to Microsoft’s official website and download the latest service pack compatible with your Windows version. The installation process may take 30 minutes to install. And you will be prompted to restart your PC about halfway through the installation process. Once the Windows Service Pack is installed, the ehshell.exe application error will be fixed. If the error still persists, then try method 2.

Method 2 - Scan for Malware

Ehshell.exe application error may also appear on your PC due to malware infection. Malware programs like viruses, Trojans, and worms deliberately give their malicious processes similar .exe file names, so it is hard to identify the malware. In such an event, it is advisable to download a powerful antivirus and scan your entire PC. Run it to remove all the hidden malware programs on your system. Once malware is removed, the ehshell.exe application error will be resolved.

Method 3 - Clean Registry

Sometimes .exe files can also get corrupt when the registry gets overloaded with unnecessary and obsolete files. If this is the underlying reason for the error code occurrence then it is advisable to download Restoro. This is a multi-functional and user-friendly PC Fixer deployed with a registry cleaner. It removed all the unnecessary files, cleans and repairs the registry in seconds thereby fixing all registry-related errors. Click here to download Total System Care and resolve the Ehshell.exe application error on your PC.

As you know, the Windows Firewall is designed not just to protect your computer from viruses and malware, and other security threats but it’s also designed to block any program from accessing the internet. Users are given the option to block both inbound and outbound traffic for any apps on their computers. However, this kind of option can often lead to not being able to access the internet. In such cases, when you try to run the Windows Firewall Troubleshooter or the Windows Network Diagnostic troubleshooter, it will throw an error message that says, “Windows Firewall is preventing connections to your computer. The Windows Firewall rule HSS DNS Leak Rule may be blocking your connection”. If you are in this kind of scenario, then you’ve come to the right place as this post will guide you on how exactly you can fix this error. When you encounter this kind of error, there are several options you can check out to fix it. You can try to allow an app or feature through the Windows Firewall or uncheck the HSS DNS leak rule in both private and public. For more details, refer to the suggestions provided below.

Option 1 – Try to allow an app or feature through Windows Firewall

The first thing you can do to get rid of the error is to allow a feature or app through the Windows Firewall. To do this, follow these steps:

• Open the Windows Defender Security Center.
• From there, select the Firewall and Network Protection option.
• Next, click on the “Allow an app through firewall” option and then click on the “Change Settings” button and make sure that you have administrative privileges.
• After that, select the app or feature you want to allow through the Firewall from the menu. You also have the option to manually add the app by using the “Add an App” option.
• Then select the between the type of network an app can access such as:
  • Private Network will allow the app to connect to the internet only at home or work.
  • Public Network will allow the app to connect to the internet from anywhere, including Public WiFi hotspots.

• Once done, restart your computer and see if it fixed the error or not.

Option 2 – Try to uncheck the HSS DNS leak rule in both private and public

The next thing you can do to fix the error is to uncheck the HSS DNS leak rule in both private and public. You can do this by following these steps:

• Open the Windows Defender Security Center.
• From there, select the Firewall and Network Protection option.
• After that, click on the “Allow an app through firewall” option and then click on the “Change Settings” button and make sure that you have administrative privileges.
• Next, scroll down until you see the HSS DNS leak rule in both private and public option and then uncheck it.
• Now restart your computer and check if the error is now gone.

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.

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.