Moving mouse pointer via the keypad in W11

Although the Google Chrome browser is one of the most used browsers, a lot of things could still go wrong when browsing the web using it. One of the errors you might encounter is the “ NETWORK_FAILED ” error. This kind of error in Chrome indicates that Chrome wasn’t able to send your request through the network connection. It could be that your computer has trouble connecting to a stable internet connection or there is some plugin in your Chrome browser that is causing the issue. The worst-case would be malware. But worry not for this post will guide you on what you can do when you encounter the NETWORK_FAILED error in Google Chrome. Make sure to follow each one of the options given below and see which one of them worked best for you.

Option 1 – Disable or remove any unwanted extensions in Chrome

As you know, browser extensions help in enhancing the browsing experience but there are also times when it does exactly the opposite, and such is the case with the NETWORK_FAILED error in Chrome. It could be that one of the extensions in your browser is the one that’s causing the trouble. To disable or remove these unwanted extensions, here’s what you have to do:

• Launch Google Chrome, press Alt + F, move to More tools, and click Extensions.
• Look for Search.tb.ask.com or any other unwanted add-ons, click the Recycle Bin button, and choose Remove.
• Restart Google Chrome, then tap Alt + F, and select Settings.
• Navigate to the On Startup section at the bottom.
• Select “Open a specific page or set of pages”.
• Click the More actions button next to the hijacker and click Remove.

Option 2 – Run the Malware Scanner and Cleanup tool in Chrome

If removing or disabling the unwanted extension didn’t help in fixing the error, you can try using the built-in malware scanner and cleanup tool in Google Chrome. These tools help you get rid of any unwanted pop-ups, ads, unusual Startup pages, toolbars, and even malware.

Option 2 – Run the Malware Scanner and Cleanup tool in Chrome

• Launch Google Chrome and 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 the option and click on the “Restore settings to their original defaults” option to reset Google Chrome.
• Now restart Google Chrome.

Option 3 – Try to disable the Proxy

If you are using a proxy, you might want to consider disabling it as it could have something to do with the NETWORK_FAILED error.

• Tap the Win + R keys to open the Run dialog box.
• Then type “cpl” and hit Enter or click OK to open the Internet Properties.
• After that, go to the Connections tab where you should see the LAN settings. Click on it.
• Next, uncheck the “Use a Proxy Server for your LAN” and ensure that the “Automatically detect settings” option is checked as well.
• Then click Ok and then Apply to save the changes made.
• Restart your PC.

Option 4 – Flush DNS and reset TCP/IP

• Click the Start button and type in “command prompt” in the field.
• From the search results that appear, right click on Command Prompt and select the “Run as administrator” option.
• After opening Command Prompt, you have to type each one of the commands listed below. Just make sure that after you type each command, you hit Enter
  • ipconfig /release
  • ipconfig /all
  • ipconfig /flushdns
  • ipconfig /renew
  • netsh int ip set dns
  • netsh winsock reset

After you key in the commands listed above, the DNS cache will be flushed and the Winsock, as well as the TCP/IP, will reset.

• Now restart your computer and open Google Chrome then try opening the website you were trying to open earlier.

Option 5 – Delete the WLAN Profiles

Deleting the WLAN Profiles might be a good idea if you are not able to connect to the internet on your computer and if you’re using Wi-Fi. It could be that the networks that were connected previously have gone rogue which is why it is not connecting properly. And so deleting the WLAN profiles would be for the best. That should do it.

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.

One of the most common hardware issues with any PC usually has something to do with the hard drive so if your hard drive experiences some errors, you could end up losing a lot of important information that’s stored in your computer. This is why Windows provided users with the CHKDSK utility which helps in looking for bad sectors on the drive. However, there are times when the CHKDSK utility could also face issues like the following error:

“Failed to transfer logged messages to the log event with status 50.”

