This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
i have a strange problem. I running a required Windows 10 deployment to update 20H2 to 21H2 and on some clients (there are 79 to update) some colleagues reported that they are not receiving the update messages every 3 hours like i told them in the info mail.
I mean this:
Some machines and Windows 10 20H2 "think" that 21H2 version is already installed, but however this is not the case:
The deployment is distributed only to 20H2 systems:
The version on the "operating system upgrade packages" shows 10.0.19044.1586 and the image has been edited with dism, but nothing special, some default apps have been removed.
Cheers!
Hi,
some colleagues reported that they are not receiving the update messages every 3 hours like i told them in the info mail.
About user notification, we should check if these clients are focus on tasks, Windows offers lots of ways to minimize distractions so it's easier to focus on tasks. Please navigate to Action Center and check if the status is Focus assist.
Here is the article we could refer to:
https://support.microsoft.com/en-gb/windows/make-it-easier-to-focus-on-tasks-0d259fd9-e9d0-702c-c027-007f0e78eaf2#ID0EBD=Windows_11&WindowsVersion=Windows_10
Some machine have not install 21H2, it means some clients have installed, is not it? Could we know it is deploy by task sequence? if so, 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 the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
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,
it is not about a 3 hour message thing. It is about laptops/windows 10 displaying that they already have 21H2 although this is not correct. They are running 20H2, this happens only on couple of clients. The upgrade once started WORKS without problems. IT is only about a display message in software center like in my screenshot.
BR
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
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.