MSMG ToolKit

Well you can use the WMC Key to activate over phone, that's not issue, when you install the os and use phone activation all they ask is for the installation id which is displayed in the phone activation dialog box, just enter the installation id in phone/Skype method and they will give you the activation id and then enter the activation id into the box provide in the phone activation dialog and click next that's it done, it will be activated.

They won't check whether it's a key you purchased or promotional key.

 

am talking about the both the windows 8.x retail and free wmc keys
and I didn't say that if you change the cpu, that's not a issues, read my previous comments, what I told was a minor changes in hardware won't harm but the cpu/hdd/network will break the activation.

see I do have a free wmc which I use and when ever I do want to do fresh activation I do it by phone method and it gets activated.

rest of the time I do integrate my activation with the windows 8.1 pro wmc iso so I don't have to activation every time.

you don't get a new CODE every time you do activation, instead you get the same activation code.

you said you have only FREE WMC Key, see windows 8.1 pro won't activate with just wmc key without the pro version getting activated and that's why I did this toolkit. this toolkit inserts the generic wmc activation tokens which have been extracted by upgrading windows 8.0 pro to pro wmc with generic key by store upgrade method. so this helps to activate the windows 8.1 pro wmc with just the wmc key and no need for pro key. so to do pre-activation you need to once activate the os with the wmc integration did with the toolkit and then again copy the activated tokens back to the "PreAct" folder and then use the toolkit function integrate pre-activation tokens for auto-activation.

and also you can't use pro key to activate the prowmc edition.

edit: in the above message its should have been - this toolkit inserts the generic wmc activation tokens which have been extracted by upgrading windows 8.0 prowmc to windwos 8.1 prowmc with generic key by store upgrade method.

 

what I said was I do have a free wmc key which I do get activated by phone method when there is a fresh activation in the sense when i do upgrade the drivers coz when even there is change in some drivers the activation give up error some times as I have read it in other threads.

and rest of the time when I do use the same drivers for installation I do use the pre-activated iso so there is no need for fresh activation. the reason i do use phone activation is because the Microsoft will block the online activation after some number of times, hope you got it.

 

ok I will try to implement it in next version of toolkit and about the re-build the image, re-building the image something like defragmenting a hardrive to cleanup the leftover space and organise the files. when you remove or add any files/components to a wim image it alters the way the image stores the files. so a re-build is made to clean-up unwanted stuffs and to reduce the size of the final wim image. it's not necessary to re-build the image every time but you can use the re-build the image the last time before you are going to make a iso image or use the image for deployment. before I had set the re-build to do automatically but in the present edition I did gave a choice coz if there are a lot indexes in the image then it will take a lot of time so.

 

ok I will see what's the cause, I don't have a UEFI boot system so will take time

 

WADK 8.1 by default install to Program Files or Program Files (x86). ToolKit has option to copy the WADK 8.1 Tools to Bin\WADK folder so that you can use the toolkit on another system without installing the WADK 8.1

 

Need Suggestions, Feature Requests for next versions of ToolKit, The next version comes with Windows 7/2008R2 support. just thinking of doing a GUI based ToolKit for future version coz that solve most of problems/limitations.

 

When a download a ISO file, say for example windows 8.1 pro and when the ISO file is downloaded and stored in your computer, it will be saved as something like this fr_windows_8_1_pro_x64_dvd.iso right, this fr_windows_8_1_pro_x64_dvd.iso is the ISO File Name

When you Burn this ISO file to a DVD and insert the DVD into the Computer, then in my computer under the CD/DVD section you will see something like W81_Pro for the DVD you inserted and this W81_Pro is the ISO Label.

 

Since the Error (0xc0000135) appears for many reasons and not just for dism, so can't say what's exactly the issue.

On this windows 7 pro system did you installed the wadk 8.1 tools?
if no did you just copied the toolkit with the bin\wadk folder to this system and then you are using the toolkit.
if yes then the toolkit when starting up configure the dism path to bin\wadk instead of the one present in the windows 7 default system32\dism.exe and once the toolkit closes the path gets cleared.

so if you trying to edit wim outside the toolkit i.e on windows 7 pro then it uses the dism present in the windows\system32 folder and you can't service the windows 8.x wim with the previous version of wadk and so you need wadk 8.1 tools

if you don't want to install wadk 8.1 tools but you want to use the one in toolkit bin\wadk directory then you can use this simple script

save this below code block to file named SetWADK.cmd and place it inside the toolkit folder and run it and then try to use the commands in other command windows

Code:

@echo off

set OSArch=
set WADKPath=%~dp0Bin\WADK

If Defined ProgramW6432 (
   set OSArch=amd64
) else (
    set OSArch=x86
)

set dism=%WADKPath%\%OSArch%\DISM\dism.exe
set imagex=%WADKPath%\%OSArch%\DISM\imagex.exe
set oscdimg=%WADKPath%\%OSArch%\Oscdimg\oscdimg.exe
set etfsboot=%WADKPath%\%OSArch%\Oscdimg\etfsboot.com
set efisysbin=%WADKPath%\%OSArch%\Oscdimg\efisys.bin