According to security experts, this error is most likely due to the hard drive or RAM being in a “Read-only” state. It could also be due to some physical issues with the hard drive. On the other hand, it could be that the system is prevented from creating logs by some drive, service, or malware. To fix this error, you have to check if the hard disk is writable. You could also try to run the CHKDSK utility in Safe Mode or you could also check the physical status of your hard disk or external drive.

Option 1 – Check if the hard disk is writable

Although the CHKDSK utility checks for bad sectors in the hard drive, it also has to create logs of the result. And as states in the error message, the CHKDSK utility is not able to log the logged messages. This kind of error occurs when the log can’t be written to an installation disk. You can find the log in this location, “C:WindowsSystem32LogfilesSrtSrtTrail.txt”. Now you have to check if the drive writable by following these steps:

• Log in as administrator and right-click on the system drive.
• Select Properties and then go to the Security tab. Here, check if you are allowed to modify the drive. If not, click on Edit (as an administrator).
• Now edit the permissions for the SYSTEM and Administrators group. Note that these are the only default settings for these two groups or usernames.
• Then click on the Apply button save the changes made and exit.

Option 2 – Run the CHKDSK utility in Safe Mode

You could also try to run the CHKDSK utility in Safe Mode as this might solve the error.

• Boot your computer in Safe Mode.
• Next, open Command Prompt with admin privileges.
• Then type and enter this command to execute it: chkdsk c: /f /r
• Wait until the process is completed and boot your computer normally and then run the CHKDSK utility again and check if the “Failed to transfer logged messages to the log event with status 50” error is now fixed.

Option 3 – Try to check the hard disk or external drive physically

If the first two options didn’t work, you might want to check the physical status of your hard disk or external drive as the problem could root from there. You can try to tighten the wires that connect the hard disk to the motherboard. However, if it doesn’t help, you should seek out assistance from a hardware technician.

There are cases when you encounter some issues while updating your Windows 10 computer. One of these issues is the error 0x80240034. This particular error is a Windows Update Error that appears on the Windows Update pane every time an update fails to install. When this happens, your Windows Update will only get stuck at 1% and nothing happens afterward and eventually fails. If you click on the View Installed Update History, you will see the error code 0x80240034 for the failed updates. You will see this error each time you try to update your Windows PC. Take note that this issue doesn’t only happen to a specific version of the Windows Update but on various different Windows builds based on many users. What’s more, is that some users are also seeing a different error code when their Windows Update fails but they still end up seeing the error code 0x80240034 when they check the Windows Update history. At the time of writing, it isn’t determined yet what really causes this error but it’s most likely due to some corrupted files in the computer which is why the most common solution you can try is resetting the Windows Update cache. On the other hand, other users also resolved the issue by using the ISO and selecting the “Do not keep previous settings” option during the Windows Update so it might be something to do with transferring the previous settings through the update client. For clear instructions in fixing this issue, refer to the two options provided below.

Option 1 – Try to clear the Windows Update Cache/Distribution Folder

As mentioned earlier, a lot of users tried clearing the Windows Update cache 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.

• Step 1: Tap the Windows key once.
• Step 2: Next, type in “command prompt” in the Windows Start Search, and from the search results that appear, right-click on Command Prompt and select the “Run as administrator” option from the context menu.
• Step 3: After opening Command Prompt, type in “net start wuauserv” and hit Enter.
• Step 4: Then type in “rmdir %windir%SoftwareDistribution /S /Q” and hit Enter.
• Step 5: Now type in “net start wuauserv” and hit Enter. Once it’s done, try updating your Windows PC again, it should now work just fine.

Option 2 – Update Windows via ISO file

If option 1 didn’t work for you, you can try this second option of updating your Windows 10 computer using an ISO file which means that you will have to create a Windows 10 bootable media and use it to install the latest Windows 10 version. The most user reported that this option works and the reason why it does have something to do with the Windows Update client since the Windows Updates downloaded from the regular Windows Update client seems to create issues such as the error 0x80240034. However, issues like this one don’t occur when the very same Windows Updates are downloaded and installed via an ISO file. Take note that when using a Windows ISO file, you will be asked to choose what you want to do with the previous settings and apps. A lot of users opted for the “Not to keep the old Windows settings” option which has resolved the issue. So if you want to keep the previous settings then you must try to update Windows first while keeping the old settings. However, if it doesn’t work, you have to try installing the latest version of Windows without keeping the previous settings.

