Windows 10 Hotfix Repository

Discussion in 'Windows 10' started by Tito, Oct 1, 2014.

  1. drew84

    drew84 MDL Expert

    Mar 13, 2014
    1,397
    2,378
    60
    #3861 drew84, May 9, 2017
    Last edited: May 9, 2017
  2. digital john

    digital john MDL Senior Member

    Mar 30, 2008
    265
    69
    10
    ok..thanx..will try
     
  3. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,665
    103,469
    450
  4. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,665
    103,469
    450
    It's for updating the "ISO:\Sources" folder.
     
  5. murphy78

    murphy78 MDL DISM Enthusiast

    Nov 18, 2012
    7,418
    11,685
    240
    When you add these dynamic updates to sources folder you need to test them. Sometimes they update key files that cause errors with boot installs.
    This is because they're intended for upgraders only.
     
  6. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,665
    103,469
    450
    #3867 Enthousiast, May 9, 2017
    Last edited: May 9, 2017
    I know, but i never encountered any problems after that single incident at the beginning of 10.

    Content:

    Code:
    926fc794441212d0388815ef2d70ee19fce1f99e *acmigration.dll
    6bd81804db88d29a10076b746914c3ca3dfebeb9 *appraiser.sdb
    
     
  7. drew84

    drew84 MDL Expert

    Mar 13, 2014
    1,397
    2,378
    60
  8. drew84

    drew84 MDL Expert

    Mar 13, 2014
    1,397
    2,378
    60
  9. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,665
    103,469
    450
    #3870 Enthousiast, May 9, 2017
    Last edited: May 9, 2017
    Looks like dynamic update for 1703 "KB4020001" is superseded by the new CU "kb4016871".
    It doesn't show after the /resetbase command in W10UI_1.8 in winre.wim and boot.wim (which still can't be used when updated x64).

    Code:
    ============================================================
    Updating winre.wim
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0
    
    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Checking Updates...
    ============================================================
    
    
    ============================================================
    Installing Updates...
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0
    
    Image Version: 10.0.15063.0
    
    Processing 1 of 2 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~15063.296.1.5
    [==========================100.0%==========================]
    Processing 2 of 2 - Adding package Package_for_KB4020001~31bf3856ad364e35~amd64~~10.0.1.0
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0
    
    Image Version: 10.0.15063.0
    
    [====                       8.4%                           ]
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0
    
    Image File : D:\W10UI_1.8\winre.wim
    Image Index : 1
    Saving image
    [==========================100.0%==========================]
    Unmounting image
    [==========================100.0%==========================]
    The operation completed successfully.
     
  10. drew84

    drew84 MDL Expert

    Mar 13, 2014
    1,397
    2,378
    60
  11. murphy78

    murphy78 MDL DISM Enthusiast

    Nov 18, 2012
    7,418
    11,685
    240
    Just wanted to give a heads up for integrators.
    the CU for x64 version of 15063: KB4016871 adds a hwcompat.txt and hwexclude.txt to sources folder and it completely borks boot setup.
    Since it's packaged you will need to takedown and aclcls to delete and replace with older versions.
    It's possible that this is simply a VM compatibility issue and it works on a real system, but I'm not taking that chance.

    I also replaced the ones in my iso\sources folder so I don't have to take any chances.
    I'll update if my upgrade testing reveals any problems.

    This is just for the x64 version and only for boot.wim bootable index (2)
     
  12. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,665
    103,469
    450
  13. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,665
    103,469
    450
    Every new edition had it's own faults :D 15063 has at least a few :)
     
  14. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,665
    103,469
    450
    I did what you suggested:

    Extracted "hwcompat.txt" and "hwexclude.txt" from the original x64 15063.0 boot.wim index 2 and after integrating the CU (15063.296), i replaced the updated files with the original files and the uptodate x64 boot.wim worked and i did not get the "cannot find the ...list" error i posted when i encountered it the first time.