Apple M2 Chip review

PrintNightmare vulnerability has been a struggling issue for Microsoft in the past weeks, each time it seems to be addressed and fixed something new popped up and it still had issues. Microsoft finally addressed the issue but with a price. The default behavior of Point and Print is changed. From this fix onward, the Point and Print driver installation and update behavior will require administrator privileges, which should prevent the exploit to the Windows Print Spooler that could be used by malicious individuals to gain administrative privileges in Windows. The drawback of this fix from Microsoft is that non-elevated users may have difficulty adding or updating printers. Microsoft feels that the security risks caused by PrintNightmare are worth the tradeoff, though. If you really want to let non-elevated users add printers, you can follow the instructions in this Microsoft Support article to disable this mitigation with a registry key. However, doing so will expose you to this known vulnerability and isn’t recommend.

Error C00D11B1- What is it?

Error C00D11B1 is a type of Windows Media Player error code. The error C00D11B1 hampers your ability to play videos, MP3 files and songs on Windows Media Player. The error is displayed in the following format:

Error C00D11B1:’Windows Media Player can’t play the file.’

Solution

Error Causes

The cause of error C00D11B1 message pop up on your computer can be narrowed down to one particular reason virtually because this error may be triggered due to several reasons, these include:

• Corrupt DRM license
• Enabled codec of the video in Windows Media Player codecs section
• Registry Corruption

The good news is that this error is not fatal and does not pose serious PC threats like runtime and BSoD error codes. However, it is still advisable to resolve to ensure you are able to watch movies and listen to songs on Windows Media Player without any difficulty.

Further Information and Manual Repair

Here are some of the best and effective do it yourself methods to resolve the error C00D11B1 on your PC right away:

Method 1- Disable the codec of the video option in the Codecs Section

If you are unable to play downloaded movie files on your PC on Windows Media Player, then try this method to resolve the issue. Simply open Windows Media Player, Go to Tools, Options, DVD and then click Advanced Tab. Here find the codecs section, scroll down to the codec of the video you are trying to play and see if it says enabled. If it does, then disable it and then select a decorder for the codec. Now try running the video again on your Windows Media Player. This will hopefully resolve the issue. Nonetheless if the error still persists, try method 2.

Method 2- Delete DRM Licenses & cache and Download it Again

Sometimes the error C00D11B1 can also be trigged by corrupt DRM licenses & cache. To resolve the issue, simply delete all files. First open Windows Explorer (Windows key + E) and then go to C:ProgramDataMicrosoftWindowsDRM. Now delete all files in this folder. Once deleted, Let Windows Media Player download your license again. After downloading the DRM license again, run the Windows Media Player to see if it works.

Method 3- Disable Firewall Temporarily

Firewall can also be responsible for blocking the Windows Media Player streaming. Firewalls often block important ports that are required in order to run some programs. If this is the cause, then simply disable Firewall temporarily to resolve the issue.

Method 4- Repair the Registry

Registry is that part of your computer that saves all the activities performed on the PC and all the files too including both important and unimportant files like cookies, junk files and bad registry entries. If these unimportant and obsolete files are not removed frequently, the registry gets corrupt and damaged. And due to this reason you may experience error code C00D11B1 on your system. To resolve this issue, simply repair the damaged registry by downloading Restoro. This is a powerful PC Fixer integrated with a registry cleaner. The registry cleaner removes all unnecessary files, cleans and repairs the registry in seconds. Click here to download Restoro and fix error C00D11B1 on your PC right now!

If you encounter an error saying, “error accessing the registry” when you try to merge a registry key on your Windows 10 computer, you’re not alone as some users also experienced the same problem. According to these users, they encounter the error after they’ve re-installed their Windows version and tried to open a .reg file. Based on the reports, this error could occur if the registry file does not have administrative privileges. Meaning to say, the program does not have the necessary permission to merge the .reg file. This is common with fresh installs as well as reinstalls. Moreover, this kind of issue could also occur due to system file corruption. Whichever the case may be, here are some troubleshooting tips you can check out to resolve the error.

