How to Fix msrtn32.exe error or high CPU usage

This post will guide you in fixing high CPU, Memory, and Disk usage problems caused by NTOSKRNL.exe. NTOSKRNL stands for “NT Operating System Kernel. This file is a kernel image that is responsible for a lot of systems-based processes such as Hardware Virtualization, Process, and Memory. Aside from that, it is also the one that compresses the old pages of memory that reduces the overall amount of memory being used. If you notice that your computer is running slowly and you find that the NTOSKRNL.exe file is hogging your resources such as disk usage, CPU usage as well as memory usage, then read on as this post will guide you in fixing the problem caused by NTOSKRNL.exe. Make use of the options given below to resolve the issues caused by NTOSKRNL.exe. 1] Scan your computer for potential malware There might be a good chance that your computer might be infected with malware. And this malware might be associated with the NTOSKRNL.exe file and hence making it consume a lot of system resources. So, I would really recommend you to make sure that your Antivirus is up to date and then scan your computer with it specifically the C:/Windows/System32 folder because this is the location where the NTOSKRNL.exe file is located.

Option 1 – Put your computer in a Clean Boot State

The first thing you have to do is to put your computer in a Clean Boot State as this can help you in finding any incompatible programs that are causing the problem.

• 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.

Once you’ve found any incompatible programs, you need to uninstall them. Refer to the steps below to do so.

• 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.

Note: If you have downloaded the app from the Windows Store, you can simply right-click on it from the application list and then uninstall it.

Option 2 – Update or rollback drivers

If the first option didn’t work for you, then it’s time to either update or roll back the device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Open the Devices Manager from the Win X Menu.
• Then locate the device drivers and right-click on them to open the Properties.
• After that, switch to the Driver tab and click on the Uninstall Device button.
• Follow the screen option to completely uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically.

Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 3 – Try to run the DISM tool

If the first two options didn’t work, then running the Deployment Imaging and Servicing Management might. 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.

Option 4 – Try to stop the Runtime Broker process

The RuntimeBroker.exe or the Runtime Broker process is the one that monitors access to Windows APIs to make sure that the apps do not violate the core security of Windows. This process usually leaves a very small footprint. However, there are times when it consumes more resources than it’s supposed to and does not release memory after the work is done that results in a memory leak. As a result, it affects NTOSKRNL.exe which is why you have to stop the Runtime Broker process. To do so, refer to these steps:

• Tap the Ctrl + Shift + Esc to open the Task Manager.
• After opening Task Manager, go to the Processes tab and look for the Runtime Broker process.
• Once you find it, check if it is using more than 15% of your memory. If it is, then you most likely have an issue with an app installed on your computer.
• Select the Runtime Broker process and right-click on it and then click on the End Task option to end its process.

Option 5 – Try to run the Performance Troubleshooter

• Tap the Win + R keys to open the Run dialog box.
• Type “msdt.exe /id PerformanceDiagnostic” in the field and hit Enter to open the Performance troubleshooter.
• Then click on Next to get started. Wait until the process is completed.

Option 6 – Try using the Windows Performance Toolkit

You can also use the Windows Performance Toolkit in finding the root cause of the problem. Just refer to the following steps to use this toolkit.

• Search for “cmd” in the Cortana Search box and click on Command Prompt from the search results to open it.
• Next, type in the command given below or copy and paste it and then hit Enter:

xperf -on latency -stackwalk profile -buffersize 1024 -MaxFile 256 -FileMode Circular && timeout -1 && xperf -d cpuusage.etl

• After executing the command, wait for at least 60 seconds and then check the logs of the Windows Performance toolkit which is stored in a file named cpuusage.etl in the folder located at C:/Windows/System32. From there, you should see a list of all the causes of the System Resources being hogged.

Windows 11 has brought some new features and changed some of the existing ones. One of these changes includes quick switching of audio devices which will play audio. Audio switching can still be done under the taskbar, it is just a little different and one could say even hidden. Follow this quick guide and you will be switching from your headphones to speakers as an example in a matter of seconds.

