Preventing installation of Removable Devices

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

Option 1 – Try installing the KB Update 4505903

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

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

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

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

Option 3 – Try enabling Telemetry via Settings

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

Option 4 – Try to enable Telemetry via Registry Editor

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

If you suddenly encounter an error message saying, “ File Record Segment is Unreadable ” on a blue screen while booting your PC, it means that your hard drive is in an error state. This particular blue screen of death error might have a lot of bad sectors or might have reached its end. The workarounds you can try to resolve the issue is by locating the bad sectors or checking your hard drive for any discrepancies in the mapping and fix them. Follow the detailed instructions laid out below for these workarounds.

Option 1 – Try to check for any bad sectors and wrong configurations in your hard drive

The first thing you have to check is the boot files on your PC. As you know, your PC boots from these files and if there is anything wrong with any one of them or if one of them ends up getting corrupted, you will most likely see the blue screen of death error or a prompt with an error message saying, “File record segment is unreadable”. According to some users who reported this issue, new hard drives aren’t exempted from this error. That’s why it is recommended that you carry out this solution no matter what kind of scenario you are in. You will have to launch the Command Prompt in recovery mode and see if you can fix the problem by executing the check disk commands.

• Upon booting, restart your PC and tap F11 to go to the recovery environment then select Troubleshoot.
• Next, click Advanced from the given options and select Command Prompt.
• After opening Command Prompt, execute the commands listed below, and don’t forget to hit Enter right after you type in each one of them and if you have installed Windows to some different directory, you must replace “C” with the name of the drive you’ve installed Windows with.
• chkdsk C: /r /x
• chkdsk C: /f

Note: The Chkdsk function might take a while before it finishes its operations so you need to be patient and wait until the entire process is completed. And depending on the situation, it might even take a day at most so patience is really the key here.

Option 2 – Try connecting the hard drive to a different computer

If option 1 didn’t work for you and you’re still seeing the error, you can try connecting the hard drive to a different computer and then copy the data first. Make it a priority to salvage the data just in case the hard drive won’t make it in the future. After replicating your hard drive, you can then try running the chkdsk commands that are listed in option 1 above in the new computer you’re connecting your hard drive to and make sure that you key in the correct drive letter that’s assigned to the hard drive you’re using. After executing the chkdsk commands, plug your hard drive back into the previous computer and then check if you can now boot it without any issues.

Option 4 – Replace the faulty hard drive

If none of the options provided above really worked out then maybe it’s time to consider getting a replacement for your hard drive. In about 50% of the cases about this error, some unfortunate users were left with no choice but to replace the hard drive since the problem is with the hard drive itself. Hard drives have a complex running mechanism which includes a head and the disk that rotates accordingly so you can check if the cables connected to the hard drive are connected properly and if it is in a correct position or not. In addition, you also have to make sure that the SATA adapters where the hard drive is connected are working properly. If the drive is showing problems in the I/O operation, there is little chance for you to use it as a normal hard drive. If the hard drive is in warranty, get it checked and replace it. If not, you might consider taking it to the service center for the specialists to take a look into it.

What is 0x0000007B Error?

0x0000007B is the most common Windows stop error. The error is displayed on the blue-colored screen which is also called the blue screen of death. You may receive a 0x0000007B error message during Windows XP setup or while running the setup program. The message is often displayed as ‘a problem has been detected and Windows has been shut down to prevent damages’ or ‘inaccessible boot device error’.

Solution

Error Causes

The 0x0000007B error code is usually triggered by:

• Poor Window XP installation
• Registry corruption
• Device Drivers Issues
• Boot sector viruses

Further Information and Manual Repair

The 0x0000007B error makes your system vulnerable and reduces its speed significantly. And besides, you can’t run the programs smoothly on your PC either. Therefore, it’s advisable to fix the error right away. To fix and repair the 0x0000007B error successfully, you must first understand the cause of the error. Let’s take a look at all the solutions available to fix the 0x0000007B error.

Cause: Boot Sector Viruses

Solution: If your computer is infected with boot sector viruses, then you will first have to download a powerful antivirus. After downloading the antivirus program, run it on your PC to check your computer for viruses. Delete the viruses found and click the repair option. Sometimes even an antivirus program may fail to remove the virus and repair the system. In such cases, you must repartition and format your hard disk and also reinstall Windows XP.

Cause: Device Driver Issues

Solution: Device driver issues may occur if the boot controller is not properly configured or the driver is not up to date. If device driver configuration is the cause of the 0x0000007B error on your PC, then all you need to do is restart your PC, and while restarting press F8 to go to the advanced boot options. Now choose the ‘Last Known Good Configuration’ option. After selecting it, boot into windows and then perform a system restore. Now go to Device Manager and perform a driver rollback to reinstall the drivers. This will resolve the configuration issues. However, if you need an updated driver, all you need to do go on the web and download software to update the driver. It is advisable to download software from the manufacturer’s website in order to successfully update the device driver.

