Hi xinso, just noticed: Checking Windows version in Install_and_Forget.cmd doesn't work on Windows 7. before: set FL=/format:list set SS=wmic path SoftwareLicensingService for /f "tokens=2 delims==" %%A in ('%SS% get version %FL%') do (set VS=%%A) set CV=%VS:~,3% if %CV% LSS 6.2 (if %CV% GTR 6.3 echo Unsupported Windows.&echo.&pause&exit) the "if" version check goes wrong. Content of variable CV is ok. echo %CV% output: 6.1 after I changed code to: if %CV% LSS 6.2 echo Unsupported Windows.&echo.&pause&exit if %CV% GTR 6.3 echo Unsupported Windows.&echo.&pause&exit then it works as expected.
Hi xinso, nice work! i just wonder why it only supports Windows 8.x. Is there any reason it doesn't work on all of the NT6.x series Windows?
@xinso For 9600, you are using user made GVLKs for build 17029 (not RTM) of the following SKUs: Code: :ProfessionalStudent :CoreConnected :CoreConnectedSingleLanguage It leads to confusion. I suggest you to remove them & add after leak of RTM.
The "RenewalTask" it is a splendid idea! Edit : I think of expecting Windows 8.1 Update 2 before creating a new AIO
Sorry I have a question, what is the difference between Select-Slipstream and Slipstream_KmsRenewalTaskLogon ? The Slipstream_KmsRenewalTaskLogon is only for 8.1 with Office 2013 or not
1. Same. To cut down the file name length. 2. Extra Scheduled Task is for Windows 8.1 the weird only. Actually, KMS-QADhooker does not need Scheduled Task, because it'll be called automatically by sppsvc. And this is why there are options at OP for different tastes. For example, some like to activate the System at last second, yet some like to see 259200 every day. I belong to the former, because I wish it to sleep 259200 Mins and wake up to activate at 259201, then go to sleep another 259200... In short: Without Scheduled Task, KMS-QADhooker works only when activation is requested. With Scheduled Task, KMS-QADhooker works always, like normal KMS Service. Edit: Correction With Scheduled Task, if Renewal Interval is too short, e.g. 2 or 3 Mins, KMS-QADhooker works always, like normal KMS Service. Thanks.
We should not generate keys - at least not at MDL , as the outcome can be (does not have to be) unexpected sebus
Exactly, sometimes more knowledge is dangerous. Wzor made a 'keygen' using this, without giving any credit. @xinso Your thread is excellent but the outcome of the guide posted before may not be welcomed. Good to see that you have removed it.