Fix Error Accessing the Registry in Windows

In the last article, we have covered various advantages of Apple hardware over Windows PC, however, PC has their own strengths and advantages over MACs as well. Join us as we explore why would you choose Windows PC over MAC.

Hardware customization

If you like to customize and build your own hardware and customize your existing computer then MACs are out of the picture, on other hand, computers based on Windows operating system are much more flexible in terms of customization.

While Apple hardware is locked and only allows small changes to it, computers running on Windows are free and open to various upgrades and modifications so if you like to play with hardware Windows is your platform.

Gaming

There are games on MAC true but their numbers can not compare to games available for the Windows platform. On top of that, most latest and best gaming hardware is not even available on Apple platforms so if you plan to game in high resolutions and play the latest games there really is no option other than Windows.

Windows Platforms also has multiple emulators that you can use to play games from other older platforms and Microsoft since it owns Xbox has some great plans for both PC and Xbox gaming.

Software back compatibility

Since the introduction of the new MAC OS X, apple really lost a lot of application back compatibility, and a lot of old legacy software can not be run on modern Apple computers. Windows on the other hand have always tried and succeeded in keeping maximum compatibility with older and legacy software.

Also on the Windows platform, there is a lot of community support for old and legacy software so even if it is not officially supported it is backed up by the community.

Software variability

In terms of where can you find the most different software, you need to look no further than the Windows platform. How Windows itself has great backward compatibility and a lot of developers are using it to create new software thanks to Visual Studio and .NET Windows has cemented itself as a platform with the most available software.

The popularity of Windows as the home operating system and as a gaming platform has made it quite interesting in eyes of various developers and tons of small applications are made daily for it. Windows 11 has also brought native android support to it and that has just expanded its already impressive catalog of applications.

Freedom of choice

Overall Windows PC is most appealing for users that like to be able to choose everything, from hardware components to software they would like to use. No other platform will give you larger freedom of choice and better personalization options.

In case you don’t know, there is a built-in tool in Windows 10, known as Reliability Monitor that provides a day-to-day snapshot of the health of your system. It warns users of any looming issues or disasters before your computer breaks down finally. So obviously, Reliability Monitor is useful, however, there are times when it could behave incorrectly. For instance, it might fail to show you any updates even when they are installed. Thus, if you experience any malfunctions with the Reliability Monitor tool in Windows 10, read on as this post will guide you in updating or working in Windows 10. To fix the problem with the Reliability Monitor, there are several fixes you can check out. You can try to enable the data collection for Reliability Monitor or reset it, as well as put your computer in a Clean Boot State. For more information, refer to each one of the options given below.

Option 1 – Try to enable the Data Collection for Reliability Monitor

The Reliability Monitor tool uses data provided by the RAC Agent scheduled task and it will start to display a Stability Index rating and specific event information 24 hours after the system installation. The RACAgent scheduled task, by default, runs after the operating system is installed. And if it is disabled, it must be manually enabled from the Task Scheduler snap-in for MMC or Microsoft Management Console. Thus, you need to enable the Data Collection for Reliability Monitor to fix the problem.

Option 2 – Try to reset the Reliability Monitor

The next thing you can do to fix the issue with the Reliability Monitor might want to reset it to resolve the problem. If the Reliability Monitor is already open, you have to close it and open it again. After the reset is done, it may take up to 24 hours for the Reliability Monitor to display results again. This should fix the problem.

Option 3 – Troubleshot the problem in a Clean Boot State

There are some instances that some conflicting programs installed in your computer might be the one that’s causing the Black border issue. 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.)
• From there, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

Microsoft Visual C++ Runtime Library Error

