@bfoos It is the same tool, some refer to it as KMS_VL_ALL but the full name is KMS_VL_ALL-SppExtComObjPatcher-kms-28 (28 is latest version atm) Important is to difference between KMS_VL_ALL and KMS-VL-ALL (Underscores vs. Hyphens) KMS_VL_ALL use SppExtComObjPatcher.dll as activator KMS-VL-ALL use vlmcsd.exe as activator
The reasons why KMS_VL_ALL-SppExtComObjPatcher is better than qewpal's KMS-VL-ALL or any other offline KMS Activator, for Win 8.1 and 10 OS. This activator is based on SppExtComObjPatcher-kms (localhost bypass with built-in KMS) by @qad, AFAIK only this emulator provides instant activation whenever windows and office need it, without any activation scheduled task. And any other non SppExtComObjPatcher based kms emulator needs to have a scheduled task which runs on a specific date and time, to renew the activation. AFAIK only abbodi1406 made a proper script to use this patcher. The advantage of SppExtComObjPatcher is, (in 8.1 and 10) for example, After activating windows with the activator, if you later decide to install/change office in that case, the office will auto-activate itself, Hardware change, date change, windows, and office edition change, or any other cause of failed KMS activation, SppExtComObjPatcher will simply auto activate it. you do not need to run it again. Furthermore, abbodi1406 is the first one who incorporates the latest changes in the activator, and he provides the best support if there is a problem. That's why its the best.
True there is one downside windows keeps detecting the patcher trough windows defender hehe but you can make an exclusion for that so
Good morning, I would like to create an even slimmer version of LTSC 2019. What I would like to remove is: 1) System Apps which exist in LTSC 2) Languages that exist in system32/syswow64 folders 3) Useless drivers for me 4) Any other useless component for me I saw that 1 is done by optimize offline script but I am not sure if these stuff are removed from the image. Which other tool could help me to see all these options or as many options as there are? Besides of course going the dism way.
Thanks for the info. I use KMS_VL_ALL just for Office activation, I've yet to give LTSB/C a try and am currently using 10 Pro Education activated via HWID. Yes, it does create a scheduled task that is triggered every logon and it doesn't get picked up by defender. I guess I'll stick with it as it does exactly what I need. Prior to that I was using MTK's autokms as a scheduled task or service and I find KMS_VL_ALL to be a superior solution. But I can see based upon your detailed explanation that KMS_VL_ALL-SppExtComObjPatcher is the better option. When I get my SSD in a day or so and do a nice fresh install I plan on using it. Thanks again.
I´m on Window 2016 LTSB and unzipping KMS_VL_ALL-SppExtCombObjPatcher on the Desktop or any other place in Windows How curious! I´m on Window 2016 LTSB with Defender activated and unzipping SppExtCombObjPatcher-kms2 on the Desktop or any other place or folder doesn´t set off any alarm.
He probably meant the hook patcher itself, when running the scripts for activation with renewal. @abbodi1406 made the scripts to autocreate the defender exclusion itself.
It's excellent but not allowed to discuss in these forums (MDL) better go to those forums where nsane people are lol and look for @s1ave77 's one.
That activation is great but if you are using kms for your office install (which is most likely) then it doesn't make sense to use kms38, why? because kms38 won't survive hardware change or edition change, that's my personal approach.
That scheduled task is not for the system activation but to solve an issue if Renewal Interval is changed. According to the @abbodi1406