Windows 10: Announcing Windows 10 Insider Preview Fast Build 17123 - Mar. 16

Perhaps we're all getting bored *Smile

 

Just a bit of banter as we are all bored with 17123, and are awaiting the day we get no watermark, then we can all speculate whether this is the official release.

Actually I know one former UK dependency that has decided to move from left to right but cannot afford to change all the system in one go, so they have decided to phase it in with lorries and vans in 2019, followed by cars in 2020 :-D.

 

We could play the now traditional "guess the final build number game"?

 

It will not be 17123.1 from what I hear the final release build will be out on 3.25 with it going to the public on 4.25.18,,But rumor control can be wrong.

 

I said ages ago 10/04/18 as that is day AU becomes unsupported.

 

I know but I do not see the connection to what I posted about when The SCU build 17123.1 will become final??

 

Does it have to have a connection?

My logic is that when AU finishes, MS would want to update them immediately and it would not make sense to update to FCU and then reupdate two weeks later. Still a pure guess like anybody elses.

 

MS may want to but I think the end user still has a choice.*Wink

 

Well, I have tried every trick I know to get 17123 to clean install as a dual boot host option. I have tried following - I turned off secure boot as well.

1) creating bootable flash drive using mounted drive/fat32 - even making partition active

2) Rufus

These would not boot at all from usb drive - just the perennial circles

3) copying install.wim to a FCU installer - got further but fell over later with language problems

4) copying FCU boot.wim to flash drive created by 1 above - failed with some missing driver

5) Copying install files to a hard drive, and creating boot entry - failed like 1&2

6) Running FCU and running setup from sources folder - got further and looked good until it rebooted and the dreaded circles

7) Installing 17123 in a vm, and attaching vhd to host - just goes into a reboot loop

8) sysprepping 17123 vm install, and attaching vhd to host - failed same as 7

The only option that worked was to install 16299 and upgrade but that was not what I wanted to do.

I then tried same with official Slow Ring iso - same problems.

I am certain it is a driver issue but have no way if working out what!

 

That was the only way I could get it to install as well.

 

Interesting - problem is MS will not recognise using iso as unofficial and will not investigate.

 

They are probably concerned that the ISO may not be authentic? But if you download it from MS how can it not be??

 

I made the 17123 manually but it still failed with the latest slow ring version which is authentic.

 

Every 17XXX build failed for me using an ISO. I gave up on it for a few months and stayed on The FCU. Then I ran sfc and checkdsk and all was OK so I tried using WU and Build 17115 installed the first try. Maybe it will only work as a clean install.. I don't know..

 

Well Kari--I hate to disappoint you but yesterday I downloaded your latest UUP to iso version 4.00 onto my computer and having installed it, I used it to create an x86 iso of build 17123. I used that iso to clean install that build but it would direct me to keyboard selection instead of the installation screen. The only clue I can give you is that while creating the iso the software pauses after creating the boot.win file and then says" access denied". Kindly guide me.