/build/static/layout/Breadcrumb_cap_w.png

Having an issue using Custom Deployments to upgrade Win7 to Win10

Hello All,


I followed this article; https://www.itninja.com/blog/view/upgrading-to-windows-10 to setup Custom Deployment tasks in attempt to do an in-place upgrade of Windows 10. As you can see in the attached images, all tasks up to [Upgrade] Set Engine Run Key are completed. Upon the first reboot, I am presented with the following error below. Once I click on OK, it continues with the remaining tasks and completes them, reboots one final time, but Windows 7 does not upgrade to Windows 10. I have searched for this error, but have not had any luck. The environment that I am working in is on a fresh installation of Windows 7 Pro with latest updates, a newly created VM. Any insight on the issue below would be greatly appreciated. I have a project to upgrade all of our users to Windows 10 - 300+ users. :/


2Q==Z


4 Comments   [ + ] Show comments
  • We have successfully carried out "in-place upgrades" using the SMA as per my #TenFourTen posts on LinkedIn, Feel free to reach out if you want to get more information - Hobbsy 5 years ago
    • Thanks for the reply. Unfortunately, we do not have a K1000. Only the K2000 at the moment. - agonzalez 5 years ago
  • Hi agonzalez See if the machine has any antivirus installed or firewall. This can block the upgrate. - madro 5 years ago
    • No Anti-virus. It is a clean installation of Windows with only updates installed. Perhaps the windows firewall? I will test. There is hardly any information on this error. It's throwing us a big wrench into our project. :/ - agonzalez 5 years ago
      • Be sure that if you use Windows 7 Professional, you must use Windows 10 Professional. - madro 5 years ago
  • Make sure your Win7 is not OEM licensed.

    Because of the error, I believe this is some kind of issue with the ISO or the way the ISO is configured. - Channeler 5 years ago
    • SW_DVD5_Win_Pro_7w_SP1_64BIT_English_-2_MLF_X17-59279 is the name of the .iso wich was downloaded from our MS licensing portal. I will verify what other licenses/isos are available for download. Thanks for replying! - agonzalez 5 years ago
  • Thank you all for the guidance. It turns out that we upgraded the K2 appliance to the latest version, then reuploaded the custom deployment scripts and everything started working as it should. Chalk this up as a learning experience. :)

    Thanks again all! - agonzalez 5 years ago

Answers (1)

Answer Summary:
Posted by: Ziggi 5 years ago
Blue Belt
0

Top Answer

First of all, you should try the command locally on a test machine just to confirm that it works.

You can sometimes receive that error if you have not specified the version of Windows 10 you are upgrading to (Pro,Ent,Edu). The new ISO's have Pro,Ent,Edu built-in and you need to specify a Product key to upgrade.

This is my command line with Windows 10 Pro KMS Key

%systemdrive%\win10\setup.exe /auto upgrade /pkey W269N-WFGWX-YVC9B-4J6C9-T83GX /installfrom %systemdrive%\win10\sources\install.wim /postoobe %systemdrive%\KACE\setupcomplete.cmd /noreboot /dynamicupdate disable


(Just make sure the KMS or Real key is correct)

https://docs.microsoft.com/en-us/windows-server/get-started/kmsclientkeys

Also, please have a look at https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-command-line-options


Works for me, hope it works for you!






Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