KMS-QADhooker for Localhost Self-Activation

I unpack the MSU to CAB temporarily and add them in an order given by a text file:

Code:

:furtherAP5
    set "COUNT="
    set "z="
    for /F "tokens=*" %%G in (%path10%) do set /A z+=1
    for /F "tokens=*" %%G in (%path10%) do (
        cls
        echo:
        SET /A COUNT+=1
        echo ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ
        Echo Adding Package !COUNT! of %z% = %%G
        echo:
        echo ßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßß
        echo:
        echo:
        Dism /Image:"%path5%" /Add-Package /PackagePath:"%TMP%\CABS\%%G.cab"
        echo:
        echo ßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßß
        echo:
        timeout /t 3
    )

path10 = path to TXT file, e.g. C:\Update\order.txt
path5 = path to mount folder

text file:

Code:

Windows8.1-KB2934018-x64
Windows8.1-KB2959977-x64

 

Downloaded ADK tools and guess what it failed again!!!
I wonder due the fact I am working on a standard user account has something to do with this issue. But I wonder why since I open a cmd prompt as an admin.

 

You need to login to view this posts content.

 

After installing Assessment and Deployment Tools there is an Command Prompt for them in Start Screens All Apps View . Open as admin and try from there.

 

You need to login to view this posts content.

 

Well, I can't use D: drive because no free space and no sufficient partition size. Could you re-write your code using my paths? Please.
This would be my last attempt for this thing, I don't know what's going on...

 

Yours:

Code:

for %%A in (W:\Upd_x86\KB\*.msu) do (cmd /c "dism /image:W:\win81aio\mount /Add-Package /PackagePath:%%A")

With adapted pathes:

Code:

for %%A in ("W:\Upd_x86\KB\*.msu") do (Dism /Image:"W:\win81aio\mount" /Add-Package /PackagePath:"%%A")

 

Thanks mate but no success, it throws the same error. I will do it without loop, just like this:

Code:

Dism /Image:W:\win81aio\mount /Add-Package /PackagePath:W:\Upd_x86\

Hopefully all KBs get correctly integrated and no issues arise as murphy78 warns.

 

You need to login to view this posts content.

 

xinso, using your code within a cmd file, DOES WORK!!!!!
I wonder why it doesn't work manually...
I guess you don't need any link to my msu files anymore as they are in my PC so there's no download links.

 

@ Mr.X

BTW: When using for-loop directly in CMD change %%A to %A and it will work even there .

 

@xinso and s1ave77
Just came back home and wanted to thank you as it seems to be working (the loop command) as long a cmd file is created. If I copy-paste the loop code into the cmd prompt it just don't work for me.

 

This is pretty neat. I just tested this on an 8.1 VMWare image and it worked flawlessly. On a side note, I'm completely clueless as to how it goes about activation. My limited knowledge in cmd scripting made my eyes bleed when trying to decipher the scripts. But here's what I've gathered.

1. It copies KMS-QADhooker.exe and KMS-QADhooker.dll to the %systemroot%.
2. It somehow activates Windows through the scripts at an emulated? KMS server on a local address? 192.168.1.255.

Can someone please explain to me what it does exactly?

 

Honestly, I could only sort of imagine how it activates. It's much more complicated than simply running a KMS server each boot. But on the plus side, it seems a lot more lighter and faster (due to the file size) in addition to its capability to be slipstreamed into an ISO. Thanks for the hard work on the project!

 

I initially thought that AutoKMS was only ran once during boot

 

As said .....when used in a script:

Code:

for /R "W:\Upd_x86\KB" %%A in (*.msu) do (dism /image:W:\win81aio\mount /Add-Package /PackagePath:%%A)

When used in command prompt directly:

Code:

for /R "W:\Upd_x86\KB" %A in (*.msu) do (dism /image:W:\win81aio\mount /Add-Package /PackagePath:%A)

 

Ooooopsie, corrected my post (copy 'n paste fail ) .

 

Just one more question because I'm processing my script right now and don't want to stop it, just by taking out just one % then the loop should work directly on a cmd prompt? Is that it? LOL

 

Yep, inside script it must read %%A and in command prompt it must read %A.