Option 1 – Try to import the .reg file with admin privileges

As pointed out, the error may be due to a lack of admin privileges. It could be that the Registry Editor does not have admin privileges to merge the registry file. This is common with new Windows installations especially since the Registry Editor hasn’t been opened before. So you need to import the .reg file again and this time, with admin privileges.

• Tap the Win + R keys to open the Run dialog box.
• Then type “Regedit” in the field and tap the Ctrl + Shift + Enter keys to open the Registry Editor with admin privileges.
• A User Account Control or UAC prompt will appear where you have to click Yes to proceed.
• After opening the Registry Editor, go to File > Import using the ribbon bar at the top.
• Next, use the import menu to go to the location of the file you were trying to merge. Once you’ve found it, click Open to merge it with your current registry. This should fix the problem. If not, refer to the next options below.

Option 2 – Try performing a System Restore

Running System Restore can also help you fix the error when accessing the Registry. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

• 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.
• Once the next startup is complete, you have to merge or import the file again and see if the error is now fixed or not.

Option 3 – Try to perform repair install by creating a Windows 10 installation media

• Click this link and then click the Download Tool Now button.
• 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.
• Now select the ISO file option in step 5.
• After that, you should now have an ISO file.
• Next, go to the location where you’ve downloaded the ISO file.
• Then right-click on the Windows 10 ISO file and select the Open with option and then select File Explorer.
• 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.

Option 4 – Try running the System File Checker Scan

As mentioned, the error when accessing the Registry might be caused by file corruption. And that’s where the SFC scan comes in. The SFC or System File Checker scan could detect and automatically repair damaged system files. SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files. To run the SFC command, follow the steps given below.

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

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

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

• Now restart your computer.

In case you don’t know, Windows 10 supports installation and use of a number of removable devices which includes plug and plays mouse, keyboard, and other USB-based devices. But this could actually pose a threat to the integrity of a computer system and thus, some organizations pose a restriction in using these kinds of devices. the restriction on these devices is also useful especially if you keep on leaving your computer idle and someone tries to mess it up by plugging in a removable device. In such situations, the restriction will defend the user against data theft. Thus, in this post, you will be guided on how you can prevent the installation of removable devices on your Windows 10 computer. There are two options that can help you in preventing the installation of any removable devices on your computer – you can either try to use the Registry Editor or use the Group Policy Editor instead. Follow whichever option you want to use the instructions given below but before you start, don’t forget to create a System Restore Point first.

Option 1 – Prevent installation of Removable Devices via Registry Editor

• Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and hit Enter to open the Registry Editor.
• Next, navigate to this registry path: HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsDeviceInstallRestrictions
• From there, look for a DWORD named “DenyRemovableDevices” and set its value to “0”. On the other hand, if you can’t find this DWORD, just simply create it and set its value to 0.
• Once done, exit the Registry Editor and reboot your PC to apply the changes made.

Option 2 – Prevent installation of Removable Devices via Group Policy Editor

Keep in mind that the Group Policy Editor is not available in the Home Edition of the Windows operating systems. Thus, if you are using one, just stick to the first option, otherwise, proceed to the following steps.

• Tap the Win + R keys to open the Run utility and type “gpedit.msc” and click OK or tap Enter to open the Group Policy Editor.
• After that, go to this policy setting: Computer ConfigurationAdministrative TemplatesSystemDevice InstallationDevice Installation Restrictions
• Next, look for the “Prevent installation of removable devices” entry and once you find it, set it as “Enabled”. From this window, you should see the following description of this policy setting:

