Important Notice: On February 29th, this community will be put into read-only mode. All existing posts will remain but customers will be unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Upgrade Win 10 computers to 2004

Hi everyone!,


I have a few computer that need upgraded from 1903 and 1909 to 2004, We have done a few manually and worked just fine, however we were wondering if there is a way of doing it via PDQ?.





Date Votes
  • Untried but here is some inspiration:

    Do you have the possibility of running powershell on the clients? Either remote with PSSession or locally via PDQ.

  • Yes, this is possible. I do this today with each version update. You'll need the 2004 ISO. If you don't have it, you can visit and click on Download Tool Now. Run the executable and select the option to create an ISO file. Once created, mount it and copy the files to a new folder in a location of your choice. In PDQ Deploy, create a new package.

    Step 1 - File Copy.

    Select the Folder option. Source would be the folder that has the extracted files from the 2004 ISO. For target folder, I do C:\Tech\2004. Check overwrite existing files, Include Subfolders and Copy All Files.

    Step 2 - Command.

    Put in the following: C:\Tech\2004\setup.exe /auto upgrade /migratedrivers all /ShowOOBE none /Compat IgnoreWarning /Telemetry Disable

    Finally, change the Timeout to be a custom timeout with 120 minutes. Can be found on the Properties > Options tab on the package.

  • Jayme Hester, how long does deployment typically take for you?

  • Daniel,

    It really depends on the computer and speed of your network. I've seen it take anywhere from 25 - 90 minutes personally. We run with core i7, 16 GB RAM and NVMe as our minimum along with gig network.

  • Jayme,


    Thank you for the response. Your instructions worked. The deployment took about 1 hour 21 minutes.

  • aren't you left with a large folder on each of the devices you deploy to after the install has completed?

    how do you then remove the insall media folder (in your case c:\tech\2004\) from the devices ?

  • David,

    Good question. You do have leftover files. I have another PDQ package that removes the leftover files. I tried using it in the same deploy package, but kept running into timing issues, so I made it in to it's own package. I run it after the 2004 upgrade is completed. It's a command step: RD /S /Q "C:\Tech\2004"

  • Does anyone know if we can use the ISO from the link in Jayme's post if we're running Win 10 Education?  There was so much back and forth on this in the first few version of Win 10 that I didn't bother.  I'm looking at doing this again and I tried googling now only to find conflicting answers.

  • Aaron,

    That link looks to be for home and professional editions only. I did find this site that does the same thing, but for Education edition. 

  • Thank you very much, do the process and the update is complete, however, my computers are joined to the domain, when the update is finished it does not keep its domain and changes the name of the pc

  • Gustavo,

    That is very weird. Mine were all domain joined and never un-joined or renamed them... Which windows edition did you upgrade with?

  • windows 10 1909 to 2009

  • Gustavo,

    Which edition? Pro, Enterprise, Education, Home....?

  • sorry  is a pro version


  • Hello Jayme, my bad, mayusc sensitive command,
    ok now, the installation program started, I am working in a restricted network, so the PCs do not have free access to the internet, the installation program stuck in checking updates, I already stopped the windows updates service and cleared the distribution software cache, but the installation is stuck in Getting updates.
    any idea how i cant skip the updates check


  • Gustavo,

    I believe you can skip checking for updates by adding the following line: /DynamicUpdate disable

  • When i try the script of Jayme Hester

    I get: (after 11 minutes)

    Runner service died unexpectedly on target computer and left no last will and testament


  • Mike Teseling, are you using the local administrator account?

  • No an domain account, that has admin rights

  • I finally managed to upgrade to computers from a version 1909 to 2009 (20H2)

    step 1 - Copy all ISO files from fileserver to target machine

    step 2 - Delete all temp cache updates, stop and restar windows update related services and for me delete restriction policies

    net stop wuauserv
    net stop cryptSvc
    net stop bits
    net stop msiserver
    ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
    ren C:\Windows\System32\GroupPolicy GroupPolicy.old
    net start wuauserv
    net start cryptSvc
    net start bits
    net start msiserver

    step 3 - execute the command

    c:\w102009\setup.exe /auto upgrade /migratedrivers all /ShowOOBE none /Compat IgnoreWarning /Telemetry Disable /DynamicUpdate Disable

    the timeout is a case of trial and error, I have updated several PCs of different roles with different apps and in each different role I have had to change the timeout. It depends a lot on the resources of the pc and what you have installed

  • I am testing with 20H2.

    How are you guys dealing with the necessary reboot after the setup runs? From my testing, the actual update does not occur until you reboot.

    I added a PDQ reboot step after my "setup.exe /with all my switches" and I get the following for that step:
    The account name is invalid or does not exist, or the password is invalid for the account name specified

    The reboot seems to timeout because the target machine is actually applying on the update on restart.

  • I'm also running into this issue. 


    Do the 20H2 upgrade, but then any other steps afterwards fail. If I log onto the machine later on, it's been successfully upgraded to 20H2. 


    I'm thinking that PDQ thinks the installation is complete after only 11 minutes. That's what the deployment log is saying. I'll try adding a "sleep" step in PDQ directly after the 20H2 installation, which I removed the /noreboot argument from. 


    It's likely seeing the machine come back online after a reboot, but Windows is still processing the update so it denies access to the deploy account. 

  • Gustavo Fr 

    I finally managed to upgrade to computers from a version 1909 to 2009 (20H2)

    Thanks for your solution. it works also with 1903 to 20H2 :)

  • So I am going to try but wonder if anyone has? Why not run the update form a central network location like  \\servername\w102009\setup.exe /auto upgrade /migratedrivers all /ShowOOBE none /Compat IgnoreWarning /Telemetry Disable /DynamicUpdate Disable

    we have run the setup from the network before so I think this would work and would avoid the copy command.

  • @Burke, that’s how I do it.

    I have a share and granted everyone read to it.

  • Cool I am testing now we have a bunch of PC's with small drive so the copy was not an option.

  • Has any one experienced errors with the actual update?  On my test box it is going thru the install but fails during the actual update after the reboot and makes me select keyboard type before it actually boots.  

  • @Burke Swanson that is how my manger want me to deploy. Will you please go a little further in depth about how to set up PDQ Deploy to do this? Sorry new here trying to learn all I can.  Thank you very much!!

  • I have not gotten it to work well Jeffjackson80 maybe you could share the package and how you setup the share. Kind of frustrating can not see the progress even if its working.,

  • I need to deploy the same thing in my work place ,, can someone please share the steps on pdq on how to accomplish(screen shots will help) with out demoting or removing the  the machine from the domain 


Please sign in to leave a comment.

Didn't find what you were looking for?

New post