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(220.8, 95%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EF%3C/text%3E%3C/svg%3E)
Hi All,
We are deploying the June Month patches from SCCM Server (Automatic Deployment Rule - ADR) to Windows 10 version 1809.
All the Windows 10 Clients getting Error "Delivery Optimization: Download of a file saw no progress within the defined period - Error Code 0X80D02002"
But O365 Patches to Windows 10 Machine successfully deployed and Windows 2016 Server Patches also successfully deployed to the Server Machines.
I tried to Following steps to troubleshoot,
Redistributed the content to the Distribution Point
Restart the WMI Services on SCCM Site Server
Repair the CCM Client on the DP
Remove the Windows 10 Patches Deployment and Redeployment to the Collection
SCCM Server Details :
Microsoft Endpoint Configuration Manager 2010
Console version : 5.2010.1093.3100
Site version : 5.0.9040.1000
CCM Client Version(Server and Windows 10) : 5.0.9040.1044
Anyone help on this issue? Advance Thanks!
![](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(28.799999999999997, 0%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBW%3C/text%3E%3C/svg%3E)
I received this error with a 21H2 Enablement Feature Update and it was caused by the content not being distributed to the distribution point. You may want to redistribute the content if it is already showing as copied successfully.
Windows 10 1809 is past its end of life and is no longer supported.
Hi Jason,
Thanks for the response!
The Microsoft Support only Ended. But If patches is not available to push to Client, it will show as Compliance success in SCCM Console. Am I right?
And in our Environment some machines have Windows 10 version 1903, 1909 and 20H2 also have the same issue. Sorry, I not mentioned this version in above question.
I have seen some issues related to June and July Windows 10 patches. However, the one you are reporting is some what different. Have you tried re-downloading the updates in question?
Hi Rahul,
I not tried the re-downloading. But I tried removed content from DP and then redistribute the content to DP.
Yes, that's not specifically your issue, I was just calling out that you have a bigger issue to address as well. 1903 is also past its end of life.
We have planned to upgrade version 20H2 within this month. Is it again same issue will appear after version upgrade? Because now 20H2 Machine also getting same error so only I asking.
Hi @Flint ,
But If patches is not available to push to Client, it will show as Compliance success in SCCM Console. Am I right?
As you mentioned 'Compliance', is it the tab of 'compliant'? which located in Monitoring --> Deployments --> specified update --> Completion Statistics. If so, a configuration item rule is not evaluated if it is not detected or not applicable on a client device; however, the rule is returned as compliant.
Here is the article we could refer to:
https://learn.microsoft.com/en-us/mem/configmgr/compliance/deploy-use/monitor-compliance-settings#view-compliance-results-in-the-configuration-manager-console-1
If the response is helpful, please click "Accept Answer" and upvote it.
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.
Hi,
Just checking in to see if there is any update. May we know the current status of the question? If there is any other assistance we can provide, please feel free to let us know, we will do our best to help you.
Thanks and regards,
Amanda
![](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(32, 99%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERD%3C/text%3E%3C/svg%3E)
Hello Mates,
We're experiencing the same issues when we deploy April 22 updates through ADR. We're in early adopters phase but all of them are failing.