The Steam Autumn sale is coming!

What Is Sndvol32.exe Error?

Sndvol32.exe is actually an important part of the Windows operating system. Responsible for managing the sound-card volume and running programs properly, the problem occurs when error messages appear. The user will be unable to listen to music on the system. Usually, Windows XP users encounter the Sndvol32.exe error.

Solution

Error Causes

Sndvol32.exe error can be caused by any one or several of the reasons listed below.

• Accidental deletion of the DLL file from the system
• Damage to the DLL file due to spyware or virus infection
• Improper removal of software
• Unintentional overwriting on the DLL file by a mismatched version
• Obsolete hardware drivers
• Several obsolete/invalid registry entries
• Corrupt registry entries

Regardless of what triggers the Sndvol32.exe error, it is of utmost importance to take immediate measures to fix the problem and to keep it from occurring again.

Further Information and Manual Repair

If you are looking for ways to fix this error manually, the Windows functionality of System Restore will come into play in this particular scenario. In case the error is caused by a damaged or corrupt file, performing System Restore is an ideal choice as it will allow you to not only get a fresh copy of the operating system, it will be possible for you to remove the error at the same time as well. The procedure for performing System Restore is outlined below as follows.

• Click on the Start menu and type ‘System Restore’ in the search box.
• When the icon for ‘System Restore’ appears, click on it.
• Now type ‘Restore’ in the search box that appears on the start menu.
• The window for the System Restore center will now appear.
• Now you have two options. You can either opt for “Recommend Restore” which is the case where the system itself will choose a restore point for you or you can select “Choose a different restore point”. Users are advised to choose the latter option as it is more customizable.
• Users can now select from a list of restore points that have been created before. If you observe closely, you will realize that one of the restore points is prior to the occurrence of the Sndvol32.exe error.
• Click on the restore point. Once you have confirmed your selection, your system will restart and it will roll back to its previously selected restore point.

One recommendation is to perform the system restore in Windows Safe Mode. This is just to ensure that the System Restore is performed smoothly and any potential problems are kept at bay.

In case you don’t know, Windows 10 supports installation and use of a number of removable devices which includes plug and plays mouse, keyboard, and other USB-based devices. But this could actually pose a threat to the integrity of a computer system and thus, some organizations pose a restriction in using these kinds of devices. the restriction on these devices is also useful especially if you keep on leaving your computer idle and someone tries to mess it up by plugging in a removable device. In such situations, the restriction will defend the user against data theft. Thus, in this post, you will be guided on how you can prevent the installation of removable devices on your Windows 10 computer. There are two options that can help you in preventing the installation of any removable devices on your computer – you can either try to use the Registry Editor or use the Group Policy Editor instead. Follow whichever option you want to use the instructions given below but before you start, don’t forget to create a System Restore Point first.

Option 1 – Prevent installation of Removable Devices via Registry Editor

• Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and hit Enter to open the Registry Editor.
• Next, navigate to this registry path: HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsDeviceInstallRestrictions
• From there, look for a DWORD named “DenyRemovableDevices” and set its value to “0”. On the other hand, if you can’t find this DWORD, just simply create it and set its value to 0.
• Once done, exit the Registry Editor and reboot your PC to apply the changes made.

Option 2 – Prevent installation of Removable Devices via Group Policy Editor

Keep in mind that the Group Policy Editor is not available in the Home Edition of the Windows operating systems. Thus, if you are using one, just stick to the first option, otherwise, proceed to the following steps.

• Tap the Win + R keys to open the Run utility and type “gpedit.msc” and click OK or tap Enter to open the Group Policy Editor.
• After that, go to this policy setting: Computer ConfigurationAdministrative TemplatesSystemDevice InstallationDevice Installation Restrictions
• Next, look for the “Prevent installation of removable devices” entry and once you find it, set it as “Enabled”. From this window, you should see the following description of this policy setting:

“This policy setting allows you to prevent Windows from installing removable devices. A device is considered removable when the driver for the device to which it is connected indicates that the device is removable. For example, a Universal Serial Bus (USB) device is reported to be removable by the drivers for the USB hub to which the device is connected. This policy setting takes precedence over any other policy setting that allows Windows to install a device. If you enable this policy setting, Windows is prevented from installing removable devices and existing removable devices cannot have their drivers updated. If you enable this policy setting on a remote desktop server, the policy setting affects redirection of removable devices from a remote desktop client to the remote desktop server. If you disable or do not configure this policy setting, Windows can install and update device drivers for removable devices as allowed or prevented by other policy settings.”

• Then click the Apply and OK buttons to save the changes made.
• Now restart your computer to save the changes made. This should prevent the installation of any removable devices in your Windows 10 computer.

TPM, also known as Trusted Platform Module, is a specialized chip used for security as well as encryption of users’ private data like Fingerprint, Facial data, and many more. TPM also comes with a Management Console and if you are not able to load the Management Console and you got the “Cannot load Management Console” error instead, read on as this post will guide you in fixing the problem. This type of issue usually happens when you clear or disable the TPM using the settings in the BIOS and so when you run the Trusted Platform Module Management console, you encounter the error. To fix the “Cannot load Management Console” error in your Windows 10 computer, here are some options you should check out.

Option 1 – If TPM is cleared in the BIOS:

If the Trusted Platform Module is cleared in the settings of the BIOS, you have to close and restart the TPM Management console or TPM.msc once again. It could be that the TPM Management has to reload the changes again after you’ve made them which is why you encounter the “Cannot load management console” error.

Option 2 – If TPM is disabled in the BIOS:

If you opted to disable TPM using the BIOS settings or you have turned it off by accident, then you have to enable it back and you have two options to do that – you can either enable TPM from the BIOS or using the Windows PowerShell. For more details, refer to the instructions below.

Enabling TPM from the BIOS:

• You need to first reboot your PC and then go to the BIOS.
• From there, look for TPM under the security options and in case the TPM management option has been disabled or greyed out, refer to the sub-steps given below to make it active again
  • Enable the Admin password in the BIOS.
  • Then go back to the TPM settings and check if the TPM management is already available.
• After that, you should now be able to enable TPM. Remember that it’s always a good idea to have an ADMIN password for your BIOS as it makes sure that no one can change the settings in your computer BIOS and Security level options.

Enable TPM via Windows PowerShell:

• This second option is a lot easier compared to the first one if you have admin privileges. So once you’ve opened the Windows PowerShell with admin privileges, you need to run the following command:
  • $tpm = gwmi -n rootcimv2securitymicrosofttpm win32_tpm
  • $tpm.SetPhysicalPresenceRequest(6)
• After you execute the commands given above, you need to restart your computer.
• Now, once your computer has restarted, you need to accept any BIOS prompts and then check if the “Cannot load management console” error is now fixed.

A computer with no internet connection is like a mobile phone that can’t call nor text though you can still use it for other things. So if you are having problems with your computer’s internet connection, worry not as there are some basic things you can try before you go over the actual troubleshooting. Just make sure that you really have working internet. To verify it, try connecting your other devices. Aside from that, you must also make sure that your computer is connected properly over cable or connected to the router over the Wi-Fi. Once you have all these things covered, now’s the time to start troubleshooting the problem with the help of the instructions prepared below. To be more specific, this guide will walk you through what you can do when you encounter a particular internet connection problem where you get the Media State Media disconnected error message on your Windows 10 computer.

Before you troubleshoot the problem, you need to first check the internet connection status on your computer. To do that, follow these steps:

• Type in “cmd” in the Cortana search box.
• From the search results, right-click on Command Prompt and select “Run as administrator” from the context menu.
• After opening Command Prompt with administrator privileges, type in the ipconfig /all command and hit Enter.
• After you enter the command, you will see a list of all the connected media like the Ethernet, Wi-Fi along with its status, and more. From there, you need to check everything closely. I notice a message that says, “Media State . . . . . Media disconnected”, then your internet connection is indeed having issues.

Refer to the options below to fix the Media State Media disconnected error message on your Windows 10 PC.

Option 1 – Try resetting WINSOCK and IP Stack

• Type in “cmd” in the Cortana search box.
• From the search results, right-click on Command Prompt and select “Run as administrator” from the context menu.
• After opening Command Prompt, type in each one of the commands listed below
  • netsh winsock reset catalog – This command will reset the WINSOCK entries.
  • netsh int ipv4 reset reset.log – This command will reset the IPv4 TCP/IP stack.
  • netsh int ipv6 reset reset.log – This command will reset the IPv6 TCP/IP stack
• Once you’ve executed the commands listed above, restart your PC to successfully apply the changes made.

Option 2 – Check if your Network Adapter is disabled

If you’ve disabled the network adapters on your computer, then it’s most likely the reason why you’re getting the Media State Media disconnected error message. Thus, you need to enable it back.

• Open Settings and go to Network and Internet > Select Ethernet > Change adapter options.
• From there, right-click on the adapter and enable it.

Option 3 – Check the Wi-Fi Properties

Though this case is not common, Wi-Fi sharing has actually caused issues for some users. That’s why you need to check the Wi-Fi properties. Go to Network Connections and right-click on Wi-Fi and select Properties. From Properties, go to the Sharing tab and select the first option and click OK.

Option 4 – Try updating the Network driver

• Tap the Win + R keys to open the Run dialog box and then type in devmgmt.msc and tap Enter or click OK to open the Device Manager.
• Expand the section for the outdated device drivers.
• And then select the Network driver or any other outdated driver(s) and right-click on it/them.
• From the drop-down menu, select the Update Driver option and follow the on-screen instructions to install the latest version of the driver.
• Then also click on the option, “Search automatically for updated driver software.
• Restart your PC after the installation.

Note: If updating the Network driver didn’t work, you can go to the website of your PC manufacturer and look for the support section where you can download the drivers for your computer. You just need to take note of your PC’s correct model and model number so you can find the appropriate driver.

The Windows Update service, just like other services in Windows 10 may sometimes experience some issues and stop behaving properly. One of the issues you might encounter as you use the Windows Update service is the Windows Update error 0x8024A10A. This kind of error code signifies that the Windows Update service is shutting down. So if you encounter this error, read on as this post will guide you on how you can fix it. When you receive the Windows Update error 0x8024A10A, you may see this error message on your screen: “USO_E_SERVICE_SHUTTING_DOWN indicates that the WU Service is shutting down. This may happen due to a very long period of time of inactivity, a system hang leading to the service being idle and leading to the shutdown of the service. Ensure that the system remains active and the connections remain established to complete the upgrade.” You could try to restart your computer to resolve the problem since there are instances when a simple restart can fix errors. However, if it does not work, you might find the options provided below useful.

Option 1 – Try to restart the Windows Update Service

The first thing you can do to fix Windows Update error 0x8024A10A is to restart the Windows Update Service from the Services Manager. To do so, follow these steps:

• In the Cortana search box, type “services” and click on the Services icon to open the Services Manager. Alternatively, you can also tap the Win + R keys to launch the Run prompt and then type “services.msc” in the field and hit Enter to open the Services Manager.
• After opening the Services Manager, look for the Windows Update Service.
• Once you found it, right-click on it and check if the Service is stopped. If it is, then select the Start option. On the other hand, if the Windows Update Service is already started, just select the Restart option.
• After that, try to run the Windows Update again and see if the error 0x8024A10A is now fixed.

Option 2 – Run the Windows Update Troubleshooter

Since the Windows Update troubleshooter reviews the status of the services that support the process, it would prompt and fix it if there is anything that’s not right. Thus, you might want to run a built-in Windows Update troubleshooter to resolve the Windows Update error. It is one of the things you can check out as it is known to automatically resolve any Windows Update errors like error 0x8024A10A. To run this troubleshooter, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 3 – Run Microsoft’s online troubleshooter