• Step 1: Click this link and then click the Download Tool Now button.
• Step 2: Next, click the “Use the tool to create installation media (USB flash drive, DVD, or ISO file)…” option and follow the next given instructions on the screen.
• Step 3: Now select the ISO file option in step 5.
• Step 4: After that, you should now have an ISO file.
• Step 5: Next, go to the location where you’ve downloaded the ISO file.
• Step 6: Then right-click on the Windows 10 ISO file and select the Open with an option and then select File Explorer.
• Step 7: Now click on “setup.exe” and follow the next instructions that appear on the screen. When asked, you have to select either: Nothing (clean install) or Keep personal files only option. Take note that you must not select the “Keep personal files, apps, and Windows settings since it doesn’t really work.

Isn’t it annoying when you get an error message pop up stating ‘Cannot find propsys.dll” or “propsys.dll not found” when you start your computer or open a particular program? The propsys.dll file is crucial to the Windows operating system. This file is located in one of the following locations: "C:\Windows", C:\Program Files, C:\WINDOWS\system32, or C:\Program Files\Common Files". And the propsys.dll error indicates that the propsys digital library file is damaged and corrupt. The propsys.dll error may lead to a very unstable operating system. It may also hamper your ability to access many programs on your computer, lead to program and system crash and slow down the system’s performance. Therefore, to avoid these system threats, it is advisable to fix the error immediately.

Solution

Error Causes

The common causes of propsys.dll file error are:

• Registry problem
• The propsys.dll file is damaged due to a virus or spyware
• Improper software removal
• Hardware Failure

The propsys.dll error message is displayed in either of the following forms:

• Propsys.dll not found
• Cannot find [Path]propsys.dll
• This application failed to start because propsys.dll was not found. Reinstalling the application may fix this problem
• The propsys.dll file is missing

Further Information and Manual Repair

There are many ways to fix the propsys.dll error. However, for optimum results from the fix, you must first identify the cause of the error and then choose the solution accordingly.

• Recommended Solution for Registry Issue

If you use your system daily the resulting wasted/invalid/junk entries may dilate the registries. This can result in registry malfunctioning which may result in a propsys.dll error on your screen. When this happens, it is advisable to use a registry cleaner to fix the problem. Registry cleaner helps clean up the junk entries and repairing the corrupted registries. For this, you will first have to download a registry cleaner repair tool. Download and install the software on your computer. After downloading it, click the start scan button to run. This helps scan and diagnose system errors on your computer in seconds. Once the scanning is complete, click on the fix button to repair the registry problem.

• Recommended Solution for File Damage and Corruption

Use the ‘System Restore’ option to restore corrupt and damaged files.  The ‘System Restore’ function will help you get a fresh copy back and simultaneously help fix the error. Here’s how to use and access the ‘System Restore’ function on your computer: Simply go to the start menu and in the search box type restore. Once you type, it will show you the system restore option. Now select ‘choose a different restore point’. After this, you will be presented with a list of restore points. Choose a point that you believe happened before the propsys.dll error. Confirm your selection and restart. Another alternative solution for file damage is to run a virus scan of your entire system; the damage could be related to a virus or malware infection.

• Recommended Solution for Hardware Failure

If a propsys.dll error occurs due to hardware failure, then it is advisable to update the drivers for hardware devices that you think are related to propsys.dll. For example, if you receive the propsys.dll error when you play a 3D video game, then try updating the driver for your video card.

