Photo viewer on clean Windows 10 instalation

There is no doubt that the VLC media player is one of the best kinds of media players available today. However, it is not without any issues and one of the common issues encountered by users is VLC’s inability to be updated. And when you try to update VLC, you only get an error message saying, “An error occurred while checking for updates”. This inability to update VLC can be quite a headache for many users especially the ones who are facing other issues in VLC and has to update it in order to resolve them. So how will you update VLC and fix its issues when you can’t even update it in the first place? Worry not as this post will help you out. Refer to the suggestions laid out below to resolve the issue in updating VLC.

Option 1 – Check if VLC is not being blocked by the Firewall

There are instances when the Firewall like the Windows Defender Firewall blocks VLC for some unknown reason without your knowledge. Thus, you need to allow VLC to get past the Firewall in order for you to fix the issue else you won’t be able to send out a network communication. To do that, follow the steps below.

• Tap the Windows key + I to open the Settings app.
• Then click on the Update & Security option.
• After that, click on Windows Security and click the Open Windows Defender Security Center option. This will open the Windows Defender antivirus and antimalware program.
• From there, click on Firewall & network protection.
• Next, click on Allow an app through Firewall. You should see a list of programs. Scroll down until you see VLC and make sure that all the boxes are ticked including the Public and Private ones.
• Once you’re done, restart your PC and then try updating VLC again.
• Just open VLC and select the Help menu and click on Check for Updates.

Option 2 – Try running the VLC media player as an administrator

There are programs designed for Windows 10 that won’t work fully unless some parameters are met. In most cases, starting the program as an admin should resolve the problem, thus, that’s what you have to do to try and fix the “An error occurred while checking for updates” in VLC.

• First, right-click on the VLC Media Player desktop icon and then select the “Run as administrator” option or you could also right-click on the icon and click on Properties.
• After that, click the Compatibility tab and then tick the box labeled “Run this program as an administrator”.
• Next, click the OK button and then open VLC again and try updating it. That should fix the problem.

One of the errors you can encounter while browsing the web using your Google Chrome browser is the ERR_TUNNEL_CONNECTION_FAILED error. If you happen to encounter this error, then this post could help you resolve it. This kind of error in Chrome can occur due to incorrect website domain configuration, conflicting browser data, incorrect proxy settings, and DNS connection issues. To resolve the ERR_TUNNEL_CONNECTION_FAILED error in Chrome, here are some suggestions you can check out.

Option 1 – Try disabling the proxy server for your LAN

If your PC was just attacked by some adware or malware as of late, it is possible that it has changed the network settings in the system and might display spam advertisements. Thus, you have to disable the proxy server for your LAN. To do that, refer to these steps:

• Tap the Win + R keys to open the Run dialog box.
• Then type “inetcpl.cpl” in the field and hit Enter to pull up the Internet Properties.
• After that, go to the Connections tab and select the LAN settings.
• From there. Uncheck the “Use a Proxy Server” option for your LAN and then make sure that the “Automatically detect settings” option is checked.
• Now click the OK and the Apply buttons.
• Restart your PC.

Note: If you are using a third-party proxy service, you have to disable it.

Option 2 – Try to reset Winsock, TCP/IP & Flush DNS

Resetting Winsock, TCP/IP, and flushing DNS might help you resolve the ERR_TUNNEL_CONNECTION_FAILED error. To do so, follow these steps:

• Right-click on the Start button and click on Command Prompt (administrator) so you can pull up an elevated Command Prompt.
• After that, execute each one of the commands listed below. And after you typed in one after the other, you have to hit Enter.

1. netsh winsock reset – type in this command to reset Winsock
2. netsh int ip reset resettcpip.txt – type in this command to reset TCP/IP
3. ipconfig /flushdns – type in this command to flush the DNS cache

• Next, restart your PC and check if the problem’s fixed.

Option 3 – Try using a VPN connection

There are instances when the network that your computer is logged on might have blocked your access to the website you are trying to open and so to fix it, you can try to use a VPN connection. Once you’ve connected using VPN, try to open the website again and see if you can now access it.

Option 4 – Try clearing browser data

There are times when some data in the browser is conflicting with the loading of the website and triggers errors like ERR_TUNNEL_CONNECTION_FAILED. And so you can try to clear your browser’s data. This might be a very basic solution but oftentimes it works in fixing this kind of error in Google Chrome. Follow the steps below to clear the data in your browser.

• Open your Google Chrome browser.
• After that, tap the Ctrl + H keys. Doing so will open a new panel that allows you to delete the browsing history and other data in your browser.
• Now select every checkbox that you see and click on the Clear browsing data button.
• Then restart your Chrome browser and check if you can now open any website or not.

Option 5 – Get rid of any conflicting browser extensions

• Open Chrome and press Alt + F keys.
• Go to More tools and click Extensions to look for any suspicious browser extensions or toolbars.
• Click the Recycle bin and select Remove.
• Restart Chrome and press Alt + F keys again.
• Proceed to On Startup and mark Open a specific page or set of pages.
• To check if the browser hijacker is still active, click Set pages, if it is active, overwrite the URL.

Note: If removing the browser extensions or toolbars didn’t work, you can also try to reset your Google Chrome browser.

• Open Google Chrome, then tap the Alt + F keys.
• After that, click on Settings.
• Next, scroll down until you see the Advanced option, once you see it, click on it.
• After clicking the Advanced option, go to the “Restore and clean up option and click on the “Restore settings to their original defaults” option to reset Google Chrome.
• Now restart Google Chrome.

There are cases when you want to undo some changes you’ve made to your computer and to do that you have to perform the System Restore task. However, if you encounter an error that states “To use System Restore you must specify which Windows installation to restore”, when doing so, read on as this post will help you fix the problem. This kind of error in System Restore could be due to corrupted files in the system. There are also situations where you are not able to boot up once you encounter this error which could be a big problem. On the other hand, this error might have something to do with corrupted BCD files. Whatever the cause is, here are some potential fixes you have to try.

Option 1 – Try to run System File Checker offline

Like pointed out, since the error might be due to corrupted system files, you can try to run System File Checker offline. How? Refer to these steps:

• You need to go to the Advanced Startup Options and from there select Troubleshoot.
• Next, select the Advanced Options and then Command Prompt.
• After opening Command Prompt, type the commands given below and tap Enter right after you type each one of them.
  • Cd /
  • Dir

• If you can see the “Users” folder, that is your system’s drive. However, if you can’t see it, you can just change the drive-by assigning “D” as its alphabet volume.
• Then execute this command where “C” is the system drive: sfc /scannow /offbootdir=C: /offwindir=C:Windows
• Now repeat the given steps sequentially.

Option 2 – Try to run DISM tool

You can also run the DISM tool to repair the potentially corrupted system image. First, you have to check the health of the system like checking the integrity of the system files and Windows services. To run DISM, follow the given steps below sequentially.

• Open Command Prompt from the Advanced Startup options.
• After that, execute this command where “C:” is the system volume: DISM /Image:C:Windows /Cleanup-Image /RestoreHealth /Source:C:WindowsWinSxS
• If you encounter an error after executing the given command, insert the Windows USB or DVD and then execute this next command where “E:” is the USB or DVD drive: DISM /Image:C:Windows /Cleanup-Image /RestoreHealth /Source:esd:E:SourcesInstall.esd:1 /limitaccess
• In some cases, “install.esd” would be “install.wim” and in such case, you have to modify and execute this command: DISM /Image:C:Windows /Cleanup-Image /RestoreHealth /Source:wim:E:SourcesInstall.wim /limitaccess

Option 3 – Try to repair corrupted BCD

As mentioned, the error could also be due to corruption in BCD, and to fix it, you can use Bootrec.exe – a built-in command-line tool used to troubleshot issues related to boot up and Windows Startup. Before you run this tool, make sure that you have inserted a bootable USB or DVD into your computer. Once you have that covered, follow these steps:

• You need to go to the Advanced Startup Options.
• Then click on Troubleshoot.
• Next, select the Advanced Options and then Command Prompt.
• Once Command Prompt has been pulled up, enter each one of the following commands and in the sequence that they are given to rebuild BCD files and repair MBR files:
  • Bootrec /Fixmbr
  • Bootrec /FixBoot
• After you execute the commands given above, you should see a confirmation message that says, “The operation completed successfully”.
• Now type the “Bootrec /RebuildBCD” command to rebuild BCD.
• Finally, close Command Prompt and then restart your computer to successfully apply the changes made.

Option 4 – Try to run the Automatic Repair Utility

You might also want to use Automatic Repair in fixing the error. To do so, follow the steps below.

• You can start by creating and booting from a bootable Windows 10 USB Stick.
• After that, click on Repair your computer located in the bottom left corner when you are on the initial Windows Startup screen.
• Next, click on Troubleshoot, and then on the other screen, click the Startup Repair option.
• Now select the operating system you want to repair. Once you do that, it will start to repair your operating system. Wait until the process is completed and then check if the problem’s now fixed.

Option 5 – Try to use the Windows Recovery Environment

If the four options given above didn’t help fix the problem, you could try running Windows Repair and a Windows bootable USB or DVD.

• First, insert the bootable USB or DVD and boot into it, and select the “Repair your computer” option.
• Next, once you see the manufacturer logo on your computer, tap the key to enter into Windows Recovery Environment.
• After that, change the Boot sequence to DVD drive under the UEFI Firmware settings and restart your computer.
• Once your computer has restarted, select the boot order and make changes accordingly as displayed in the BIOS.

Option 6 – Try running System Restore in Advanced Startup Options

Since you probably can’t boot into your Windows 10 computer, you can try to run System Restore again in the Advanced Startup Options.

• Boot your computer into the Advanced Startup Options screen.
• From there, you will see some options to troubleshoot when you can’t log in to Windows in the usual way.
• Now select Troubleshoot > Advanced Options > Command Prompt.
• After that, type “exe /OFFLINE:C:Windows” and hit Enter to execute the command which will start the System Restore process.

Note: You need to replace “C” with the drive where Windows Installation is located.

If VirtualBox suddenly displays a black screen without any text or mouse cursor when you are trying to boot a guest operating system, then read on as this post will guide you in fixing such an issue. This black screen occurs when Windows 10 failed to provide a specific setting that VirtualBox requires. Consequently, you will not be able to install or use any guest operating system in VirtualBox even if your PC has virtualization support, the best thing you can do now is to fix this black screen issue. There are two ways you can fix this black screen in VirtualBox, you can either try to disable Hyber-V or disable 3D Acceleration. For more details, refer to each one of the given options below.

Option 1 – Try to disable Hyper-V

Hyper-V is a built-in virtualization tool available in Windows that helps users in creating a virtual machine as well as install a guest operating system without using any third-party tool like VMware, VirtualBox, and many more. However, the problem with this virtualization tool is that some systems cannot run it and VirtualBox simultaneously which is most likely why the screen abruptly turns into black. Thus, you have to disable Hyper-V to resolve the problem. How? Refer to these steps:

• In the Start Search, type “Turn Windows features on or off” and then click on it from the results.
• Once you’ve opened the Windows Features window, remove the checkmark from the Hyper-V box.
• Click the OK button and then restart your computer.
• Now try to use VirtualBox again and see if the problem is fixed.

Option 2 – Try to disable 3D Acceleration

The guest operating system will use the host computer’s GPU to render 3D graphics if you enable the 3D Acceleration for the virtual machine. To simply put it, it will enhance the graphics of the virtual machine and will let you use 3D graphics. Although it may seem nice, it can actually cause the black screen to appear as well so you might have to disable it to isolate the problem. In fact, a lot of operating systems have failed to use the 3D Acceleration for the guest operating system because of this black screen issue. To disable it, follow these steps:

• Open VirtualBox on your computer and select the virtual machine.
• Next, click on the Settings button and go to the Display section.
• After that, look for a checkbox named “Enable 3D Acceleration” located on your right-hand side and then uncheck it.
• Save the changes you’ve made and reboot your PC and see if you can now run the virtual machine without any problem.

Upgrading your Windows 10 computer does not always go smoothly and you often encounter not just one but various errors so, in this post, we are going to cover several Windows 10 upgrade errors such as 80240020, 8007002C, 80246007, 80070004. All these upgrade errors are related to the Windows Update folder. Thus, you need to clear the Software Distribution folder, repair the System Image and fix System Health in order to resolve all these Windows 10 Upgrade errors. Before you get started on the steps to resolve these tons of errors, you have to disable your security program for the meantime, disconnect your peripherals, remove USBs connected to your PC and then make sure that your PC is connected to the main power supply. Once you have everything covered, carefully follow the options given below.

Option 1 – Delete Windows 10 Update Files 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, 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.
• 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.

• Now Open Settings and check for Windows Updates. Windows 10 should begin the download right away.

Option 2 – Try using the DISM tool

Running the DISM Tool helps in repairing the Windows System Image as well as the Windows Component Store in Windows 10. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt with admin privileges.
• Then type in the following commands and make sure to hit Enter right after you type each one of them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • exe /Online /Cleanup-image /Restorehealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Note: If it happens that the Windows Update client is broken, you need to run the following command to repair it then restart your PC and click on Update once again.

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:RepairSourceWindows /LimitAccess

Note: The Windows Upgrade error, with error code 80240020 is an expected error message that happens when the upgrade requires customer user action. Thus, you need to do the following steps to resolve this particular Windows Upgrade error.

• Tap the Win + R keys to open the Run dialog box.
• Then type “regedit” in the field and hit Enter to open the Registry Editor.
• After that, navigate to this registry key: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWindowsUpdate
• Now right click on WindowsUpdate located in the left pane and then create a new key and name it as “OSUpgrade”
• Next, right-click in an empty space in the left pane and create a new DWORD and name it “AllowOSUpgrade” and enter “1” as its value.

Option 3 – Try running the Windows Update in a Clean Boot State.

Putting your PC in a Clean Boot state can also help you install Windows Updates or Upgrades without any trouble because, during this state, you can start the system with a minimum number of drivers and startup programs that will surely help you in isolating the root cause of the issue.

• 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” checkbox 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” checkbox.
• 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.)
• After that, try to install the Windows Updates or upgrade again.

If you encounter a Windows Update error with an error code 0x80070652 and an error message saying, “ERROR_INSTALL_ALREADY_RUNNING”, then it indicates that there was a previous Windows Update that was not installed successfully. This kind of Windows Update error typically happens when it gets stuck and so to resolve it, here are some suggestions that might help.

Option 1 – Restart your computer and try installing the Updates again

You can restart your computer and then try installing the updates once again. There are instances when a simple restart resolves Windows Update errors. Thus, after you restart your computer, check for updates once again and see if you’re still getting the error or not.

Option 2 – Try running the Windows Update troubleshooter

You might also want to run the Windows Update Troubleshooter as it could also help in fixing Windows Update error code 0x80070652. 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 3 – Try downloading the Windows Update that failed

If the Windows Update that has failed 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.

Option 4 – Try to restart the Background Intelligent Transfer Service

The Background Intelligent Transfer Service or BITS is a part of the Windows Update service and is the one that manages the background download of Windows Update, as well as scans for new updates and so on. And if Windows Update is experiencing some problems, you can try restarting BITS but make sure that you have admin privileges to do so.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “services.msc” in the field and hit Enter to open Windows Services.
• From the list of Services, look for the Background Intelligent Transfer Service and double-click on it to open Properties.
• After that, you need to set the Startup type to “Automatic (Delayed Start) and click on Apply.
• Now click the Stop button to stop BITS and then click the Start button to restart the service.
• Click OK to save the changes made and then restart your PC.

Option 5 – Try to update Windows after a couple of minutes or an hour

There are times when the issue is from Microsoft’s end. It could be that there’s some issue with Microsoft’s server so it would be better if you give it a couple of minutes or an hour or so before trying to run Windows Update again.

I do not know about you, but I prefer to set my Windows to be more to my liking and not how Microsoft thinks it should be. Let’s face it, not all users feel comfortable whit Microsoft settings and idea how things should be. One of the things I particularly did not like even in Windows 10 is icons that come by default on my taskbar, now so far, well until the latest Windows 11 update you could remove default taskbar icons the same way as in Windows 10, just right-click on them and unpin, sadly with latest update build on Windows 11 this option has been removed. In order to remove default icons from the taskbar, one must go now to Windows 11 settings and choose from there which one you would like to be placed on it. Of course, this is nothing game-breaking but it still feels strange why the standard option has been removed, it just makes no sense but lately not many things that come from Microsoft do. I do not know about you, but I prefer to set my Windows to be more to my liking and not how Microsoft thinks it should be. Let’s face it, not all users feel comfortable whit Microsoft settings and idea how things should be. One of the things I particularly did not like even in Windows 10 is icons that come by default on my taskbar, now so far, well until the latest Windows 11 update you could remove default taskbar icons the same way as in Windows 10, just right-click on them and unpin, sadly with latest update build on Windows 11 this option has been removed. In order to remove default icons from the taskbar, one must go now to Windows 11 settings and choose from there which one you would like to be placed on it. Of course, this is nothing game-breaking but it still feels strange why the standard option has been removed, it just makes no sense but lately not many things that come from Microsoft do.

There are times when the WMI Repository gets corrupted which results in the Provider Load Failure. To resolve this issue, you need to repair or rebuild the WMI Repository in your Windows 10 computer. In this post, you will be guided on how exactly you can do that. In case you don’t know, the WMI which stands for Windows Management Instrumentation is a set of specifications from Microsoft to consolidate the management of devices and applications in a network. The WMI is a database that stores meta-information and definitions for WMI classes. Using only these, the conditions of the systems can be known. You can find the WMI Repository in %windir%System32WbemRepository. It provides end-users with the status of the local or remote computer system. Keep in mind that you must not use this on the Server 2012 Cluster machine. Although there are command-line tools that can fix or restore the Windows Management Instrumentation repository. However, Microsoft suggests that it’s better if you verify if there is corruption. Here are a list of errors as well as permission issues you might encounter:

• Unable to connect to root default or rootcimv2 namespaces. It fails with the error code “0x80041002” pointing to “WBEM_E_NOT_FOUND.”
• 0x80041010 WBEM_E_INVALID_CLASS
• When you open Computer Management and Right Click on Computer Management (Local) and select Properties, you get the following error: “ WMI: Not Found” or it hangs trying to connect
• Trying to use wbemtest , and it hangs
• Schemas/Objects missing
• Strange connection/operation errors (0x8007054e)

To verify if there is corruption, you can try running the following command in an elevated Command Prompt:

winmgmt /verifyrepository

 After you enter the command, if there is a response saying, “repository is not consistent”, then the repository has an issue. If not, then something else is causing the problem. Since you are certain that corruption exists in the WMI repository, then here are some suggestions you need to check out to repair or rebuild the WMI repository.

Option 1 – Try to reset WMI Repository

• Type “command prompt” in the Start Search and right-click on Command Prompt from the search results and then select “Run as administrator”.
• After opening Command Prompt with admin privileges, type and enter this command: winmmgmt /salvagerepository

The command you entered is used when the winmmgmt command performs a consistency check. So if an inconsistency is detected, it will rebuild the repository.

• Next, execute this command to see if the WMI repository now comes back as consistent: winmgmt /verifyrepository

This command will perform a consistency check on the WMI repository.

• If it states that the WMI repository is not consistent, then you need to type and enter this command: winmgmt /resetrepository

This command is used to reset the repository to its initial state when the operating system was first installed.

Option 2 – Try to force recover the WMI Repository

The WMI Repository comes with a built-in self-recovery process so when the WMI service restarts or detects any corruption, it will automatically trigger the self-recovery procedure. This can happen in two ways:

• AutoRestore: This will use the backup images if the Volume Shadow copy or VSS backup is turned on.
• AutoRecovery: The rebuilding process will generate fresh images of the WMI repository based on the registered MOFs. The MOFs are available in the registry located at HKLMSoftwareMicrosoftWBEMCIMOM: Autorecover MOFs

Note: Autorecover MOFs is a key so double click on it to check its value. On the other hand, if the self-recovery procedure does not work, you can try to use the force-recovery process instead. How? Refer to these steps:

• First, you need to check the reg key value is empty or not under this registry path: HKLMSoftwareMicrosoftWBEMCIMOMAutorecover MOFs
• If the reg key value is empty, you have to copy-paste the reg key value from another computer. Just make sure that it’s from the System which is equivalent to the computer in question.
• Next, type and enter this command: Winmgmt /resetrepository
• After you enter the command, if you get an error that says, “WMI repository reset failed. Error code:0x8007041B. Facility: Win32”, then you have to stop all the Dependency Services on the WMI service by running the following commands:
  • net stop winmgmt /y
  • Winmgmt /resetrepository

This should fix the problem.

There are times when after you upgrade your Windows operating system, the System Logs under the Event Viewer will display an error message saying, “Event ID 10010 error – The server did not register with DCOM within the required timeout”. What is DCOM? DCOM stands for “Distributed Component Object Model”. It is a proprietary Microsoft technology that allows the Component Object Model or COM software to communicate across a network. You can consider it as an extension of COM which is equipped with the capability of solving a couple of inherent problems related to the COM model to the better use over a network. COM is a tool that’s used for advanced configuration and troubleshooting in Windows 10. Developers usually use it to configure routine components and application behavior like participation in transactions and object pooling and so on. The Component Services needs the DCOM wire protocol in order to communicate with the Component Object Model components on other computers. By default, in a Windows-based system, the network computers are configured initially to enable DCOM. There are also some components in Windows that might require registering themselves with DCOM. However, if they fail to do so, you will encounter the “The server did not register with DCOM within the required timeout” error. To fix this, here are some suggestions you can check out.

Option 1 – Try to use the Component Services

• Tap the Win + R keys to open the Run dialog box.
• Then type “dcomcnfg” in the field and tap Enter to pull up Component Services.
• Next, double click on the Computers folder located in the right pane and right-click on My Computer, and select the Properties option.
• After that, switch to the COM Security tab under My Computer Properties and then go to the Access Permissions section.
• From there, click the Edit Default button and in the new window that appears, apply the correct permission to objects under the Group or user names section.
• Once you’re done, click OK and exit. This should fix the error.

Option 2 – Make sure that Function Discovery Resource Publication Properties Services is running

• In the Cortana search box, type “services” and click on the Services icon to open the Services Manager. Alternatively, you can also tap the Win + R keys to launch the Run prompt and then type “services.msc” in the field and hit Enter to open the Services Manager.
• Next, scroll down and look for the “Function Discovery Resource Publication” entry and double click on it.
• Then switch to the General tab and from there, make sure that the Startup Type is set to “Manual (Triggered).
• You also have to make sure that the service is running so if it’s not, just click on the Start button to start the service.
• Now click on Apply to save the changes made.

Option 3 – Try resetting the default DCOM permissions

• Tap the Win + R keys to open the Run dialog box.
• Then type “dcomcnfg” in the field and tap Enter to pull up Component Services.
• After that, expand Component Services > Computers and right-click on My Computer, and then select Properties.
• Next, go to the Default Properties tab, and in the Default Distributed COM Communication Properties section, make sure that:
  • Default Authentication Level is set to Connect
  • Default Impersonation Level is set to Identify.