Aside from the Windows Update troubleshooter, running Microsoft’s online troubleshooter might also help you fix the Windows Update Error 0x8024A10A. 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.

Option 4 – Try to run the Windows Update Service in a Clean Boot State

There are some instances that some conflicting programs installed in your computer might be the one that’s causing Windows Update error code 0x8024A10A. To identify which program is causing the problem, you need to put your computer in a Clean Boot State. To do so, follow the steps below.

• 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.)
• Now try to run the Windows Update Service again and see if Windows Update error 0x8024A10A is now gone.

Virtual Reality is slowly becoming standard in gaming. More and more affordable headsets are coming out lowering entry prices and making them affordable for all. But in a sea of new VR headsets, it is important to at least purchase a decent one that will perform nicely and hopefully last longer. Therefore in today’s article, we will address some of the best options currently available on the market,

Oculus Quest 2

With its Rift model, Oculus set itself as a big player in VR. Now the company is slowly bowing out of the dedicated, tethered VR headset with its latest Quest 2 designed to primarily be a standalone headset. In case you do not know, tethered headset means that the headset itself is connected to your PC and is using its power to drive your VR experience. Now technical specifications of Quest 2 are pretty OK and it can drive stuff pretty decently and if you want you can purchase the dedicated cable to connect it to your PC for the full experience of games requiring more capable hardware. Oculus Quest 2 is the cheapest headset on this list and with its stable performance, is highly recommended.

Valve Index VR

Although the headset itself is nothing revolutionary or special its controllers are. They can track individual finger movements, making games (that take advantage of them) much more immersive than the standard trigger grips on other controllers. The Index's higher refresh rate makes for smoother action, as well, which is another nice bonus. If you already have an HTC Vive or Vive Cosmos Elite, and their base stations (not the regular Cosmos), you can buy only the controllers.

Sony PlayStation VR

The PlayStation VR is compelling thanks to Sony backing its development, plus the PlayStation 4's affordability and availability compared with gaming PCs. All you need is the headset, a PlayStation 4, and a PlayStation Camera (now included with most PlayStation VR bundles). Not really the best of the bunch but still one of the top ones for console gaming. Sony is working on a new PlayStation VR system for the PlayStation 5, with redesigned controllers. The new headset hasn't been revealed yet, but the company has released a preview of the new controllers.

HP Reverb G2 VR

HP headset is one which you get if you want the best image quality in VR headset, sadly controllers did not follow the same quality of headset itself. But this is still a pretty decent headset overall and worth the purchase.

HTC Vive Cosmos

HTC's Vive Cosmos is the upgraded version of the Vive. It features a higher resolution and replaces the external base stations with outward-facing cameras for motion tracking. It's a comprehensive package for whole-room VR. HTC recently released the Vive Pro 2, a high-end VR headset targeting both enterprise users and consumers. This new headset features a 2,448-by-2,448 resolution display for each eye, making it the highest-resolution headset currently available. It's also more expensive than the Cosmos Elite. Sadly one thing that is bringing this headset down is the price.

Compare Exchange128 error – What is it

Some Windows 7 and Windows 8.1 users reported experiencing a Compare Exchange128 error when trying to upgrade to Windows 10. The error reads, “You can’t install Windows 10 because your processor doesn’t support CompareExchange128”. In order to upgrade to Windows 10 (64-bit), the CMPXCHG16B instruction must be present. If you receive this error, this mostly means that your CPU doesn’t have the CMPXCHG16B instruction.

Solution

Error Causes

The CompareExchange128 error normally occurs due to two possible reasons:

• CPU lacks CMPXCHG16b Instruction
• Old & Outdated BIOS – Even if your CPU has the CMPXCHG16b instruction, the CompareExchange128 issue can still occur if you have an older BIOS.

