How to fix error 0x80041003 on Windows 10, 8, 7

Milan Stanojevic avatar. By: Milan Stanojevic
8 minute read

Home » How to fix error 0x80041003 on Windows 10, 8, 7

Windows 10 is a solid operating system, but it’s not error-free. Speaking of Windows errors, users reported error 0x80041003 in Event Viewer. This can be an annoying error, and in this article we’re going to show you how to fix it.

How to fix error 0x80041003 on Windows 10, 8 and 7?

Solution 1 –Disable User Account Control

User Account Control is a security feature in Windows that prevents users from changing settings that require administrative privileges. Even though this feature can be useful, many users tend to disable it because it can become rather annoying over time. Despite being annoying, this feature can sometimes interfere with Windows and cause this and other errors to appear. To prevent this error from appearing, you need to disable User Account Control. To do that, follow these steps:

  1. Press Windows Key + S and enter user account. Choose User Account Control from the menu. Alternatively, you can just open the Start Menu and search for user control.
  2. User Account Control Settings window will appear. Move the slider all the way down to Never notify and click OK to save changes.

After you disable User Account Control, the problem should be completely resolved. Disabling this option might slightly reduce your security, but you shouldn’t worry about it too much.

Solution 2 – Create a vbs script and run it

This solution was originally provided by Microsoft for Windows 7, but it might also work for Windows 8 and 10. To fix this problem, you need to create a vbs script and run it. This is an advanced procedure, but you can do it by following these steps:

  1. Open Notepad.
  2. Now paste the following code:
    • strComputer = “.”Set objWMIService = GetObject(“winmgmts:” _
    • & “{impersonationLevel=impersonate}!\\” _
    • & strComputer & “\root\subscription”)
    • Set obj1 = objWMIService.ExecQuery(“select * from __eventfilter where name=’BVTFilter’ and query=’SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA “”Win32_Processor”” AND TargetInstance.LoadPercentage > 99′”)
    • For Each obj1elem in obj1
    • set obj2set = obj1elem.Associators_(“__FilterToConsumerBinding”)
    • set obj3set = obj1elem.References_(“__FilterToConsumerBinding”)
    • For each obj2 in obj2set
    • WScript.echo “Deleting the object”
    • WScript.echo obj2.GetObjectText_
    • obj2.Delete_
    • next
    • For each obj3 in obj3set
    • WScript.echo “Deleting the object”
    • WScript.echo obj3.GetObjectText_
    • obj3.Delete_
    • next
    • WScript.echo “Deleting the object”
    • WScript.echo obj1elem.GetObjectText_
    • obj1elem.Delete_
    • Next
  3. Now choose File > Save as.
  4. Set Save as type to All Files and enter myscript.vbs as File name. Choose your desktop as a save location and click the Save button.
  5. After doing that, close Notepad.

Now that you have your script ready, you need to run it using Command Prompt. To do that, follow these steps:

  1. Press Windows Key + X to open Win + X menu and choose Command Prompt (Admin) from the menu. If Command Prompt isn’t available, choose PowerShell (Admin) instead.
  2. When Command Prompt starts enter cd %userprofile%\Desktop and press Enter to run it.
  3. Now enter cscript myscript.vbs and press Enter to run it.

After running this script, the problem should disappear completely. Keep in mind that older warnings related to this error will still remain in Event Viewer, so you’ll have to delete them manually.

Solution 3 – Create a bat file and run it

Sometimes in order to fix this problem you need to run several commands. The easiest way to do that is to use a bat script. Creating a bat script is relatively simple, and you can do it by following these steps:

  1. Open Notepad.
  2. Now paste the following code:
    • @echo on
    • cd /d c:\temp
    • if not exist %windir%\system32\wbem goto TryInstall
    • cd /d %windir%\system32\wbem
    • net stop winmgmt
    • winmgmt /kill
    • if exist Rep_bak rd Rep_bak /s /q
    • rename Repository Rep_bak
    • for %%i in (*.dll) do RegSvr32 -s %%i
    • for %%i in (*.exe) do call :FixSrv %%i
    • for %%i in (*.mof,*.mfl) do Mofcomp %%i
    • net start winmgmt
    • goto End
    • :FixSrv
    • if /I (%1) == (wbemcntl.exe) goto SkipSrv
    • if /I (%1) == (wbemtest.exe) goto SkipSrv
    • if /I (%1) == (mofcomp.exe) goto SkipSrv
    • %1 /Regserver
    • :SkipSrv
    • goto End
    • :TryInstall
    • if not exist wmicore.exe goto End
    • wmicore /s
    • net start winmgmt
    • :End
  3. Now go to File > Save as.
  4. Set Save as type to All Files and enter script.bat as the File name. Set your Desktop as a save location and click the Save button.
  5. Close Notepad. Locate script.bat on the Desktop, right click it and choose Run as administrator from the menu.

