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(124.80000000000001, 57.99999999999999%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFM%3C/text%3E%3C/svg%3E)
Hello,
currently we deploy the Windows 10 20H1 feature update via ConfigMgr / Servicing. The update seems to be installed correctly (no issue in softwarecenter) - Softwarecenter tells "Reboot required" after the reboot the Clients are still on 1909 and the installation process will start again. A few minutes later the next reboot prompt appears etc. This will go on the whole day.
Any ideas what is the problem here?
Our clients came mostly from 1703 and then were upgraded to 1909 the same way. Can it be that the sources still contain only 1909 although the update 21H1 is deployed (sources not updated)?
That would explain why after the reboot, 1909 is still installed and the installation of 21H1 starts from the beginning and another reboot is necessary. (Because 1909 is always installed over it and after installation 20H1 is not detected).
You can find the log files here:
https://feintool.sharefile.com/d-sc105bf308a5e4bde9d47321934ea050d
Appreciate your help
Best regards
Michael
Hi @feintool-m ，
The update seems to be installed correctly (no issue in software center)
We could check UpdatesDeployment.log to see if the update is really installed.
Here is the screenshot about update installation process:
After the updates are installed, Updates Deployment Agent checks whether any updates require a reboot, and then it notifies the user if client settings are configured to allow such notification. We could refer to UpdatesDeployment.log and UpdateStore.log.
Here is the screenshot about update restart process:
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 @Amandayou-MSFT , thank you for the reply.
I've started the installation right now and will check the UpdatesDeployment.log
In UpdatesStore.log is see the update is queried 2 times with different IDs but the same name:
Also I've checked the checkbox to run a updates deployment evaluation cycle if a reboot is needed for the deployment.
Thats why after reboot the Client is directly checking for updates again. And because the client is still on 1909 it detects that the update to 20H1 is missing and is trying again and again.
I will comment again if the restart is done and check UpdatesDeployment.log
A
It looks like the client is stopping at 61% and then there is an error "GetUpdateInfo - failed to get target update, error = 0x87d00215"
After reboot I can see install completed but presence state still not compliant:
Sounds like the OS is being rolled back. Check the eventvwr, panther logs for clues. The issue could be with outdated drivers or BIOS.