[DISCUSSION] Windows 10 1903/9 'FINAL' Build 18362/3.xxx (PC) [19H1/2 Release]

Made my day.

 

@Wonder Woman : .svf file repositories are the result of the great effort / time put in by our seniors / colleagues. They are fully genuine / authentic & every .svf file has an exact check sum value. Besides, you can always compare / check the ISO's check sums ( sha-1, etc. ) with the original check sums.

( To say briefly : An .svf file is the exact difference file which was recorded between the two pure / genuine ISOs ( base & target ), with the help of SmartVersion Tools .
When you take a base ISO & use the corresponding .svf file(s), you can make the target ISO. You will need to use a tool like SVF eXtractor by @GezoeSloog )

Thanks. ...

 

You need to login to view this posts content.

 

+
sha256 already

 

Due to the lack of a laugh reaction, I'm liking this comment.

 

You need to login to view this posts content.

 

Thanks for your brief explanation.

You know what? SVF eXtractor by GezoeSloog has been flagged as malicious by five engines on VirusTotal.

GezoeSloog should have provided us the source code of said extractor.

 

You need to login to view this posts content.

 

I'm not surprised. Why?

SHA-2 family of FIPS 180 is susceptible to checksum collisions.

 

Did you mean that I could always compare the checksums of the Franken-ISO with the original ISOs released by MVS?

Won't it be easier to just download the target ISOs from MVS?

 

Let's consider the following scenario:

1. I downloaded the ISO released by MVS in April.
2. There are two updates released by MVS in May.
3. I use SVF to apply the May updates to the April ISO.
4. I have a Franken-ISO that has the May updates.
5. I compare the SHA-1 hashsum of the Franken-ISO with the May ISO released by MVS. Their hashsums must be identical, right?

Won't it be easier to just simply download the May ISO when it's released by MVS? After all, I need to compare the checksum of the Franken-ISO with the target ISO (in this example, it's the May ISO).

In addition, you wrote that an *.svf file is the exact difference between two official MVS ISOs (base and target). It means that someone already has in his possession the target ISO (released by MVS). Why can't he simply upload the target ISO to some free file-hosting sites? In my opinion, it's much easier and less time-consuming to just upload the target ISO than to produce an *.svf file and then share it here or on some websites.

The only scenario where applying *.svf files is advantageous is when bandwidth and download speed are severely constrained. I don't have these problems because I'm able to download a 5GB-ish ISO in just two minutes.

 

@Wonder Woman
the good think is that you learned something+ for the svf patchs

 

Do you have any idea how many ISOs he's supposed to download and then reload every month?

 

Hello,

Does someone have the official Windows 10 1909 May Update ISO + SVF ?

Thanks in advance

 

latest is (updated april 2020)

 

Well, if he's a superfast internet connection (I'm thinking of at least 3 Gbps speed) and unlimited bandwidth, he can download all the ISOs within 10 days, yes? Like 10 ISOs per day? (After all, MVS only releases the ISOs once a month......)

 

Just so you know.... I've read the tutorials on SVF patching many months ago and I thought it would be better for me to wait for MVS to release the ISOs. After all, I ain't in a hurry to download them. I download the ISO in case I need to reinstall Microsoft Windows 10 due to hardware failure.

 

MVS usually releases Windows 10 1909 ISOs (updated to May 2020) at the end of May. Just be patient.

If you can't wait because you need the ISO to reinstall your OS, you could reinstall it using the April ISO. When your OS is up and running, use Windows Update to download the latest security fixes. That's what I would do if I were you.