No clue regarding Rufus (didn't use it for quite a while) . If you are checking for LTSC, the latest is SW_DVD5_WIN_ENT_LTSC_2019_64-bit_English_MLF_X21-96425 which is 17763.107. en_windows_10_enterprise_ltsc_2019_x64_dvd_74865958 is 17763.1 (aka the vanilla 'RTM' release).
@s1ave77 I see, thank you for the swift response! Would you say using the 17763.1 is fine (I'll be able to update it after installing it, correct?) or should I try to download the 17763.107 one from another source? @Sajjo Thanks for the link! I was mainly torn between FAT32 and NTFS since I've read that FAT32 can't format some USB drive sizes.
No problems for fresh installs, but the vanilla still has the file-deletion-bug when upgrading from an older build. EDIT: In case there are no peronal files stored at Windows default locations (i prefer to have NO personal files on c:\ and don't even let Windows control them) the upgrade is fine though, i had no problems at all.
Hi All I've tried downloading again with my AV turned off and no other security software running and I'm still getting a checkhash mismatch error, not sure what I'm doing wrong. Any advice please. Thank you
Getting issues with LTSC19_2_VLSC/standard/consumer/eng-gb/x64 Makes the ISO image SW_DVD5_WIN_ENT_LTSC_2019_64-bit_English_International_MLF_X21-96427 However during a fresh install windows flags up "something went wrong" messages for the following... OOBEKEYBOARD OOBEZDP OOBEISPS Thought this could of been a corrupt D/L so re-downloaded but same messages flagged up, any idea's why? Thanks.
I just got the OOBEREGION error during setup of my uptodate 17763.253 AiO testing, after selecting/signing in at the network part of the OOBE, i started reinstalling the same sku and all worked at the second attempt. As long as the ISO sha-1 is correct, it's not the tool causing it.
Hope this helps SVF tool is fine and the Rufus partition / target system selection very important. On a Test bed just used Rufus version 3.4.1430 on this ISO medium SW DVD9_Win_Pro_Ent_Edu_N_10_1809_64-bit_English_International_MLF_X21-96503.iso from the SVF ISO Converter tool version 0.32.01. No errors and installation It comes out brilliant and activated up and running.
@nothyn if not late --- Rufus partition system if GTP or MBR and machine depending how old BIOS or UEFI, Using minimum 8GB USB drive FAT32 default and cluster byte 4096 and don't forget secure boot option during installation
Press M for "My Visual Studio Downloads" and then "[7] START LTSC 2019 PROCESS [17763.1]" -- x64 -- 0 - 8 (for english) -- S for start download, then this I got the 1809 December refresh consumer/business x64/x86 no problems so I assume it's not an issue on my end and there's a typo in the script somewhere?
@Agret I downloaded images with no errors, I used same CMD version as you did. [HEADER] LTSC 2019 SVF ISO CONVERSION [ INFO ] Source: 17763.1.180914-1434.rs5_release_CLIENT_LTSC_EVAL_x64FRE_en-us [ INFO ] Hash : fba7f17ffdf018e4cffd49a9819d719d3708cf09 [ TO ] [ INFO ] Target: en_windows_10_enterprise_ltsc_2019_x64_dvd_74865958 [ INFO ] Hash : 0b8476eff31f957590ade6fe671f16161037d3f6
Not done installation on testbed this morning but iso hash clean so tool working as says on the tin with ltsc
Atm the SSD has still a MBR layout. Best is to delete all Partitions on the SSD and let it install on the unassigned space, it will create the correct partition layout.
Ohhh, didn’t know that possible, I tried formatting the SSD but it kept getting the same error so I never thought about deleting the partitions, haha. You’re a lifesaver, thanks so much!
If not late I believe you got through after the partition conflict. Just to add a tip if the machine stalls at restart before installation complete don't forget to change the boot option in setup for the SSD