Hi, I'm converting an enterprise eval. to normal iso (17763.107.101029-1455.rs5_release) but I got two different ones here: cliententerpriseeval_oemret_x64fre and serveressentials_oem_x64fre Which one do I choose, if any difference at all ? I must admit I'm still on win7 and know near to nothing about these procedures for win10 deployment. There's so many different versions it's a bit confusing. I'm just gonna play around with win10 in a vm for a while, see what's what, and try to get 'a bit' up to speed with it. Meanwhile I understand I can download and convert an enterprise eval to normal iso, and then activate through kms, so I'll try that first, but so which one of the above should I use ? Thanks a bunch.
Can't be converted to non EVAL. Why don't you just download the MVS ISO? Or use UUP (doesn't work well on 7).
That's weird cause I just did it for both of them with s1ave77s svf2iso converter... both are in the list and download...
That's not really converting but the only option that works, i only wonder where you got the eval>full svf patches from, they are not available anymore.
Nowhere, I downloaded the evaluation iso from ms, then copied it in the same folder with svf2iso.exe, so that the download is skipped and goes straight to conversion. I hope I'm doing it right though...
You can use SVF2ISO for the svf>iso conversion, but it needs the en-US consumer iso as source iso (provided by @GezoeSloog at his cloud repo's). For more general info about the use of SVF files: https://forums.mydigitallife.net/threads/smartversion-tools-scripts.79415/ My personal tutorial: https://forums.mydigitallife.net/threads/smartversion-tools-scripts.79415/#post-1517617
I'm sure I'm missing something because the svf2iso doesn't do anything when I put in the source and svf name. Both are in the same folder as the exe. I'm also looking at using svfx through your tutorial but when pointing to the iso it doesn't find it, although it is there.
Don't know if that's the cause and svfx is made by @GezoeSloog, but could be the spacings in the filepath.
I think I found the cause...I accidentally took the x86 consumer in stead of the x64, so the source was wrong... I'll try this again when the correct iso has downloaded. EDIT : it's working now