[DISCUSSION] Windows 10 Insider Preview Build 17110 (PC) [FAST Current - RS4_Release]

Someone can explain this exactly ?

• We’ve updated the new notification to fix blurry apps so that it now will persist in the Action Center to be accessed later once the toast has timed out and dismissed.

 

They probably used the replicant old converter from tenforums

i'm OK with forking our converter (mine or adguard's), but for the love of God, at least keep up with latest version

 

I'm using your latest converter and I had issues reaching the installer on both of my devices

 

I always dual boot, so the easiest way for me to install is to boot into my other Windows 10 install, quick format the drive I want to install 17110 on, and run this command

Code:

DISM /Apply-Image /ImageFile:"path to install.wim" /Index:1 /ApplyDir:path to install drive:\ /compact

Then I reboot to finish the installation.

 

I did a clean install from usb using fat32 (win10 pro x64 en-us)
So far so good. Zero problems founds
Way better than rs3 imo.

 

Personally,
I use exclusively uup-converter-wimlib-14 & esd-decrypter-wimlib-37 acquired right here @MDLF

 

This build little boring. I had no problem with Store in this build.

 

I used "Miniserver-UUP-Master" to download the 17110 UUPs (x64 and x86) and created install.esd based ISOs for both using "uup-converter-wimlib-14". the sizes were: 3,631,687,680 bytes and 2,758,318,080 bytes respectively.

The X64 ISO fresh installed on VMWare Workstation 14.1.1 successfully.

However, the X86 ISO failed to upgrade on VirtualBox 5.2.8 and restored the previous build 17107. I increased the Hard Disk space and tried again, but faced with the same failure. I then formatted the Hard Diak and tried a fresh installation on VirtualBox, but it failed again (twice). So, I tried a fresh installation on VMWare, failed again.

I then used "uupdl-master" to download the 17110 x86 UUPs and again used "uup-converter-wimlib-14" to create install.esd based ISO. this time the size was: 2,759,026,688 bytes.

It has just finished a fresh installation on VirtualBox successfully.

 

Let's mention @mkuba50 for an opinion, but actually both solutions use/share the same API to determine the needed files .

 

@s1ave77 is right, both solutions use the same base to fetch needed files. I'm not sure even why ISO got correctly created by converter if something was missing.

 

That was the thingie puzzling me like fleas in my fur .

 

new buildinfo:10.0.17112.1 (rs4_release.180227-1537)

 

If you are trying to say this build is about to be released, it was compiled yesterday.

 

no i never say anything im sharing the info only..

 

I re-downloaded X86 UUPs using "Miniserver-UUP-Master" again, they came as 22 files and total of 2,009,044,932 bytes, the same as with "uupdl-master" !!

I am recreating the install.esd ISO using "uup-converter-wimlib-14" to check the total size again (obviously they should be identical, but I will still do it).

Well, that's wierd, it came as 2,758,645,760 bytes !!??

 

Damn you. No i have that picture of a rotten corpse grinded as comic...

 

You might complain at MS for inconsistencies .. i refusew to be held responsibble. I draw the 'ZONK' at WU servers.

 

I was suspecting the problem may have been caused during Microsoft repositories replication or possibly the download process, also it may be the compression process.

I have changed the "7z.exe" and "7z.dll" dates 04 Oct 2016 in "uup-converter-wimlib-14/bin" to the latest from 7zip18.01, dated 28 Jan 2018 and reproduced "17110.1000.180223-1515.RS4_RELEASE_CLIENTPRO_OEMRET_X86FRE_EN-US.ISO" again from the same UUPs downloaded by "Miniserver-UUP-Master" and got the size (2,758,731,776 bytes).

I will see if it installs.

Update:

It fresh installed fine..