Fix Microsoft Visual C++ Runtime Library Error, Microsoft Windows operating system supports a form of shared libraries that are known as DLL (Dynamic-link libraries). These are also known as code libraries that are used by multiple processes while one copy is loaded into memory. Runtimes are also code libraries that are loaded by applications when the application is called to run on the system. The most common runtime libraries that are used today are Visual C++ Runtime Library and Java Runtime Environment. These libraries are practically used for nearly every single application you run on your system. Therefore it is very important that these libraries are in good working order. Microsoft Visual C++ Runtime Library Error occurs when this runtime library becomes corrupted. When Microsoft Visual C++ Runtime Library Error occurs, the applications powered by this runtime library fail to run smoothly, resulting in locking you out of those applications and hampering your ability to work on them. Generally speaking, this error indicates system instability and poor PC maintenance. If this error is not fixed timely it can expose your system to serious PC damages like system freeze, crashes, and data loss.

Solution

Error Causes

Microsoft Visual C++ Runtime Library Error is triggered for numerous reasons. These include:

• Poor program installation
• Disk fragmentation
• Missing and damaged .dll files
• Registry corruption
• Malware invasion

In a nutshell, it can be said that the deep-rooted cause of the Microsoft Visual C++ Runtime Library Error is the registry. All the causes listed above are associated with the registry. For simplification, the registry is the main database of your system that stores all the activities executed on the computer in the RAM, the hard disk. This includes both the important data and junk files such as temporary files, internet history, bad registry keys, invalid registry entries, and also the files from the uninstalled programs. If these files are not removed from the registry frequently, it overloads the hard disk and leads to obscure error message displays on your system like the Microsoft Visual C++ Runtime Library Error as warning signs. Sometimes, rebooting the system may fix the Microsoft Visual C++ Runtime Library Error. However, this is temporary. Error message pops again after some time. So, instead of seeking out a temporary solution, it is advisable to look for a solution that can repair this error for the longest time.

Further Information and Manual Repair

There are two ways to fix the Microsoft Visual C++ Runtime Library Error code. One is to reinstall the Visual C++ runtime libraries. This can be a complex task if you are not a computer programmer or technically sound. However, the second way, or let’s just say the best and easiest way to resolve this problem is to download Restoro. This is truly an easy way as it requires no technical expertise or programming knowledge to repair the Microsoft Visual C++ Runtime Library Error. Restoro is an advanced, user-friendly, and multi-functional repair tool integrated with profound powerful utilities like an intuitive registry cleaner, system stability scanner, and anti-virus. It has a smooth interface, easy navigation, and a simple layout making it easy for users and even novices to operate it to resolve the Microsoft Visual C++ Error in seconds. The registry cleaner scans your entire PC for registry issues. It wipes out all the invalid, unnecessary, and obsolete files clearing up your disk space. In addition to this, it repairs fragmented disks, damaged .dll files (runtime code library), and repairs the registry. Along with these benefits, Restoro also functions as a system optimizer thus boosting the performance of your system. It can be downloaded by all PC Windows users as it is compatible with all Windows versions. Click here to download Restoro on your PC to resolve the Microsoft Visual C++ Runtime Library Error code and to ensure optimum PC performance and health.

External hard drives have become essential these days as they tend to be very useful to many users. They are usually used for storing system images like system backups, Windows installation media, or for personal use. However, if you are not able to utilize your external drivers for some reason then that could be a huge problem. One of the common issues with hard drives is when your USB device or external hard drive just keeps connecting and disconnecting. This kind of issue could be caused by a faulty USB port, some issues with the USB drivers, your computer’s Power Options, corrupted or damaged system files, and many other factors. The connecting and disconnecting issue with USB devices and external hard drives isn’t really new and has been experienced by many users for years now. Although this issue has somewhat decreased in Windows 10, there are still some users who encounter it every now and then. Worry not though for there are fixes that you can try to resolve the problem. Refer to the following straightforward solutions to resolve the issue with your USB device or external hard drive.

Option 1 – Plug your external device on a different port

If your USB device keeps on connecting and disconnecting then the first thing you can do is to try connecting it to a different port. This will help you isolate the problem. In some cases, the port where the USB is connected can be malfunctioning or obsolete so you need to check that possibility by plugging your USB device into a different USB port.

Option 2 – Update or reinstall your USB drivers

As mentioned earlier, the problem could be due to some issues with the USB drivers. It could be that it has to be updated or you need to reinstall it. To do that, follow these steps:

