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(140.8, 8%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBB%3C/text%3E%3C/svg%3E)
I'm deploying the windows 10 21H2 update using MECM via windows servicing. In some cases when I deploy to systems which have older versions like 1909 (18363) I see the deployment succeeds yet when I check locally on the client the windows version was not updated.
Is this expected behavior? I acknowledge 1909 is at end of servicing based on the MS version website.
Hi,
1,Can we manually upgrade to Windows 10 21H2 from the older versions devices?
2,Can we find any useful information in the UpdatesDeployment.log, UpdatesHandler.log and UpdatesStore.log?
Thanks for your time. Have a nice day!
Best regards,
Simon
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,
Hope everything goes well. 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.
Best regards,
Simon
Hi, I apologize for the delay confirming this. So Indeed, servicing should still be possible. Your troubleshooting helped me confirm this. Some of our remote systems are quite backed up in updates. AND they don't connect to VPN frequently. When a situation occurs where there are current critical updates queued and we create the deployment for the servicing feature update via enablement, well that doesn't get seen until these queued updates are handled, sometimes this takes 2-3 reboots even and if the user continues the same usage pattern, unaware of what is happening, things take awhile and sometimes we even need to have the user come in.