Upgrading Windows 10 1909 to 20h2 using ConfigMgr- status still says "Installing" after successful upgrade, why?

Elroy 11 Reputation points

We are running Configuration Manager 2111 with KB12959506 installed. I have created an upgrade task sequence to upgrade my Windows 10 1909 Enterprise clients to Windows 10 20H2.

The upgrade works. However, after completion and reboot on some of my clients, if I look in Software Center the upgrade is still listed with a status of "Installing".

Why does this happen and what is an easy way to fix it?


Microsoft Configuration Manager Deployment
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Deployment: The process of delivering, assembling, and maintaining a particular version of a software system at a site.
923 questions
Microsoft Configuration Manager
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Amandayou-MSFT 11,051 Reputation points

    Hi @Elroy ,

    Could we know the upgrade is actually works? Do these client version change windows 10 1909 to windows 10 20H2?

    If so, we could check Smsts.log to see if task sequence activities is ended on the side of client.
    On the side of server, please navigate to monitor, deployments, the task sequence we deployed, check the status is successful.


    If the task sequence is normal, we could run the policy on the side of client or restart the client to check if the problem is solved.

    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.

    0 comments No comments

  2. Elroy 11 Reputation points

    The deployment works. The clients upgrade to 20H2.

    If I look at the deployment under monitoring, I can see that the upgrade task completes successfully. then a reboot is initiated. That is the last status message that I get.

    I suspect the reason I don't get status messages after that is that some clients are upgrading over VPN connection and after the reboot they lose their VPN connection and are unable to report their status message in time? They would also be unable to complete the 'post processing' section of the task sequence, which does not contain any tasks that they would run.

    Is there a way for me to clean this up? Or is the only solution to remove them from the deployment group so they don't get policy for the task sequence anymore?

  3. Rahul Jindal [MVP] 9,546 Reputation points MVP

    Is SMS agent host service getting disabled after the OS upgrade finishes? Is the ConfigMgr agent getting stuck in provisioning mode?

    0 comments No comments