• First, click the Start button and type “device manager”.
• Then click on the “Device Manager” from the search results to open it.
• From there, look for the “Universal Serial Bus controllers” option and then right-click on each one of the USB drivers and select the Update Driver from the menu.
• Restart your PC and then click the “Search automatically for updated driver software” option.

You also have the option to update the motherboard and the USB driver from the manufacturer’s official website.

Option 3 – Try turning on the USB External drive

There are times when your system turns off some drives in order to conserve your computer’s power, etc. as a result, the driver that’s required to run your external hard drive properly ends up getting disabled. To fix this, you can prevent your system from turning off your external USB drive by following these steps:

• You need to make sure that the external drive is connected to your system first.
• Next, go to the Start Menu and type “device manager” in the field, and click on the appropriate result to open the Device Manager.
• After opening the Device Manager, expand the category of the Universal Serial Bus controllers.
• Then double click on your USB Mass Storage device and take note that the name might be different on your system.
• Now go to the Power Management tab and uncheck the checkbox for the “Allow the computer to turn off this device to save power” option and click OK to save the changes made.

Option 4 – Turn off USB Selective Suspend

Another thing you can try is to turn off USB Selective Suspend especially when the issue has something to do with the Power Options. There are certain systems that are configured to disable USB devices after some time which could be the root cause of the problem. Thus, you need to turn off USB Selective Suspend. Here’s how you can do it:

• In the Start Menu, search for “control panel” and open the related search result.
• Then go to Power Options and click on the “Change plan settings” option.
• Next, select “Change advanced power settings” and look for the USB settings and then expand it.
• From there, you will see the USB Selective Suspend setting. Disable it and click OK.
• Now restart your computer and check if it resolves the problem or not.

Option 5 – Format your drive

• To get started formatting your drive, tap the Win + E keys and then go to the access page of the drive.
• Next, right-click on the drive and select Format.
• After that, uncheck the “Quick Format” option and then format your drive properly.
• Now once the formatting process is finished, unplug the drive and plug it back in afterward.
• Check if the error is already fixed. If the drive is not initialized, tap the Win + R keys and hit Enter.
• After opening the Run dialog box, type “diskmgmt.msc” and hit Enter to open Disk Management.
• From there, right-click on the drive volume and select initialize disk.
• Next, select the correct partition type and proceed.

Default Taskbar inside Windows 11 is pretty good if we are talking about its height. Sitting at 48 pixels it is a pretty decent size considering functionality and size ratio but if you want to make it a little larger or smaller know that you can do that as well in order to customize it for your personal needs. Sadly in order to actually change height size, you will have to do it inside the registry editor, but worry not, we are here with you to guide you all the way, one step at a time. Also, note that you can only change Taskbar from normal size of 48px to either small of 32px or large gapping at 72px. Icons will also be scaled proportionally with the taskbar.

Guide

1. Press ⊞ WINDOWS + R to open the run dialog
2. Inside run dialog type in RegEdit and press ENTER
3. In registry editor locate and find HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced
4. Right Click on it to select it and create a new DWORD (32-bit) value
5. Name the value TaskbarSi
6. Inside TaskbarSi double click in order to set the value to 0 if you want a small size Taskbar, 1 is if you want to revert back to medium (standard one), or type in 2 if you want a large Taskbar.
7. Save and close the Registry editor
8. Reboot PC

And there you go, you have successfully changed Taskbar size inside Windows 11. If you want to revert back to standard size just repeat steps and place 1 as a value in point 6.

We couldn’t update system reserved partition” - What is it?

Customers will most likely encounter the “We couldn’t update system reserved partition” error when upgrading to Windows 10 from Windows 7 or Windows 8.1. This error may also come with error code 0xc1900104 or error code 0x800f0922.

Solution

Error Cause

“We couldn’t update system reserved partition” Windows 10 upgrade error is normally caused by too little space on the System Reserved Partition (SRP). The System Reserve Partition is an additional small partition created by Windows, which stores boot files. The SRP can be filled up with security apps and third-party anti-virus. Once this partition has insufficient space, the system will not be able to upgrade to Windows 10.

