System Configuration Checker WMI Error: Fixing SQL Server Setup

The System Configuration Checker WMI error means SQL Server setup could not talk to Windows Management Instrumentation, so it stopped before it installed anything. Your installer is fine. The repair happens on the Windows side, and it takes about ten minutes.

What you see on screen

Years ago I had my laptop formatted and put Windows Vista SP1 on it. Same night, I tried to install SQL Server 2005. Setup refused within seconds with this message.

The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine
Error:2147749896 (0x80041008)

I was tired, it was late, and I really wanted that install. I never learned exactly what had broken on that machine. A script from a friend fixed it, and I have wanted a readable version ever since. The steps below are that version.

Read the number first

The error shows the same code twice. One is decimal and one is hex. Windows tools quote the hex form, so that is the one to search for. This query converts both ways, so you can match whatever your own screen shows.

SELECT 2147749896 AS DecimalCode,
       CONVERT(bigint, 0x80041008) AS FromHex,
       RIGHT(CONVERT(varchar(16), CONVERT(varbinary(8), CONVERT(bigint, 2147749896)), 2), 8) AS AsHex;

The decimal 2147749896 and the hex 80041008 are the same number. Codes that start with 8004 belong to the WMI family, so the message is honest: the problem sits in WMI, not in SQL Server.

Check the service before you repair anything

Press the Windows key, type Services, and look for Windows Management Instrumentation. Its status should say Running. If it is stopped, start it and run setup again. That alone fixes some machines, and it costs nothing, so always look here first. You can also check from PowerShell, where the Status column should read Running.

Get-Service winmgmt

Repair the WMI repository in order

These are steps to follow, not results I measured on your machine. Go in order and stop as soon as setup passes.

1. Close SQL Server setup. Open Command Prompt with Run as administrator. Without admin rights the repair commands fail. When I ran the first command below from a normal prompt on Windows 11, it printed Access denied with code 0x80041003.
2. Ask Windows whether the repository is healthy. It reports that the repository is consistent or not.

winmgmt /verifyrepository

3. If it is not consistent, let Windows try to rebuild it from whatever it can still read.

winmgmt /salvagerepository

4. Still broken? Reset it. This returns the repository to its starting state, so settings added by other software may disappear. Use it last.

winmgmt /resetrepository

5. Restart Windows.
6. Prove that WMI answers before you touch setup. If this prints a caption and a version, WMI is talking again. If it prints an error, do not start setup yet.

Get-CimInstance Win32_OperatingSystem | Select-Object Caption, Version

7. Run SQL Server setup again.

Confirm the install and skip the mystery script

Once setup finishes, connect and run this. The first number tells you the major version. On SQL Server 2025 it is 17. The second is the full build, which differs from server to server.

SELECT SERVERPROPERTY('ProductMajorVersion') AS MajorVersion,
       SERVERPROPERTY('ProductVersion') AS FullVersion;

A friend once sent me a batch file that fixed my Vista machine. It worked, but I could not tell you what each line did. Neither could the pages where I found copies. I would not run an unreadable script as administrator on a server today. The steps above are built into Windows, and you can read every one before you press Enter.

Walk the steps in order, stop when setup passes, and get your evening back.

This error is not a SQL Server problem, it is a Windows one.

Published by Pinal Dave on SQLAuthority. More of my work at pinaldave.com.