Hi,
Thank you very much for your feedback and sharing. We're glad that the question is solved now. I think maybe other peoples with the same needs will benefit from it. Here's a short summary for the problem.
Problem/Symptom:
A required Windows 10 20H2 can not install the latest 21H2 version, but software center shows it has installed.
Solution:
Create a brand new Task Sequence and insert the data from the steps of the original one.
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,
About the installed 20H2, we should notice the side of logs. How we deploy it? If task sequence, please check smsts.log between the the normal client and the issued client. If the update is deployed by feature update, we could check UpdatesDeployment.log.
If it is UpdatesDeployment.log, we could refer to the following screenshot:
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.
Thanks and regards,
Amanda
Hi,
it seems that my copying of the the previous upgrade TS is what caused the issue. I am waiting for the confirmation on this and will write as soon as I receive an update.
BR
It has been confirmed by an colleague of mine which is a MECM specialist that this behavior is being presented only when an upgrade Task Sequence is being copied, which most of us do to save time.
Solution is to create a brand new Task Sequence and insert the data from the steps of the original one.
BR
Sign in to comment