For that reason i build my own ProWMC from Pro WIM with dism and insert the tokens manually. Works like a charm with any given ProWMC key .
Then do as s1ave77 said, create the wim file then use MSMG Toolkit i don't have any ProWMC keys o test
As the script creates install.wim, it only needs to mount it and copy the tokens manually from Toolkits \Packs\WMC\ subfolder to mounted Windows\system32\spp\store\2.0\, applies for data.dat and tokens.dat. The cache.dat would belong to Windows\system32\spp\store\2.0\cache\.
I've tried to make an ISO for interest only: Spoiler Code: Running Decryption program... ERROR: Cannot find <ESD> tag within the embedded XML data. =============================================================== Creating ISO Structure Layout... =============================================================== Deployment Image Servicing and Management tool Version: 6.3.9600.17029 Applying image Error: 5 Access is denied.
I just made a test with a ProWMC key grabbed from the internet and wim file created using esd-decrypter-v3 the key accepted and installed just fine after clean install you do know that Win8 keys do not accepted for install (at setup phase) and valid just for activation after install, right?
I had no idea this was even possible, as I've made sysprep'd Win8 images before... BTW, I used murphy's .esd file from PTB, the May 01 one, but when I check WU with the above fix, I get a 890mb update 1 offered... I thought that was integrated in those .esd's already? I'm using the single language x64 one. Microsoft really trying hard to piss everyone off with Win8, aren't they All this trouble for nothing better than Win7.
That seems to be a feature/bug of WU, as it is not very explicite in that regard . With MSDN Update 1 ISO you will still get KB2919355 showing up there although it only installs KB2934018 and KB2959977 (these are not part of the ISO but added to KB2919355 at WU). It shows it while download/install only .
Hmm, well it did make the install from 8.4gb to 10.0gb when backing up the VM (vhd) before finalizing. So now I'm hoping this increase in size does not reflect in the resultant image after sysprep. Man, I can't believe it, every time I work with Win8.x it sucks so bad and I start remembering why I keep going back to Win7. I need to work with it a bit to test some things for compatibility, but seriously, what is good about it? It's ugly as hell, it is not faster (forget it, not true), who uses Store apps (joke), and it's way more problematic to work with in matters of sysprep, activation, WU, even damned Disk Cleanup got stuck in the VM when trying to clean up Updates... In my view it is really a big fail. OK, enough ranting, I'll sysprep the thing.
Can't complain about Win 8.1 with update here. Ressource usage is phantastic after the update . Also a nice feature is the update cleanup via dism. Code: dism /online /cleanup-image /AnalyzeComponentStore Cleanup the WinSxs folder: Code: dism /online /cleanup-image /startcomponentcleanup Purge all update related stuff (will make updates permanent): Code: dism /online /cleanup-image /startcomponentcleanup /resetbase For the update problem, my JATD script (see sig) is shipped with the Powershell Module and some basic functions predefined .
Install.wim is 3.32 after capture, I guess not too bad for Win8.x? Thanks for the reminder on the WADK options, it's been a while
Would guess it could be a bit smaller for a single-index wim . You could either cleanup offline or export it with /compress:maximum switch. The commands in previous post are for standard dism (note the /online switch) on running Windows, but this can be also done oflline with adk.
I did enable .NET 3.5 though, so that would increase the size by quite a bit. I did apply the first 2 of those commands on the vm backup I made and sysprep'd again but it only saved 20mb on the install.wim. Of course, I have not converted to .esd yet, which could make a good bit a difference in size