Cause: Poor Windows Installation

Solution: In this case, you will have to perform a Windows start-up repair. To do this: boot Windows XP from CD. Press ‘enter’ at setup Windows Screen when prompted. Then press R to repair Windows Installation. This procedure will not delete any user data and files. In fact, it will copy only the original Windows files over the bad or existing ones. Some of the best ways to avoid Ox0000007B blue screen errors are

• To scan for viruses every time you use your PC
• Never open web pages, emails, or download content that you think looks suspicious because that’s probably a virus.
• Always keep your computer updated.

When you receive Error 0x800704C8 when trying to move a file inside Windows 10 operation is stopped and it can not continue leaving you with the file in its original location without a copy. Several issues can be the cause of this type of behavior and error and after some digging and analyzing we are bringing you various solutions for this error and how to fix it.

Ownership issues

It turns out that not having ownership of fie can cause this error and prevent you from copying it. For some reason, Windows can assume that file is owned or used by another application or process and thus prevents you from making a copy since you do not have ownership of it. Resolving this particular issue will require you to install a third-party application that is tailored for this kind of task. After some talk and research, we found out that there is a freeware application that can solve this issue quite fastly. Unlocker is the name and the download link is here. Once downloaded, install it and run it. Once inside the application browse to the location where you need to change the ownership, click on it to select it, and click OK. Use the No Action drop drown menu to select Move, then click OK

Antivirus Issue

As with other file and application issues, this error could also be a product of antivirus marking it inaccessible to Windows and thus preventing copy or move operation on it. note: Do not turn off Windows defender since it was proven that it is not the cause of this kind of error, so if you are using only Windows defender you can skip this solution. How temporary turning off each security suite is different and it depends on the application itself we can not cover in detail the procedure here. Go to your security suite manufacturer's website and get information there or if you want, go directly to applications and features inside Windows and uninstall the software.

Visual Studio issue

• If the file you are trying to move is part of a Visual Studio project then the issue can be linked directly to Visual Studio itself, luckily the solution is quite easy. All you have to do it to exit Visual Studio and then run it with administrator privileges.
• In order to run Visual Studio with elevated privileges locate its executable file and right-click on it.
• Choose properties and go to the compatibility tab
• Inside compatibility tab check box that says run this program as an administrator

Corrupted system files

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

1. Run SFC scan

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

2. Run DISM scan

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

There is a lot of software on the market today, but from time to time we discover something extraordinary and unique worth sharing and today we have a threat for you. Ventoy is a tool that will help you with system reinstallations and system maintenance once and for all.

If you are a computer user that has multiple operating systems or you are installing and maintaining different hardware via different OS there is a high chance that you have multiple USB sticks with different operating systems on them.

Now the problem with that is that there are probably too many unlabeled sticks around or you do not have enough so you keep making system USBs depending on which one you might need.

Ventoy solves all of these problems by letting you have as many operating systems images as your USB has capacity. The only thing you need to do is get the software here: https://www.ventoy.net/en/index.html and make a USB with it, then you can freely just copy your ISO images onto the USB and once it is inserted into the computer you will be given a menu to choose which one you would like to start with, simple as that.

Features

• 100% open source (license)
• Very simple to use (Get started)
• Fast (limited only by the speed of copying the iso file)
• Can be installed in USB/Local Disk/SSD/NVMe/SD Card
• Directly boot from ISO/WIM/IMG/VHD(x)/EFI files, no extraction needed
• Support to browse and boot ISO/WIM/IMG/VHD(x)/EFI files in local disk Notes
• No need to be continuous in disk for ISO/WIM/IMG/VHD(x)/EFI files
• Both MBR and GPT partition styles are supported
• x86 Legacy BIOS, IA32 UEFI, x86_64 UEFI, ARM64 UEFI, MIPS64EL UEFI supported
• IA32/x86_64 UEFI Secure Boot supported Notes
• Linux Persistence supported Notes
• Windows auto installation supported Notes
• Linux auto installation supported Notes
• Variables Expansion supported for Windows/Linux auto-installation script Notes
• FAT32/exFAT/NTFS/UDF/XFS/Ext2(3)(4) supported for main partition
• ISO files larger than 4GB supported

• Menu alias, Menu tip message supported
• Password protect supported
• Native boot menu style for Legacy & UEFI
• Most types of OS supported, 1000+ iso files tested
• Linux vDisk(vhd/vdi/raw...) boot solution Notes
• Not only boot but also complete the installation process
• Menu dynamically switchable between ListView and TreeView mode Notes
• "Ventoy Compatible" concept
• Plugin Framework and GUI plugin configurator
• Injection of files into runtime environment
• Boot configuration file dynamically replacement
• Highly customizable theme and menu style
• USB drive write-protected support
• USB normal use unaffected
• Data nondestructive during a version upgrade
• No need to update Ventoy when a new distro is released

