question

AliTaqvi-2831 avatar image
0 Votes"
AliTaqvi-2831 asked ·

Windows Version still old even after successful upgrade

I have upgraded 1809 system via task sequence to 1909. In Software center 1909 is showing as completed but windows version still shows 1809 if check via winver. I have ran the all the actions as well under SCCM Actions. Please help

mem-cm-generalmem-cm-updatesmem-cm-osd
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

EswarKoneti-MVP avatar image
0 Votes"
EswarKoneti-MVP answered ·

If winver shows 1809 then the upgrade did not finish successfully.
There are chances that, the upgrade is failed or rollback.
Task sequence is something that you have created. you will need to look at the client logs (smsts.log) for information.

Thanks,
Eswar

· 4 ·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

But why Software center shows as completed Installed ?

0 Votes 0 ·
Garth avatar image Garth AliTaqvi-2831 ·

As the saying goes "there is no magic bullet", you will need to review the logs and eventviewer to determine why the upgraded failed.

0 Votes 0 ·

The Task Sequence run complete without error, but that doesn't always mean that the upgrade run successfully.
Did the Upgrade step run and not skipped?

0 Votes 0 ·

As the saying goes "There is no magic bullet." you need to read the log and event viewer. The system could have successful install but on reboot it failed and rolled back. Onlyu review the logs and event viewer will give you that answer.

0 Votes 0 ·
Amandayou-MSFT avatar image
0 Votes"
Amandayou-MSFT answered ·

Hi @AliTaqvi-2831,

Agree with EswarKoneti and Garth, we need review the logs and event viewer first to check if any error in them. If so, please troubleshoot it. If not, please check if the operating system upgrade package is 1909, kindly refer to this picture:

75377-381.png



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.



image.png (104 B)
381.png (16.6 KiB)
· 1 ·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,

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,
Amanda You

0 Votes 0 ·
GaryBlok avatar image
1 Vote"
GaryBlok answered ·

Your question is basically the same as this: https://docs.microsoft.com/en-us/answers/questions/307556/sccm-in-place-upgrade-ts-installed-but-the-os-not.html

What it comes down to, your TS does NOT equal Windows Upgrade.
The TS is a deployment mechanism to run tasks, so a Task Sequence can complete successfully (depending on conditions and logic), and not actually upgrade the OS.


Example situation:

Running 1809 -> 1909 Upgrade Task Sequence.
Task Sequence Starts and gets to Upgrade Step
Windows Setup Engine Fails after the intial Reboot.
Task Sequence is kicked back in by the SetupRollback.cmd file and the TS goes into the "Rollback" Section
The TS finishes successfully because it completed without erroring

If you want the TS to fail if after the Upgrade Step, the machine isn't on the new version of windows, you would need to create a condition on a step to force it to error and have the TS fail out.

To download an example of error trapping in an upgrade task sequence, you can download a complete / complex example here: https://garytown.com/waas-1909-ts-download


·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.