Is so great ! I test now ! Update : I have this code Code: ngrpci.sys = 1,,,,,,,,3,3,,1,4 vlmcsd.cmd = 1,,,,,,,2,0,0 nhelper.exe = 1,,,,,,,2,0,0 nlite.cmd = 1,,,,,,,2,0,0 nlite.inf = 1,,,,,,,20,0,0 nlsdl.dll = 1,,,,,,,2,0,0 nmas.dll = 100,,,,,,,,3,3 But is work
Thanks, Paky89. I don't think there's necessity for the reasons: Since this is for silent integration, and activation process is kinda quick. Otherwise we can simply use INSTALL.cmd to reveal DOS messages at foreground. Like Now is installing Office 2010 ... Powerpoint is being installed ... Word is being installed ... Now is activating Office 2010 ... Activating PowerPoint ... Activating Word ... . . . Of course, users can modify the script for their own needs. But not a good idea for me. People are different from each other.
Hey Xinso I would like to know if it's possible to use "Qewpal's Manual_for_Pre-Activated Windows 8 - wim integrated with KMS-QADhooker" to also create a pre-activated Windows 7 pro & Office 2013. Bornung1
That's for sure if 1. the target device is compatible with Hook Bypass 2. you don't mind EventLog's debugger-warning which will be generated for each activation on Pre-V6.2 System. Bornung1, please feel free to let me know if you need a hand. V6.3 (Windows 8.1 and Server) V6.2 (Windows 8 and Server) 1. KMSHook.dll and KMSHook.exe in C:\Windows 2. KMSHook Server parameters registry 3. KMSHook Debugger registry a. for Windows and Office 2013 b. for Office 2010 4. KMS Client IP/PORT registry a. for Windows and Office 2013 b. for Office 2010 V6.1 (Windows 7 and Server) 1. KMSHook.dll and KMSHook.exe in C:\Windows 2. KMSHook Server parameters registry 3. KMSHook Debugger registry a. for Windows b. for Office 2010 and Office 2013 4. KMS Client IP/PORT registry a. for Windows b. for Office 2010 and Office 2013 V6.0 (Windows Vista and Server) 1. KMSHook.dll and KMSHook.exe in C:\Windows 2. KMSHook Server parameters registry 3. KMSHook Debugger registry a. for Windows b. for Office 2010 4. KMS Client IP/PORT registry a. for Windows b. for Office 2010
Or simply use $OEM$ View attachment KMS-QADhook_Localhost-Self-Activation_W60-61-62-63_O14-15w_Slipstream_W63-RenewalTask.7z