/build/static/layout/Breadcrumb_cap_w.png

Sysprep Creator ERROR with Windows 10 build10586.218

Hi All After doing all the windows 10 latest updates I have a error saying *Windows upgrade was detected... Any ideas how to fix this or is there a newer version of Sysprep Creator ? I have v.3.7.2.1 ...

1 Comment   [ + ] Show comment
  • Same problem here. Installed windows 10 and was able to sysprep fine. Create a new vm, installed windows 10, did update after update and suddenly I had a windows.old folder. cleaned up unnecessary files, deleted windows.old - try to sysprep and get Windows upgrade was detected. It's got to do with the updates. Need a fix. - smf 7 years ago

Answers (4)

Answer Summary:
Posted by: cserrins 8 years ago
Red Belt
3

Top Answer

For some reason, one of the big updates for Windows 10, forces it to be considered an upgrade.  I don't know why.  It is recommended that you build your image from newer media that already has the update in it.
-Corey
Posted by: nheyne 8 years ago
Red Belt
0
Is it an upgraded OS?  If so, then building an image from it is both unsupported and not recommended.  However, there is a reg workaround:

http://www.harrycaskey.com/how-to-run-sysprep-on-an-upgraded-operating-system/
Posted by: psaussey 8 years ago
Blue Belt
0

Hi

Not an upgrade from Windows 7 or 8.1, I installed Windows 10 and then did the updates...

thanks

Posted by: DLCurtis 8 years ago
Purple Belt
0
Any update on this one? I have done a clean install of Win10 ent. Ran updates and then tried to sysprep but got the same error.

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