“This policy setting allows you to prevent Windows from installing removable devices. A device is considered removable when the driver for the device to which it is connected indicates that the device is removable. For example, a Universal Serial Bus (USB) device is reported to be removable by the drivers for the USB hub to which the device is connected. This policy setting takes precedence over any other policy setting that allows Windows to install a device. If you enable this policy setting, Windows is prevented from installing removable devices and existing removable devices cannot have their drivers updated. If you enable this policy setting on a remote desktop server, the policy setting affects redirection of removable devices from a remote desktop client to the remote desktop server. If you disable or do not configure this policy setting, Windows can install and update device drivers for removable devices as allowed or prevented by other policy settings.”

• Then click the Apply and OK buttons to save the changes made.
• Now restart your computer to save the changes made. This should prevent the installation of any removable devices in your Windows 10 computer.

If you are trying to run Windows Upgrade on your Windows 10 computer but suddenly interrupted by the error 0x800F081E – 0x20003, worry not for this post will guide you on how you can fix this Windows Upgrade error. This particular Windows Upgrade error is a Windows status code for CBS_E_NOT_APPLICABLE which indicates that some of the update requirements are missing or the files that are installed are already of a higher version compared to the ones that are still pending. In most cases, this error occurs when you try to upgrade to earlier versions of the Windows 10 N edition to a later version. Here’s the full content of the error message:

“0x800f081E-0x20003, The installation failed in the SECOND_BOOT phase with an error during BOOT operation”

In case you don’t know, Microsoft distributes special “N” editions of Windows in Europe and the “KN” editions in Korea. These editions are the same as the standard editions of Windows except that they do not have the Windows Media Player as well as the multimedia playback features. Thus, when the Windows Upgrade fails with the error code and error message and it doesn’t provide much information as to why the update couldn’t be installed, there is something you can do about it to fix the error. Since Windows uses generic error codes and so if you see the error code 0x800f081e, you have to check the error log first. For more details, follow the instructions laid out below. Step_1: You need to navigate to C:$WINDOWS.~BTSourcesPanther and from there look for the text file named “setuperr.log” and open it with a text viewer/editor program like Notepad. Step_2: After opening the setuperr.log file, you should see content that’s similar to this:

C:WINDOWSSoftwareDistributionDownload80b2677d6e15a2a206625bb25a7124feamd64_Microsoft-Windows-MediaPlayer-Package~~AMD64~~10.0.17134.1. Error: 0x800F081E 2019-09-10 20:26:57, Error SP Operation failed: Add [1] package C:WINDOWSSoftwareDistributionDownload80b2677d6e15a2a206625bb25a7124feamd64_Microsoft-Windows-MediaPlayer-Package~~AMD64~~10.0.17134.1. Error: 0x800F081E[gle=0x000000b7]

Note: From the content above, it is clear that the Windows Upgrade failed due to complete due to the Windows Media Player. It could be that the log file may contain other error messages and other error codes and if you see the error code 0x800f081e from the list, then you need to uninstall the Media Feature Pack. Step_3: You have to uninstall the Media Feature Pack.

• Tap the Win + R keys to launch the Run dialog box and type “optionalfeatures.exe” in the field and hit Enter to open the Windows Features wizard.
• Next, you need to wait until the list of Windows Features populates and then click on the + sign to collapse the folder of the Media Features.
• After that, uncheck the “Windows Media Player” option from the Media Features folder.
• Now click on the Yes and OK buttons to save the changes made and then close the Windows Features dialog box.
• Restart your computer and boot, try to run the Windows Upgrade process again, and check if the error is fixed or not.

Note: If the installation has been successfully completed, you have to go back to the Windows Features and enable the Windows Media Player again. And if you are using the Windows 10 N Edition, then you can just download and install the latest version of the Media Feature Pack for your Windows 10 N edition. On the other hand, running the built-in Windows Update troubleshooter could also help you resolve any Windows Update-related problems, including the error 0x800F081E – 0x20003. 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.

Error Code0x80070426 - What is it?

