If a Configuration Manager (SCCM) Management Point installation stops with mp_ccmConfig_Defaults.mof and error 0x80044015, inspect the generated MOF before rebuilding WMI or troubleshooting unrelated prerequisites. In the documented Configuration Manager 2103 case, a locale-generated decimal comma (0,04166667) had to be changed to a decimal period (0.04166667), after which the MP installation could retry. This is a version- and environment-specific workaround, not a proven universal fix for every current-branch release.
What the Management Point error looks like
The failure appears while the Management Point role registers WMI/MOF definitions. The useful entries are normally in MPSetup.log and MPMSI.log:
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
System Center 2012 R2 Configuration Manager: A Practical Handbook for Reporting | $55.00 | Buy on Amazon |
Product: ConfigMgr Management Point -- Error 25140.
Setup was unable to compile the file mp_ccmConfig_Defaults.mof
The error code is 80044015
CustomAction CcmRegisterWmiMofFile returned actual error code 1603Error 25140 identifies the ConfigMgr custom action that could not compile the named file. Error 1603 is the generic MSI/custom-action failure returned afterward. The more diagnostic value is 0x80044015, together with the exact MOF line that fails.
The log says the file could not be compiled. Describing this as a compression failure is inaccurate and can send troubleshooting in the wrong direction.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →What 0x80044015 means
In this context, 0x80044015 is a WMI MOF type-conversion or parsing error: a value could not be coerced to the data type expected by the MOF compiler. Microsoft Q&A examples associate the HRESULT with the message “The value specified could not be coerced into the appropriate type” (Microsoft Q&A).
That HRESULT does not by itself prove that the WMI repository is corrupt, nor does it always mean a decimal separator problem. Other malformed or incompatible literals can produce the same code.
Why a regional decimal separator can break the generated MOF
MOF numeric literals need syntax the compiler can parse consistently. In the reported incident, the generated value was:
CacheExpirationInterval = 0,04166667The comma was the server or execution-account decimal separator. The expected MOF representation was:
Free tools Windows power users keep installed
One-click scans. No signup required.
CacheExpirationInterval = 0.04166667The installation process may run under LocalSystem or another service context. Therefore, the interactive administrator’s Control Panel locale is not necessarily the locale that generated the file. Check the server’s system settings and the account context used by the installation action before assuming the user profile is responsible.
Confirm that this is the decimal-separator case
The strongest available report concerns Configuration Manager 2103, released globally in April 2021. A troubleshooting article published August 27, 2024, documents the symptom and workaround (HTMD case report). It does not establish that every later Configuration Manager build has the same defect.
- Open
MPSetup.logandMPMSI.logand capture the first compilation error, not only the final 1603 entry. - Confirm that the failing file is exactly
mp_ccmConfig_Defaults.mof. - Record the site version and build, Windows Server version, system locale, decimal separator, and whether the role is being installed, reinstalled, or repaired.
- During the failed installation window, inspect the generated file and search for
CacheExpirationIntervalor other numeric literals containing a comma. - Use the workaround only if the file contains a value that is demonstrably inconsistent with the compiler’s expected syntax.
Step-by-step workaround
The following sequence reflects the documented case. Paths are observed locations; verify them on your server because customized installations can use different directories.
- Start or restart the Management Point installation and wait until the compilation error appears. Do not dismiss the failure immediately if doing so removes the generated file.
- Open
C:WindowsCCMmp_ccmConfig_Defaults.mofwith an elevated editor. - Make a dated backup copy of the original before changing anything.
- Locate
CacheExpirationInterval. The reported copy placed it near line 108, but line numbers can differ. - Change only the malformed decimal literal:
CacheExpirationInterval = 0,04166667to:
CacheExpirationInterval = 0.04166667 - Preserve all classes, namespaces, qualifiers, encoding, and unrelated settings. Ensure the editor does not save the file as
.mof.txt. - Save or copy the corrected file into the reported ConfigMgr directory,
C:Program FilesSMS_CCM, if that is the path expected by your installation. - Allow Configuration Manager to retry, or restart the relevant installation process/server according to your change window.
Because the file is generated, a later retry can overwrite your edit. If the comma returns, investigate the locale or generation process rather than repeatedly editing a regenerated copy. Manual modification is an operational workaround, not a documented permanent Microsoft remediation.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsVerify that the Management Point is healthy
Use independent checks rather than relying on the installer dialog alone:
- Confirm the specific MOF compilation error no longer appears in
MPSetup.logandMPMSI.log. - In the Configuration Manager console, open Monitoring > System Status > Component Status and review
SMS_MP_CONTROL_MANAGER. - Review Management Point logs under
SMS_CCMLogsand confirm the role reports healthy. - Assign a test client to the MP and verify that it can locate the MP, retrieve policy, and communicate successfully.
Microsoft’s Management Point deployment guidance recommends monitoring the installation asynchronously, checking SMS_MP_CONTROL_MANAGER, reviewing MP logs, and testing client communication.
If changing the decimal separator does not work
The comma returns after a retry
The generated file is being recreated with the same locale-sensitive value. Recheck the system or LocalSystem execution context and document any regional-setting change before applying it. Changing the entire server locale can affect unrelated applications, so do not do it casually.
The file uses a period but compilation still fails
- Read the exact line and value named by the log; another numeric literal may be malformed.
- Check for unexpected characters, altered encoding, or an accidental extension such as
.mof.txt. - Verify that the installer is reading the copy you edited and that a retry has not replaced it.
- Confirm that installation media and client binaries match the site version.
The log changes to a different failure
Stop treating the issue as a decimal-separator problem. Investigate the new evidence, including IIS and Windows Authentication, .NET Framework, BITS, WMI/IIS registration, SQL connectivity, site-system installation-account permissions, certificates, HTTP/HTTPS or Enhanced HTTP configuration, DNS, firewall rules, and supported OS/Configuration Manager combinations. Microsoft’s example MP deployment lists IIS, .NET Framework, BITS, Windows Authentication, ISAPI extensions, IIS compatibility components, and WMI-related features among relevant prerequisites.
WMI appears broadly unhealthy
Do not rebuild the WMI repository solely because one generated MOF failed. First establish whether other providers, namespaces, or MOF files fail. Microsoft publishes a script for compiling registered MOF files (MOF compilation script), but labels the sample “AS IS” and outside standard Microsoft support. Treat it as an advanced diagnostic, not the first-line response to this isolated MP error.
Should you permanently change regional settings?
Only change the system or service-context decimal separator after confirming that it is the cause and assessing application impact. The reported case implicates LocalSystem’s regional setting, but the available documentation does not provide a universal, Microsoft-supported procedure for changing a service account’s locale. Prefer an applicable Configuration Manager update or hotfix when Microsoft documents one for your exact build. Record any locale change and its effect on other software.
Is this fixed in current Configuration Manager versions?
The documented incident is tied to Configuration Manager 2103; the available evidence does not prove that it remains a universal defect in 2026 current-branch releases, nor that it is limited exclusively to 2103. Check release notes and support guidance for your exact site build. If a supported current build generates a malformed MOF without an environmental explanation, preserve the logs and open a Microsoft support case.
When this workaround is not appropriate
- The failing file is not
mp_ccmConfig_Defaults.mof. - The log reports a missing namespace, provider-registration failure, access denied, invalid class, or another error before MOF registration.
- No suspicious decimal value exists in the generated file.
- The underlying problem is an unsupported OS/build combination, IIS, SQL, certificate, DNS, firewall, or permissions issue.
In those cases, editing a generated MOF can hide the real fault and delay recovery. Preserve the original logs and follow the new error’s diagnostic path.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
