Enable or Disable Automatic Encryption

After so many years World of Warcraft is still among the most played MMORPG games in the world. It is still constantly updated with new content and tweak graphically in order to be relevant and fresh. But even the best or most popular ones can still have some minor issues and bugs from time to time. CAS System Was Unable to Initialize is the error that was reported lately by WOW players all around the globe and it happens in multiple Windows systems. In this guide, we will take with this issue and provide you with solutions on how to fix it so you can get back to enjoying the game itself.

1. 1. Repair WOW

      In battle.NET launcher select WOW and click on Options Click on Scan and Repair Let the process finish and then launch the game again

   2. Clean Windows registry

      Windows cleaning registry operation is a complex task and we will not cover each possible scenario here, instead of trying manually to find issues and clean registry download and install third party registry cleaner software.

   3. Run WOW with command line argument

      One of the solutions for this particular error is to run WOW with a specific command line switch: Run battle.NET client as administrator by right-clicking on it and choosing run as administrator If you are not signed in, sign in now Click on World of Warcraft to select it Click on options Click on Game settings Check the box associated with Additional command-line arguments When the box is selected you should've able to add inline argument or switch, add -uid wow_engb and confirm Run World of Warcraft

   4. Enable Secondary logon service inside Windows

      It was reported that enabling this service can fix the issue. Press ⊞ WINDOWS + R to open the run dialog Inside run dialog type in services.msc to open services windows Locate the Secondary Logon service Right-click on Properties from the context menu Inside the properties, screen click on the general tab Change the Startup type to Automatic and hit Apply to save the changes Run World of Warcraft

   5. Delete the cache folder

      Both indices and cache folder needs to be deleted in order to reset corrupted data. Make sure that both World of Warcraft and battle.NET are fully closed For this step to work, you will need to go into the folder where you have installed the World of Warcraft game. By default this is in C:/Program Files/World of Warcraft/ but if you have used another folder go there via file explorer. Once you are inside the folder locate the indices folder and delete it After that locate and delete the cache folder as well Restart your computer and start battle.NET

   6. Remove read-only attribute from WoW folder

      Another reason for CAS System Was Unable to Initialize error is because the World of Warcraft folder has been set to read-only and since the client does not have write privileges it will throw this error. To remove the read-only attribute from the folder go to your World of Warcraft installation folder but do not enter it Right-click on it instead and choose properties Under properties uncheck the read-only box and confirm. Run World of Warcraft

What is Error 1723?

Error Code 1723 is a peculiar error type common in Windows PC. It is related to the Windows Installer package. This error is displayed in the following format:

"Error 1723- There is a problem with this Windows Installer package. A DLL required for this install could not be run. Contact your support personnel or package vendor...”

You are most likely to come across the error code 1723 if the Java installation is not completed successfully. In other words, the error indicates that the installation process has failed.

Solution

Error Causes

The 1723 error may occur due to several reasons, the most common being:

• Corrupted installers
• Files are not extracted successfully
• Registry problems
• Missing DLL files

Further Information and Manual Repair

To resolve this issue on your PC, you don’t always have to hire a professional technician and pay hundreds of dollars to get it fixed. The error code 1723 may not be a common Windows PC error but it is easy to fix. Here we have listed some of the best and easiest DIY ways to resolve this error on your system. These solutions are so easy to perform that even if you are not a computer programmer or technically adept, you can work through them and resolve the error in just a few simple clicks. So, let’s get started:

Solution 1: Install the latest Java Version

If the Java version previously installed on your system is not working properly and showing 1723 error messages then it is advisable to install the latest Java version. However, to do this first you will have to uninstall the old version and then download the latest Java version on your PC from a trusted website to ensure it does not contain malicious viruses and malware.

Solution 2: Ensure the Required Files are extracted in the ‘Temp’ Folder for Installers

