Force Windows 10 update 1803 to 1903

Follow
Yoan Dumont

Hello Guys !

We have 300 PC's still running Windows 10 1803 with personnal image

We would like to create a package for update windows 10 1803 to 1903 (not a new installation with a ISO, without WSUS just the windows update).

If anyone has any suggestions ?

Thanks so much.

Yoan

0

Comments

8 comments

Date Votes
  • Erin

    We did this with the standard ISO with the following command line

    setup.exe /auto upgrade /DynamicUpdate enable /noreboot /quiet

     

    Had 2 have 2 different versions 32, 64bit

     

    Success rate was about %80. 1903 can fail for a lot of reasons, disk space, old drivers, because its tuesday :-)  

     

    2
    Comment actions Permalink
  • Tom Brennan

    Can you provide a little more detail on this?  Newbie for PDQ and using it for 1809 --> 1903 is what I want to learn how to do.

     

    0
    Comment actions Permalink
  • Yoan Dumont

    Hi,

    I put ISO build 1903 in the Repository files and I make a new package with a command step  but after many test with many PC, it doesn't work yet.

    I always try another command for setup but it the same (setup.exe /Auto Upgrade /MigrateDrivers All /ShowOOBE none /Compat IgnoreWarning)

    Best regards.

     

     

    0
    Comment actions Permalink
  • Erin

    OK, screen shot shows you are using the wrong step type i think. We used the install step type and made sure 'include entire directory' is checked.

    that way the installer downloads the entire installation to the machine. 

     

    0
    Comment actions Permalink
  • Yoan Dumont

    OK, I Try it with a new package with step instal but always bad :

     

    0
    Comment actions Permalink
  • Erin
    • Edited

    No, thats very different, you have an error code it means the package likely got down to the machine but the windows installation itself has failed, before it never even started.

    Googling that error message can help. it returns a lot of results, incompatible app installed. could be an old/bad driver

    Also looking in the c:\windows~BT folder for error logs will help pinpoint the issue. i believe from memory the logs are in the panther folder underneath there with error xml files you can look and see what has gone wrong. Maybe even Google 'Win 10 upgrade error logs' to give you the exact path

     

    We're now away from an issue with PDQ - thats working fine, and its now a troubleshooting issue of the Windows install itself.

    0
    Comment actions Permalink
  • Erin
    • Edited

    here's a screenshot of my 64bit package. We suppress the reboot for package we deploy during the day with the /noreboot switch. then have a job at night that reboots them

    0
    Comment actions Permalink
  • Yoan Dumont

    Hi, thank you very much for help me.

    After Googling, I find this :

    Unknown Error Code -1047526904 (Incompatible apps present in the system is blocking the upgrade).

    Trend micro office scan is the culprit :

    Everything seems to work well :)

     

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post