Windows 10 error issues and how to fix them

In this article, we gather the common Windows 10 errors and their solution.

Event 10016 DistributedCOM error 2593F8B9-4EAF-457C-B68A-50F6B8EA6B54

Error 2593F8B9-4EAF-457C-B68A-50F6B8EA6B54 doesn’t briefly ignite any damage to the function. But if you anyway want to resolve the problem, be cautioned and make sure to avoid mistakes while editing the registry. Any minor mistake may implicate complications in the system.

First, open the registry editor by pressing W8K + R, followed by putting the regedit in the Run dialog. Then navigate the HKEY_CLASSES_ROOT\AppID\{F72671A9-012C-4725-9D2F-2A4D32D65169} registry key in the registry editor window.

Find the {F72671A9-012C-4725-9D2F-2A4D32D65169} key and right-click on it to select permissions and the Advanced button after that.

On the Advanced security settings, you’ll learn that the current owner is TrustedInstaller. Proceed with the change link option and right away take the ownership.

Subsequently, you’ll be redirected to the permissions sheet. Select your account, then the system listed under Group, and finally the Allow box against Full control.

Now you have total control, with the system allowing you to manage any further registry key and activities. Press apply and click.

Likewise, take the HKEY_CLASSES_ROOT\CLSID\{8D8F4F83-3594-4F07-8369-FC3C3CAE4919} key’s ownership, take ownership, and get control for yourself and SYSTEM. Hit W8K + R and then find the dcomcnfg in the Run dialog box. After this, press enter, and component services will be opened.

Now at the component services, proceed with console root, then components services, then my computer, then DCOM Config, click View in details.

Spot {F72671A9-012C-4725-9D2F-2A4D32D65169} and right click to select properties.

Change to the Security tab in the property sheet and then choose ‘customize’ located under the Launch and activation permissions section. Click edit, again in the launch and activation permission, select Add.

Type SYSTEM on the object name (select users or groups), followed by clicking check names. There you’ll find SYSTEM is underlined and also connected to the SYSTEM object. Click OK.

Go to group or user names again in the Launch and activation permission and then select SYSTEM. Check the Allow box, click OK, and that’s it!

Exit the registry editor to reboot your device. Few hours or after a couple of restarts, the error will cease popping up.

6B3B8D23-FA8D-40B9-8DBD-B950333E2C52

To fix the 6B3B8D23-FA8D-40B9-8DBD-B950333E2C52 error, open Regedit, and then navigate the flagged keys and start changing their ownership. Get full control permission to the key owner that you have just corrected.

Move to the DCOM Config and take off editing the security properties you’ll find in the WPN Srumon Server. That will give you the launch and activation permissions. Lastly, reboot!

9E175B6D-F52A-11D8-B9A5-505054503030

To fix error 9E175B6D-F52A-11D8-B9A5-505054503030, follow the steps you did to fix the other 10016 errors, first by editing registry, changing permissions, taking ownership, and getting full control. But make sure that you change the ownership to trusted installer after again.

After this, reach the component services from Administrative tools. From the component services, open Computer, my computer, and then DCOM Config. After this, click on search and then right-click on it to ‘properties’ and lastly, the Security tab. Edit the security permissions on Launch and activation permissions. Close the component services UI, and you are fixed!

C2F03A33-21F5-47FA-B4BB-156362A2F239

The C2F03A33-21F5-47FA-B4BB-156362A2F239 error occurs when the machine-default permission settings do not grant local activation permission (just as the error defines).

Start by logging in and opening the registry editor as the administrator. Then navigate to the HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{C2F03A33-21F5-47FA-B4BB-156362A2F239}.

Over the Registry Editor, right-click on {C2F03A33-21F5-47FA-B4BB-156362A2F239} and then select permissions and then click administrations. Check the Full box control, followed by allowing click advanced. There, in the security settings, follow with the change, type administrators, and OK. This is all for the CLSID.

You have to do the same for APPID by navigating HKEY_LOCAL_MACHINE \ SOFTWARE \ Classes \ APPID \ {316CDED5-E4AE-4B15-9113-7055D84DCC97} and right-clicking on it.

After the security settings part, open the component services (as an administrator). Then in the component services, go to computers, my computers, and DCOM Config. Down you’ll have the immersive shell and click properties.

