KUC a utility to check you Windows 7; 2008 R2; WMS; or Win embedded update status

Discussion in 'MDL Projects and Applications' started by komm, Dec 2, 2011.

  1. Supern00b

    Supern00b MDL Addicted

    Dec 30, 2010
    763
    558
    30
    Was going to say something similar. People often forget that it's not just a 5-minute thing. Maintaining such a project is very time consuming.
    Personally I'm in no hurry to see a new KUC.
    I do not update my images each month, so no problem if komm takes his time.

    Cheers.
     
  2. tistou77

    tistou77 MDL Expert

    Mar 22, 2008
    1,952
    614
    60
    Komm

    Thanks for your last KUC, I think I found an error

    The KB2796313 isn't superseded by KB2951611

    2796313: iphlpsvcmigplugin.dll, 6.1.7601.22214 (amd64)
    2951611: iphlpsvcmigplugin.dll, 6.1.7601.22150 (amd64)

    But for "wow64" iphlpsvcmigplugin.dll, 6.1.7601.22670
     
  3. komm

    komm MDL Addicted

    Jun 16, 2011
    894
    3,066
    30
    Too much work at the uni.
    Sorry of that.
     
  4. komm

    komm MDL Addicted

    Jun 16, 2011
    894
    3,066
    30
    2796313 contains:
    windows-i..oexistencemigration 6.1.7601.22214
    windows-netcorehelperclasses 6.1.7601.22214

    2951611 contains:
    windows-i..oexistencemigration 6.1.7601.22670
    windows-netcorehelperclasses 6.1.7601.22670

    So you have to decide:
    so if you need phlpsvcmigplugin.dll 6.1.7601.22214 you must not install 2951611
    since the package version is higher you will get the older version.
    this may be a mistake of MS or they switched back to the old version.
    but then you have to live with the older netcore version of 2796313.
     
  5. quetzalin

    quetzalin MDL Junior Member

    May 25, 2011
    84
    11
    0
    For some reason the update IE11-Windows6.1-KB2929437-x64.msu isn't being integrated with the last KUC version.
     
  6. komm

    komm MDL Addicted

    Jun 16, 2011
    894
    3,066
    30
    I see no problems with that update.
    I need more info from you if you want further investigation.
     
  7. komm

    komm MDL Addicted

    Jun 16, 2011
    894
    3,066
    30
  8. quetzalin

    quetzalin MDL Junior Member

    May 25, 2011
    84
    11
    0
    #630 quetzalin, Jun 16, 2014
    Last edited: Jun 16, 2014
    Sorry if i'm not being clear enough.

    I'm integrating the updates into a Win7 DVD image, i'm also integrating IE11 at the same time. When i finish running your tool several times until i get nothing to do then i create the .iso and install the system, everything is up to date on Windows Update but not that update, it asks for it to be installed.

    I finally managed to get it integrated manually using DSIM. Don't know if this update is a superseded one or part of a "WU Satisfy".
     
  9. quetzalin

    quetzalin MDL Junior Member

    May 25, 2011
    84
    11
    0
    #631 quetzalin, Jun 16, 2014
    Last edited by a moderator: Apr 20, 2017
  10. Supern00b

    Supern00b MDL Addicted

    Dec 30, 2010
    763
    558
    30
    #632 Supern00b, Jun 16, 2014
    Last edited by a moderator: Apr 20, 2017
    Hi Quetzalin,

    Look in the packages_out.txt:

    Code:
    ADD/EXCLUSIVE Update is missing! Install KB2969339 exclusively!
    Copy that update to the workfolder and KUC will pick it up.

    Also, I have the same issue with KB2949621 and KB2939471 on both x86 and x64 wims, those are "permanent updates" and can't be removed, but KUC tries it anyway and errors out.
    Furthermore, the x86 wim can't be updated by KUC, image becomes "unusable".
    Edit: It happens when installing Windows8.1-KB2964736-x86.

    The x64 wim updates fine.

    Cheers.
     
  11. quetzalin

    quetzalin MDL Junior Member

    May 25, 2011
    84
    11
    0
    #633 quetzalin, Jun 17, 2014
    Last edited by a moderator: Apr 20, 2017
    Thanks!, don't know why i missed that part, guess i didnt scroll completly to the right lol.

    But i still dont get why KUC isn't creating the copy.bat tho?.

    About the other two updates KUC is trying to remove i guess it is something komm has to fix.

    Thanks again :)
     
  12. komm

    komm MDL Addicted

    Jun 16, 2011
    894
    3,066
    30
    If 2949621 and 2939471 were permanent updates it would also be impossible to remove them online.

    When working with wims, you should 1. remove the old updates and then add the new ones.

    If you are not able to remove an old update you should
    1. try to add it (even it shows it is installed).
    2. try to remove it again.

    If that does not work
    you have to go the long way and look inside the dism.log file to find the reason.
    sometimes you have to
    1. add an older update first.
    2. add the update that can not be removed
    3. remove the update that can not be removed
    4. remove the older update
    sometimes you also have to change the order of 3 and 4.
     
  13. komm

    komm MDL Addicted

    Jun 16, 2011
    894
    3,066
    30
    If a wim becomes unusable, when trying to add a new update
    the update itself must not be the reason.
    In most cases the wim was not correct before you add the update.
    Look inside the dism.log to find the reason.

    This case can not easily be solved.
    I most cases it's quicker to start with a new clean wim file.
     
  14. Supern00b

    Supern00b MDL Addicted

    Dec 30, 2010
    763
    558
    30
    I forgot to say that I tried also with a clean, unmodified x86 wim (with update 1) from MS.
    The result was exactly the same, running KUC on it the image becomes unusable.

    Cheers.
     
  15. adric

    adric MDL Expert

    Jul 30, 2009
    1,398
    1,519
    60
    #638 adric, Jun 20, 2014
    Last edited by a moderator: Apr 20, 2017
  16. Kees030

    Kees030 MDL Novice

    Feb 11, 2014
    28
    9
    0
    #639 Kees030, Jul 1, 2014
    Last edited: Jul 2, 2014
    I followed the guide "How to integrate updates inta a DVD image". After mounting the image I ran KUC. In Overview 2 I selected remove superseded updates and use "Satisfy WU updates". In Select Output Options all creates were selected (create Remover included). Current packages= 191; to Remove=67, to Add=376, Bad=8 (all regarding KB2656356).
    There's no Remove old in the INFO screen nor in the WU folder :confused:

    EDIT: problem solved with automatic creation of packages.txt and selecting WMF4.0 made the 8 bads disappear and generated Remove_OLD.cmd :)
     
  17. Kees030

    Kees030 MDL Novice

    Feb 11, 2014
    28
    9
    0
    #640 Kees030, Jul 2, 2014
    Last edited: Jul 2, 2014
    Size of install.wim

    I integrated updates into a DVD image (with updates till 2014, May). The size of the original install.wim was 4.639.742 kB.

    KUC with standard settings (except WMF4.0; selected to solve 8 bads) resulted in 68 to remove and 377 to add. I couldn't remove 5 (KB2533552 error 0x800f082e) and only 377 were added.

    After finishing KUC the size of the new install.wim was 5.369.700 kB. And with "
    imagex /export /check /compress fast c:\W7\sources\install.wim * c:\W7\sources\newinstall.wim" it even increased: 5.439.861 kB :eek:

    1. Original

    C:\>imagex /info f:\sources\install.wim

    ImageX Tool for Windows
    Copyright (C) Microsoft Corp. All rights reserved.
    Version: 6.1.7600.16385

    WIM Information:
    ----------------Path: f:\sources\install.wim
    GUID: {d045e9aa-9613-4477-9502-be79024335ce}
    Image Count: 1
    Compression: LZX
    Part Number: 1/1
    Attributes: 0x8
    Relative path junction​

    Available Image Choices:
    ------------------------
    <WIM>
    <TOTALBYTES>4751093533</TOTALBYTES>
    <IMAGE INDEX="1">​
    <DIRCOUNT>17227</DIRCOUNT>
    <FILECOUNT>82956</FILECOUNT>
    <TOTALBYTES>17315776357</TOTALBYTES>
    <HARDLINKBYTES>5165129817</HARDLINKBYTES>
    <CREATIONTIME>​
    <HIGHPART>0x01CF73F3</HIGHPART>
    <LOWPART>0xD6013470</LOWPART>​
    </CREATIONTIME>
    <LASTMODIFICATIONTIME>​
    <HIGHPART>0x01CF7503</HIGHPART>
    <LOWPART>0x90235A82</LOWPART>​
    </LASTMODIFICATIONTIME>
    <WINDOWS>​
    <ARCH>9</ARCH>
    <PRODUCTNAME>Besturingssysteem Microsoft® Windows®</PRODUCTNAME>
    <EDITIONID>Ultimate</EDITIONID>
    <INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
    <HAL>acpiapic</HAL>
    <PRODUCTTYPE>WinNT</PRODUCTTYPE>
    <PRODUCTSUITE>Terminal Server</PRODUCTSUITE>
    <LANGUAGES>​
    <LANGUAGE>nl-NL</LANGUAGE>
    <DEFAULT>nl-NL</DEFAULT>​
    </LANGUAGES>
    <VERSION>
    <MAJOR>6</MAJOR>
    <MINOR>1</MINOR>
    <BUILD>7601</BUILD>
    <SPBUILD>18409</SPBUILD>
    <SPLEVEL>1</SPLEVEL>​
    </VERSION>
    <SYSTEMROOT>WINDOWS</SYSTEMROOT>​
    </WINDOWS>​
    <NAME>Windows 7 Ultimate</NAME>
    <FLAGS>Ultimate</FLAGS>​
    </IMAGE>​
    </WIM>


    2. After KUC (remarkable differences only)

    C:\>imagex /info C:\w7\sources\install.wim

    WIM Information:
    ----------------
    Path: C:\w7\sources\install.wim
    ...
    Compression: LZX
    ...

    Available Image Choices:
    ------------------------
    <TOTALBYTES>5498570448</TOTALBYTES>
    ...
    <DIRCOUNT>18915</DIRCOUNT>
    <FILECOUNT>96049</FILECOUNT>
    <TOTALBYTES>18689022125</TOTALBYTES>
    <HARDLINKBYTES>5196546199</HARDLINKBYTES>
    ...
    <SPBUILD>22653</SPBUILD>
    ...


    3. After imageX (remarkable differences only)

    C:\>imagex /info C:\w7\sources\newinstall.wim

    WIM Information:
    ----------------
    Path: C:\w7\sources\newinstall.wim
    GUID: {0aa99802-c4bb-4581-b71b-8b71907a817c}
    ...
    Compression: XPRESS
    ...
    Attributes: 0xc
    Integrity info
    Relative path junction

    Available Image Choices:
    ------------------------
    <TOTALBYTES>5570404662</TOTALBYTES>
    ...
    <DIRCOUNT>18915</DIRCOUNT>
    <FILECOUNT>96049</FILECOUNT>
    <TOTALBYTES>18689022125</TOTALBYTES>
    <HARDLINKBYTES>5196546199</HARDLINKBYTES>
    ...
    <SPBUILD>22653</SPBUILD>
    ...

    Please advise if the increase in sizes make sense and -if not- what went wrong :confused: