Upgrade Windows 7 to Windows 10 with ConnectWise Automate Learn More
Upgrade Windows 7 to Windows 10

Upgrade Windows 7 to Windows 10 1903 – With ConnectWise Automate


    1. ) Download the ConnectWise Automate Script. Get here!
    2. ) Windows 10 Ent. x64 v1903 ISO File: To get Windows 10 Ent. x64 v1903 ISO file. Click here..
    3. ) Windows 10 v1903 ISO Files: To get Windows10 Pro/Home x64/x86 v1903 ISO files. Click here..
    4. ) Place On LTShare: Place the file(s) to L:\Transfer\Windows10\
        • a) Windows_10_x64_Pro.isoUse this naming convention for Windows 10 64bit (including ultimate, pro, enterprise).
        • b) Windows_10_x86_Pro.iso  – Use this naming convention for Windows 10 32bit (including ultimate, pro, enterprise).
        • c) Windows_10_x64_Home.iso  – Use this naming convention for Windows 10 64bit (including starter, home, and whole-home family).
        • d) Windows_10_x86_Home.iso  – Use this naming convention for Windows 10 32bit (including starter, home, and whole-home family).

      Note: If you want to change default naming convention, feel free to make changes in the script called “Function Script to Fulfill Initial Upgrade Requirements”->Global Parameters section. Script only downloads win 10 Pro  & Home ISO files. If you want it to download win 10 Enterprise files, please make changes in the global parameters section.

  1. 10 Gb free disk space on any drive to download the setup files and extract it.
  2. More than 5 GB disk space on the system drive.
  3. 2 GB RAM

How does the script work?

      1. Create a ticket to record the upgrade process. On upgrade success, the ticket will be closed with proper time entry. Else, it remains in the open state.
      2. Disk Space: the Script checks the all drives internal drives on target machine choose the one that has maximum free disk space to store the windows setup file (and other related files). The target machine must have at least 10GB free disk space on any drive and 5GB on the system drive.
      3. If Laptop: Laptop should be on charging mode if the script finds it on battery mode then exit with ticket comment.
      4. Windows 10 setup file. Script downloads setup to file %Drive%:\WindowsSetupFolder\Windows10.iso. location. – First, the script tries to copy the windows setup file from the Location Cache directory %cachedir%\Windows_10_x64_Pro.iso to %Drive%:\WindowsSetupFolder\Windows10.iso. – If it couldn’t find the file in the cache directory, it tries to download the ISO from LTShare folder. – If it won’t find ISO file on LTShare then exit with a ticket notes.
      5. Note: Please make sure you set up a network (cache) directory on the location if you want the script to copy the required *.iso file from a network drive. Please take look on how to setup Cache directoy documentatoin given on Docs.Connectwise.com. https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Documentation/060/070
      6. Check User logged in: If a user logged into the system and working, then script sends message to the user asking for permission to upgrade. If it doesn’t respond or says no to upgrade, then the script exits with a ticket notes.
      7. System Restore Point: It creates a system restore point on the target machine before it runs the upgrade.
      8. Export last logged in user reg file: The script exports last logged in users that it imports after the upgrade.
      9. Upgrade process: it runs the upgrade process by sending a shell command.
        Supported parameters:
          • Setup.exe path: %Drive%:\WindowsSetupFolder\setup\setup.exe.
          •  Windows License Key: You can assign Windows License key in the EDF called Windows License Key on the Computer Management screen to use in the script. Windows setup will upgrade Windows to the specific edition by checking the license key.
        With license key, you can upgrade Home Basic (or any other Home Family OS versions like Starters, Home Basic, Home Premium, etc.) 32bit machine to Pro, Enterprise or Ultimate 64bit Edition. It all depends what License key you’re using to upgrade.
      10. Import Last logged in User’s Reg file: After the upgrade, it imports the last logged user’s details to the registry. It helps users who don’t remember their user names.
      11. How much time it takes: it depends on the performance of the machine, but it usually takes 40 to 60 minutes.
      12. Ticketing: Script records everything (failure or success) in LabTech ticket to check.


– Windows setup handles it very smoothly. Users won’t see any difference then Windows 10 graphics and working environment. This upgrade is the same as you upgrade your windows 7 to windows 10 by the double-clicking Migration tool.

– The script creates the system restore point. However, we recommend you to take a bare mental backup before running the upgrade. As you always have a backup if anything went wrong.

However, I have seen if anything went wrong with your machine upgrade process will be canceled and it restores to windows 7.

– Yes, It depends on what Windows 10 version you have placed on LTShare folder. I Upgrade Windows 7 to Windows 10 1703, Windows 10 1803 and Windows 10 1903. It the matter of setup file you give the script to run.

– It is a major upgrade as we know, we could not make it 100% silent upgrade, but yes, we were able to make the script to do 60% of its job in the background. Windows upgrade requires several reboots that’s why we couldn’t make it 100% silent.

– Yes, you can migrate Windows 7 32bit machine to windows 10 64bit if you supply Windows license key. Windows upgrade checks the license key and runs the upgrade accordingly.

– Yes you can. We recommend supplying windows license key with the upgrade.

– Yes, it does support the hostedRMM. But you need to place ISO file behind the IIS Server, FTP Server or AWS S3 space so that script can download the iso file without any problem.

– Attempts an upgrade without suspending BitLocker. If the upgrade fails, Windows Setup will suspend BitLocker and complete the upgrade.  

If fails again, then it is recommended to remove the encryption and run the script again.

If the script doesn’t work for you, and you don’t know why!

Then, run the Command prompt as Admin and run the following command. The script runs the same command as the System user account.

  • Without Windows Key:

    %Drive%:\WindowsSetupFolder\setup\setup.exe /auto upgrade /migratedrivers all /Compat IgnoreWarning /dynamicupdate enable /showoobe full

  • Or with Windows Key:

    %Drive%:\WindowsSetupFolder\setup\setup.exe /auto upgrade /pkey xxxxx-xxxxx-xxxxx-xxxxx-xxxxx /migratedrivers all /Compat IgnoreWarning /dynamicupdate enable /showoobe full

– The problem was the .iso file not being defined within the MIME Type in IIS.
– To resolve we have defined .iso as the MIME Type in IIS.

Need to follow the mentioned steps to set MIME Type for .iso files:
  1. Open IIS Manager (Start >> Run >> type inetmgr hit enter).
  2. Select the root node from the connections pane. Double-click MIME Types from features pane.
  3. Click on Add.. link in the Actions pane. This will bring up the dialog box. Enter file extensions, specify corresponding MIME type and click on OK button.

  4. File name extension: .iso
    MIME Type: application/octet-stream
  5. Restart your IIS Server from IIS Manager.

Term and Conditions: Click here