Further Information and Manual Repair

One main requirement to upgrade to Windows 10 is for your CPU to have the CMPXCHG16b instruction. You also need the right BIOS version to guarantee a smooth installation. See below on how to manually fix this issue.

NOTE: If you don’t feel confident using the manual methods listed below, it’s highly advisable to get help from an expert technician. If you don’t know someone, you can also use an automated tool to fix this.

Before performing any fixes, try to determine first if the cause of the error is due to your CPU lacking the CMPXCHG16b instruction. You can use a CPU Info tool that provides complete details about your processor, memory, and motherboard. If you’re looking for more in-depth information, you might also try command-line utilities. But, the safest and easiest way to check this is by simply searching online. Try using the search query: <CPU Model> CMPXCHG16b

Method 1 – Update your BIOS

This method will download the latest BIOS from your motherboard’s manufacturer. This makes sure your CPU has the CMPXCHG16b instruction needed to complete the Windows 10 64-bit installation. To update your computer’s BIOS, complete the following steps:

1. Determine first the current BIOS you have on your computer. Open System Information Windows app and type msinfo32 in the search bar. The BIOS version will appear under the processor speed. Record it somewhere.

2. Go to the support page of your motherboard’s manufacturer. Find if there’s any update on the BIOS that you’re currently using. If you find one, download the BIOS update file available. Make sure that you’re looking into the right model and you download all the necessary documentation. Otherwise, the BIOS update might not work.

3. Update your BIOS. Most BIOS update steps are straightforward. Just make sure to follow the steps provided.

Method 2 – Install Windows 10 32-bit version

If updating the BIOS doesn’t work, what you can do is install a 32-bit version of Windows 10 instead of the 64-bit version. Here’s how to do this:

1. Download and install the 32-bit version of Windows you currently have. If you have a Windows 7 64-bit version, get the 32-bit version of Windows 7. The same goes for Windows 8.1. When you do this, you might want to back up your files first. Remember that installing the 32-bit version works like other installations, and could delete some of your files.

2. After installing the 32-bit version, go to Updates and install all the necessary updates. This includes upgrading to Windows 10 if you’re asked to.

3. When you installed the Windows 10 upgrade, you’ll now have the Windows 10, 32-bit version installed. This will be the version activated on Microsoft servers. Despite this, the activated version stored is only applicable to your computer’s hardware, not the version of Windows 10.

4. Download Windows 10, 64-bit version.

5. Prepare an empty DVD or USB flash drive. Use Creation Media software then click the Create Installation Media for Another PC option.

6. Install the 64-bit Windows 10 version you downloaded from Step 4. Make sure not to put anything when you’re asked to input the serial number.

7. Once the installation is complete, you’ll have the 64-bit version of Windows 10.

Method 3 – Buy a new processor/motherboard

If the above two methods don’t work, there’s a great chance that this error occurs because of an outdated processor/motherboard. Your next possible solution is to buy an updated model that’s fully compatible with 64-bit Windows 10.

Method 4 – Download an automated tool

If all else fails, you might want to consider using this powerful automated tool to quickly fix the problem and any other computer-related issues.

Error Code 47 – What is it?

It is a device driver error that users encounter when they use Windows 2000 operating system and its later versions.

The error occurs when the connected peripheral device, upon removal using the ‘Safe Removal Hardware’ program, hangs up a problem within the process. The error prompt you then see is referred to within the operating system as error code 47.

It usually pops up on your computer screen with the following message:

Windows cannot use this hardware device because it has been prepared for "safe removal", but it has not been removed from the computer. (Code 47)

Solution

Error Causes

There are many factors responsible for the Error Code, the primary ones are listed below:

• An incomplete program installation
• An incomplete program uninstallation
• System recovery from viruses
• Corrupted Windows system registry entries

Further Information and Manual Repair

Error Code 47, like other device driver error codes, is relatively easy to solve. You can fix the error code in the following ways:

Method 1 – Reconnect the device to your computer

Unplugging and plugging the USB cable of the device into the computer is the easiest way to resolve the error.

Doing this will help refresh the system and increase the likelihood of the device driver files loading and function properly.

Method 2 – Restart your PC

Another simple method you can use to solve your PC error code is to simply restart your Windows system.

It may be that the error prompted upon connecting the device you have connected is merely a temporary problem, and upon restart, will resume functioning smoothly.

Method 3 – Manually uninstall then reinstall the device driver

If both of the above-listed methods fail to resolve the problem, you may have to resort to manually uninstalling and then reinstalling the device driver causing the problem.

This would be necessary since the remaining incomplete files due to a partial removal or installation of programs is what contributes to the error code. By uninstall and reinstalling the device driver program, it would lead to the completion of the files.

You can do this by firstly logging in as Administrator and open Device Manager. Select the device that is causing the problem and double click it and make sure that the peripheral is connected properly to the PC.

Upon opening, click on the ‘Driver’ tab and then select ‘Update Driver’. Make sure to refer to the system documentation that you received with your PC or computer to check for the motherboard details and driver specifics.

Method 4 – Use software to automatically download the driver

Manually uninstalling and reinstalling the driver will usually do the trick; however, it may be time-consuming especially when you would have to resort to your hardware user manual.

Therefore, using a program such as DriverFIX can save you a lot of time and frustration in having your device work properly on your computer.

DriverFIX, with its user-friendly approach to help you fix your PC issues, comes with an integrated database that detects which drivers you need to reconfigure within just a few seconds and downloads it automatically. It further ensures that your drivers are installed in their entirety leaving no room for any incomplete files to remain that create Error Code 47. It also has the added advantage of being able to backup and restores your files should there be the slightest possibility of system file damage. Thus, registry damage can be averted by letting the software roll back the system files to an earlier healthy checkpoint. DriverFIX is the answer to fixing your PC error codes accurately and quickly. Click here to download DriverFIX to fix Error Code 47 quickly and effectively!

Some Windows users are encountering the 0x800705b3 error code after failing to install a pending update on Windows 10. Most commonly this particular issue is reported to occur with Integrated webcam drivers updates and Bluetooth adapter driver updates. Follow the guide below in order to fix the issue and update your Windows successfully

Running the Windows Update Troubleshooter

The majority of users that were dealing with this issue reported that the issue was fixed after they ran the Windows Update Troubleshooter and applied the recommended fix.

1. Open a Run dialog box by pressing ⊞ WINDOWS + R. Inside the text box, type ‘ms-settings:troubleshoot’ and press ENTER to open up the Troubleshooting menu. Opening the Troubleshooting tab on Windows 10
2. Once you’re inside the Troubleshooting tab, move over to the right-hand section of the screen and click on Windows Update (under Get up and Running). Next, from the context menu that just appeared, click on Run the Troubleshooter.
3. Once you’re inside the Windows Update troubleshooter, wait until the initial scan is complete and see if a viable repair strategy is found.
4. If the scan has identified a strategy with the potential to fix your ongoing issue, click on Apply this fix and wait until the procedure is complete. Applying the fix Note: Depending on the type of fix that was recommended, you might need to follow an additional set of instructions before the fix will be properly imposed.
5. After you’ve done this, reboot your computer and wait for the next startup to complete.
6. Open Windows Update once again and see if the installation of this pending update is now successful.

Installing the pending Update Manually

Whether you’re experiencing this issue with an integrated webcam driver or with anything else, chances are you’ll be able to circumvent the apparition of the 0x800705b3 error by using the Microsoft Update Catalog to find, download and install the pending update manually.

