NEW Microsoft Policy Platform fails to install as part of the MECM client install

[C-Bear]

First post here, but I reference the site often in my MECM troubleshooting travels.

I've hit a snag whereby Microsoft Policy Platform fails to install as part of the MECM client install on an older 2012 R2 server.

This particular 2012 R2 server was running fine, but with a wonky, out-dated MECM client. It worked to install monthly updates for the most part, but seemed to cause grief deploying applications.

Trying to be proactive and get it updated to the current version of the MECM client, I uninstalled the existing version using "ccmsetup /uninstall", and then followed that up by running "Ccmclean.exe".

I copied the current MECM client locally to the system and ran ccmsetup, which promptly failed. Here are the relevant errors in the ccmsetup.log:

File C:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi installation failed. Error text: ExitCode: 1603 Action: ErrorMessages:
InstallFromManifest failed 0x80070643 ccmsetup 2023-12-20 2:27:44 AM 516 (0x0204)

The MicrosoftPolicyPlatform log file had these errors:
-- LoadPolicyPlatformWmiProviders -- There was a failure in ParseProviderLists() (hr = 0x80730b07).
-- LoadPolicyPlatformWmiProviders -- Failed to unload WMI providers. (hr = 0x80730b07).
-- LoadPolicyPlatformWmiProviders -- A failure occurred in Lantern::Setup::CustomActions::LoadPolicyPlatformWmiProviders() -- file:C:\__w\1\s\src\lantern\build\setup\customActions\CustomActions.cpp, line:447, (hr = 0x80730b07)
CustomAction LoadPolicyPlatformWmiProviders_Rollback returned actual error code 1603 but will be translated to success due to continue marking

Referencing my notes from an older case I had opened with Microsoft when I had another system complaining about the Microsoft Policy Platform, I ran the Microsoft "MicrosoftProgram_Install_and_Uninstall.meta.diagcab" diagnostic tool, which was able to successfully uninstall Microsoft Policy Platform from the system. This had helped resolve the other issue, but failed in this instance.

After cleaning up Microsoft Policy Platform, the MECM client installer still complained, giving all the same errors again.

As an aside, the WMI repository on the system passed. I also searched for *.ipi files in the %systemroot%\installer directory, but found none. I have also tried to install Microsoft Policy Platform as a standalone using the MSI, but it also fails with the same errors.

I have yet to reboot the system after the uninstall, as it's a production system; that's not an option at this time.
I have also neither re-registered the DLLs nor the MOF files, as this is a drastic step on an old system.

Besides the reboot and the registrations, am I missing the obvious?

 

[staze]

First post here, but I reference the site often in my MECM troubleshooting travels.

I've hit a snag whereby Microsoft Policy Platform fails to install as part of the MECM client install on an older 2012 R2 server.

This particular 2012 R2 server was running fine, but with a wonky, out-dated MECM client. It worked to install monthly updates for the most part, but seemed to cause grief deploying applications.

Trying to be proactive and get it updated to the current version of the MECM client, I uninstalled the existing version using "ccmsetup /uninstall", and then followed that up by running "Ccmclean.exe".

I copied the current MECM client locally to the system and ran ccmsetup, which promptly failed. Here are the relevant errors in the ccmsetup.log:

File C:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi installation failed. Error text: ExitCode: 1603 Action: ErrorMessages:
InstallFromManifest failed 0x80070643 ccmsetup 2023-12-20 2:27:44 AM 516 (0x0204)

The MicrosoftPolicyPlatform log file had these errors:
-- LoadPolicyPlatformWmiProviders -- There was a failure in ParseProviderLists() (hr = 0x80730b07).
-- LoadPolicyPlatformWmiProviders -- Failed to unload WMI providers. (hr = 0x80730b07).
-- LoadPolicyPlatformWmiProviders -- A failure occurred in Lantern::Setup::CustomActions::LoadPolicyPlatformWmiProviders() -- file:C:\__w\1\s\src\lantern\build\setup\customActions\CustomActions.cpp, line:447, (hr = 0x80730b07)
CustomAction LoadPolicyPlatformWmiProviders_Rollback returned actual error code 1603 but will be translated to success due to continue marking

Referencing my notes from an older case I had opened with Microsoft when I had another system complaining about the Microsoft Policy Platform, I ran the Microsoft "MicrosoftProgram_Install_and_Uninstall.meta.diagcab" diagnostic tool, which was able to successfully uninstall Microsoft Policy Platform from the system. This had helped resolve the other issue, but failed in this instance.

After cleaning up Microsoft Policy Platform, the MECM client installer still complained, giving all the same errors again.

As an aside, the WMI repository on the system passed. I also searched for *.ipi files in the %systemroot%\installer directory, but found none. I have also tried to install Microsoft Policy Platform as a standalone using the MSI, but it also fails with the same errors.

I have yet to reboot the system after the uninstall, as it's a production system; that's not an option at this time.
I have also neither re-registered the DLLs nor the MOF files, as this is a drastic step on an old system.

Besides the reboot and the registrations, am I missing the obvious?

Did you ever find a solution to this? I'm seeing this issue on a machine as well, and completely unclear what's going on. Am right now trying to rip the Microsoft Policy Platform off, but sounds like that error might be a red herring...
Update:
Okay, got it working. Uninstalled Microsoft Policy Platform via the .msi in C:\Windows\Installer, then deleted all the left over .tmp files in C:\Program Files\Microsoft Policy Platform (wonder if these were the issue), then a reboot and deleted C:\Program Files\Microsoft Policy Platform directory and rerun ccmsetup (initial install said couldn't install because an install was already running, but then it tried again after 10 minute wait). Successfully installed, finally, and client is talking properly (it LOOKED like it was talking previously, but ccmrepair wouldn't work and uninstall left it in this broken state).

If I had to guess, this system was a Win7->Win10 upgrade and some stuff got a bit wedged...