Further Information and Manual Repair

Caution: The following steps are complex and need to be done by experienced users especially using the command line. Once an error is made in entering commands, there’s a chance that your device can be put in a no-boot situation, or data stored on the device can possibly get lost.

To upgrade to Windows 10, your device needs to have at least 15MB free space on the System Reserved Partition. Follow the procedure below and then try upgrading again.

First, know if the System Reserved Partition is whether in GPT or MBR partition style:

1. Open the Run window by pressing the Windows key + R. Type msc in the window then press Enter.
2. Right-click on the Disk where SRP is located then select
3. Click over the Volumes
4. On the Partition Style line, you’ll see which partition style your device is using, either Master Boot Record (MBR) or GUID Partition Table (GPT)

Second, determine which method you will need:

Depending on what partition style your device has and whether you’re currently on Windows 7 or Windows 8/8.1, there are various methods you need to do.

Method 1: Windows 7 or 8/8.1 with GPT partition

1. Click on the Start button and search for cmd. In the results, right-click on Command Prompt then choose Run as administrator. The command prompt window will appear.
2. Type mountvol y: /s at the command prompt then press Enter. This command will add the Y: drive letter where you can access the System Partition.
3. Type taskkill /im explorer.exe /f then hit Enter. Afterward, restart explorer in Admin mode by typing exe and hitting Enter.

NOTE: While in Admin mode, some apps like OneNote will not run.

4. Open File Explorer then type Y:EFIMicrosoftBoot in the address bar. Hit Enter.
5. Choose the language folders you want to permanently delete. Language folders are named with four letters split with a hyphen. For instance, you want to delete the German language: choose de-DE.
6. Optional: You can also delete unused font files for more space. Type Y:EFIMicrosoftBootFonts in the address bar then press enter.
7. Once you permanently deleted the unnecessary files, reboot the device to return to explorer.exe to normal mode and remove the Y: drive letter.

Method 2: Windows 7 with MBR partition

Doing this method will make a permanent, but small increase in the free space of the device’s SRP.

1. Delete language folders

a. Open the Run window by pressing the Windows key + R. Type diskmgmt.msc then hit Enter. b. Select System Reserve partition then right-click on it.

c. Choose Change Drive Letter and Paths then select Add.

d. Type Y for the drive letter then click OK.

e. Click on the Start button and search for cmd. In the results, right-click on Command Prompt then choose Run as administrator. The command prompt window will appear.

f. Type Y: at the command prompt then press Enter.

g. Once you’ve switched to drive Y, type takeown /d y /r /f . then hit Enter.

NOTE: Ensure that the space and period after “f” is included in order for the command to work properly      

h. Type icacls Y:* /save %systemdrive%NTFSp.txt /c /t then hit Enter to back up the permission to the drive.

NOTE: Ensure that all files are marked as successful and that no files are marked as failed.

i. Type whoami then hit Enter. Record the username that appears. Afterwards, type icacls . /grant <username you got from whoami>:F /t then press Enter.

NOTE: Ensure that there’s no space between the username and “:F” or the command will not work.

j. In the File Explorer, open the SRP drive and select the Boot folder. Choose the             language folders you want to permanently delete. Language folders are named      with four letters split with a hyphen. For example: de-DE is the German language          while en-US is the U.S. English language.

2. Truncate the NTFS Log:

a. Open the Command Prompt then type chkdsk /L Y: to check the size of the NTFS Log. If the NTFS Log size is less than 5000KB, you need not truncate the file.

b. Type chkdsk /L:5000 /X /F then hit Enter to truncate the NTFS Log.

c. Return to Disk Management window. Select Action menu then select Check if the device’s SRP now has a larger amount of free space. Once there’s enough space, right click the System Reserve Partition then select Change Drive Letter and Paths. Choose Y: then select Remove.

3. If there’s still not enough available space after truncating the NTFS Log, resize the USN journal:

a. Open the command prompt then type fsutil usn queryjournal Y: to display the size in hex value. Convert the hex value to decimal then divide it by 1048576. The result you will get will be in MB. If the journal size is 30MB or more, proceed with truncating the file.

NOTE: To convert the Hex value to Decimal, open the Calculator app in Windows then choose View menu. Select Programmer then choose Hex. Type the Hex value then choose Dec.

b. Type fsutil usn deletejournal /D /N Y: then hit Enter to delete the journal. Type fsutil usn createjournal m=1500 a=1 Y: to recreate the journal having the new log size value.

4. Restore permissions

a. Type icacls Y: /restore %systemdrive%NTFSp.txt /c /t in the Command Prompt. Check if the files were successfully processed before proceeding. If you see a message saying some files failed while processing, this is normal since some of the files have already been deleted before performing a backup. However, if there are no successful files indicated, the command was not properly executed.

b. Type icacls . /grant system:f /t then hit Enter to adjust the ACL back to System. Now, you can set the owner of the drive by typing icacls Y: /setowner “SYSTEM” /t /c then press Enter.

c. Check if the device’s SRP now has enough free space by going back to Disk Management and refreshing the data. If the SRP already has sufficient space, you can now remove the drive letter. Right-click on the System Reserved Partition then choose Change Drive Letter and Paths. Select the Y: drive then choose Confirm deleting the drive letter by clicking OK.

Method 3: Windows 8/8.1 with MBR partition

This method makes a larger, but temporary, increase in the SRP free space.

1. Be sure you have an external drive having at least 250 MB free space and formatted as NFTS.

2. Open Run by pressing the Windows key + R. Type mscthen to choose the Recovery Partition. Right-click on it then choose Change Drive Letter and Paths.

3. Select Add then type Y for the drive letter, click

4. Click on the Start screen then type cmd in the search bar. In the results, right-click on Command Prompt then choose Run as administrator. The command prompt window will appear.

5. Switch to another drive by typing Y: in the command prompt. Once you’re in the drive Y, type takeown /d y /r /f .

NOTE: Ensure that space and period after “f” are included in order for the command to work properly.

6. Type whoami then hit Enter. Record the username that appears. Afterward, type icacls . /grant <username you got from whoami>:F /t then press Enter.

NOTE: Ensure that there’s no space between the username and “:F” or else the command will not work.

7. Once the command is completed, type attrib -s -r –h Y:RecoveryWindowsREwinre.wim then hit Enter.
8. Open File Explorer and check the drive letter of the external drive you’re using (In this case, let’s assume F: is the drive letter of the external drive so when you see F: for the rest of the steps, this means the drive letter of the external drive you’re using).
9. Type mkdir F:RecoveryWindowsRE in the Command Prompt then hit Enter. Afterward, type xcopy Y:RecoveryWindowsREwinre.wim F:RecoveryWindowsREwinre.wim /h
10. Type C:WindowsSystem32Reagentc /SetREImage /Path F:RecoveryWindowsRE /Target C:Windows to map the new path
11. Verify if the copy was successfully done then type del Y:RecoveryWindowsREwinre.wim /F
12. Return to Disk Management window. Click on the Action menu then hit Check if the device’s SRP now has a larger amount of available space. Once there’s enough space, you can proceed with the upgrade.
13. Upon completion of the upgrade, move back the wim file to the Recovery Partition. At this point, you can re-map now the location by:
    1. Open the Command Prompt then type xcopy F:RecoveryWindowsREwinre.wim Y:RecoveryWindowsREwinre.wim /h and press Enter.
    2. Type C:WindowsSystem32Reagentc /SetREImage /Path Y:RecoveryWindowsRE /Target C:Windows to re-map to the original path.
14. Return to the Disk Management window. Right-click on the Recovery Partition then choose Change Drive Letter and Paths. Select the Y: drive then choose Remove.

Method: Download a Powerful Automated Tool

Not inclined to go through a long and technical process (as highlighted above)? Download and install a powerful automated tool and get the job done in a jiffy.

You might have experienced a situation where your Windows computer was interrupted due to some battery issues or power failure. It could be that the upgrade process was interrupted because you’ve signed out of your computer or you restarted it by accident. In this case, you will most likely get a Windows Update or Upgrade error 0x80200056. If you are getting this error, read on as this post will guide you in fixing it. This kind of error pops up when the upgrade process was interrupted and could be caused by anything but the baseline here is that your computer was restarted accidentally or someone could have signed out your PC. To resolve the problem, here are some fixes you ought to try:

Option 1 – Try updating or upgrading your computer again

This is the basic thing to do since the process was suddenly interrupted. Just log in to your account and restart the Windows Update or Upgrade process but make sure that your internet connection is stable and that you don’t touch anything so as not to interrupt the upgrade/update process again.

Option 2 – Check if your PC is plugged in or if the battery is full

It is always best to update your computer always when you’re really sure that the power won’t fail. If you’re using a desktop computer, make sure that everything is plugged in. And if you’re using a laptop when this error occurred, make sure that its battery is at 100% but it’s better if you just plug it into power just in case as there are times when the Windows update or upgrade gets stuck for too long like for hours so it will really help if your device is connected to power.

Option 3 – Try running the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows Update errors as well as the error 0x80200056. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button.

Option 4 – Delete the contents in the SoftwareDistribution folder

The Software Distribution folder in the Windows operating system is a folder that can be found in the Windows directory and is used to store files temporarily which might be required to install the Windows Update on your PC. Thus, it is required by the Windows Update and maintained by WUAgent. A lot of users tried deleting the files in this folder to fix the problem and so far it has worked. Like them, you can try clearing the Windows Update cache by simply deleting the contents of the folder named “SoftwareDistribution” since Windows apparently can’t clear and re-download the update contents once they are corrupted. Thus, deleting the contents of this folder will make Windows download the contents again which will fix the problem. To do that, follow the steps below.

• Open the WinX Menu.
• From there, open Command Prompt as admin.
• Then type in the following command – don’t forget to hit Enter right after typing each one of them.

net stop wuauserv net stop bits

• After entering these commands, it will stop the Windows Update Service and the Background Intelligent Transfer Service.
• Next, got to the C:\Windows\Software\Distribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.
• Once all the contents in the Software Distribution folder are deleted, restart your PC and then go back to Command Prompt and input the following commands again.

net start wuauserv net start bits

Since the folder has already been flushed, it will be populated afresh the instant your restart your computer and open Windows Update.

Option 5 – Try running the System File Checker scan

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files that might be causing the error 0x80200056. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

Option 6 – Run the Chkdsk utility to repair hard disk errors

You can also run the Chkdsk utility to resolve the Windows Update error 0x80200056. 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 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

Option 7 – Run the DISM tool to repair the Windows Update client

The Windows update/upgrade error 0x80200056 might be caused by some issues in the Windows Update client so you need to run the DISM tool to repair it. Note that you have to use another computer or another Windows from a shared network to fix it.

If you are trying to install or upgrade your Windows 10 computer but suddenly encountered an error message saying, “Windows Could not configure one or more system components”, read on as this post will show you how you can fix the problem. You are not alone in experiencing this problem as other users also reported having the same scenario. Some of them reported getting the following error message:

“Windows could not configure one or more system components. To install Windows restart the computer with error code 0xc1900101-0x30018.”

When you check on the Windows 10 rollback log, you will see a part with the “iisetup.exe” that’s related to the abort. Usually, the upgrade process completes over 50% and gets stuck and then rolls back later on and generates the error logs. This kind of error, in most cases, appears during the upgrade of Windows 10 and is related to the Internet Information Services or IIS in Windows 10. For some unknown reason, it restricts the installation or the upgrade which causes the error to appear. To fix the “Windows could not configure one or more system components” error, you can try to remove the IIS from the Windows Features or rename the “inetsrv” folder. You could also move all the folders related to IIS to another drive. For more details, refer to the options provided below.

Option 1 – Try to remove the IIS from Windows Features

