Thank you, LostED. The script has been slightly modified for Windows 10 10240: Before Code: for /f "tokens=2 delims==" %%A in ('wmic path %SPS% get version /format:list') do (set VS=%%A) set CV=%VS:~,3% if %CV% LSS 6.2 (echo.&echo Unsupported Windows.&echo.&pause&exit) After Code: for /f "tokens=3 delims= " %%A in ('reg query "%HK%" /v CurrentVersion') do (set CV=%%A) if %CV% LSS 6.2 (echo.&echo Unsupported Windows.&echo.&pause&exit)
$OEM$ folder did not activate OS when added to 10240 Enterprise 64 disk. Activated OK with install.bat file after OS installation.
Why is that? Is that statement also true for the latest version? I just tried KMS-QADhook_Localhost_W62_W63w_KmsRenewalTaskLogon_O15w_Slipstream.7z on W7SP1 and there is only a warning about another service process connected (e.g. debugger) every time the Software Protection service is started. Activation is working fine. A little bit of information in the opening post on how this hook works exactly would be nice. Is it working like SECOInjector, by writing directly to the response buffer? Or is it redirecting the IP connection to its own inbuilt KMS emulator? I like the logging functionality of deagles' emulator very much, would it be possible to add something similar to the hook? Thank you.