Click customize from the Launch and Activation permissions and edit. Again, in the Launch and Activation window, click Add, type the local service, and OK. Then check Local Activation and OK. Conclude by rebooting your computer, and you have it solved!

0x80080008

The 0x80080008 error confides majorly when you are proceeding to an update. Updating windows formulates many errors for the users, and error 0x80080008 is no different from those. Most of the time, the reason for this error is due to the update being stuck, or else some of the updating files are not downloaded successfully.

Start by checking your antivirus system. Antivirus concerned problems, too, may lead to 0x80080008 update error. Maybe turn off the antivirus and find out if that somehow helps to solve the error? If it doesn’t seem to be effective, wholly discontinue the antivirus and again find out if that works.

The second method is by performing SFC and DISM scans. This will yield an effective result when the Windows installation is either damaged or corrupted. An SFC scan that hunts for the corrupted files is adequate to heal the error.

But when SFC isn’t working, DISM is the alternative option.

The third day you can fix the error 0x80080008 is by restarting the Windows Update components.

0x800f081f

0x800f081f error is a common counterpart that generally occurs when you are permitting the .NET Framework through the installation wizard. If not the installation wizard, then either by the DISM or Windows PowerShell commands.

Error 0x800f081f, though common, isn’t so problematic to destroy. To do so, open the group policy editor and reach the computer configuration, followed by opening the administrative templates and system. Then, double click on the specified settings to optional component installation and component repair. Click on Enable.

0x0000142

0x0000142 error happens to surface mostly in the wrong settings of the configured system. In other cases, it might be due to system element’s not such regular entries. These situations will want you to rebuild the system element and stability through system settings. Specific software built for this reason is an answer here.

0x0000142 depicts the existence of malfunction, the cause of its occurrence, the component malfunctioned, and some more details. The appearance of this code simply means that the desktop or the laptop is experiencing a malfunction in the system operation. To be more specific, there’s a failed installation or a failed uninstallation. Another reason is the inappropriate way of the shutdown, generally because of a power failure and deleting a system file accidentally that is important for the system to function.

Fixing up the system elements will help to solve the error 0x0000142 instantly. But make sure that you do it carefully and have in-depth knowledge already, else get a professional. Any sort of mistake may leave your system destroyed.

0x000007b

0x000007b error also has many reasons for occurrence, out of which launching an application (Fortnite, for example) is the most common one. The error is a big problem and acts as a barrier from entering the application.

Few other reasons why 0x000007b is popping up. Is it maybe because of an outdated or corrupted Microsoft .NET framework? Or maybe corrupt system files and broken windows registry? Well, the causes don’t end here, and similarly, the ways of fixing are plenty. Let’s emphasize three of them:

First, reinstalling Microsoft Visual C++. For this, get the licensed version Reimage. To have one, go to Cortana and search for it. From the ‘programs,’ find out entries that may be pointing with Visual C++, and uninstall. Then, reinstall the virtual studio from the Microsoft website. Do this to the one application causing the error 0x000007b. For an application developed in 2018, get a visual studio of 2017.

Second, reinstalling the Microsoft .NET framework. Since the .NET framework is an essential part, errors to it are obvious. Downloading Microsoft .NET framework four from the official Microsoft website will help fix the error.

Third, resetting the application that is creating problems. Select the problematic application, and select the Advanced options for it. Then, at the bottom of the panel, you will see the Reset the app option whenever the error 0x000007b comes out. The following time you launch the application, you should be all sorted.

0x80070490

0x80070490 error points out that there is a file corrupted in either the system component store or CBS (functioning the operations of windows update).

The most common event when 0x80070490 usually pops up is while you update an app that was earlier installed from the Microsoft store or have initiated the system update through Windows Update.

There are many other reasons for the error that bring you to 5 different ways of how you can fix them. The five ways include Running the system file checker scan, restoring a system, discontinuation of 3rd party antivirus, altering the WU component settings, and repairing WU.

0x80070422

You might have faced the yearning of 0x80070422 error on the screen while trying to update windows ten from the Windows update. The frustrating part is when this error fully terminates you from downloading the latest windows. So, try solving it!

Start attempting to fix it by making sure that the windows update service is still running in the background. If the problem continues to persist, try disabling IPv6 options. And if the problem isn’t leaving yet, restart the network list service or run the windows ten update troubleshooter.

 

Check out other posts: