He showed the "points" very clear, didn't he? SVF patches of over 1.5GB are going to take huge amounts of filehost space (50-60GB instead of the current max. size of approx. 12-13GB), per architecture and thats only for the Ultimate ISO's.
Step by step, just talking about 1 iso. (btw mega.nz give u 50gb for free each account) So you actually dont want? I dont get why you say "maybe i will try".. Whatever... I would help if I could.
You do know the tool uses my SVF files? Do you have TB's of ad/malware free filehost space to host over 1TB of svf patches?
Please don't take it bad, we are just talking about different things, I would not even say its because of my English. I can just repeat myself as I did multiple times in above, not worth at all... Just let me say: I thank everyone here for help. And yes, I know you are helping, too. Lets make a point here and end this discussion.
Just tested, works perfectly here. Make sure no Antivirus or Firewall is interferring with the download of the SVF.
Kaspersky never gave me problems generating ISO but I deactivated it and it worked, should have thought of it before writing the post, sorry. Thank you guys
Today I tried with the two following versions and both gave mismatch errors for EVAL ISOs. What might be the issues? Code: 11:18:45 Language: en-us 11:18:45 ISO Name: en_windows_server_2019_x64_dvd_4cb967d8 11:18:45 ISO Hash: 2047f4e9fe2894f138395f3fac037c007dd1493e 11:18:45 EVAL Name: 17763.107.101029-1455.rs5_release_svc_refresh_SERVERESSENTIALS_OEM_X64FRE_EN-US 11:18:45 EVAL Hash: fbb32c6761640640e48d1652225e6af117eae0ad 11:18:45 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 11:18:46 Downloading EVAL ISO... 11:44:16 EVAL ISO exists. 11:44:16 Checking hash... 11:44:16 Check Hash: ࣘ | MISMATCH! Code: 4:32:59 Language: en-us 14:32:59 ISO Name: SW_DVD9_Win_Pro_Ent_Edu_N_10_1809_32-bit_English_MLF_X21-96500 14:32:59 ISO Hash: bdeb8f7867cb8dc9bf14869d621ad9b94fa01e3c 14:32:59 EVAL Name: 17763.107.101029-1455.rs5_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_en-us 14:32:59 EVAL Hash: eee2167b0ea9fe9654357c06d44a9c44eff62f1d 14:32:59 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 14:32:59 Downloading EVAL ISO... 14:50:11 EVAL ISO exists. 14:50:11 Checking hash... 14:50:11 Check Hash: ᔌ | MISMATCH!
Not Working for Windows Server 2019 Process 2 [17763.107] Code: [HEADER] SERVER 2019 Oct Refresh SVF ISO CONVERSION [ INFO ] Source: 17763.107.101029-1455.rs5_release_svc_refresh_SERVERESSENTIALS_OEM_X64FRE_EN-US [ INFO ] Hash : fbb32c6761640640e48d1652225e6af117eae0ad [ INFO ] Target: en_windows_server_2019_x64_dvd_4cb967d8 [ INFO ] Hash : 2047f4e9fe2894f138395f3fac037c007dd1493e [ USER ] tart or ack ?: S then it gives [HEADER] SERVER 2019 Oct Refresh SVF ISO CONVERSION [ INFO ] Source: 17763.107.101029-1455.rs5_release_svc_refresh_SERVERESSENTIALS_OEM_X64FRE_EN-US [ INFO ] Hash : fbb32c6761640640e48d1652225e6af117eae0ad [ INFO ] Downloading Source ISO (if not already pesent). Compressed 2 txt : r85decode _temp~ ... Microsoft (R) File Expansion Utility Copyright (c) Microsoft Corporation. All rights reserved. Adding .\_temp\aria2c.exe to Extraction Queue Adding .\_temp\busybox.exe to Extraction Queue Adding .\_temp\CURL.EXE to Extraction Queue Adding .\_temp\smv.exe to Extraction Queue Expanding Files .... Expanding Files Complete ... 4 files total. [ INFO ] Source Eval ISO present. [ INFO ] Checking Eval ISO Hash. [ INFO ] Hash : fbb32c6761640640e48d1652225e6af117eae0ad [ WARN ] Hash Mismatch [ INFO ] Hash : a7a18ee41ba5dc38e3390fb6abda9e1290fd343b Press any key to continue . . . the file 17763.107.101029-1455.rs5_release_svc_refresh_SERVERESSENTIALS_OEM_X64FRE_EN-US.iso was itself downloaded by this script at first phase.
I noticed MSFT defender being triggered by svf2iso, just allow it and recover it from quarantine if it happens.
Can anyone explain what's the significance of this? E.g. In the GUI tool I see LTSC2019 and LTSC2019_2 VLSC. Why is newer version in VLSC, not MVS? Also, if I download LTSC2019_2 VLSC I only get EVAL ISO. Is this normal? How do I convert it to non-eval?
Only difference between VLSC and MVS is the naming scheme. LTSC is Volume in both cases (only the IoT version is Retail by design). The process downloads the EVAL as source ISO, then downloads the SVF to convert to the chosen target ISO. Make sure your antivirus isn't interferring with the SVF download. Create an exclusion for the tools folder. Some of the used files tend to look suspicious since they download files.
The refresh 1809 MVS iso's have incorrect filenames, like 4 x en_ instead of 2 x en_ and 2 x en_gb, same for es and fr iso's. The VLSC iso filenames are correct, so we used the VLSC iso's. Content is the same.
having issues with activation after running scripts I get this message Key management service machine name set to *********** successfully then this error after ATO error: 0xC004C003 the activation sever determined the specified product key is blocked any help is appreciated!
This is not a thread about activations. The forum software seems to have blocked the kms server info, you posted, so i presume it's not a local kms emulator, but maybe post it in the tread of the used activation tool?
Considering it's not a broken feature that 2019 LTSC can't be HWID activated, i suppose the answer will be no