After running the script, the problem should be completely resolved. According to users, this issue appears because the current user doesn’t have the necessary privileges to perform the operation in WMI. To fix the problem, you might have to change your security permissions. Changing the permissions could be potentially dangerous, so keep that in mind. To change the permissions, follow these steps:

  1. Press Windows Key + X and choose Computer Management from the menu.
  2. When Computer Management opens, in the left pane navigate to Services and Applications > WMI Control. Right click WMI Control and choose Properties from the menu.
  3. When Properties window appears, navigate to Security tab. Now select Root from the menu and click on Security.
  4. If you’re a member of Administrators group, check if Administrators have full control option checked. If you aren’t a member, you might have to add your account and give it full control. To do that, click on Add button.
  5. In Enter the object names to select field enter your user name and click on Check Names. If everything is in order click on OK.
  6. Now select your user name from the list and check all options in the Allow column. Click on Apply and OK to save changes.

After you change your security permissions, you just have to restart your PC in order to apply the changes.

Solution 4 – Delete the Repository folder

According to users, this issue is caused by a problem with WMI and it’s likely that your WBEM repository is damaged. To fix the issue, you need to stop Windows Management Instrumentation service by following these steps:

  1. Press Windows Key + R and enter services.msc. Press Enter or click OK.
  2. When Services window opens, locate Windows Management Instrumentation service and double click it.
  3. Once the Properties window opens, click on Stop button and click on Apply and OK. If you get a warning message, just click on Yes or OK.
  4. After you stop the service, close the Services window.

Now you need to delete the Repository directory. To do that, follow these steps:

  1. Go to C:\Windows\System32\WBEM directory.
  2. Locate Repository directory and copy it to a safe location on your PC. If anything goes wrong, you can copy this directory back to the original location and fix the problem.
  3. Now delete the Repository directory from WBEM folder.
  4. After doing that, close all applications and shut down your PC.
  5. Turn on your PC again. After the PC turns on, leave it idle for about 10-15 minutes. During this time your PC will recreate Repository directory.
  6. Turn off and back on your PC and the problem should be resolved.

Few users reported that this solution worked for them, so feel free to try it out.

Solution 5 – Check your RAM

Sometimes you can get a BSOD error followed by error code 0x80041003. This type of error might be related to your RAM, so it’s advised to check it. The simplest way to do that is to leave only one memory module connected and test it for errors with Memtest86+. Keep in mind that you need to scan your RAM for a couple of hours in order to test it thoroughly.

If you have more than one RAM modules, you’ll have to repeat this solution with every RAM module individually. This solution requires you to remove your RAM from the PC case, so if your PC is under warranty or if you don’t know how to do it properly, you might want to skip this solution. This solution only applies if you’re getting a Blue Screen of Death followed by 0x80041003 error code. If your PC doesn’t restart due to this error, you should skip this solution.

Solution 6 – Check your BIOS

If you’re experiencing high CPU usage due to this error, you might want to check your BIOS. According to users, the cause for this problem is the Turbo Mode option in your BIOS. To fix the issue, you need to navigate to BIOS and turn Turbo Mode off. For detailed instructions on how to do that, we advise you to check your motherboard manual.

Solution 7 – Reset Windows 10

Few users claim they fixed this problem by resetting Windows 10. Resetting Windows will remove all your files from your system drive, therefore we advise you to back up important files beforehand. To perform a Windows 10 reset, you might need an installation media, so be sure to create one with Media Creation Tool. After doing that, you can reset your PC by following these steps:

  1. In Windows, open the Start Menu, click the Power button, press and hold the Shift key and click on Restart.
  2. Choose Troubleshoot > Reset this PC > Remove everything.
  3. To proceed to the next step, you might be asked to insert Windows 10 installation media, so be sure to have it ready.
  4. Select your version of Windows. Now click on Only the drive where Windows is installed > Just remove my files.
  5. You’ll see a list of changes that reset will perform. If you’re ready to start click the Reset button.
  6. Follow the instructions on the screen to complete the reset.

After the reset is completed you’ll have a fresh installation of Windows 10. Now you just have to move your files from the backup and install the applications again. This is a drastic solution, so you should use it only if other solutions can’t fix the problem.

Error code 0x80041003 usually isn’t dangerous, but if your PC starts restarting or freezing due to this error, feel free to try any of our solutions.

READ ALSO:

Discussions

Next up

KB4471331 fixes major Adobe Flash Player zero-day vulnerability

Giles Ensor avatar. By: Giles Ensor
2 minute read

Microsoft has released an update for Adobe Flash Player, that was described in Adobe’s Security Bulletin which was released December 7th, 2018. The update fixes […]

Continue Reading

You’ll be able to install Chrome extensions on Edge in the future

Giles Ensor avatar. By: Giles Ensor
2 minute read

It looks like we are now going to be enjoying constant updates, Reddit discussion comments, and rumours and gossip about the new Chromium-based Microsoft Edge […]

Continue Reading

5 USB Christmas decorations for a cozy and merry desk

Madeleine Dean By: Madeleine Dean
Less than a 1 minute read

Having a nice Christmas tree in your house helps you to bring the winter holiday mood to your home. You can also bring this mood […]

Continue Reading