[DISCUSSION] Windows 10 Enterprise (N) LTSB 2016

Thank you Where can I find checksum for:

en_windows_10_enterprise_2016_ltsb_x64_dvd_9059483.iso
en_windows_10_enterprise_2016_ltsb_n_x64_dvd_9057894.iso

 

The tool checks them when the iso is done downloading and creating.

 

You need to login to view this posts content.

 

Now i think , I can grab the new ISO provided by the svf2iso and normally use RUFUS to prepare my usb and voila install windows, disable antivirus then just KMS PICO? and thats it ?
If so thanks to everyone here for the fully support you guys rocks

 

Yep, should work that way .

 

Just format the USB FAT32, extract the ISO to it, and use KMS_VL_ALL v25

 

You need to login to view this posts content.

 

Just format the USB FAT32 in windows explorer, if you never used any of the other methods it works fine, it will be able to boot uefi and legacy bios.

 

Thank you by the way I didn't know that i could activated the iso itself with KMS server? before the first boot of windows which is amazing

so all i need is to put the KMS_VL_ALL.cmd in the flash drive along with the Microsoft windows 10 iso files, and just runs the batch?
And then just reboot pc and boot from Flash drive, and my Windows will be pre-activated, and it will have 6 months period?

Thanks im quite noob on this.

 

You need to put the $OEM$ folder of the KMS_VL_ALL v25 zip in the "iso:\sources" folder, and when you use a consumer OEMRET iso you need to also put an ei.cfg in, but the 2016 LTSB iso already contains an ei.cfg, so all should work.

But this is the svf repo, not to be used for kms support.

 

And what about If Just skip the KMS_VL_ALL? and skip the serial installation, and normally disconnected the Ethernet cable, and disable antivirus and run the
https://forums.mydigitallife.net/threads/kmspico-official-thread.65739/?

Will it reduce windows performance? would be better the KMS_VL_ALL like you explain?

Thanks sorry for making many comments don't want to fatigue you or the community, english is my second language, so sometimes It took me a while to properly understand.

 

KMSpico will run fine, no matter if the install is online, does LTSB ask for a key?

KMSpico seems to be abandoned and not uptodate anymore for the more current sku's and scenario's.

KMS_VL_ALL by @abbodi1406 is the most uptodate and fast supported KMS solution ever.

 

I don't know if ask for a key haven't yet formated my hard-drive was trying to properly prepared everything before, I ended up copiying the $OEM$ folder and thats it, i will now try the windows 1607 after all to see if ask me for a key at the very beginning. xD

 

LTSB is VL install and doesn't ask for a key.

 

This is so good, everything seem smooth and is pre-activated with your help guys, thanks alot.

By the way, should I use cummulative updates via Microsoft Catalog? or just regular updated through microsoft ?
Cause i don't really like to use windows updating cause it will install automatic drivers, so I always ended disable the device automatic driver install via WIndows10shutup

 

The updates offered on Catalog are the updates WU offers too. Except sometimes catalog offers catalog only released updates.

 

You need to login to view this posts content.

 

I am curious what windows 10 LTSB 2016 can get Digital Lisense. Oem_COA_NSLP Channel for example

 

All Win 10 sku's can get a DL, not allowed to be discussed at MDL.

 

Ok, I understand not here, but I want to know more, where can I learn about this?

Also, does any LTSB key work on any LTSB release? I see very cheap 2015 LTSB keys on ebay, they would work with 2016, and the 2018 that is coming soon?
Thanks