1. Open your default browser and navigate to the root web page of the Microsoft Update Catalog.
2. Once you’re inside the Microsoft Update Catalog, use the search function (top-right corner of the screen) to search for the update that is failing.
3. After the search is completed and you get the list of results, look for an updated driver version that is compatible with your Windows version and CPU architecture.
4. Once you manage to identify the correct Windows Update, click on the hyperlink associated with the update that you want to install, then click the Download button and wait for the process to complete.
5. After the download is complete, use File Explorer to navigate to the location where you previously downloaded the update.
6. When you get to the correct location, right-click on the .inf file and choose Install from the context menu that just appeared. Note: If you have multiple failing updates with the same 0x800705b3, repeat the instructions above with every Windows Update that you’re having trouble installing.
7. At the end of this operation, reboot your computer and see if the problem is fixed at the next computer startup.

Enabling the Windows Installer Service

The Windows installer service is responsible for installing pending updates that get downloaded by the Windows Update component. If this service is disabled on your configuration, none of the updates waiting to get installed will get completed.

1. Press ⊞ WINDOWS + R to open up a Run dialog box. Inside the text box, type ‘services.msc’ and press ENTER to open up the Services utility.
2. Once you’re inside the Services screen, move over to the right-hand tab of the screen, scroll down through the list of services and locate the Windows Installer service. When you find it, right-click on it and choose Properties from the context menu that just appeared.
3. Once you are inside the Properties screen of the Windows Installer services, access the General tab, click on the Start button to force-start the service. Note: If you can, also change the Startup type to Automatic via the associated drop-down menu. However, depending on your administrator settings, this might not be possible.
4. Restart your computer and wait for the next startup to complete. Once your PC boots back up, attempt to reinstall the driver that was previously triggering the 0x800705b3 error and see if the issue is now fixed.

Performing a Winsock Reset

In case the 0x800705b3 error is related to some kind of network inconsistency (TCP or IP related), you might see Windows Updates failing due to bad data that forces the Windows to abort the installation of new pending updates. In this case, you should proceed by doing a complete Winsock reset procedure to fix the majority of the socket and temporary data-related issues that might cause this behavior. Several affected users have confirmed that this method was the only thing that allowed them to finally fix the Windows Update issue and install pending updates normally. Here are some step-by-step instructions that will walk you through the process of performing Winsock Reset:

1. Open up a Run dialog box by pressing ⊞ WINDOWS + R. Inside the text box, type ‘cmd’, then press CTRL + SHIFT + ENTER to open up an elevated Command Prompt. Accessing an elevated CMD prompt Note: When prompted by the UAC (User Account Control) prompt, click Yes to grant admin access.
2. Inside the elevated CMD prompt, type and taste the following commands in order and press ENTER after each one to effectively reset the TCP and IP data that might be responsible for the apparition of the 0x800705b3 error code:

   nbtstat -R
   nbtstat -RR
   netsh int reset all
   netsh int ip reset
   netsh winsock reset

3. Once every command above is processed successfully, you can go ahead and close the elevated Command Prompt and reboot your computer.
4. After the next startup is complete, repeat the installation of the Windows Update that was previously failing and see if the issue is now fixed.

Performing SFC and DISM Scans

If none of the ‘superficial’ causes have worked in your case, you should start considering some type of system corruption that might affect your computer’s ability to complete pending updates that are currently waiting to be installed. In case you find yourself in this particular scenario, you should run a couple of built-in utilities capable of fixing corrupted instances that might be currently affecting the Windows Update component. Our recommendation is to start with a simple System File Checker scan. An SFC scan will cross-check every Windows File against a local archive that maintains healthy copies. In case corrupted instances are found, this utility will swap the corrupted instance with the healthy equivalent.

Performing an SFC scan

Once the SFC scan is complete, reboot your computer and wait for the next startup to complete. After your computer boots back up, initiate a DISM scan. This utility works differently in the sense that it relies on a sub-component of Windows Update to download healthy copies for the corrupted Windows files that need to be replaced. Because of this, it’s important to make sure that you have a reliable Internet connection before initiating this operation.

Doing a DISM scan

After the DISM scan is complete, reboot your computer one final time and see if the issue is fixed once the next startup is complete.

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.