[TOOL] s1ave77s S-M-R-T SVF ISO CONVERTER v0.51.01 [1903/LTSC2019/Techbench]

[QUOTE="Enthousiast]


The content of the iso's can be found at the OP of the sticky 1809 thread[/QUOTE]

I don't see anywhere in the OP that answers the question of what choice of version you get to install?

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Check convo

 

You need to login to view this posts content.

 

@
Enthousiast

Ah, cool! That' so much better than the old Win 7 way of installing then. Excellent.

I've only ever updated Win 10 as a freebie 2 years ago, but wanted to do a fresh ISO install that can be activated using the KMS_VL_ALL-SppExtComObjPatcher-kms-28 method (1809 breaks MTK ) on a new PC, so this will be a new experience.

Thanks for the help mate.

One other quick question:

Does anyone actually bother with Windows Media Player nowadays?! I always use PotPlayer. So an Enterprise N install seems the way to go?

 

Never install N versions, it lacks more things then WMP only, N versions are not made as a feature but MSFT is forced to do, by EU law.

 

@Enthousiast

OK, that's good info, thank you.

 

Hi, I just used the new updated tool to convert up-to-date ISO. However, source and target is the same. It seems there wasn't any conversion.

This is the new screen:

Code:

[HEADER] 1809 [17763.194] SVF ISO CONVERSION

[ INFO ] Source: en_windows_10_business_editions_version_1809_updated_dec_2018_x64_dvd_f03937a3
[ INFO ] Hash  : 7153e3071366017a24c1fda22c0d1e486dbb0401


[ INFO ] Target: en_windows_10_business_editions_version_1809_updated_dec_2018_x64_dvd_f03937a3
[ INFO ] Hash  : 7153e3071366017a24c1fda22c0d1e486dbb0401


[ USER ] [S]tart or [B]ack ?:

And this is the previous screen with different target name and different hash:

Code:

[HEADER] 1809 [17763.1] SVF ISO CONVERSION

[ INFO ] Source: 17763.1.180914-1434.rs5_release_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-us
[ INFO ] Hash  : b8a6ffac9e15240c39f2ed2b16204341f564208d
[  TO  ]
[ INFO ] Target: en_windows_10_business_edition_version_1809_updated_sept_2018_x64_dvd_d57f2c0d
[ INFO ] Hash  : 0be4e80687d8d7eff8c80c5aa8c03b15e2f77256


[ USER ] [S]tart or [B]ack ?:

And with the new version, I don't have any .svf file in the directory after completing the process.

Thanks.

 

Seems you have selected to download the 17763.194 en-US business iso, then there is no conversion anymore, because it already is the source iso.

On 17763.1 we used the EVAL iso as source for the creation of the selected iso.

 

I see. Where does the script download the new target ISO from? MS servers directly?

I'd like to use this ISO to update my 1803 Enterprise by installing it on top of 1803. I also have KMSPico installed. Do I need a new KMS or the old man still work with the new version of Windows?

Thanks.

 

LTSB 2019? Well I guess some tech news sites were wrong by saying that the new LTSB (now LTSC...) will release in 2019, guess MS changed their plans...
Would be cool to mark the "LTSB 2019" build from MVS as something like "blocked by Microsoft" if it's the one that has the personal file deletion bug.

 

LTSC 2019 has been out for a couple months now, I'm running it. With the 2019 release they changed the name from LTSB to LTSC, branch to channel making the name convention more inline with the others. Initial release was 17763.1 which you can grab with the tool.

They did one refresh, but from what I understand they don't refresh the LTSC ISO regularly like they do the other ones. I just use the 17763.1 iso after updating the image offline with the latest cumulative update. Makes install.wim a bit smaller that way, trying to avoid splitting it.

 

You need to login to view this posts content.

 

Is the GUI version not updated yet?