Another method to resolve the 1723 error code is to check whether the required files are extracted in the temp folder for installers or not. The error may occur if the location is incorrect and the account is not permitted to extract files in the temp folder. In this scenario, the best way to resolve the issue is to change the permissions of the temp folder. This can be done by logging in to your account and opening file explorer or ‘My Computer’. Now copy and paste this link address in the address bar: DL:UsersUSERNAMEAppDataLocal. Please note, here DL is the drive letter of the Windows drive, and in the username insert the username of the account that you are using. Now right-click the ‘temp’ folder. Select properties and click on the Security tab. After that click edit below the list and press add. Again type the username here and click OK. The next step is to select the added account from the list and tick ‘FULL CONTROL’ box under ‘Permissions for Username’. Click OK and then close the properties. Once this process is complete, now try running the installer again. This will most likely resolve the issue. Nonetheless, if the error still persists, then this means the underlying cause of the error is deeper than you think. The error may be related to registry issues. In such situations, try solution 3 to fix the error 1723 on your system.

Solution 3: Download Restoro.

When the error code 1723 is triggered due to registry issues, then it is advisable to scan your PC with Restoro. Registry issues should be resolved immediately because they pose serious threats to your system. It can lead to system failure, crash and valuable data loss. Registry basically saves practically all the information and activities performed on your PC including the unnecessary and obsolete files like junk files, cookies, temporary files, and invalid entries. If these files are not removed they can corrupt the registry, damage dll files and installers thereby generating error codes like 1723 on your system. The easiest way to repair and clean the registry in seconds is to run Restoro on your PC. It is a smart, intuitive, advanced, and multi-functional PC repair tool. It is embedded with multiple powerful utilities and is a one-stop solution for all PC related issues. This software is compatible with all Windows versions. It is deployed with a highly functional registry cleaner that scans and detects all registry issues on your PC and removes them right away. It wipes out the unwanted files, repairs the damaged dll files and restores the registry. Other powerful utilities that are embedded in this software include an antivirus, a system optimizer and Active X controls and class modules. To resolve 1723 error code on your PC today, click here to download Restoro.

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.

Program and features are Control panel section where once accessed contains all programs installed on the operating system. From these windows, any logged-in user can modify applications, uninstall them, etc. If for whatever reason you want to limit this access to users and remove this group from the control panel please do keep reading as we show you how you can achieve this desired result using two methods: via policy editor or registry editor. Feel free to use any provided method as both works (except on Windows 10 Home edition) and achieve the same thing, it all comes down to preferred preference on how you wish to do things.

Local group policy editor method

This method is more straightforward and easier perhaps than its counterpart but it has one significant drawback, it will not work on Windows 10 Home edition which does not have in itself a policy editor included. If you are using Windows 10 Home edition then feel free to skip this method and do it via registry editor. That being said let's start:

• Press ⊞ WINDOWS + R to open the run dialog
• Inside run dialog type in gpedit.msc followed by ENTER to open Group policy editor
• Go to User Configuration\ Administrative Templates\ Control Panel\ Programs\
• Double-click on the setting named Hide Programs and Features page
• Change the toggle option from Not Configured to Enabled
• Click on the Apply button and then the Ok button to save the changes
• at this point, everything is supposed to be applied and your changes should take effect immediately. However, it has come to our attention that sometimes this is not the case. If you are one of these users which for whatever reason have not experienced applying to set momentarily do not despair and follow this quick guide on how to refresh settings and apply them right away.
• Press ⊞ WINDOWS + X to open the hidden menu
• Click on command prompt (admin)
• In command prompt type in gpupdate /force and press ENTER in order to force update and set setting right away

Registry editor method

The registry editor method is a more complex one but it will be your only way of doing it if as mentioned you are running Windows 10 Home edition. As always it is highly recommended to make a backup of the Windows registry before tempering with it.

