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

cereberus said:

That will normally work. Put iso on sd card or flash drive to save space on pc.

It will use a usb flash drive as temporary space, but you still need around 4GB spare for it to work. My method was a last resort really.

Ahh, well, then - I have a 128 GB USB 3 Flash drive, so I am good to go.

But your methodology is still good for bookmarking if I ever come to a point where I need to do something like this in the future on a client's machine with similar issues.

f14tomcat said:

Maybe cause I changed the name? Stuck the (WU) on the end so I would know what the source was? Just a S.W.A.G.

Don't think that is gonna cause an issue.

The 1803 feature update I downloaded Tuesday and the one I downloaded today are the exact same size to the byte, but have different names.

The IP 17133.1 I downloaded 28 March is significantly smaller (close to 1.4 MB), and it never had a name change, so the name change is not causing the difference in bytes.

slicendice said:

That sounds a bit weird.

I just checked 17133.1 Pro EN_US x64 for the 2 different releases available via UUP-Dump and the file hashes match 100%.

johngalt said:

You downloaded both of them made an .ISO and checked them against each other?

That's what I am about to do (well, I can't re-download the one from 3 April as that is the same name as the current 1803 listed, and the file size is identical but a different hash).

The other 17133.1 I should still be able to DL and make a new .ISO

OK, redownloaded the IP 17133.1 build. First off, as the .ISO is built, I have to say that the byte size for both today's 1803 feature update file dump as well as the IP build file dump is identical 5,148,559,663 (all editions, En-US and x64).

Now let's see what happens with the resulting .ISO.

johngalt said:

You downloaded both of them made an .ISO and checked them against each other?

That's what I am about to do (well, I can't re-download the one from 3 April as that is the same name as the current 1803 listed, and the file size is identical but a different hash).

The other 17133.1 I should still be able to DL and make a new .ISO

No I only verified the hashes from UUP-Dump. It lists all there before you press Download. The same information is in the cab or .json files...or wherever they get stored during update.

slicendice said:

No I only verified the hashes from UUP-Dump. It lists all there before you press Download. The same information is in the cab or .json files...or wherever they get stored during update.

Yeah, and I verified by file size and a side by side compare of the directories for each dunno. All file sizes are identical as well.

I have a theory, just trying to prove it now.

slicendice said:

No I only verified the hashes from UUP-Dump. It lists all there before you press Download. The same information is in the cab or .json files...or wherever they get stored during update.

Also, I use those same hashes to run a second check after downloading via miniserver. But until now I have been deleting the dumps and the hashes that I save into a file named 0.sha1 to check the individual files.

I may need to keep them until I get this figured out, assuming my theory is proven incorrect.

First issue, and if my memory serves me well, someone else did already mention this very same issue for latest Builds!?

I have Bluetooth Connection/Disconnection problems. My BT headset connects fine and Windows gladly tries to play sound, but no sound comes out. The bars are however moving. A few seconds later the headset disconnects and turns off.

Anyone else having this issue?


More Info:
I am on Intel Bluetooth drivers. Tried 3 versions already, and same with all of them. It sounds to me like an Audio re-routing issue. My main audio is some Realtek chip (RTL HD Audio), and works fine from speakers or wired headphones.

johngalt said:

OK, redownloaded the IP 17133.1 build. First off, as the .ISO is built, I have to say that the byte size for both today's 1803 feature update file dump as well as the IP build file dump is identical 5,148,559,663 (all editions, En-US and x64).

Now let's see what happens with the resulting .ISO.

Both .ISOs from today, one of the IP build and one of the RP build, came out to the exact same byte length. But they have different hashes.

I still have the files I downloaded from earlier today for the RP build, so I am going to make another .ISO of it and check the hash - I suspect I know what is going on, but I'll be sure in a few minutes.