1. Click on the speaker icon located in the far-right part of the taskbar.
2. After the quick settings menu appears click on the right arrow located right of the volume slider. If the arrow is not present, instead of click on the pencil icon, then on add, and finally select Volume from the list.
3. After clicking on the arrow icon, a list of all enabled audio devices on the system will replace the volume slider. Click on the desired audio device in order to make it active.
4. Click anywhere outside the quick setting menu to save changes and close it.

Note: in the Quick settings menu if you choose More Volume Settings it will bring you to System > Sound where you can access more sound input and output options.

ActiveX Controls are plugins you may constantly come across when working with Internet Explorer. An illustration of these kinds of control is the MICROSOFT IE Flash Player. They frequently result into significant problems for the Computer, yet they're vital for IE to operate correctly. You shouldn't ever overlook that after you install Active Controls in your Personal Computer, you effectively provide them with access to other areas of your PC. The ActiveX Controls not only tracks your search routines, but in addition puts malicious software, which might possibly be hazardous to your Computer.

Solution

Error Causes

ActiveX Controls make your Internet Explorer work as required and are usually great and beneficial to your own Computer. Yet, they can function as a source of problems because of the following factors.

• You should stop installing  ActiveX Controls from Un Trustworthy Resources

In the event they are installed by you from un trustworthy resources new threats are likely introduced by ActiveX Controls to your PC. One of the more regular types of ActiveX Controls worth necessary for installation is Flash Player. Yet, never be in a hurry to install these Controls from resources that you don't trust.

• Limit The Number of ActiveX Controls You Install on your PC

Prevent installing java/oracle ActiveX controls, because of its weak security measures which could make your Personal Computer and any additional information there in, open to attacks. Limit to the variety of ActiveX Controls that you install on your PC as these could increase the vulnerability canvas on your computer.

Further Information and Manual Repair

You can manually fix any malfunction that springs up from ActiveX Controls. Yet, more than mending the harm, produce the setting that ensures you never have troubles from them to start with. Just how do you do that?

a) Stop installing or downloading ActiveX Controls from Un Trustworthy Sources

This has been mentioned above, but it's worth repeating because it's the most common reason behind ActiveX Controls malfunctions. You might anticipate that for this kind of obvious reason for ActiveX Controls malfunctions, PC consumers would be extra cautious, however that is never true.

b) Limit ActiveX Controls Softwares

You can restrict ActiveX controls from running automatically on your PC. To limit them, head to Tools in Internet Explorer, and choose Internet Options. Proceed to the Security tab, and select Customs level Browse completely down before you get to the area designated "ActiveX". Subsequently, mark "Prompt" under every choice that you encounter. But don't mark the choice indicated "Run ActiveX Controls and Plug-Ins", together with, "Script ActiveX Controls Marked Safe for Scripting". By performing the measures emphasized above, you happen to be in substance stating that, you will not permit any installation of ActiveX Controls, without express authorization by you. In this manner, you have better control over different forms of ActiveX Controls you permit to be installed, therefore reducing potential threats to your PC.

If you encounter the CLOCK_WATCHDOG_TIMEOUT Blue Screen of Death error while using your Windows 10 computer then it is most likely caused by a specified processor which is not processing interrupts. This occurs when the processor is deadlocked or nonresponsive. Specifically, this kind of Stop error occurs when the processor is having a hard time with the cooperation of its threads and cores. The threads are the tasks performed by cores and some cores can have many threads at the same time. And this is where the problem begins – one thread is waiting for an adequate response from another thread or one kernel is waiting for a response from another kernel and those responses are not coming. In other words, when the processor is unable to continue the processing of tasks since its resources are occupied and are interdependent to get free, such a state is called Deadlock. The CLOCK WATCHDOG TIMEOUT bug check has a value of 0x00000101 which means that an expected clock interrupt on a secondary processor, in a multiprocessor system, was not received within the allocated interval. To troubleshoot the problem, you can check out the possible fixes provided below but before you proceed, make sure that you boot your computer into Safe Mode with Networking only.

Option 1 – Undo or disable overclocking if you have overclocked your system

• Go to the Start Menu and open Settings.
• Next, select Update and Security and go to the Recover tab.
• From there, click on Restart now in Advanced startup. This will restart your computer.
• Once you’re in the Advanced startup, go to Troubleshoot and then select the Advanced Options.
• From there, select the UEFU Firmware Settings.
• Now click on Restart. Once your computer has restarted, it will automatically open BIOS.
• From the BIOS, go to the Advanced tab and navigate to Performance and then look for Overclocking.
• Once you’ve found Overclocking, make sure that it is disabled. If it’s not, then disable it and then save the changes made by tapping the F10 key.
• Start your computer normally and check if the CLOCK_WATCHDOG_TIMEOUT 0x00000101 error is now fixed.

Option 2 – Try running the Memory Diagnostic Tool

The Memory Diagnostic tool in windows can help resolve the CLOCK_WATCHDOG_TIMEOUT 0x00000101 Blue Screen error by checking and automatically fixing any memory-based issues. To run it, refer to these steps:

• Tap the Win + R keys to open Run and type mdsched.exe and hit Enter to open the Windows Memory Diagnostic Tool.
• After that, it will give two options such as:
  • Restart now and check for problems (Recommended)
  • Check for problems the next time I start my computer
• Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.

Option 3 – Try to rollback, update or disable drivers

The next thing you can do to fix the CLOCK_WATCHDOG_TIMEOUT 0x00000101 Stop error is to roll back, or update, or disable device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Open the Devices Manager from the Win X Menu.
• Then locate the device drivers and right-click on them to open the Properties.
• After that, switch to the Driver tab and click on the Uninstall Device button.
• Follow the screen option to completely uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically.

Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 4 – Try running the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like CLOCK_WATCHDOG_TIMEOUT 0x00000101. 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 5 – Try to disconnect or disable 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 CLOCK_WATCHDOG_TIMEOUT Blue Screen error.

Option 6 – Troubleshoot the BSOD error in Clean Boot State

You can also troubleshoot the Blue Screen error in a Clean Boot state. There are times when third-party applications cause BSOD errors. Putting your computer in this state can help you identify which program is the culprit and thus isolates the problem. In a Clean Boot state, your computer will start using only the pre-selected minimal set of drivers and startup programs. Note that you have to disable and enable one process at a time.

• 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 to 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.

Option 7 – Try to update the BIOS

Updating the BIOS can help you fix the CLOCK_WATCHDOG_TIMEOUT BSOD error but as you know, BIOS is a sensitive part of a computer. Even though it is a software component, the functioning of the hardware depends on it largely. Thus, you must be careful when modifying something in the BIOS. So if you don’t know much about it, it’s best if you skip on this option and try the other ones instead. However, if you are well-versed in navigating the BIOS, then follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “msinfo32” in the field and press Enter to open System Information.
• From there, you should find a search field on the bottom where you have to search for the BIOS version and then press Enter.
• After that, you should see the developer and version of the BIOS installed on your PC.
• Go to your manufacturer’s website and then download the latest version of BIOS on your computer.
• If you are using a laptop, make sure that you keep it plugged in until you have updated the BIOS.
• Now double click on the downloaded file and install the new BIOS version on your computer.
• Now restart your computer to apply the changes made.

A runtime error is commonly an error that's created after the PC is operating software and encounters a problem of some form. For instance, a runtime error like run-time error code 7 reveals an "out of memory" dilemma.

Solution

Error Cause

Run-time errors are normally brought on by clashes with TSR (Terminate and Stay Resident) applications or additional operating applications, software problems, storage problems, or pc viruses.

Troubleshooting a Run-time Error

First, enter the run-time error signal into a search engine to see what info you will get about the precise runtime issue you are receiving. Next, end - job all running applications and TSRs to make sure these aren't the origin of the issue. You can certainly do so by obtaining the job manager by striking Control Alt Delete.

In case your issue is regularly occurring with a unique program, go to that system programmer's site and obtain any upgrades and patches. If unavailable, try uninstalling the application involved and reinstalling it.

