in 99% of the cases the higher nr will be the newest, so i assume .37 is newer then .36. We mostly handle MVS ISOs, the ISO filenames you show are VLSC ISO filenames, these are the latest win 10 MVS ISOs: https://forums.mydigitallife.net/posts/1894300
That 22H2.36 and that 22H2.37 have the same version 19045.6456. It was 22H2.37 that reassembled them and signed them as November ones. Not only are the October 2025 updates integrated, but the 64BIT and Arm64 distributions are also mixed up in places.
KB5072653 is for Win 10 22H2 only (although can be installed on any 1904x build) KB5072653 has nothing to do with WinSxS
Hi, Use "Disk Cleanup", on your C: drive, and then click "Clean up system files" to find and remove old update files. Spoiler The process may take several hours to complete, on such big old update caches. My two cents. Thank you.
Then i would suggest to look around in this thread, what it is mostly about or at least look at the thread title
It's a way to patch one file into another version using only the tiny difference between two versions. So can you can "update" one ISO from one version to a later one by applying only the usually tiny difference. When this was started on this board many years ago it was called delta files if I remember right.
@Tito A lotta dead links @ https://forums.mydigitallife.net/threads/windows-10-svf-repository.63324 And https://forums.mydigitallife.net/threads/smartversion-tools-scripts.79415 (if you like to add) Kind regards
The svf.dll is not needed, you have smv.exe locally and that should be sufficient. Try to put your images in same folder like this(i think this is holding you up), delta's will be stored in svf folder (SmartVersion folder with my smv.exe here is reflected in my ini, by default it's only smv.exe) If smv.exe is not found locally(look at path in your ini if this is somehow changed), it will try Program Files\SmartVersion\smv.exe You can add a folder named SmartVersion with smv.exe to this location so you don't have to install SmartVersion