To make the Windows 10 operating system a lot more user-friendly, Microsoft introduced the Tablet Mode for Windows 10 devices, especially the 2-in-1 devices like Surface Pro and Surface Book. Despite the Tablet Mode’s efficiency, it also encounters some errors from time to time. One of the issues users reported about tablet mode is that they can’t turn off or exit tablet mode. If you are one of these users, read on as this post will guide you in what you can do to fix the issue. To fix the problem with Tablet Mode, there are several suggestions you can check out. You can try to check the full-screen setting, or perform a full shutdown or perform two buttons to restart the Surface devices. You could also disable Tablet Mode via Registry Editor or perform System Restore or change the settings in the System tab or the Action Center.

Option 1 – Try to check the full-screen setting

• Tap the Win + I keys to open the Windows Settings app.
• Then navigate to this path, Personalization > Start.
• Next, scroll down to toggle off the “Use Start Full Screen” option.
• After that, restart your computer and see if the problem is fixed.

Option 2 – Perform a full shutdown

• Open Command Prompt with admin privileges first.
• Next, execute this command to perform a full shutdown: shutdown /s /f /t 0
• The command you entered will shut down your computer and once it’s turned off, wait for a couple of minutes and then turn it back on.

Option 3 – Try to perform a two-button restart on your Surface device

• Tap and hold the power button for about 30 seconds.
• Then release them after 30 seconds.
• After that, tap and hold the volume up + the power button for 20 seconds. This will cause the display to flash a few times but you have to keep those buttons pressed until your Surface device is turned off.
• Wait for a couple of minutes and your Surface will turn back on. This should resolve the problem.

Option 4 – Try to disable the Tablet Mode via Registry Editor

• In the Start Search, type “registry editor” and right-click on the Registry Editor from the results, and then select the Run as administrator option. This will open the Registry Editor with admin privileges.
• Next, navigate to this registry key: ComputerHKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionImmersiveShell
• From there, look for the DWORD named “SignInMode” and double click on it.
• Set its value to “1” and its base as hexadecimal.
• After that, click on OK to save the changes made. This will make sure that you are signed in to the desktop mode when you log into your account.
• Now look for the DWORD named “TabletMode” and double click on it and set its value data to “0” and it's base as hexadecimal.
• Click on OK to save the changes made and then restart your computer.

Option 5 – Run System Restore

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

Option 6 – Try changing the settings in the System tab or the Action Center

• Go to Settings and navigate to System > Tablet Mode.
• After that, scroll down to set the “Use desktop mode” from the drop-down menu under the “When I sign in” section.
• Now restart your computer and see if the issue is fixed.

Error Code 0xc004f034 – What is it?

Error code 0xc004f034 occurs when Windows 10 users fail to activate their operating system. This activation error code affects not only Windows 10 but those using other versions of the Windows operating system including Windows 8.1. Users experiencing this problem will notice the following common symptoms which occur:

• Inability to activate Windows 10 operating system
• Message box with error code 0xc004f034

Solution

Error Causes

Error code 0xc004f034 usually results from issues related to activation servers. In such cases when servers are busy, users will not be able to complete the activation process which would result in access to their Windows 10 edition of choice. The error code may also result from issues related to your product key. For this reason, be sure to use the correct product key when you attempt to activate Windows 10.

Further Information and Manual Repair

The completion of manual repair methods can be an effective way to correct issues like error codes in Windows 10. To begin, however, ensure you follow the instructions as given as making even a slight mistake will result in unfavorable results. If, for whatever reason, you have trouble completing the steps suggested below, feel free to contact a Windows repair technician. This type of IT professional is usually equipped with knowledge and expertise to access your particular situation. Otherwise, see the manual repair methods listed below and complete at least one method to fix error code 0xc004f034.

Method One: Ensure You Enter a Valid Product Key

If there is a problem with your product key, you will need to ensure you fix it before you can resolve error code 0xc004f034. Follow the instructions below after ensuring you have a valid product key.

• Step one: Click the Start button then select Settings
• Step two: Select Update & security then Activation
• Step three: Click the Change product key
• Step four: Type in your valid product key with its 25 characters in the correct order

Your system will activate Windows 10 if the issue was related to the use of an invalid product key. However, attempt manual method two if error code 0xc004f034 reappears and you are unable to complete the activation process.

