Download

Windows 10 Fall Creators Update (1709)

Upgrade Windows 10 to Creators Update

Description

This agent procedure will upgrade Windows 10 to the fall creators update (Build 1709.)
This will perform an entire Operating System upgrade, it is recommended to perform a backup and/or system restore point before proceeding with the OS upgrade.
The workstation will be restarted as part of the procedure.
The agent procedure comes with 3 files of about 1 Go each that will be decompressed to a 3.5Go Iso file required for the upgrade.
The whole process takes between 45 minutes and 2 hours until the workstation can be used again.
It is recommended to have at least 20Go free on the endpoint before running the procedure, otherwise the procedure could fail without giving any error message.

Categories
Developer
  • Name: Douglas Sanchez
  • Company: Kaseya
  • Website: http://www.kaseya.com
  • Contact Developer
  • Summary
  • Windows 10 Fall Creators Update (1709)
  • 96 Downloads
  • Released on November 7th, 2017
  • Reviews

    Windows 10 Fall Creators Update (1709) has no reviews.

    Discussion
    Gravatar for Sam
    Sam 2 months ago

    I am only seeing the .xml file in the zip file I downloaded?

    Gravatar for Douglas Sanchez
    Douglas Sanchez 2 months ago

    To correct the Zip files with the whole content, you need to click on "Visit Website" instead of "Download." We had to work around some website limitation due to the size of the file.

    Gravatar for Derek Russ
    Derek Russ about 2 months ago

    This doesn't seem to be working. it is giving me the following error - Execute Powershell Command (64-bit, Run As System)-0001 Check for powershell failed!

    Gravatar for Douglas Sanchez
    Douglas Sanchez about 2 months ago

    Hi Derek, Can you give me more details about the endpoint and the error ? What line is it erroring at ? And Does the agent procedure log give you any more details as to why it is failing ? I worked on all Machines and VMs I tested it on.

    Gravatar for Nicholas Tobin
    Nicholas Tobin about 2 months ago

    I have some machines in a company that uses Enterprise Volume Licensing so this installer fails and asks for a key every time that wont take. Anyone know where the ISO for that version would be?

    Gravatar for Douglas Sanchez
    Douglas Sanchez about 2 months ago

    @Nicholas, as far as I know, Microsoft now hides the ISO so that it cannot be downloaded directly. I recommend using their ISO creation tool at https://www.microsoft.com/en-us/software-download/windows10 on an endpoint with the enterprise volume. Hopefully this will create an ISO for that specific system and it won't prompt for the key.

    Gravatar for Derek Russ
    Derek Russ about 2 months ago

    it looks like it is on line7 when running the powershell. Two things i have noticed. the temp agent dir it copies the files to c:\windows\syswow64 since it's a 64bit system, but the path in the PS Script has system32. i ran the script.ps1 mnaully and changed the path to wow64 and it is running on my system now. Below is a screenshot of the log. https://imgur.com/a/mWQQS

    Gravatar for Douglas Sanchez
    Douglas Sanchez about 2 months ago

    Derek, by any chance, is the endpoint a 32bit machine ? If so I can send you an update procedure that takes into account 32 bit systems.

    Gravatar for Derek Russ
    Derek Russ about 2 months ago

    Hey Douglas, It is a 64bit machine.

    Gravatar for Derek Russ
    Derek Russ about 2 months ago

    The cleanup procedure did work though.

    Gravatar for Heather Stover
    Heather Stover 9 days ago

    This script is incredibly helpful! But we have a handful of managed machines that are 32-bit; where can I find the procedure to run the update on those?

    Gravatar for Douglas Sanchez
    Douglas Sanchez 9 days ago

    @Heather, I would recommend using this link https://www.microsoft.com/en-us/software-download/windows10 to create a new ISO on a 32 bits machine. Then you can split it in 3 files similar to the way it is done in the procedure, and redirect to that folder with the procedure. You may want to duplicate the procedure so that you have one for 32bits machine and one for 64 bits.

    Gravatar for Fleet Admin
    Fleet Admin 9 days ago

    Hi all, A bit new here so excuse me in advance. I am trying to use this procedure to upgrade Windows 10 (1703) x64 machines. I placed all 3 files, Windows.zip.001 Windows.zip.002 Windows.zip.003 In Window ISO folder under the shared folder... and followed the rest of the instructions... however i cannot see it working when i execute it... can you share some tips on what should i be seeing or monitor to see errors etc.? Cheers, EldadiO

    Gravatar for Douglas Sanchez
    Douglas Sanchez 8 days ago

    You cannot really see much while the procedure is working. You can eventually check the kworking folder as the WIndows ISO folder should get created and the files should slowly transfer there. Then it will mount the ISO, and then a Windows Upgrade process will be up for a little while before restarting.

    Gravatar for Rob Shaw
    Rob Shaw 7 days ago

    Hey Douglas, I tried testing out this procedure last night on two different 64-bit Win 10 computers here in my office. The procedure downloaded one of the ISO's and after a few hours eventually the procedure states that it was successful. The clean up procedure was also triggered and removed the left over files. The only problem is that neither computer took the update. Do you have any idea why this might be? One of the computers is sitting at version 1607 (OS build 14393.1944)

    Gravatar for Douglas Sanchez
    Douglas Sanchez 7 days ago

    Hey Rob, I cannot say for sure, but there might be an issue with going from 1607 directly to 1709 ? Eventually try letting the procedure run and cancel the cleanup one. You'll then be able to give it a shot manually and see if you have any compatibility issues.

    Gravatar for Wynema Ware
    Wynema Ware 7 days ago

    I have successfully upgraded from every version of Windows 10 to Creator's 1703 and 9. Failures like this that I experienced were due to that 4gb file never fully downloading. Not sure why the procedure says it is successful. I found out by remoting into the machine and kworking had partial files.

    Gravatar for Wynema Ware
    Wynema Ware 7 days ago

    I have successfully upgraded from every version of Windows 10 to Creator's 1703 and 9. Failures like this that I experienced were due to that 4gb file never fully downloading. Not sure why the procedure says it is successful. I found out by remoting into the machine and kworking had partial files.

    Gravatar for Douglas Sanchez
    Douglas Sanchez 7 days ago

    This is the exact reason why I ended up splitting the file into 3 different files that needed to be decompress. Send me an email at douglas.sanchez@kaseya.com and we can take a look at improving it.

    Gravatar for Rob Shaw
    Rob Shaw 7 days ago

    Yeah I did notice that only one of the ISO files transfered over and it only ended up at about 800MB. Any idea why the procedure would quit transferring? Could there be a size limit in place on our end? Forgive me, I'm still rather new to Kaseya.

    Gravatar for Nicholas Tobin
    Nicholas Tobin 7 days ago

    @Rob, This file is rather large to host in Kaseya. What I did, was using 7 zip broke the iso into 3 equal parts and hosted them on our AutoTask. I then created a public link and used GetURL within the script to download the 3 parts. The rest of the procedure "should" be the same iirc as far as unzipping the 3 parts and then running the install. IF you have any enterprise versions, you will need a different ISO.

    Gravatar for Rob Shaw
    Rob Shaw 7 days ago

    Yeah I have three different files and they are about 1.2 GB a piece. Did you break these down further? From what I understand, Douglas already broke the primary ISO down into these three files, much like what your stating.

    Gravatar for Nicholas Tobin
    Nicholas Tobin 7 days ago

    No, my files are about that same size as well. But I placed them in AutoTask rather than Kaseya file server.

    Gravatar for Nicholas Tobin
    Nicholas Tobin 7 days ago

    IF you have a place to host the files, I can email you what I use and you can edit your download links. Mine is actually 4 scripts. One is the download/Extract, The second is the Install, third script is a Checksum that ties into the Download/Extract script to ensure the file fully downloaded and extracted before you run the install that ties into a custom field as Pass or Fail. The fourth is the cleanup of the files.

    Gravatar for Rob Shaw
    Rob Shaw 7 days ago

    I am not sure that I do have a place to host them. I need to talk to some people in the office to get more information. I'll get back to you. Thank you!

    Gravatar for Douglas Sanchez
    Douglas Sanchez 7 days ago

    @Rob, as Nicholas mentioned, it could be faster to host the files in a server and use GetURL to download them instead of transferring from the VSA server. It all depends of the Network configurations. It is possible the download stops because it is slow and the procedure times out. You can also use them on a local file server (If you have one) and edit the procedure to transfer the files from that server to the endpoint.

    Gravatar for Karel P Kerezman
    Karel P Kerezman 2 days ago

    If you're trying to do this to Enterprise, well, the ISO creation tool won't help you either: "Windows 10 Enterprise isn’t available in the media creation tool." And since the volume download center still doesn't show a 1709 ISO (as of our check on Monday, Jan 15th 2018) we're still out of luck. Not that Enterprise comes up often, but WE'RE on it, and I was hoping to test this procedure on an in-house system. D'oh.

    Gravatar for Rob Shaw
    Rob Shaw 2 days ago

    Speed isn't an issue. Douglas, you were correct. The procedure was failing due to the procedure timing out before all the files could download. I bypassed this by creating 3 simple procedures to download 1 chunk of the iso each. Then I just pulled the download part out of your script and had it trigger after the last file downloaded. Only been able to test it on one computer so far but it worked flawlessly.