In the event the issue is occurring with the os, you may consider reinstalling it although it is a huge commitment. A much better idea would be to try a fix for both Windows XP or Windows 2,000. It is possible to fix and scan files by typing : sfc / scannow, heading to the Begin switch, Run, and then pushing enter. Make certain to put an area between sfc and the reduce.

You might have an equipment or storage dilemma if these measures have not resolved your run-time errors. If that is the situation, contact the support of the application under consideration for potential support accompanied by the pc or motherboard manufacturer.

Many run-time problems can be solved by upgrading the application that's creating the problem. This is only because the programmer's frequently releasing patches and improvements for their applications as insects are found and repaired.

Storage problems may frequently be fixed by rebooting the pc. Consider a reboot a short-term repair. Rebooting clears the memory but in case your COMPUTER does not have adequate memory for your applications you're operating, or sufficient hard-drive space you'll immediately run out of memory again. Something less than this sum may cause memory issues since the computer's swap file isn't in a position to expand in dimension as required.

To assess the quantity of free area, available My Computer and right-click on the HDD, generally the D: drive. Select Attributes in the menu and see the disc's ability. Perform the disk clean-up function by following prompts and pressing the Disk Clean-up button, if the room is reduced.

You may be getting run-time errors, in case your storage chip is really failing. Eliminating and changing the awful memory chip will solve the difficulty. If you're encountering other runtime-related errors, like an install runtime issue, try cleaning away the portions of the registry with some software solution. 

What is 0x3D55? As you know, Windows 10 is loaded with various Universal Windows Platform or UWP apps such as the Microsoft News, Weather, Calculator, Windows Mail, and many other applications that are based on the modern UWP platform of Microsoft that was introduced in Windows 10. Each one of these apps has a shared piece of code in the kernel for them to be able to get executed across any device that runs the Windows 10 OS which includes laptops, PCs, 2-in-1 devices, mobile phones, mixed reality headsets, and many more. However, there are times when the runtime information for these apps ends up getting corrupted which causes them not to function as expected and throws errors like the error 0x3D55. This kind of error can be pinned down when the UWP app malfunctions and you can also find an error message in the Event Log that reads, “0x3D55: Package family <App name with ID> runtime information is corrupted”. So if you encounter this error, read on for this post will walk you through fixing it. There are three suggestions you need to check out to fix this error – first, you can try to reset the Microsoft Store cache, second, you can try to re-register or reinstall the problematic app and lastly, run the Windows Store App troubleshooter.

Option 1 – Try to reset the Microsoft Store cache

Just like browsers, Microsoft Store also caches as you view apps and games so it is most likely that the cache is no longer valid and must be removed. To do so, follow the steps below.

• Right-click on the start button and click on Command Prompt (administrator).
• Next, type in the command, “wsreset.exe” and tap Enter. Once you do, the command will clear the cache for the Windows Store app.
• Now restart your PC and afterward, try opening Microsoft Store again and then try to install your app or update your computer again.

Option 2 – Run the Microsoft Store Apps troubleshooter

The Microsoft Store Apps Troubleshooter will help you in fixing the error 0x3D55. This is a great built-in tool from Microsoft that helps users fix any app installation issues. So this is worth a try to solve the problem. This built-in tool also helps you fix the Windows 10 Store if it isn’t working. To use the Windows Store Troubleshooter, follow the steps below.

1. Tap Win + I keys again to open the Windows Settings panel.
2. Go to Update & Security and then go to Troubleshoot.
3. On your right-hand side, scroll down to find the Windows Store Apps and then click on the Run the troubleshooter option and see if it fixes the problem.

Option 3 – Try to re-register the UWP app via PowerShell

• First, type “command prompt” in the Start Search and right-click on Command Prompt and then select the “Run as administrator” option.
• Next, navigate to this location in the command line utility: C:/Users/<Insert Username>/AppData/Local/Packages
• After that, execute the “DIR” command to view the list of all the directories in the given location.
• Once the list appears, look for the ID of the problematic app and take note of it.
• Now tap the Win + X key combination or right-click on the Start button and click on the Windows PowerShell (Admin) option.
• If a User Account Control or UAC prompt appears, just click on Yes to proceed and open the Windows PowerShell window.
• Next, type in or copy-paste the following command to re-register the Microsoft Store app and tap Enter:

PowerShell -ExecutionPolicy Unrestricted -Command "& {$manifest = (Get-AppxPackage Microsoft.<YOUR APP ID HERE>).InstallLocation + 'AppxManifest.xml' ; Add-AppxPackage -DisableDevelopmentMode -Register $manifest}"

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

When Windows is installed on a clean hard drive it usually finds most of the needed drivers for our computer to run, but if we by any chance have any old unsupported hardware or some exotic one chance are very high that Windows will not be able to locate and install drivers for it. And sometimes we do not even have drivers from where to download them, let's say for example you have purchased a second-hand laptop with Windows on it, you wish to create a clean and fresh copy of new Windows installation but you do not have drivers, and let us say the model is not supported so you can not download them. In this case, this shown method will help you a ton and save you a lot of time and frustration. So, in order to back all of your drivers from your Windows follow this simple guide step by step. Note please that this method will backup drivers themselves, you will not backup installation packages of drivers or similar stuff, only drivers installed in Windows itself.

Backing up the drivers

First thing first, create a folder where you want your drivers to be backed up somewhere in your HD and give it any name. Second, press ⊞ WINDOWS + X to open the secret Windows menu. From the menu choose Command Prompt (administrator) When the command prompt is active type the next command in it: DISM /online /export-driver /destination:C:\DriverBackup where: C:\DriverBackup is the folder and the hard drive where you want to store your backed-up drivers. Press ENTER That's it, you have now successfully backed-up all of your installed Windows drivers. Now, save all of your drivers on USB and reinstall Windows.

In order to now return backed drivers do the following:

Press again ⊞ WINDOWS + X to open the secret Windows menu. but this time choose Device manager From decide, manager right-click on any device Windows has not been able to install appropriate driver and choose update driver

• Click on the Browse my computer for driver software option.
• Click the Browse button.
• Select the folder with the driver backup.
• Check the Include subfolders option.
• Click the Next button.
• Click the Close button.

The microphone has become from exclusive niche hardware to everyday requirements. In today's world when we live in a pandemic most of the work has shifted from office to home where people need working computers with microphones, working microphones. So what do we do when the microphone stops working? Keep reading on to find out and hopefully, we will fix this as fast as possible.

Check Microphone Privacy Settings

In 2019, Microsoft introduced new privacy features to Windows that give you more granular control over which apps are accessing your microphone. The side effect of this is that certain apps may be blocked from using your microphone without you even knowing. To find out if this is the issue, go to Settings > Privacy > Microphone. Click Change and make sure the slider is set to On. This will broadly mean that the mic is now enabled on your PC. Next, make sure the slider under Allow apps to access your microphone is set to On, then look through the list of Microsoft Store apps to make sure the apps you want to use are selected. You’re likely to be using many apps, not from the Microsoft Store, so to make sure these are enabled, scroll down even further and set the Allow desktop apps … slider to On.

Check Microphone Driver

The outdated or corrupted driver could be the issue for the microphone not working in Windows 10. To check the driver status, follow these steps:

1. In your Start menu search for Device Manager
2. In the device manager window search for sound and expand it.
3. Once expanded, you should see your audio drivers. Note that the names of these will vary depending on the manufacturer.
4. On Audio, right-click, and select properties. On the General tab, check to see if the device is working properly.
5. If it is not working properly, click on the driver tab and select the update option.
6. Repeat for the other audio drivers.
7. Restart the computer.

Check the Sounds setting

1. In the taskbar, right-click on the speaker icon at the far-right corner and select the sound option.
2. On the Recording tab, click on the microphone and select the Properties option.
3. Select the levels tabs and increase the volume for both microphone and microphone boost.
4. Go to the Enhancement tab of the same pop-up and make sure that the immediate mode checkbox is checked.
5. Click Ok and restart the computer.

The sound troubleshooter