Method Two: Reattempt Windows 10 Activation Until Process Completes

In many cases, error code 0xc004f034 occurs simply due to a busy server. This was the case in 2015 in particular when Windows users first received access to editions of Windows 10 like Windows 10 Pro. To complete this process, you will need to follow the instructions below, repeating the last step until the activation occurs.

• Step one: Click the Start button then select Settings
• Step two: After selecting Settings, click Update & Security
• Step three: Select Windows Update then the Check for updates tab
• Step four: Click Activate Windows 10 update

If this method is successful, you will finally be able to update your system to the Windows 10 edition of your choice. This process may take just a few minutes – and several attempts – before you resolve the issue. Remember to be patient. However, contact a Windows repair technician to evaluate your system if the issue persists for more than a few days.

Method Three: Use an Automated Tool

If you wish to always have at your disposal a utility tool to fix these Windows 8 and other related issues when they do arise, download and install a powerful automated tool.

Error Code 0xC1900101, 0x30018? - What is it?

Users, when upgrading to Windows 10 from Windows 7 or Windows 8/8.1, or when upgrading to a new version, build, service pack, or major update of Windows 10, can encounter error code 0xC1900101, 0x30018. Windows 10 installation fails and stops or hangs. During the installation process, it will reach a certain maximum limit (normally at 6% or 32%) then reverts back to the previous version of the operating system and displays the following message:

We couldn’t install Windows 10. We’ve set your PC back to the way it was right before you started installing Windows 10.

0xC1900101 – 0x30018 The installation failed in the FIRST_BOOT phase with the error during the SYSPREP operation.

Solution

Error Causes

In attempting to fix Error Code 0xC1900101-0x30018, it is vital to know what causes this issue. The most probable causes of this error are:

• Incompatible hardware or driver
• Incompatible security programs or antivirus or incompatible utility software
• A device driver possibly stopped responding to setup.exe while on the installation process.

In some cases, you might be opened to other error messages when attempting to update to Windows 10, including error code 8007002c.

Further Information and Manual Repair

In fixing issues related to error codes, it is best to employ manual repair methods. Using these methods helps users pinpoint the root causes of the issue and apply solutions permanently to fix the issues. While most manual repair methods can be done by every Windows user, even those without technical abilities, there are certain cases where help from a Windows professional is needed. If you’re not up to facing risks in implementing manual methods yourself, consider getting help from a professional Windows technician or you can use a powerful automated tool. In fixing Error Code 0xC1900101-0x30018, you can repeat the same steps used for 0xc000021a (Method One) or you can try doing the following:

• Disable or uninstall your Antivirus program before proceeding to upgrade the system
• Ensure that the machine name is simple (having at least 8 characters) with no special characters like hyphens or dashes.
• Restart the device a few times then try again.
• Disable General USB Devices such as the Smart Card Reader.
• If you use an SCSI hard disk, ensure that you have available drivers you can use for your storage such as a thumb drive and make sure that it is connected. During the Windows 10 setup, select the Custom Advanced Option and use the Load Driver command to be able to load the suitable driver for the SCSI drive. If this fails, try switching to an IDE-based hard disk.
• You can now perform a clean boot. Restart your device then try again.
• If you are using the .ISO file for upgrading the system, you need to disconnect from the Internet first before proceeding to the setup. If you are connected to Wi-Fi or by Ethernet (LAN), make sure to disable both connections then you can proceed to set up again.
• If you’re performing the update through Windows Update, once the download reaches 100%, disconnect from the Internet, and then proceed with the installation.

NOTE: If this fails, if possible, you can try using the .ISO file in upgrading.

• Switch to a local account if the device is connected to a domain.
• Disconnect all external devices attached to the computer such as gaming controllers, printers, or USB keys.

If you’re using Windows Update in installing Windows 10, you can implement the following:

1. Open the Command Prompt window by pressing Windows Key + X. Select Command Prompt (Admin) from the menu.
2. Stop the BITS, Cryptographic, MSI Installer, and the Windows Update Services. In order to do this, Type or Copy and Paste the following commands one at a time:

NOTE: Don’t forget to hit Enter after every command.

net stop wuauserv

net stop cryptSvc

net stop bits

net stop msiserver

3. Rename the Catroot2 and SoftwareDistribution In order to do this, Type or Copy and Paste the following commands one at a time:

NOTE: Don’t forget to hit Enter after every command.

                        ren

C:WindowsSoftwareDistribution SoftwareDistribution.old

                          ren

C:WindowsSystem32catroot2 Catroot2.old

4. Restart the BITS, Cryptographic, MSI Installer, and the Windows Update Services. In order to do this, Type or Copy and Paste the following commands one at a time:

NOTE: Don’t forget to hit Enter after every command.

net start wuauserv

net start cryptSvc

net start bits

net start msiserver

5. Type Exit in the Command Prompt then close the Command Prompt window then restart the computer.

Can’t seem to put up with the long and technical manual repair process? You can still fix this error by downloading and installing a powerful automated tool that will surely get the job done in a jiffy!

There is a lot of high resource utilization by any process that slows down a Windows operating system and one of the services that could cause such a thing is the utcsvc.exe process. This particular process at times can cause high CPU and disk usage. So if you are currently facing this problem, read on as this post will guide you on how you can resolve the problem. UTC which stands for Universal Telemetry Client is a software that runs a service named Diagnostic Tracking Service or DiagTrak. This service is used by Microsoft to collect customer feedback, analyze customer’s problems, and push resolution via updates in order to make the Windows 10 operating system better. This service is an executable file that could be translated to Service Host and even though the process does not usually cause problems, there are actually times when it does especially if it results in high resource utilization. In such cases, you might want to consider disabling it to fix its high CPU and disk usage.

According to Microsoft:

“We collect information about you, your devices, applications and networks, and your use of those devices, applications, and networks. Examples of data we collect include your name, email address, preferences, and interests; browsing, search and file history; phone call and SMS data; device configuration and sensor data; and application usage.”

There are several ways you can disable the utcsvc.exe process. You can disable it using the Service Manager, Registry Editor, and Group Policy Editor. For more details, refer to the instructions laid out below.

Option 1 – Disable the Connected User Experience & Telemetry Service via Service Manager

Note that this option is for standalone systems, so if you’re not using one, refer to the next given options below.

• Tap the Win + R keys to open the Run dialog box.
• Then type “services.msc” in the field and tap Enter or click OK to open the Services Manager.
• From the given list of services, look for the Connected User Experience service. Once you found it, click on it and you’ll see its description which states:

“The Connected User Experiences and Telemetry service enables features that support in-application and connected user experiences. Additionally, this service manages the event-driven collection and transmission of diagnostic and usage information (used to improve the experience and quality of the Windows Platform) when the diagnostics and usage privacy option settings are enabled under Feedback and Diagnostics.”

• Next, right-click on it and select Properties.
• Now, change its Startup Type to Disabled and click on the Apply and OK buttons to save the changes made.

Option 2 – Disable the Connected User Experience & Telemetry Service via Registry Editor

• Tap the Win + R keys to launch the Run utility and type “Regedit” in the field and click OK to open the Registry Editor.
• Next, navigate to this registry path: HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsDataCollection
• After that, right-click on the folder named “DataCollection” and select New > DWORD (32-bit) Value.
• Now name the new value “AllowTelemetry” and make sure that its Value data is “0” and then click on OK to save the changes made.
• Restart your computer.

Option 3 – Disable the Connected User Experience & Telemetry Service via Group Policy Editor

If you have to disable the service related to the Universal Telemetry Client for company-managed systems, then you can do that using the Group Policy Editor.

• Tap the Win + R keys to open the Run utility and type “gpedit.msc” in the field and hit Enter to open the Group Policy Editor.
• Next, navigate to this path: Computer Configuration > Administrative Templates > Windows Components> Data Collection and Preview Build
• After that, double-click on Data Collection and Preview Build to open its settings.
• From there, look for the “Allow Telemetry” item and double click on it to open its Properties.
• Next, set the radio button to Disabled and then click on the Apply button to save the changes made.
• Restart your computer.