The IIS is installed from the Windows Features and you can find it at Control Panel > Programs. From there, uncheck the checkbox for the Internet Information Services. Once done, click on the OK button to save the changes. Note that this process will get rid of all the related programs, services, and folders from Windows 10. So if you want to, you can just install them later on or use an offline installer from the official site of Microsoft.

Option 2 – Try renaming the inetsrv folder

The next option you can check out to resolve the problem is to rename the “inetsrv” folder. If you have uninstalled IIS from the Windows Features, this should remove the folders as well, however, it didn’t remove the folder then you have to delete the folders that are related to the IIS by following these steps:

• First, you have to boot into the Advanced Recovery Mode and from there, open Command Prompt.
• Next, execute this command to rename the folder from this location, C:Windowssystem32inetsrv: rename C:/Windows/system32/inetsrv/inetsrv.old
• Once done, boot into your computer normally and try to upgrade Windows 10 again, and check if the problem is fixed or not.

Option 3 – Try to move the folders related to IIS to a different drive

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• Next, look for the Application Host Helper Service from the list of services and stop it.
• Once done, take ownership of the “WinSxS” folder and then move the *windows-iis*.*” folders to another drive. You can just search using the “*windows-iis*.*” keyword in the Start Search.
• Next, tap the Ctrl + X keys and paste the folders to another drive.
• After that, start the update process for Windows 10 again.

A couple of Windows 10 users have reported an error on domain-connected systems when they tried accessing their computer systems remotely. This occurs when the network level authentication or NLA is enabled on the computer. If you are one of these users, you better keep reading as this post will guide you on how you can fix this error. To resolve this issue, there are several workarounds you can try. You can either disable this option directly via properties or you can also modify some registry entries or sub-keys and restart the system. When you encounter this problem, an error message pops up that states:

“The remote computer that you are trying to connect to requires network level authentication (NLA), but your windows domain controller cannot be contacted to perform NLA. If you are an administrator on the remote computer, you can disable NLA by using the options on the Remote tab of the System Properties dialog box.”

Or you could also see this error message instead:

“The remote computer requires Network Level Authentication, which your computer does not support. For assistance, contact your system administrator or technical support.”

Before you proceed in troubleshooting the problem using the options provided below, you need to create a backup for your data or system restore point as well as make a copy of any registry entries you are going to modify.

Option 1 – Disable Network Level Authentication via Properties

The NLA is a useful tool that provides your computer with extra security and helps network administrators in controlling who can log into the system with just a click of a single box. However, there are times when it can become a disadvantage and could prevent you from accessing your system remotely. Thus, you need to disable it using Properties.

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” and tap Enter to open System Properties.
• Next, go to the remote tab and uncheck the checkbox for the “Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)” option.
• Now click the Apply button to save the changes made and exit System Properties and then try logging into the remote computer again and see if the problem is fixed or not.

Option 2 – Disable NLA via Registry Editor

Note that you can only use this option if the first one didn’t work for you. Take note that this option will require you to restart your PC completely which could mean some downtime if your computer is running a production server. So make sure to save all your work.

• Tap the Win + R keys to open the Run dialog box and then type in “Regedit” in the field and tap Enter to open the Registry Editor.
• From there, click on File > Connect Network Registry and input the details of the remote computer and then try to connect.
• Navigate to the path below after you’re connected:

HKLM >SYSTEM > CurrentControlSet > Control >Terminal Server > WinStations > RDP-Tcp

• After that, change the values given below to “0”
  • SecurityLayer
  • UserAuthentication
• The navigate to PowerShell and execute this command – restart-computer

Option 3 – Disable NLA via PowerShell

PowerShell allows you to tap into the remote computer and once you’ve targeted the machine, you can execute the commands given below to disable NLA.

• Tap the Win + S to open Search and then type in “PowerShell” in the field. Right-click on the related result and select the “Run as administrator” option.
• After opening PowerShell, execute the command below:

2. Once in the PowerShell, execute the following command:

$TargetMachine = “Target-Machine-Name” (Get-WmiObject -class “Win32_TSGeneralSetting” -Namespace rootcimv2terminalservices -ComputerName $TargetMachine -Filter “TerminalName=’RDP-tcp'”).SetUserAuthenticationRequired(0) Note: In the command given, the “Target-Machine-Name” is the name of the machine you are targeting.

Option 4 – Use the Group Policy Editor to disable NLA

Another option you can use to disable NLA is via the Group Policy Editor. This is ideal for you if you are blanket disabling. Just take note that the Group Policy Editor is a powerful tool and that if you make some mistakes by changing values you have no clue about, you can render your computer useless so make sure that you create a backup for all the values before you proceed.

• Tap the Win + R keys to open the Run dialog box.
• Then type in “gpedit.msc” and tap Enter to open the Group Policy Editor.
• From there, go to this path – Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security
• After that, search for “Require user authentication for remote connections by using Network Level Authentication” and set it to disabled.
• Now check if the error is fixed or not.

If you encounter Windows Update error 0x80092004 while trying to update your Windows 10 computer, then this post is for you. This kind of Windows Update error could be due to many reasons but none of them includes your hardware or installed driver software. Microsoft releases updates that are either not supposed to go out, or you install them when you click on the Check for Update button which can install updates that have not finished testing yet. As a result, you may encounter the Windows Update error 0x80092004 To resolve the Windows Update error 0x80092004, here are some fixes you can try.

Option 1 – Try removing recent updates and packages

When a Windows Update fails, it mostly rolls back and cleans up all its residues. However, there are times when it doesn’t and you can clean that package manually. To remove recent updates and packages, you can go to the Update History and find out what KB updates were installed and once you’ve figured it out, you can execute the DISM tool to remove it manually.

• Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
• After that, execute the “Dism /online /Get-Packages”. This will give you a list of packages that were recently installed.
• Now run the Remove Package program to remove the concerned update and package.

dism.exe /online /remove-package /packagename:Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~16299.248.1.17 /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.125.1.6 /packagename:Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~16299.192.1.9 /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9 /norestart

• Now restart your computer and log back in.
• After that, run the following command:

Dism.exe /online /Cleanup-Image /StartComponentCleanup

• Then scan for updates.

Note: Keep in mind that the remove package command is made for AMD 64-bit machines specifically.

Option 2 – Try deleting the files from the SoftwareDistribution folder and resetting the Catroot2 folder

The downloaded Windows Updates are placed in a folder called “SoftwareDistribution”. The files downloaded in this folder are automatically deleted once the installation is completed. However, if the files are not clean up or if the installation is still pending, you can delete all the files in this folder after you pause the Windows Update service. For complete instructions, refer to the steps below.

• Open the WinX Menu.
• From there, open Command Prompt as admin.
• Then type in the following command – don’t forget to hit Enter right after typing each one of them.

net stop wuauserv net start cryptSvc net start bits net start msiserver

• After entering these commands, it will stop the Windows Update Service, Background Intelligent Transfer Service (BITS), Cryptographic, and the MSI Installer
• Next, go to the C:/Windows/SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.

After resetting the SoftwareDistribution folder, you need to reset the Catroot2 folder to restart the services you just stopped. To do that, follow these steps:

• Type each one of the following commands.

net start wuauserv net start cryptSvc net start bits net start msiserver

• After that, exit Command Prompt and restart your computer.

Option 3 – Try to run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the “We couldn’t install some updates because the PC was turned off” error. To run it, 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 4 – Try to manually install the Windows Updates

Windows Update Error 0x80092004 might be due to a Windows Update that has failed. So if it is not a feature update and only a cumulative update, you can download the Windows Update and install it manually. But first, you need to find out which update has failed, and to do so, refer to the following steps:

• Go to Settings and from there go to Update and Security > View Update History.
• Next, check which particular update has failed. Note that Updates that have failed to install will be displayed under the Status column which has a label of “Failed”.
• After that, go to the Microsoft Download Center and look for that update using its KB number and once you find it, download and then install it manually.

Note: You can also use the Microsoft Update Catalog, a service from Microsoft that provides a list of software updates that can be distributed over a corporate network. With the help of this service, it can be easier for you to find Microsoft software updates, drivers as well as fixes.