Created the following iso in a vm using uuptoiso. That was when this thread was first posted. It would appear this the correct RTM? I will look into installing it on my hard drive and then imaging it if no further builds are expected. Actually Wzor posted this was RTM on 9/19.
17763.1.180914-1434.RS5_RELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US.ISO
Last edited by martyfelker; 26 Sep 2018 at 03:56.
few tech journalists on twitter are saying they planning to release October update next Tuesday the 2nd surely would been announced by now if was going to be released then
Arghhh - what a disaster. I upgraded my main laptop to 1809 Insider and my secondary ssd got totally nuked! Drive was not recognised by any version of windows or Linux, Winpe etc.
I thought drive had failed as everything sid "drive not ready, size 0 bytes" etc.
However I could access it via diskpart, used clean etc. and drive is still accessible. Am currently running Recuva, and it looks like I will be able to recover my main files. I also had a backup offline of C drive and restored that to 1803 - little out of date but main apps all thre - just need to do a few updates. Fortunately no critical data lost as I use Onedrive for saving that.
Hi there
UUPDump or UUP (Unified Update Platform) Generation Project (v2.4.2_RC) [by @RGAdguard & mkuba50] IMO are the best ways to generate the ISO.
Then I simply use WintoUSB to install to an external USB3 ->SATA connected SSD and test.
From WintoUSB choose install windows and point to the ISO. Target disk will be the ssd.
In the middle of installing the Windows - will see what happens with a boot later.
I find where possible testing these on real hardware is a lot better than trying with VM's -->also using external SSD's means that if they don't work -- no probs (OK with VM's you can delete them too) but with an external ssd you can boot from different machines easily too to test drivers etc. So long as the machines have a digital license - no probs attaching the SSD to different computers - windows update finds any necessary drivers on the whole and activation is preserved.
Note - you can't update to a "WintoGo" type of device so you will have to re-install existing programs.
However a way round that is to
1) Backup existing W10 (non Win To Go)
2) do the update
3) use wintogousb to create wintogo windows on ssd "cloning existing system"
4) restore original system
5) boot external ssd. (it's possible you might need macrium to repair windows boot one or 2 times --generally I find it works first time.
Cheers
jimbo
Took ISO made on 9/18 on my insider machine and ran setup on both 1803 machines. They didn't care that it was an Insider update they both just updated with no problems. Both seem to be working just fine.
Quote
