New
#500
Understand that- so could you add some clarification and state that there is no official source from which to download older iso's, and therefore people using older builds and wishing to retain them should NOT use the media creation tool.
This became confusing in a couple of threads where I quoted your tutorial, forgetting or not noticing or asking if they were using 1511.
Any better solution? Thanks!
hello Brink
thanks a lot for your useful threads.. you are a legend.
Following up on the question by dalchina, does it matter which the 'sub' build of the iso needs to be? e.g. it was created with 10586.xxx and your system has been updated to 10586.yyy in the meantime?
Plus, what would be a use case/advantage to do a repair install when anyway one would update to higher build (e. g. AU) right after?
Thanks in advance!
Why repair install an older build e.g. 1511 and keep it? Some people simply find problems with 1607 insuperable (could be hardware or even incompatible programs - perhaps pending update) and so want to stay with what works for them, sometimes in the hope that at some point in the future they can try upgrading when things are more stable or appropriate updates have been applied- or maybe when they have time to try to deal with issues.
Hello GalaxyGe, :)
I would recommend to upgrade to the latest build. If your Windows installation is too badly messed up, then you might consider clean installing to the latest build instead. Be sure to back up first though.
I have 1511 installed and hit the issue with a couple of updates not installing so I can't install the Anniversary and follow-on upgrade so, using the Media creation tool, I created the Win 10 Home/Pro x64 v.1607 USB stick to perform an in-place upgrade/repair.
Perhaps I missed this part reading through this thread; once you wade through the option selection process (keep files, apps, settings) and it starts the actual upgrade/repair, when do you remove the USB stick to prevent the PC from booting from the USB on restart?
Note: It's currently at the "Checking for updates" stage as I type this.....
TIA!