Option 4 – Run the Hardware and Devices Troubleshooter or the Performance Troubleshooter

Hardware and Devices Troubleshooter:

• The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
• After opening Settings, look for the Update and Security option and select it.
• From there, go to the Troubleshoot option located on the left-hand side of the list.
• Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
• After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.

Performance Troubleshooter:

• Tap the Win + R keys to open the Run dialog box.
• Type “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.

DLL files have certain functions that help the programs in the computer run properly. One of these DLL files is the Msvcr120.dll_clr0400.dll. This particular DLL file is responsible for the extraction of the required resources during the installation of a program and is used when the program is launched or when games are launched in the C++ language. However, a number of users recently reported that they’ve encountered an error that says, “Msvcr120.dll_clr0400.dll is missing” when they tried to install an application or when they tried opening an application. This kind of error could be due to several factors. It is possible that the DLL file is corrupted or there are some programs that interfere with the DLL file. On the other hand, it is also possible that it has been infected by a virus. To resolve this error, here are some potential fixes you need to check out:

Option 1 – Run System File Checker scan

The first thing you can do to fix the error is to try running the System File Checker or SFC scan. System File Checker is a command utility built into your computer that helps restore corrupted files and missing files. Refer to the following steps to run it:

• Hit the Win + R keys 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.

• Reboot your computer.

Option 2 – Troubleshoot the missing Msvcr120.dll_clr0400.dll error in a Clean Boot State

You can also troubleshoot the isDone.dll error in a Clean Boot state. It could be that there are some third-party applications in your computer that are preventing the application from getting installed and to isolate this possibility, you need to boot your computer in a Clean Boot State and then try installing the program again. 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 configure Windows to use the usual startup, just simply undo the changes.)
• After you’ve set your computer into a Clean Boot State, make sure that you’re signed in as administrator and then try to install the application again.

Option 3 – Try to re-register the problematic DLL file

You can also try to re-register the DLL to resolve the problem. The Regsvr32 tool is a command-line utility that can be used to register and unregister OLE controls like DLL and ActiveX (OCX) controls in the Windows operating system. Follow the steps below to use it.

• Open Command Prompt as admin from the WinX menu.
• Next, type the following commands in the elevated Command Prompt and hit Enter to execute the command. This will re-register the affected DLL file using the Windows operating system tool, regsvr32.exe.
  • exe /[DLL file]
  • exe [DLL file]

Note: Replace “[DLL file]” with the name of the DLL file that was pointed out in the error.

• After you execute the given commands, you should see a message saying, “DllRegisterServer in vbscript.dll succeeded” if the Regsvr32 tool was able to run successfully. After that, try to install the program again and see if it now works.

Option 4 – Try to replace the DLL file with a trusted source

• First, you need to get the new DLL file from another computer with preferably the same file version number.
• After that, you need to boot your PC into Safe Mode and navigate to the paths listed below and then replace the file using a USB drive or other external storage devices.
  • x86: This PC > C:WindowsSystem32
  • x64: This PC > C:WindowsSysWOW64
• Next, type “cmd” in the Cortana search box and right-click on Command Prompt, and select “Run as administrator” to open it with administrator privileges.
• Now type the “regsvr32 ntdll.dll” command and hit Enter.
• Restart your PC and check if the error is now fixed.

Option 5 – Scan your computer using Windows Defender

The DLL file might also be infected with malware or virus and to eliminate it which could explain why you’re getting the “Msvcr120.dll_clr0400.dll is missing” error. Thus, you have to scan your computer using security programs like Windows Defender.

• Tap the Win + I keys to open Update & Security.
• Then click on the Windows Security option and open Windows Defender Security Center.
• Next, click on Virus & threat protection > Run a new advanced scan.
• Now make sure that Full Scan is selected from the menu and then click the Scan Now button to get started.