• Press ⊞ WINDOWS + R to open the run dialog
• Inside run dialog type in regedit and press ENTER to open the registry editor
• If you would like to make a backup of the Windows registry go to File > Export and save the backup on a secure location naming it as you wish
• Locate the following key inside the registry editor HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Programs
• Right-click on the right pane of the Programs key and choose the New > DWORD (32-bit) Value option
• Name the value as NoProgramsAndFeatures
• Double-click on the NoProgramsAndFeatures value to open it
• Change the value data to 1
• Save the changes
• Reboot the computer in order for changes to take effect.

note: you can always change values back in order to show again panel by changing the value to 0 in registry editor or choosing Not Configured or Disabled in the local group policy editor

A copy of Windows gets into a grace period when it is installed on a computer which means that you can use your Windows computer without any constraints on its feature. However, if you suddenly encounter an error code 0xC004F009 then this means that the grace period has already expired. In such cases, you will see the following error message on your screen:

“Error Code 0xC004F009, The Software Licensing Service reported that the grace period expired.”

One of the possible causes of this error is that it could be that the grace period has already expired way before the system was activated which is a result of which the system is in the Notifications state at this moment. The error code 0xC004F009 has something to do with MAK-enabled computers in an enterprise when it comes to Volume Licensing. One of the reasons that this error pops up is due to the possibility that the computer was not activated yet even when it was already connected to the Enterprise. Another most likely cause of the error is when the system was never connected with the Enterprise at all and the given grace period has expired before your computer system is activated. Whatever the real cause of this error, this post will guide you in fixing it. Just refer to the instructions given below to fix it.

Option 1 – Try activating Windows using the command-line tool

• First, you need to obtain your MAK key from the IT administrator.
• Once you have it, tap the Win + R keys on your keyboard and then type “cmd” in the field and hit Enter to open an elevated Command Prompt.
• After that, type this command and hit Enter to install the product key or replace the existing one: Slmgr.vbs –ipk <your mak key>
• Next, type another command and hit Enter: slmgr.vbs –ato
• Once you’ve executed the given commands, Windows should be activated after it connects to Microsoft servers and then gives it some time and try to check if error code 0xC004F009 is now fixed or not.

Option 2 – Try activating Windows using your mobile phone

Activating Windows 10 can also be done using your phone. Just note that you have to call Microsoft to do so.

• In the Start Search box, type in “Slui 4” and tap Enter.
• Next, select your country and click on Next.
• Keep the window open and call the toll-free number of the country you’re from.
• Afterward, a confirmation ID should be given by the automated system which you must take a note of.
• Finally, in the box on the window, type in the confirmation ID and click on the Activate button. That should do it.

Option 3 – Try to prolong the grace period

On the other hand, it is also possible for you to prolong the grace period but you might have to get another genuine Windows key for that. Before you proceed, you need to create a System Restore point first afterwards, refer to the steps given below to increase the grace period of the Software Licensing Service on your Windows 10 computer.

• Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field then hit Enter to open the Registry Editor.
• After that, navigate to this registry key: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionSetupOOBEmediabootinstall
• Next, change the value of the “mediabootinstall” key to “0”.
• Now open Command Prompt with admin privileges and then type this command and hit Enter: slmgr –rearm
• The command you just entered will add another grace period to your system activation. After that, you have to obtain a new key and then activate Windows.

Option 4 – Try running the Windows 10 Activation Troubleshooter

You can also try to run the Windows 10 Activation troubleshooter to help resolve the error code 0xC004F009.

• Go to Settings and then select Activation.
• After that, click on the Windows Activation and then troubleshoot. This will help you address most of the commonly found activation issues in Windows devices.

This Unresponsive Script problem information is most frequent on Firefox, which is among the top browsers worldwide. Firefox might show you these errors with the information, "Warning: Unresponsive Script". It is going to subsequently inform you that software to the web page you're trying to open is unresponsive, or has quit reacting. This means that the script has ceased functioning and may freeze or hang Firefox if not immediately resolved. You can easily solve this problem.

