KB4100375 Windows 10 Insider Release Preview Build 17133.73 - Apr.10 Insider

Dave44 said:

you wont get it you all ready on 17133.1 they exactly same builds

Thanks. I surmised as much-but thanks for verifying

magilla said:

I have 3 systems set to Release Preview Ring and nothing has been offered. But, Dona said that not everyone on Preview Ring will be receiving this. So, maybe some of us must be content with having 17133.1.

Thanks. Couldn't tell from the OP's specs or anything, thought maybe just an error.

tracit99 said:

This is what Dona said when RP was released:
Not all Insiders in the Release Preview ring will be immediately targeted to receive this flight. We are targeting full availability to Release Preview Monday 4/9 however if you’d like to install immediately, a manual check for updates under Settings > Update & Security > Windows Update will present the build.

I do not know if this works, but it might be worth a try.

I had one RP build update that came automatically shortly after booting the OS, and one I got after a check for updates, after waiting 15-20 minutes and nothing.

tracit99 said:

This is what Dona said when RP was released:
Not all Insiders in the Release Preview ring will be immediately targeted to receive this flight. We are targeting full availability to Release Preview Monday 4/9 however if you’d like to install immediately, a manual check for updates under Settings > Update & Security > Windows Update will present the build.

I do not know if this works, but it might be worth a try.

Does not work—-24hours after changing to release preview ring and several restarts later

I did some checking. I used the exact same file repository I had downloaded yesterday to conduct my tests. I have the files for the IP 17133.1 and the RP 17133.1.

I used UUP2ISO to make 2 .ISOs of each set of files. None of the mashes matched. In addition, 1 of the ISOs of the IP build had a different file size.

So, I went back and made 5 .ISOs using the IP build files. 4 of them had identical file sizes (and names, as I moved them to different drives) but none of the file hashes were the same (and I took the hashes prior to moving the files, so each hash was conducted in the UUP2ISO folder on the generated .ISO prior to moving, then verified after moving).

Sooo....All I can do now is to make sure that I keep running a second verification process on the downloaded files to have an independent verification of the files, and after that I build and .ISO and test it to make sure it boots and installs (into a VM, perhaps).

I'm perplexed why the UUP2ISO process would not produce the same results every time, but I have the empirical prof now that it does not produce a byte by byte complete copy.

I put this here as it was 17133 specifically that I built and rebuilt many times. I've also made mention of it in the UUP2ISO tutorial thread, and will continue discussions there.

johngalt said:

I'm perplexed why the UUP2ISO process would not produce the same results every time, but I have the empirical prof now that it does not produce a byte by byte complete copy.

My reply in UUPtoISO tutorial thread:

Kari said:

This is simple: Do your ISO images created with UUPtoISO work? If so, I do not see what's the issue?

I've done some tests with file hashes, for instance zipping a folder and checking it's hash, then zipping it again and getting a different hash. Nothing special, both ZIP archives can be used and extracted, producing the same content.

If you have any doubts and think that there's something wrong with this, an easy solution is to create ISO images with another method and tool and not use UUPtoISO. I've not seen / made an ISO with UUPtoISO that has not worked. To be totally honest, I've never even checked file hash of a self made ISO file because I feel it completely unnecessary.

Kari