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

Discussion in 'MDL Projects and Applications' started by MSMG, Mar 7, 2014.

Thread Status:
Not open for further replies.
  1. =)(=

    =)(= Guest

    Now it fails for me and shows errors like:

     
  2. ady199

    ady199 MDL Senior Member

    Jul 22, 2009
    314
    47
    10
    #62 ady199, Mar 8, 2014
    Last edited: Mar 8, 2014
    Finally got a working Windows 8.1 Enterprise x64 iso with the Spring 2014 update integrated into it

    I'm currently uploading it to Mega - (about 1 hour to go) - PM me if you want the link

    Thanks so much :worthy:
     
  3. murphy78

    murphy78 MDL DISM Enthusiast

    Nov 18, 2012
    7,389
    11,614
    240
    wim files are like virtual hard disks... They grow with each unique file. To shrink them you need to re-export them to a new file.
    You can also use /compress:max in the export instead of the default compression.
     
  4. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    18,681
    18,589
    340
    It should be compressed VHD with deduplication support.

    :D
     
  5. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    16,222
    84,906
    340
    Did you update both boot.wim indexes?
    did you ran the ResetBase command on both?
    did you rebuild the wim file by exporting the 2 indexes to new wim?
     
  6. murphy78

    murphy78 MDL DISM Enthusiast

    Nov 18, 2012
    7,389
    11,614
    240
    #66 murphy78, Mar 8, 2014
    Last edited by a moderator: Apr 20, 2017
    Sorry, perhaps I didn't clearly explain things well enough.
    You have to export both indexes from the boot.wim file to reduce the size.
    Code:
    if not exist c:\temp mkdir c:\temp
    dism /export-image /sourceimagefile:c:\win81\sources\boot.wim /sourceindex:1 /destinationimagefile:c:\temp\boot.wim /compress:max /checkintegrity
    dism /export-image /sourceimagefile:c:\win81\sources\boot.wim /sourceindex:2 /destinationimagefile:c:\temp\boot.wim /compress:max /checkintegrity
    move /y c:\temp\boot.wim c:\win81\sources\
     
  7. murphy78

    murphy78 MDL DISM Enthusiast

    Nov 18, 2012
    7,389
    11,614
    240
    No. doing this before doing resetbase does nothing to reduce the size. Just trust me. Do it again.
     
  8. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,487
    210
    #68 MSMG, Mar 8, 2014
    Last edited: Mar 8, 2014
    (OP)
    Yes, for Boot.wim Index 2 it won't apply coz the Windows 8.1 Update 1 KB2919355 Package is not applied for it.

    /StartComponentCleanup /ResetBase command only works when Windows 8.1 Update 1 KB2919355 Package applied to winpe images

    and also check our below command you have used /CleaomponentCleanup /ResetBase instead of /StartComponentCleanup /ResetBase


    and about the size of the wim image file, you need to export the all indexes of boot.wim image with full compression to a new file then you will get a smaller file size, check out my testing with x86 boot.wim

    boot.wim 3,47,791 KB (339 MB) - Actual Size with Updates Applied
    boot.wim 3,60,103 KB (351 MB) - Used /StartComponentCleanup /ResetBase for Index 1 and saved the image
    boot.wim 3,05,456 KB (298 MB) - Exported all the Images in boot.wim to a new boot.wim Image File



     
  9. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,487
    210
    I will update the script tomorrow with the support for applying updates to all the image indexes at once with StartComponentCleanup /ResetBase Task for Boot.wim Index 1 and Winre.wim Index 1
     
  10. murphy78

    murphy78 MDL DISM Enthusiast

    Nov 18, 2012
    7,389
    11,614
    240
    Be careful man. I'm getting bad driver errors when applying the patches to the boot.wim of an actual setup image.
    I suspect that this method is not advisable for the existing boot.wim versions...
     
  11. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,487
    210
    If you had applied Windows 8.1 Update KB2919355, KB2932046, KB2937592 for boot.wim index 2, then you will get this error that you did specified in the other thread. but still I will test it and update...

     
  12. murphy78

    murphy78 MDL DISM Enthusiast

    Nov 18, 2012
    7,389
    11,614
    240
    Yes, I believe this is the cause of my concern. Pardon the alarm.
    It seems only the non-bootable index of boot.wim and the winre.wim should be upgraded and /resetbased
     
  13. Boops

    Boops MDL Addicted

    Jan 5, 2008
    914
    1,207
    30
    Hi,

    Is it necessary to apply the updates to the two indices of boot.wim and winre.wim? :rolleyes:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. NICK@NUMBER11

    NICK@NUMBER11 MDL Expert

    Mar 23, 2010
    1,503
    720
    60
    does not work, see screenshot....

    Capture.PNG
     
  15. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    16,222
    84,906
    340
    boot.wim, no. Specially since it broke setup
    winre.wim, recommended
     
  16. Boops

    Boops MDL Addicted

    Jan 5, 2008
    914
    1,207
    30
    I am interested only Windows 8.1 Pro. Can I delete indexes number two, which are the Core version?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,487
    210
    Yes that's what I did specified...

     
  18. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,487
    210
    Yes you can safely delete the other index if you don't need it

     
  19. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,487
    210
    As I have told you before, updating boot.wim is optional but winre.wim should be done. and if you are updating boot.wim only index 1 gets all the updates but for index 2 only the KB2919442, KB2939087 gets applied safely

     
  20. armond

    armond MDL Addicted

    Jun 16, 2008
    734
    235
    30
    Hello,
    First let me thanks for your hard work in creating this script.
    I certainly know about your toolkit for integrating hotfixes. But I also want to be able to have a chance for integrating the "remaining" updates after the update 1, without having to mount and dismount the install.wim, in the same sesson of this ToolKit.
    You know that Microsoft Update still shows KB2916626 and after applying it, KB2934802 updates for Flash player, and also the update for Camera Codec, KB2899189.
    And also I want to add the DotNet 3.5. and, well, its updates!
    So is there an easy way to add those to the CMD? Just asking for safe editing that file.
    Thanks! Good job.