[Downloads, Info and DISCUSSION] "Windows 10 April 2018 Update" Final 1803 [17134.xxx] (PC)

.

 

no.
you only need to run it once. and later installed any vl office will be automatically activated.

 

That's not what the ReadMe says... Also, I don't have any new task in CCleaner after choosing the auto renewal.

 

in recent changelog of kms_vl_all v20 it clearly states that later installed office will be auto activated. i guess readme isnt updated.
i've tested it many times that auto activation for later installed office works. you dont need to worry about it.

and i've said earlier that it doesnt create task for auto activation. afaik it creates registry entries for that. you can look that in registry.

 

I'm using the v20 version. And what if I pre-activate Windows 10 with it and afterwards install Office? Should I have to run 2-Activate-Local.cmd in order to activate the latter or will it be also pre-activated?

 

if you are using $oem$ folder to preactivate, you dont need to run 2-Activate-Local.cmd again to activate office.

but if you are planing to give that iso to others, in that case i would suggest you to put info about av exclusion in desktop so users can know they have to exclude files so they dont lose activation.
you can make this directory in source folder in iso and put readme in desktop.
$OEM$\$1\Users\Public\Desktop\
so when user will install win 10, readme will appear on desktop.

p.s. kms_vl_all v20 creates exclusion in defender.

 

thanks

 

So, if I use the $OEM$ folder to pre-activate Windows it will create registry keys and copy those two files?

 

yes + creates exclusion in defender.

 

Thanks! Well, I removed Defender with MSMG ToolKit.

EDIT: I just found out that I already have a setupcomplete.cmd! It looks like it's created by NTLite. Should I do something in the Post-Setup section in NTLite or just add the line "call KMS_VL_ALL.cmd" in setupcomplete.cmd after it is created (after I copy the $OEM$ folder before mounting the image in NTLite and rename KMS_VL_ALL's setupcomplete.cmd to KMS_VL_ALL.cmd) by editing the file? Also, will it silenty execute the command after I install Windows?

 

Forgive my ot, but I can not find a link or a procedure to download or build an ISO Pro Ws 16251-16288 with Italian LP to be activated with product.ini on which then update the RS4. Does anyone have any indications in this regard?
Thanks in advance ... Also for the immense and clear work you do ...

 

Could you answer my question regarding setupcomplete.cmd?

 

I just found out that I already have a setupcomplete.cmd! It looks like it's created by NTLite. Should I do something in the Post-Setup section in NTLite or just add the line "call KMS_VL_ALL.cmd" in setupcomplete.cmd after it is created (after I copy the $OEM$ folder before mounting the image in NTLite and rename KMS_VL_ALL's setupcomplete.cmd to KMS_VL_ALL.cmd) by editing the file? Also, will it silenty execute the command after I install Windows?

 

There is a ReadMe file inside the KMS_VL_ALL archive, the Bonus section responds exactly to your question:
- if you already use another setupcomplete.cmd, rename this one to KMS_VL_ALL.cmd or similar name, then add a command to run it in your setupcomplete.cmd, example:
call KMS_VL_ALL.cmd

 

I read that but I don't know what to do. I have to edit NTLite's setupcomplete.cmd within the program or out of it like with Notepad and write "call KMS_VL_ALL.cmd"? And will it be silent or I'll have a Window opening after installing Windows or log in for the first time?

 

NTLite's?

@echo off
del /q /f "%0"

So, I have to copy the $OEM$ folder after extracting the ISO to the sources folder, rename setupcomplete.cmd to KMS_VL_ALL.cmd, create the ISO with NTLite (which creates the setupcomplete.cmd), add the "call KMS_VL_ALL.cmd" command by editing the setupcomplete.cmd afterwards and finally edit the ISO by saving the change? Can I do this in NTLite (adding the "call KMS_VL_ALL.cmd command) instead of doing it after creating the ISO (with a program like UltraISO)?