MSMG ToolKit to Convert W8.1/Srv 2012 R2 RTM/GA ISO - W8.1/Srv 2012 R2 Update 1 ISO

hmmm may b ,, i thought i might have done somwthing wrong..
well my specs are nt tht good ..

amd a8 quad core 1.9ghz
4gb ddrIII ram
1.5gb radeon graphics,
500 gb hdd

 

Well it takes time depending on the no of indexes you choose to update for install.wim. I do write and test the toolkit on my system which is half the configuration you have specified below and yes it takes quite some time to finish the task.

today I just finished testing updated toolkit script which reduces the overall amount of time for updating the install.wim when all indexes are chosen by removing the process of updating winre.wim image for all the wim indexes and instead only updating winre.wim for the fist wim index and copying updated winre.wim to the rest of the wim indexes.

also I have added option to download the Windows 8.1 Update 1 packages from Microsoft and rename them to correct filenames.

 

I have to take back what I said , last time I did this was with the old script and now I tested with the new one and it takes a bit longer, because the old one did not do resetbase IIRC. Anyway it finished 34 min total. It's the cleanup and resetbase process which takes long time.

 

I need ~50 minutes to integrate 1 index. But it is much more efficient than having to do a manual update after installation that requires ~30 minutes for each computer. (run on core2duo E7500 DDR2 3GB)

very useful tool for me

 

Is MS going to release ISO with Update 1 ?

 

We expect this will happen and people suggest around the 2/4/14

 

MS said that they will release Update 1 April 8th right ? So why the ISO should come earlier ?

 

ask for that.

 

Say MSMG,

I have read that all 6 of the update 1 KB's should be slipstreamed to all of the boot and install images one is concerned with (PE, Setup, install and WinRE). w81u1 Integrates all to boot.wim Index 1 (WinPe), KB2919442 and KB2939087 to boot.wim Index 2 (Setup) and all to install.wim and WinRe. Just curious why you digress.

 

Well it's not that all 6 of the w81u1 updates won't get integrate to boot.wim index 2, but the problem is that if you integrate all updates to boot.wim index 2, then the windows setup won't work it gets stuck at a stage where it displays a dialog box stated that some media not found.

Just because the Windows 8.1 Update 1 Packages specify that it applies to WinPE, you can't integrate them to any WinPE Image coz you should also see whether the update Package components do exists in the WinPE WIM Image, what Microsoft says is that it applies to WinPE in general.

For example if a Windows Update Package contains a .Net FX 4 components updates and the package says it applies to WinPE then you can't integrate that package to boot.wim coz there's no .Net FX 4 components present in the Boot WIM Image .

So, Just await for the official release of the Updates and also the ISO's then we can know what updates really do come with the boot.wim and winre.wim In the updated ISO Image. I know Microsoft won't release ISO for all SKU's but only for VL Editions.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Does it matter in what order we do both kits, or do we have to do 1.04 first then update 1 second?

 

its better you update w81 to w81u1 using this kit an then use the main kit for rest of the operation.

the new updated main toolkit which is yet to be released is designed in the same way.

 

after the integration is better

 

You need to login to view this posts content.

 

Well, comparing hashes for RTM iso and Update iso, only those files had been updated:

Spoiler

Code:

bootmgr
bootmgr.efi
efi\boot\bootx64.efi (bootia32.efi)
efi\microsoft\boot\cdboot.efi
efi\microsoft\boot\cdboot_noprompt.efi
efi\microsoft\boot\efisys.bin
efi\microsoft\boot\efisys_noprompt.bin
efi\microsoft\boot\memtest.efi
sources\dlmanifests\netfx4clientcorecomp-dl.man
sources\en-us\compatresources.dll.mui
sources\en-us\dismapi.dll.mui
sources\en-us\installprep.exe.mui
sources\en-us\privacy.rtf
sources\en-us\setupcompat.dll.mui
sources\en-us\vofflps.rtf
sources\replacementmanifests\microsoft-windows-appx-deployment-server\appxprovisioning.xml
sources\replacementmanifests\appxdeploymentserver-replacement.man
sources\replacementmanifests\netfx4clientcorecomp-replacement.man
sources\cmi2migxml.dll
sources\cmisetup.dll
sources\compatctrl.dll
sources\compatprovider.dll
sources\compatresources.dll
sources\csiagent.dll
sources\devinv.dll
sources\diagnostic.dll
sources\dism.exe
sources\dismapi.dll
sources\dismcore.dll
sources\dismcoreps.dll
sources\dismprov.dll
sources\drvmain32.sdb
sources\drvmain64.sdb
sources\folderprovider.dll
sources\imagingprovider.dll
sources\install.exe
sources\installprep.exe
sources\logprovider.dll
sources\migcore.dll
sources\migstore.dll
sources\migsys.dll
sources\mxeagent.dll
sources\nxquery.cat
sources\nxquery.sys
sources\pnpibs.dll
sources\queryappblock.exe
sources\reagent.dll
sources\rollback.exe
sources\schema.dat
sources\sdbapiu.dll
sources\setup.exe
sources\setupcompat.dll
sources\setupplatform.dll
sources\setupplatform.exe
sources\spwizeng.dll
sources\sqmapi.dll
sources\sysmain32.sdb
sources\sysmain64.sdb
sources\unbcl.dll
sources\upgdriver.dll
sources\upgloader.dll
sources\upgrade_bulk.xml
sources\upgradeagent.dll
sources\wica.dll
sources\wimprovider.dll
sources\win32ui.dll
sources\winsetup.dll

language mui files for setupplatform are the same
some files (like setupplatform.exe and setupplatoform.dll) updated to 17041 (i guess they will be published in dynamic updates later)

good luck in the new script