New
#60
Thank you for your continued support fg2001gf10F.
The PC that was on 18363.10024 is now back to 18362.10024 which I don't think will cause any problems with updates. Unfortunately I was idiot enough to put the earlier Insider 18362.10022 on several other machines and with further 'tinkering' they are now 18363.10022. I have tried the same tricks with one, but I cannot uninstall the 1909 features update as the drives have had Disk Clean-up run. I have tried many fixes I found over at MDL Forums but sadly they have not helped. Furthermore, the upgrade to 18683.418 will not work on any other machine (it only offers a clean install).
I know only too well that I should have imaged the drives before messing about with Insider installs, but I didn't anticipate these sort of problems with unknown builds happening.
Ho hum. I moved my daily driver to the RP ring on Thursday and got 18363.418, Friday 18363.446, and today 18363.418. I wonder what will come tomorrow.
18362.10024 why they release this for 19H2 if now is 18363.446
If you use the 18363.448 ISO to upgrade from 18362.10024 and allow check and download updates online, you may end up with different results depending on which insider ring you are in.
1) If you are in the Insider Slow Ring you will end up with 18363.10024 and that may not be your desired result.
2) If you are in the insider Preview Ring you will get to 18363.448.
I had to switch Insider ring from Slow to Preview and then the online upgrade worked as case #2 going from 18362.10024 to 18363.448.
I did not have any problem using windows update to go from 18363.446 to 18363.448.
If you are in the Preview Ring you should be already at 18363, 19H2 why did you do a clean install of 18362.446 instead of 18363.446 ?
Perhaps you can download the 18363.448 ISO and do the upgrade again ?
I'm not clear about which Insider Ring still handles 19H1 18362.446 or 18362.448 ?
Yes it worked . But a lot of work to download, convert and then make an ISO, installing windows (keeping all settings and programs), reboot a lot of times . But now I'm with you at 18363.448 (don't tell me, that yours is now 18363.449!!!)
This time Microsoft has made a mistake with all this confusion about buildnumbers, it looks more and more like Brexit here in Europa