Fix Incorrect Deployment Statuses
Deployment Status are coming back as Failed to install update(s) with an error code of 0x00000000 and Error Description of Success. Can this please be fixed? Links with more details:
Updating status to planned, see https://docs.microsoft.com/en-us/sccm/core/understand/find-help#send-a-suggestion for an explanation of each status value.
We’ve shipped fixes for a few scenarios that can cause this in 1902 but know there are some scenarios left.
May we ask anyone still experiencing it on 1902 to gather verbose logs from the client and send a frown so we can troubleshoot additional scenarios that cause the error.
same with 2004 - What logs do you want
G. Milazzo commented
Same issue with SCCM 1906 version
Will this ever be fixed? We tried 1906 and upgraded to 1910 but the same thing is happening. Machines are showing compliant when they are not and the status is blank under "software updates" on the monitoring tab.
Does anyone know if this issue has been completely addressed in 1906 or 1910? There is very little information available on this.
In my environment we have 1902 and are still getting this error, its really annoying as software update compliance looks awful until you drill down into the deployment error codes. Verbose logs, how do you produce those for this specific requirement?
Sharad Sareen commented
We are running SCCM 1902 version and we are experiencing the same issue. Majority of our clients in feature update installation reporting Failed to Install Update with Error description success. At the client side we are seeing that update showing installed in software center however, windows version still showing the old one.
JOUAULT Christophe commented
We are also seeing this problem with CM1902.
After an analysis of the SCCM client, the situation resolves itself. But, it is very difficult to follow a deployment with this error during cyber attacks.
We are noticing this behaviour with CM1902 as well, Could you please let me know which verbose logs you are referring to and procedure?
Seeing this with Feature Update deployments from 1803 to 1809, by right-clicking the feature update and deploying to a collection. The deployment does not require a reboot as part of the deployment, as the reboot occurs later at 2 am. Status is primarily Error with a few In Progress (six machines total), even though the machines have successfully upgraded to 1809.
Virgil Celestino commented
Still experiencing on 1902 but with Lenovo's thirdparty update catalog. We have confirmed on the device that the drivers have been updated. But Software Center is still prompting for a restart, even though we have restarted multiple times.
Feedback has been sent through the console.
We're still experiencing this issue in our environment. Where do we upload the logs?
The same here. Very confusing. Please Fix it.
Thomas Kremer commented
We are seeing this error also. 498 Clients Failed/Success. It's annoying.
Yes, we're annoyed by this issue also. Fix it SCCM team please.
Jeff Carreon commented
We're also seeing this... And it's causing issues with reporting.
As requested by djam on Twitter : 27 Successful failures this month.
We see this also... on the upside it makes you look good even when failing!
Marty Miller commented
Also seeing this error