1. Right-click on the sound icon at the far-right corner of the taskbar and select troubleshoot sound problems.
2. The computer will detect any fault that exists with your audio and recommend fixes for you. You just need to read through the prompts and click the options that you think will work for you.

Try microphone on another computer

If previous steps have not produced results, try the microphone on another computer, if it is not working there then it is a hardware malfunction

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.

What is DISM Error 1726? Every time you encounter some issues in your Windows 10 computer, especially when it comes to corrupted system files, you can always use the SFC scan and if the SFC can isn’t able to resolve the issue, there is also the DISM tool you can use which usually resolve the vast majority of system file corruption sufficiently. However, there are times when even the DISM commands experience issues as well. Such is the case with the 1726 error: “The remote procedure call failed”.

Some users reported that this DISM problem happens right before the process is supposed to end. According to experts, this error in DISM occurs due to any of the following reasons:

1. A third-party program might have interrupted the DISM operation and is the one that triggered the 1726 error: “The remote procedure call failed”.
2. The error could also pop up when there is a pending corruption repair. This usually happens when you tried to run a DISM command previously that was terminated manually or was halted because of some malfunction.
3. Lastly, the error could also occur because the process that’s responsible for the procedure is disabled or was prevented from running.

Whichever the case is, here are some suggestions that might help you in resolving the 1726 error: “The remote procedure call failed”.

Option 1 – Try updating your PC to the latest Windows build available

Since the problem is specific to certain builds in Windows 10, you need to make sure that your computer is updated before you try other troubleshooting steps. Thus, follow the steps below to update your Windows 10 PC.

• Tap the Win + R keys to open the Run dialog box.
• Then type “ms-settings:windowsupdate” in the field and hit Enter to open the Windows Update screen.
• After that, click on Check for Updates and then follow the next on-screen instructions to apply the latest Windows update.
• Once the update has been installed, restart your PC and run the DISM command again and see if the problem is fixed.

Option 2 – Try to change the Startup Type of the Remote Procedure Call service

As stated early on, the error might also be caused by a disabled Remote Procedure Call service or RPC or that it might be prevented from running for some reason. In case you don’t know, RPC is the service control manager for both COM and DCOM servers and it’s responsible for performing object variation requests, exporting resolution as well as distributing collection for the servers. And so if the server is disabled, all programs that are using COM and DCOM including the DISM commands, will not function correctly. Thus, you need to make sure that the RPC service is scheduled to enable itself on every system boot. To do so, here’s what you have to do:

• Tap the Win + R keys to open the Run dialog box.
• Type “services.msc” in the field and hit Enter to open Services.
• From there, scroll down until you see the Remote Procedure Call (RPC) service and then right-click on it and select Properties.
• Then go to the General tab and change the drop-down menu next to Startup type to Automatic.
• After that, click the Apply button and then OK to apply the changes made.
• Restart your PC and run the DISM command once again at the next startup.

Option 3 – Try to modify the RpcSs registry key value

If the option didn’t work, you can also try enabling the RPC service using the Registry Editor. Before you proceed, make sure to create a System Restore point first and then follow the steps below afterward.

• Tap the Win + R keys to open the Run dialog box.
• Type “Regedit” in the field and hit Enter or click OK to open the Registry Editor. And if a User Account Control prompt appears, just click on Yes.
• After that, navigate to this registry key: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services RpcSs
• After selecting the aforementioned registry key, go to the right pane and double-click on the Start value.
• Next, change the Value data of start to 2 and click OK to save the changes made.
• Exit the Registry Editor and restart your PC and check if the 1726 error in DISM has already been resolved or not.

Option 4 – Try to disable the Windows Search service temporarily

Some users also recommended disabling the Windows Search service for the meantime as it could be the one that’s interrupting the DISM process.

• Tap the Win + R keys to open the Run dialog box.
• In the field, type “services.msc” to open the Services window again and hit Enter to open it.
• Next, scroll down over the services list and double-click on the Windows Update service.
• Afterward, go to Windows Search properties and click the General tab and then click the Stop button to stop the service from running temporarily.
• Now try running the DISM commands again and see if the problem’s fixed or not.
• Restart the Windows Search service and then restart your PC as well.