Solution

Error Causes

Before you can fix this error, you need to understand its primary cause. The biggest risk is that if left unchecked, Unresponsive Scripts will hang your browser and to an extension of your computer thus limiting your productivity. You may have to uninstall and re-install Firefox if the problem persists. Listed here are several of the very most typical reasons for unresponsive script:

• Programming Errors
• Interference by other Softwares
• Using an older outdated version of the program.

Further Information and Manual Repair

Most times, you have to do very little to fix this problem. Furthermore, a lot of the remedies supplied here do not require the assistance of a qualified professional technician. You can easily perform them and completely solve the error.

• If you wish to stop the error, keep your browser and add-ons up to date.

It's easy to update your browser and any add-ons therein. In most cases it's free. By upgrading your browser and add-ons frequently, you are effectively eliminating the risk of Unresponsive Script occurring and interfering with your work.

• Check for a poorly functioning background process

The sorts of background procedures that might result in the Unresponsive Software error include Javascript code, media plugin, and browser extension. You can stop the script from running while using Firefox thus eliminating the Unresponsive script error. Shutting the dialog box is just another easy way of eliminating the unresponsive script error information. Firefox offers you two choices in case of this malfunction. Either "Continue" or "Stop Script". Whatever alternative you pick, you can be certain the dialog box shuts, thus allowing you to continue browsing. The final solution. Contact Firefox about these errors on your browser. Oftentimes, these errors occur when you attempt to visit particular websites. Mark the offending websites' URLs and include them in your communications with Firefox. Sometimes you can also contact the website owner yourself and request them to check their website's code. Following are additional measures you can take to resolve the Unresponsive Script error.

• Waiting longer for the error to resolve itself automatically
• Blocking the offending script
• Yanking the guilty add-ons
• Disabling the hardware acceleration tool.

With one of these few steps, you won't have to worry about the Unresponsive Script error, can continue enjoying your browsing activities on Firefox.

The first major update for Windows 11, 22000.65 has brought some bug fixes and some new features. The previous update was just a bunch of small fixes but this time Microsoft has brought much more with this one.

Bug and security fixes:

• Patch for the PrintNightmare vulnerability.
• Taskbar icons not displaying after you rotate the screen back and forth.
• Date and time not following format settings.
• Contrast issues with File Explorer title bar
• Search dropping the first keystroke when you press the Windows key and type
• Blurry windows in ALT + Tab

Besides bug and security fixed newest update has also brought us some functional changes:

• The start menu can no longer be moved from center
• A search box appears at the top of the Start menu.
• Taskbar appears on secondary monitors.
• The refresh option appears on the jump list when you right-click the desktop. It was on the "Show more options" list before.
• New look for certain dialog boxes such as "battery low" or "display change"
• New snap layouts for portrait mode screens.
• Option to troubleshoot sound problems when you right-click the volume icon.
• Power mode settings on Power & battery settings menu.
• Right-clicking .ps1 files offers a "Run with PowerShell" option.
• New GIFs in the emoji panel in China

Honestly, I really like a search box on top of the start menu but really dislike the option to move it to left, I am sure that there are a lot of users who would feel more like at home if they could still move and set Windows to function and work how they want. It is very strange to me that Windows 10 was made to be so user-focused and been able to be user specific and Windows 1 takes most of these things away. I am not sure why Microsoft is going this way but I cannot really see how moving the taskbar on left is a programming issue or why it is wrong for example.

As you know, the Graphics Card in a computer is one of the important components in an operating system as they are responsible for rendering various objects in your computer. However, there are cases when the performance of this rendering can degrade and your computer can trigger a VIDEO_SCHEDULER_INTERNAL_ERROR Blue Screen of Death error instead. The VIDEO_SCHEDULER_INTERNAL_ERROR bug check has a value of 0x00000119 which means that the video scheduler has detected a fatal violation in your computer. Before you troubleshoot the problem, you might want to perform System Restore first as it might help you fix the Stop error. To perform System Restore, refer to these steps:

• First, press 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 Stop error is fixed or not.

If the VIDEO_SCHEDULER_INTERNAL_ERROR BSOD error is still not fixed after System Restore, then follow the given options below to further troubleshoot the problem.

Option 1 – Try to manually check the Graphics Card hardware

You might also want to check the physical status of your Graphics card and you can do this by disconnecting the Graphics card or any other external device connected to your computer. Once you’ve removed the external device, check it for any damages. If there’s none, connect it back to your computer and check if the VIDEO_SCHEDULER_INTERNAL_ERROR Blue Screen error is fixed or not.

Option 2 – Try removing hardware or drivers that you’ve installed recently

If you have recently installed some hardware or drivers, you might want to disable or remove them since external devices are proven to be one of the factors that trigger Blue Screen errors like VIDEO_SCHEDULER_INTERNAL_ERROR. All you have to do is physically disconnect any external devices that are connected to your computer and then check if it fixes the BSOD error or not.

Option 3 – Try to rollback, update, or disable the Graphics card drivers

Since the VIDEO_SCHEDULER_INTERNAL_ERROR Blue Screen error has something to do with Graphics card drivers, you can either roll back, update or disable them depending on your preference in order to resolve the error.

• First, boot your computer into Safe Mode.
• After that, tap the Win + R keys to launch Run.
• Type in devmgmt.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. From there, look for the Display Adapters and click on them.
• After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
• Now restart your computer.
• After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.

Note: You also have the option to go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it.

Option 4 – Uninstall any faulty drivers

You can also uninstall any faulty drivers via Device Manager. How? Refer to these steps:

• Tap the Win + R keys to launch the Run dialog box.
• Then type “devmgmt.msc” in the field and tap Enter to open the Device Manager.
• From there, look for any faulty drivers. You can identify them easily as they will be marked with a yellow exclamation point. And then check which entries would not affect the normal functioning of your PC.
• Now click on the entries of every faulty driver and click on the Uninstall option.
• Once you’ve uninstalled them, restart your computer to allow your computer to reinstall the faulty drivers you’ve just removed.

Option 5 – Run System File Checker at boot time

• 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.
• After opening Command Prompt, type the “sfc /scannow” command and hit Enter to run the System File Checker scan.
• Wait until the process is completed and type “exit” to close Command Prompt and then restart your computer to successfully apply the changes made.

Option 6 – Try to run the Blue Screen Troubleshooter

As you know, the Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like the VIDEO_SCHEDULER_INTERNAL_ERROR error. It can be found in 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.

0x800ccc92 - What is it?

The 0x800ccc92 is a Microsoft Outlook error. The error restricts your ability to send and receive emails on your Outlook email address successfully. This error is very similar to 0x800cc90 and 0x800ccc91 Outlook error codes. The 0x800ccc92 error message is often displayed as:

‘Receiving reported error (0x800ccc92): Your email server rejected your login.’

This error is quite common and is faced by many Microsoft Outlook users. It is advisable to fix this error immediately because besides restricting you from sending and receiving emails via Outlook, due to this error the data on your Outlook also becomes inaccessible and unreadable, and sometimes Outlook also begins to freeze unexpectedly.

Error Causes

Some of the most common causes of the error code 0x800ccc92 are:

• PST files get corrupt
• Incorrect Outlook configuration settings
• PST file crosses its fixed file size limit
• Failure of POP3 and Protocol STMP in database server connection
• Improper synchronization between Outlook and the server
• Usage of invalid password or username
• Virus Infection

Further Information and Manual Repair

Any of the above causes may result in the 0x800ccc92 error message display. If you encounter this Outlook error, you don’t need to panic and call the network personnel in your office to fix and repair the error. In fact, it is very easy to fix and you can repair it by yourself: Here are some of the best and easy ways to resolve this error in the shortest time:

