New
#110
In addition to the reason given by f1tomcat, you can get that if you try to upgrade using an ISO with a different language from that of your existing install.
Another reason would be if you run the wrong Setup.exe. There are two, one in the root of the mounted ISO and another in its Sources folder. They are different, you must use the one in the root to do an in-place upgrade.
Hi folks
@f14tomcat
I haven't found that a problem (update from earlier build).
I've been able to install a UUPDUMP created iso as an update from much earlier builds to the 1903 one.
Have people actually TESTED the possibility before they post the information. that it can't be done !!!!
The last one I did updated perfectly OK from a 18xx Build to the 1903 build via UPDATE (not clean install).
What you CAN'T do is "Update" from a later build !!! i.e update a 1903 build to an 18xx build !!!!!!! which should seem obvious enough
Cheers
jimbo
That is precisely what I said. You read it backward.
"That's normally the occurrence if you mount an ISO of an earlier build and try to do an in-place upgrade/repair by clicking setup.exe. System will not let you go backwards in that case. Only current build or later can be done via the in-place."
Thanks for the notifications. I came back home after a couple of weeks away to find update downloads, installations and re-boots going bananas. All seems sorted now with WinVer showing Build 18362.267.
Thanks Bree I think that you explained why I had one particular problem i.e. I was installing a different language version.
Why I was doing this is because I had so many failed attempts fo downloading builds from UUP dump site where losts of files could not be found when it was trying to build an ISO image I thought that instead of installing the UK English build that I nornally do I thought that I would give the US English version a try.
I still have no idea why the UUP dump acript can't find losts of files when it tries to build the ISO!
I'm about to pull my hair out. I noticed a few days ago that the latest update (KB4505903 ver.267) had failed and I've been running through all the options I can find to get it to install. I've run sfc, DISM, storage sense cleanup, tried manually installing both the .msu and the .cab files. Nothing works.
I'm wondering if it's worthwhile to wait until the next update comes along to see if it will install, or go ahead and do an in-place upgrade. I'm also a bit confused as to whether or not a repair/in-place upgrade will nuke my installed programs. Any suggestions?
No, Repair Install (in-place Upgrade) won't nuke your Apps or Data files. They will be kept. Make sure though you have a recent system image backup (incremental or differential) to be on the safe side.
Edit: Also check the referenced link in post # 102 to see if you are OK with the related issue about Old Intel Storage drivers.
RST drivers don't seem to apply to Surface devices, so at least I can rule that one out.
As for the Repair Install, jog my memory, can that be done from System Recovery, or does it have to be initiated via install media?
EDIT:
Nevermind. I answered my own question. That's what I get for posting before searching.