If you suddenly encounter a PNP_DETECTED_FATAL_ERROR Blue Screen error, then this post can help you out. The PNP_DETECTED_FATAL_ERROR BSOD usually occurs when any new hardware that is mostly the Plug and Play type is attached. In such cases, when the device is plugged, and the driver for that device crashes or isn’t found or is not compatible, you will most likely encounter this particular BSOD error. There are several error codes that come under this category, some of them are 0x000000CA (0x01681690, 0xEA96A7BE, 0x938A81AD, 0xF8362881. This BSOD error can also occur at any time. However, the only constant thing here is when you plug a PNP device like earphones, microphones, USB drives, and many more. The PNP_DETECTED_FATAL_ERROR bug check has a value of 0x000000CA which indicates that the Plug and Play Manager encountered some severe error which is most likely have something to do with a problematic Plug and Play driver. To fix this error, here are some possible solutions that could help.

Option 1 – Run the Blue Screen Troubleshooter

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

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

Option 2 – Try disabling or removing newly installed hardware

In this option, you will have to disable or remove the hardware you’ve just installed recently since external devices could be the one that’s causing the Blue Screen of Death error to appear. To do that, just disconnect any external device that’s connected to your computer physically and then check if it fixes the PNP_DETECTED_FATAL_ERROR Blue Screen error.

Option 3 – Try disabling BIOS Memory options namely Caching Shadowing

Disabling the BIOS Memory options such as Caching and Shadowing can help you in fixing the PNP_DETECTED_FATAL_ERROR Blue Screen 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 4 – Try to run the CHKDSK utility

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

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

chkdsk /f /r

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

Option 5 – Try to uninstall programs you’ve installed recently

Chances are, some programs that you just installed might be the one that’s causing the BSOD error. Thus, you need to uninstall the program to resolve the problem.

• In the search box, type in “control” and then click on Control Panel (desktop app) among the search results.
• After that, select Programs and Features from the list which will give you a list of all the programs installed on your computer.
• From there, look for the concerned program and select it and then uninstall it.

Option 6 – Update the Device drivers

• 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. 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.
• Connect the device and Scan for hardware changes – you can see this option under Device Manager > Action.

Option 7 – Perform a System Restore

Performing System Restore might help you in fixing the PNP_DETECTED_FATAL_ERROR 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.

Instaling and removing applications from your Windows can sometimes leave some traces that are unpleasant and can cause annoyances. One of these annoyances is the program in the startup section of the task manager.

If you ever opened task manager and went into the startup section trying to disable some of the startup items on your Windows boot there might be a chance that you have experienced and seen a program without any icon or information about it just sitting there.

This is due to some applications being removed from the system but for some reason, it still shows itself in startup and it is quite annoying. So here we will show you how to get rid of this annoyance so your startup is clean again without junk in it.

Removing a program from startup

Locating the source of the issue

The first thing of course is to open the task manager itself and navigate to the startup tab. Inside the startup tab right-click on the column header and tick or enable Startup type and command line. Now you will see the location of the supposed file (that is missing or you could just go there by right-clicking on the item, but here it is greyed).

99% of the time startup type will be registry since the file is missing, if it was a file fix would be just to simply delete the file in the folder but since it was installed and not properly removed registry key is still present but the file cannot be found. After confirmation that the file is indeed missing and that the startup type is registry open the registry editor by typing Regedit in search and pressing enter.

Removing the key from registry

Inside Registry editor navigate to: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run. Inside on right part, you will see all auto-start entries added by installed applications.

Locate one that is causing issues by comparing its path with the path inside the task manager command line and delete the key. Once the key is deleted right-click on RUN on the left part and choose HKEY_LOCAL_MACHINE to quickly jump on that key location and repeat the process of key deletion if needed. HKEY_LOCAL_MACHINE will delete startup entry for all users and sometimes entry will not be present here since the application is not installed for all users or there are no other users on the machine.

After the procedure is finished, reboot your systems in order to apply changes.

Recently, a few users reported that they were unable to turn on their computers for some reason and at the same time their computers Computer makes a beeping noise couple of times or continuously whenever they try to turn them on. The sounds the computers are making can be quite annoying and it also signifies that there is something wrong with them. The problem might have something to do with the hardware inside of the computer system rather than Windows 10 itself. As you know, a computer is designed to deliver audible error sounds every time some part of the hardware is not properly working. For instance, if you hear a single beep, this indicates that your GPU is having some issues and if you’re hearing two beeps, it indicates that your RAM is not working properly, whereas three beeps that repeat after a pause when you turn on your computer means that there is something wrong with the system memory. On the other hand, if your computer is beeping continuously, this means that the problem lies with the processor. To fix this issue, here are some suggestions that might help but before you proceed, make sure that you know how to manage your computer’s hardware, if not, better have some expert do it for you.

Option 1 – Try checking the RAM

One of the basic things you can do in this kind of case is to check the RAM. Prepare some screwdrivers and dig into your PC and then look for the RAM slots and ensure that they are attached firmly. There are times when moving around your computer daily can cause certain components in your computer to become loose. Worst case scenario is that the RAM might be broken so really have to replace it.

Option 2 – Try checking the graphics card

After digging into your computer, check the graphics card and give it some good cleaning. As you know, you have to remove certain components like the graphics card regularly and clean them to help increase their lifespan and avoid errors in a startup. And if it turns out that the graphics card is broken, you have to replace it with a new one to fix the problem.

Option 3 – Try checking the processor

The processor is the brain of every computer so if it ends up not working, everything else is useless. Thus, you need to check it to see if it’s firmly attached and see if it needs some cleaning of dust and other debris. After that, try turning on your computer again. If it doesn’t work, then you might have to take your system to a technician to resolve the problem for you.

If you are having issues with your network connection and you have it configured to DHCP, then you shouldn’t have any issues in figuring your IP address out. If you want to prevent conflicts between network devices and enable their easy management, then you have to set a static IP address in your Windows 10 computer, worry not for this post will show you how it’s done. The IP addresses for computers are usually configured to the Dynamic Host Configuration Protocol or DHCP automatically by the respective router. This is really convenient since the devices instantly connect to your network and through this, you can save yourself the trouble of configuring the IP address for each new device manually. However, there’s a shortfall in the process – the computer’s IP address can change every now and then. Moreover, you might also find it a lot easier to share a printer or configure a Port forwarding when you set a static IP address. There are three ways to do it – you can set it via Control Panel or Windows Settings or using Windows PowerShell. For more details, follow the options provided below.

Option 1 – Set a static IP address via Control Panel

• Right-click on the network or Wi-Fi icon located in the Taskbar.
• Then select the “Open Network and Internet settings” option from the given list of options.
• Next, go to Wi-Fi settings and scroll down until you see the “Related Settings” section. Here, click on the “Change adapter options” link which will open a new window that will direct you to the Network Connections section of the Control Panel.
• After that, right-click on the network connection you want to set a static IP address for and then select the Properties option.
• Then select Internet Protocol Version 4 (TCP/IPv4) under the Networking tab and click the Properties button.
• Now switch the selector to the “Use the following IP address” option and make the entry for the following fields that correspond to your network setup.
  • IP address (Find it using the “ipconfig /all” command)
  • Subnet Mask (On a home network, it is 255.255.255.0)
  • Default Gateway (It is your router’s IP address.)

• Then check the “Validate settings upon exit” option to help Windows check your new IP address quickly as well as the other relevant information to make sure that it’s working.
• Once you’re done, click the OK button and close the network adapter’s properties window.

Option 2 – Assign Static IP address using Settings

• First, click on the gear icon for Settings and select the Network & Internet tab.
• Next, select Wi-Fi > Current connection where you’ll have to select the network connection your computer is connected to.
• After that, scroll down until you reach the IP settings section and then click the Edit button.
• Now click the drop-down arrow when the IP settings window pops up and select the Manual option.
• Now turn on the IPv4 toggle switch and set the static IP address. You also have to set the Subnet prefix length (subnet mask). For instance, if your subnet mask is “255.255.255.0”, then the subnet prefix length in bits should be 24.
• Afterward, configure the Default Gateway address and the Preferred DNS address and then save the changes you’ve made.

Option 3 – Assign the static IP address using Windows PowerShell

• In the Start Search, type “PowerShell” and right-click on Windows PowerShell from the search results to open PowerShell with admin privileges.
• After that, enter this command to view your computer’s current network configuration: Get-NetIPConfiguration
• Next, take note of the following information:
  • InterfaceIndex
  • IPv4Address
  • IPv4DefaultGateway
  • DNSServer

• Once you’re done, execute this command to set a static IP address: New-NetIPAddress -InterfaceIndex 15 -IPAddress 192.168.29.34 -PrefixLength 24 -DefaultGateway 192.168.29.1
• Afterward, change the default gateway with the default gateway address of your network and make sure that you change the InterfaceIndex number with the one that corresponds to your adapter and IPAddress with the IP address you want to assign to your computer.
• Now execute this command to assign a DNS server address: Set-DnsClientServerAddress -InterfaceIndex 4 -ServerAddresses 10.1.2.1
• Finally, save the changes you’ve made and restart your computer.

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 Window Key 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 Key and “S” key 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:windowsSoftwareDistribution 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.