When Windows evolved into Windows 10, the program known as Windows Security Essentials is no longer. It is now the program known as Windows Defender. When a computer is upgraded from a previous version of Windows up to Windows 10, the Windows Defender takes over and will replace the Security Essentials. In a small percentage of Windows 10 upgrades, something will go wrong and the new program will fail to replace Security Essentials. The result will be that the operating system has both of the programs installed. In this case, Windows Defender will not offer any protection and Security Essentials will not be able to defend either. This error code will also present itself when the Windows Mail App in Windows 10 fail to retrieve and sync email from the user's account.

Common symptoms include:

• There will be an error message that says: “An error has occurred in the program initialization. If this problem does continue, contact your System Admin. Error code 0x80070426.”
• The computer will be left completely vulnerable to spyware and viruses.
• The Windows Mail App will not be able to retrieve mail and will not sync with the PC user's mail.
• The user can be doing anything on their computer and the error code will show up unprompted.
• The computer will lock up, become slow, crash, or even freeze when dealing with error code 0x80070426.
• The programs from an older version of Windows do not replace the newer version from Windows 10.

Solution

Error Causes

Error code 0x80070426 will present itself when a PC user has upgraded their OS from a previous version of Windows to the new Windows 10 version. When this happens, a small portion of users will experience the disconnect between older versions of specific programs, namely the virus protection. When the previous version of the program under a different name is not completely removed and the new virus protection program is installed, the programs will cancel each other out and collectively offer no protection.

This error code may also be found when Windows 10 tries to sync the user's email with the Windows Mail App.

Further Information and Manual Repair

There are a few methods to repair this problem. It should be noted that should anyone feel that the instructions are too complicated, they should contact a Windows repair technician to ensure that the error is fixed properly.

Method One: Uninstall Microsoft Essentials

Hold down the Windows Key and press R. Type in taskmgr into the run dialogue. You should locate the Windows Defender Service (this may show up as Windefend). Right-click on it and then choose Stop.

This will stop the program, but the program will start back up automatically when the computer restarts. While this program is stopped, uninstall Essentials.

To do this: go to Control Panel, Programs, and Features, Uninstall a Program. Alternately, you may hold down the Windows Key and press R, type in appwiz.cpl, click OK, and then locate Microsoft Essentials. Uninstall it, and then restart your computer.

After this is done, go to Settings, Update, and Security. Choose Windows Defender and ensure that Real-time protection is on. Refer back to the Task Manager, Services. Make sure that Defender service is on and running.

Method Two: If the problem occurs in the Windows Mail App

When error code 0x80070426 presents itself in the form of an error with the Mail app, it may be necessary to run an SFC scan.

Right-click on the Start menu or Windows icon, and select Command prompt. The command prompt may be navigated by using shortcut keys Win and X and then select it.

Run the command prompt and then type in sfc /scannow and then press enter. The SFC scan will be run, and be careful not to abort the process before it has finished. This will scan for any files that are lost or corrupt on the PC.

If the scan has found any corrupt files, type in this code and then hit Enter: findstr /c:”[SR]” %windir%LogsCBSCBS.log >”%userprofile%Desktopsfcdetails.txt.

To skip the repair of corrupt or missing files, type in: Dism /Online /Cleanup-Image /RestoreHealth. The details of the scan can be found on the sfcdetails.txt file that will be on the desktop.

Method Three: Use An Automated Tool

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

It is a fact that Google Chrome is one of the world’s most used web browsers and it’s because this search giant is focused on following the standards of the web. Although this web browser has become quite bloated over the years, it still remains at the top of the list of browsers used most by users. If you are a user of Google Chrome for a long time now, you have most likely come across a couple of issues in the past while using this browser. In this post, we’ll help you fix one of the issues commonly encountered in Chrome which is the “No Data Received – ERR_EMPTY_RESPONSE” error. This kind of error message in Chrome pops up when you try to log into a website. It isn’t clear what’s the cause of this error but worries not, for there are several ways you can try to fix it.

Option 1 – Try checking if your network connection is working

The No Data Received – ERR_EMPTY_RESPONSE error is not usually related to a downed network. However, anything is possible so you need to check if your internet connection is working just fine or not as it might be the reason why you’re getting this error in Chrome.

