This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 36%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMP%3C/text%3E%3C/svg%3E)
For some reason in the past few weeks i've suddenly got massive issues in SCCM. I thought this may have had to do with a windows update. We are on a domain with no internet connection so I upgraded SCCM to 2111 and there was no fix.
Basically on about 1/3 of our PCs the applications in software center is empty. There even is no app logs of any kind at all. What's strange is windows updates are still being deployed and applied through it, so it's just applications. Vlan or network is irrelevant. OS is irrelevant. Some machines work, some do not.... there is no factor in regards to IP, OS, or updates that determines why.
Even the PCs that work show a 'parsing error' in the deployment evaluation tool. The computers without this error all work.
With updates when evaluating each individual update it can determine which come does and doesn't have what update.
I've checked boundaries, reinstalled MP and DP, reinstalled the client, pretty much everything I can think of short of reinstalling SCCM totally.
Not sure where to go from here/
The certificate on the microsoftpolicyplatformsetup.msi expired and so is it's certificate authority.
Cert on the file expired in 11/2/2017
Root authority in 5/9/2021 which is causing this problem.
This is probably due to enhanced security on our network it doesn't like the root authority being expired.
Is there any way to get this file updated? Without it we can't use SCCM because our policies in place are due to government mandates.
Hi,
It seems that there is something wrong with client healty.Please try uninstalling the Configuration Manager client, then reinstalling it again first.
Best regards,
Amanda
We took a computer that we freshly installed windows on, joined it to our domain, and we have the same problems there.
I turned off UAC and it still fails.
I then tried to install the MSI for that microsoft policy platform and it fails on publishing WMI classes. It does this on every computer and i'm not sure how WMI could be failing on every PC like this. This is probably the root of all of our problems.
Hi,
Please check the event viewer to trace the microsoft policy platform application, here is the screenshot of my environment:
We took a computer that we freshly installed windows on, joined it to our domain, and we have the same problems there.
How we intall the client on this Pc? Is the client is normal? It is recommended that we configure the site to automatically use client push for discovered computers, here is the link:
https://learn.microsoft.com/en-us/mem/configmgr/core/clients/deploy/deploy-clients-to-windows-computers#configure-the-site-to-automatically-use-client-push-for-discovered-computers
The client is pushed from SCCM in the normal way using the client push installation on discovery.
When I look at the log I am seeing a bunch of warnings about the localsystem account and a possible security violation. The next two logs after that it says ending windows installer transaction then installation failed.
Hi,
Is the log the event viewer or the record in event viewer? Could we show the details of these error?
Best regards,
Amanda
So i'm finding problem is bigger than just deploying the client. Even ones with clients installed are having issues with application deployments overall.
We have 3 identical networks all with SCCM. Our 3rd network has 2103 and has no problem. Our other two have 2111. Neither can deploy the sccm client OR any applications. Updates are however working.
The only difference between the 3 is that the networks where sccm are not working have dotnet 6.0 deployed along with 2111 sccm. Everything else down to windows update, deployed software, group policy, etc are identical.
All software deployments on our 2111 networks are showing 'parsing error' in the deployment evaluation.
As far as what you asked these are warnings and they say:
A provider, SoftwareInventory_StateProvider, has been registered in the Windows Mangement Instrumentation namespace root\Microsoft\PolicyPlatform\Models to use the LocalSystem account. This account is privleged and the provider may cause a security violation if it does not correctly impersonate user requests.
After that it says Microsoft Policy Platform -- Installation Failed and afte that gives a 1603 error.
Attached is the ccmsetup log and here is a link to our sccm server logs.
Can you please open a support case so that we can investigate further?
Can you validate whether or not any certificates have been removed from the trusted root cert authorities store on these systems? Specifically, the Microsoft Root Certificate Authority cert?
Have you had a chance to open a support case and/or can you validate whether or not any root carts from been explicitly revoked?
Hi @Michael Pristave ,
What resolves issue could uninstall and reinstall Microsoft PolicyPlatform msi from client install source folder, and refresh the machine policy to check if the problem is solved.
Here is the similar post we could refer to:
https://social.technet.microsoft.com/Forums/windows/en-US/5b250532-576f-46a6-99b5-70b79cab3660/parsing-error-0x87d00207?forum=ConfigMgrAppManagement
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Thanks for the suggestion and it seems that causes me to find another problem. UAC is blocking my running this, maybe that's why i'm having problems.
It's saying the application is blocked for my protection. Trying to figure this out at the moment.
Looking into more detail on the msi here and it says that the certificate had been revoked, it's bizarre because I recently upgraded to 2111.