hi edelberto someone said in the other post that the final rtm is 19041.264 but but when i install the iso en-gb its only 208 you only need to update to get the 264
This is not correct, nobody said that 19041.264 is final RTM, 19041.208 is supposed to be final RTM. 19041.264 is just a ssu/cu update released to the rp/slow ring (but it installs by WU on a running 19041.208 insttall, without being enrolled in any preview ring).
Yes And now please keep ontopic (SVF files), all other questions can be asked in the dedicated build threads
here the link where they said the 264 is the rtm https://forums.mydigitallife.net/th...19041-1-208-pc-20h1-vb_release.80763/page-126 scroll down till you find it many thanks
Too sad! I secretely hoped a MS-DOS 3.11 svf to en_windows_10_consumer_editions_version_2004_x64_dvd_8d28c5d7.iso Insert floppy #1 : a: format c: /u /q a: sys c: reboot Welcome to Windows 10, please take time to give us all. Hey Cortana !
@bwilkie2903 : Why did you make 3 consecutive posts for single lines ? P.S. You got help here & tried to give it back, that's more than enough for me! Thanks. ...
hi iam just new to the site ive not been on here for a long time and i have learing disabilities sometime i dont understand things
jus curious why it does not have EN_US #Consumer 2004 ? can i svfx.exe with EN-GB consumer and EN-US business ?
because EN_US Consumer used as source must check the svf patch what source (iso) used logical as source we use an iso most wanted , ex en-us
There is a way with SmartVersion or other external tool to extract an .svf patch file to see,manage, copy its contents ?
I mean, what's inside a .svf patch: the new files updated in full or just the binary differences between the files?