Option 2 – Try resetting the network

There are instances when a network goes into haywire because of a bad DNS. Thus, a bad DNS might be the one that’s causing this headache so it’s time for you to reset the entire network to resolve the issue. To reset the network, here’s what you have to do:

• 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 3 – Try to clear the browsing data of Google Chrome

If your browsing data in Chrome hasn’t been cleared for some time now then that might be the reason why you’re suddenly getting the ERR_EMPTY_RESPONSE error when you browse the web. To fix this error, you need to clear your web browsing data. Refer to the following steps to do so.

• Tap the Ctrl + Shift + Delete buttons to go to the Clear browsing data section in Chrome.
• Next, set the time range to “All time” and tick all the boxes and then click on the Clear data button.
• After that, restart the Chrome browser and try to open the website you were trying to open earlier.

Option 4 – Reset Google Chrome

If none of the options given above worked, you can try resetting the Chrome browser. To do that, follow these steps:

• 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 an option and click on the “Restore settings to their original defaults” option to reset Google Chrome.
• Restart Chrome and check if you can now open the webpage or not.

Referenced Memory at - What is it?

0x Referenced Memory at 0x is an error code that occurs when the random memory addresses conflict. This error causes running programs or browsers to crash. Referenced memory at error code is considered as a service violation error. It is displayed as the following:

“The instruction at 0xf77041d24 referenced memory at 0×00000000. The memory could not be read.”

Solution

Error Causes

The ‘referenced memory at’ errors is either triggered by:

• Hardware failure
• Problems with the RAM and the registry

Hardware failure may result if the driver is not installed properly. The problems in the RAM indicate registry issues that occur due to data overload in the hard disk and poor PC maintenance. The registry saves all the information and activities you perform on your system on the hard disk. This includes the junk files, temporary files, invalid registry entries, and files of both installed and uninstalled programs.  These files accumulate and take over a lot of RAM space. Also, the referenced memory at error can be considered to be a form of memory leak where unknown third-party software can take up the memory space that has been reserved for a particular program. For example, if you have toolbars and add-ons installed in your browser, it can also lead to invalid registry storage in the registry. If you don’t clean the registry, these unnecessary files can overload your data and lead to hard disk/RAM damage and corruption triggering obscure error messages like referenced memory at error.

Further Information and Manual Repair

Referenced memory is a critical error; if not resolved it can lead to serious PC damages like a system failure. To avoid this, it is advisable to fix it right away. Here are a couple of ways to repair this issue on your system:

Cause: Hardware Failure

Solution: If the referenced memory at error is generated due to hardware failure then to resolve this error you must reinstall the driver that has caused the error to appear. Let’s say if the error pops up because of the printer driver, reinstall it. For re-installation of the driver, simply go to the control panel and click on the Device Manager option. Once you click it you will see a detailed page with a list of devices. Now click on the printer (the problematic driver in this situation) to reinstall the driver software. Double click on it to open the properties dialog box and then click the driver tab and update the driver. Once you have updated the driver, try using the printer. Check if it works. If it works and the referenced memory at the error code does not appear on the screen, this means the problem was with the hardware. However, if the error still pops up then this means the problem is deeper. It’s related to the registry.

Cause: Problems with the RAM and the registry

Solution: If the problem is with the RAM and the registry, then it is advisable to download Restoro. Restoro is a new, next-generation, and highly functional registry cleaner. It detects and removes all the registry issues, unnecessary and obsolete files saved in the hard disk taking up a lot of RAM space. It clears the RAM and cleans up the disk. Furthermore, it repairs the damaged files, fragmented disk, and the corrupt registry in seconds enabling you to resume the program that you were running before the error occurred. Restoro has a user-friendly interface and easy navigation. To run and operate this system you don’t need any kind of technical expertise. In just a few clicks you can resolve the critical referenced memory at error on your PC. It is compatible with all Windows versions Click here to download and install Restoro on your PC and fix the referenced memory error code now.

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.