• If the error message 0x0800ccc92 is displayed as POP3: Invalid Password, then in this case it is advisable to cross-check your Outlook account ID and password. Sometimes this error message may pop up if you insert an incorrect password or ID. Therefore the best way to resolve it to check where you went wrong and then re-enter your ID and Password correctly.

If the error is not related to POP3 (Post Office Protocol) then you can try some other alternative to resolve this issue.

• Another alternative is to install the latest available Server Service Pack for Exchange. This solution works best if compatibility is the issue.
• However, when nothing works, then it is advisable to download PST repair tool. The PST repair software is designed to scan, detect, repair, and resolve Outlook errors like 0x800ccc92.  The PST repair software is built with special algorithms that help repair PST corrupt files in seconds. This tool works on all Windows Operating Systems including Windows 8, Windows 7, Windows Vista, Windows XP, Windows 2003, and Windows 2008.

1. All you need to do is, download and install this software on your system.
2. Once you download it, run it on your PC to detect errors.
3. Press scan to get started
4. The scanning may take about a couple of minutes to complete.
5. Once it is complete, click on the repair tab to fix the errors.
6. Now restart your Outlook again and now try sending emails. This solution is likely to work if the above-mentioned solutions don’t.

Windows 10 has displayed one of the most efficient and user-friendly interfaces. However there have been many issues on the backend of this commonly praised operating system: For example, Windows Update is still a wonky and error-laded system application. One example of this error is Windows Update Error 0x80073712 which stands in the way of users just wanting to keep their PCs updated hassle-free. The error code 0x80073712 signifies that a file needed by Windows Update to function is either damaged, missing, or corrupted. However, this does not mean that your Windows version will forever stay as-is with no mode to update it. Windows Update Error 0x80073712 is perfectly fixable with the set of provided steps below and some of Windows’ built-in troubleshooting steps:

Solution 1: Open Windows Update Troubleshooter

1. Open the Windows Update Troubleshooter by pressing the Windows and S keys simultaneously.
2. Enter the word “Troubleshoot” in the search box and select the Troubleshoot result
3. On the new window, select “Windows Update” to troubleshoot.
4. Run the troubleshooter, then open Windows Update and try to install the update again.

Solution 2: Run the DISM tool

1. Open the command prompt by pressing Windows and S keys simultaneously
2. Enter “cmd” in the search box. Right Click command prompt among the results and select “Run as administrator”
3. In the Command Prompt window type the following and press the Enter key after every command

DISM.exe /Online /Cleanup-image /Scanhealth DISM.exe /Online /Cleanup-image /Restorehealth

4. To close the Administrator: Command prompt window, type Exit, and then press Enter.
5. Run Windows Update again.

Solution 3: Rename the Software Distribution folder

1. Open the command prompt as previously mentioned
2. Input the following command pressing Enter after every line net stop wuauserv net stop cryptSvc net stop bits net stop msiserver rename c:/windows/SoftwareDistribution/softwaredistribution.old net start wuauserv net start cryptSvc net start bits net start msiserver exit
3. Restart the PC and run the updater if it works again.

Solution 4: Restart Windows Update Services

1. Press the Windows logo key and R together to open Run -> Input services.msc -> and press Enter
2. Search for the Windows Update service -> Check its status
3. If it is not indicated, right-click on the service and select Start to force start your Windows Update
4. If you see an error, locate the Startup Type option and set it to Automatic
5. Now you should reboot your computer and see if your Windows Update is OK

Solution 5: Fix Registry Issues

If after all the aforementioned solutions, you still experience problems with Windows Update, the problem may lie in the registry that is either damaged or corrupted. You may choose to do manual editing of your Windows registry by opening your Windows registry editor. But doing so is risky as one wrong letter may do incalculable damage to your system. To do so safely for more inexperienced users we recommend using a third-party registry cleaner/tools, many of which can be found online.