KMODE_EXCEPTION_NOT_HANDLED – What is it?

Some users installing or upgrading to Windows 10 experienced the theKMODE_EXCEPTION_NOT_HANDLED Blue Screen of Death (or commonly known as BSOD) error. This error can be due to different types of things, ranging from software to driver issues. When you experience this BSOD error while trying to install Windows 10, it will prompt you to restart your computer every single time you experience it. In most cases, you will also not be able to proceed with the Windows 10 set-up.

Solution

Error Causes

The “KMODE_EXCEPTION_NOT_HANDLED” error is normally caused by:

• Hardware incompatibility
• A faulty device driver or system service

Further Information and Manual Repair

You won’t be able to successfully upgrade or set up Windows 10 if you continue to encounter this BSOD error. Note that this error will always prompt your computer to restart every time it happens, preventing you from completing the Windows 10 set-up.

If you’re not tech-savvy or not capable of debugging this issue, it’s highly advisable to proceed with the basic troubleshooting techniques available in this link.

After troubleshooting, below you’ll find a few solutions to rectify the issue.

Method 1 – Check The Cause of The BSOD Error

Two common causes of the KMODE_EXCEPTION_NOT_HANDLED issue are hardware incompatibility and faulty device driver or system service.

If you experience this error, check first if any of your newly installed hardware is compatible with Windows 10. You can find the required hardware for Windows 10 from this link. 

If all your hardware is compatible with Windows 10, you might need to check the device driver or system service. Review the bug check message. If any of the drivers you have is listed in the message, either disable or uninstall them before upgrading or setting up Windows 10.

You might also find it useful to check the System Log available in the Event Viewer for other error messages that can help you figure out the driver or device that’s causing the error. Running hardware diagnostics can also be useful.

Method 2 – Disable (or preferably uninstall) Software Before Upgrading

If you’re upgrading Windows 10 from Windows 7 or Windows 8.1, you might need to disable or uninstall the software first. First, try uninstalling your Antivirus utility before starting the upgrade. Restart a few times before starting the Windows 10 installation. If you’re upgrading using the Windows 10 update, make sure that you disconnect from your Wi-Fi or Internet LAN (Ethernet) connection as soon as the download reaches 100% before attempting to start the set-up. Other users also reported that the cause of the KMODE_EXCEPTION_NOT_HANDLED issue is BitDefender. If this is what happened in your case, it will show in the error message such as KMODE_EXCEPTION_NOT_HANDLED (bdselfpr.sys). Users reported that a common solution for this is renaming the file. In the case of BitDefender, try renaming it to bdselfpr.s__. However, make sure to do this cautiously. Sometimes, renaming a file will even do more damage than good.

Method 3 – Disable/Disconnect From Hardware

If you’re connected to any general USB devices (such a smart card reader), disable it. If your computer is connected to other external devices, disconnect all of them. Examples of this include gaming controllers, printers, external hard disk, USB keys, and other non-essential devices).

Method 4 – Other Troubleshooting Steps

Other troubleshooting steps include:

• Upgrade using an .ISO file, instead of directly upgrading from Windows Update. When you do this, make sure you’re disconnected from the Internet during installation. If the process started and you forgot to disconnected, it’s best to restart the installation.
• If you’re connected to a domain while trying to set up Windows 10, disconnect and use a local account.
• If you’re using a SCSI hard disk, connect a thumb drive with the drivers for your storage device. While Windows 10 is setting up, click on the Custom Advanced Option. Using the thumb drive, use the Load Driver command to load the SCSI drive.
• Another possible cause of this error is due to BIOS incompatibility. BIOS issues can be solved by upgrading your version of your system BIOS. If you don’t know how to do this, refer to your BIOS manufacturer’s website.

Method 5 – Use A Trusted Automated Tool

If you still experience the error after doing the methods above, you might want to try a powerful and trusted automated tool to fix the job.