Windows 10 Hotfix Repository

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

  1. Enthousiast

    Enthousiast MDL Tester

    Joined:
    Oct 30, 2009
    Messages:
    35,567
    Likes Received:
    59,637
    Trophy Points:
    450
    Yeah clean boot.wim works via normal setup and murphy78's script, updated boot.wim only works with script.
     
  2. UltimateGTR

    UltimateGTR MDL Member

    Joined:
    Jul 18, 2009
    Messages:
    101
    Likes Received:
    18
    Trophy Points:
    10
    Since this policy won't apply to Enterprise 2015 LTSB, I wonder if we can take the updates from it and install it on the editions which will reach end of servicing next month?
     
  3. Enthousiast

    Enthousiast MDL Tester

    Joined:
    Oct 30, 2009
    Messages:
    35,567
    Likes Received:
    59,637
    Trophy Points:
    450
    #3763 Enthousiast, Apr 13, 2017
    Last edited: Apr 13, 2017
    @Mr.X, did you try x86? It works with updated boot.wim and standard setup.

    Wait, i did a modification, maybe that's what makes it work, will do the same modification on the updated x64 boot.wim.

    Brb.
     
  4. Enthousiast

    Enthousiast MDL Tester

    Joined:
    Oct 30, 2009
    Messages:
    35,567
    Likes Received:
    59,637
    Trophy Points:
    450
    Hmmm, looks like it's not my input, x86 uptodate boot.wim just seems to work fine using standard setup.

    Can you confirm?
     
  5. tistou77

    tistou77 MDL Expert

    Joined:
    Mar 22, 2008
    Messages:
    1,659
    Likes Received:
    550
    Trophy Points:
    60
    Hello

    There is no servicing stack for the 1703, that's it ?

    Thanks
     
  6. Mr.X

    Mr.X MDL Guru

    Joined:
    Jul 14, 2013
    Messages:
    7,625
    Likes Received:
    14,952
    Trophy Points:
    240
    Sorry I can't confirm. All my hardware setup for making compilations (AIOs) is not plugged in. Poor man here. :D
     
  7. Enthousiast

    Enthousiast MDL Tester

    Joined:
    Oct 30, 2009
    Messages:
    35,567
    Likes Received:
    59,637
    Trophy Points:
    450
  8. R23

    R23 MDL Member

    Joined:
    Apr 5, 2017
    Messages:
    124
    Likes Received:
    28
    Trophy Points:
    10
  9. Enthousiast

    Enthousiast MDL Tester

    Joined:
    Oct 30, 2009
    Messages:
    35,567
    Likes Received:
    59,637
    Trophy Points:
    450
    It's homebrew AiO ;)
     
  10. Myrrh

    Myrrh MDL Expert

    Joined:
    Nov 26, 2008
    Messages:
    1,496
    Likes Received:
    601
    Trophy Points:
    60
    Not yet anyway. I guess they didn't break it as bad this time as they did in 1607.
     
  11. antonio8909

    antonio8909 MDL Guru

    Joined:
    Feb 16, 2014
    Messages:
    2,939
    Likes Received:
    1,414
    Trophy Points:
    90
  12. Enthousiast

    Enthousiast MDL Tester

    Joined:
    Oct 30, 2009
    Messages:
    35,567
    Likes Received:
    59,637
    Trophy Points:
    450
    #3772 Enthousiast, Apr 13, 2017
    Last edited by a moderator: Apr 20, 2017
  13. antonio8909

    antonio8909 MDL Guru

    Joined:
    Feb 16, 2014
    Messages:
    2,939
    Likes Received:
    1,414
    Trophy Points:
    90
  14. kuroda

    kuroda MDL Senior Member

    Joined:
    Aug 25, 2012
    Messages:
    445
    Likes Received:
    32
    Trophy Points:
    10
  15. Enthousiast

    Enthousiast MDL Tester

    Joined:
    Oct 30, 2009
    Messages:
    35,567
    Likes Received:
    59,637
    Trophy Points:
    450
  16. kuroda

    kuroda MDL Senior Member

    Joined:
    Aug 25, 2012
    Messages:
    445
    Likes Received:
    32
    Trophy Points:
    10
  17. Flipp3r

    Flipp3r MDL Expert

    Joined:
    Feb 11, 2009
    Messages:
    1,743
    Likes Received:
    772
    Trophy Points:
    60
    I use wimlib which also lets you change date & time as well. I'm not at work so can't post/remember the exact command.
     
  18. MUKESH

    MUKESH MDL Junior Member

    Joined:
    Sep 1, 2011
    Messages:
    53
    Likes Received:
    30
    Trophy Points:
    0

    These are the steps i am doing:

    1.Downloaded the CombinedSL ESD file from the thread - [DISCUSSION] Windows 10 (1703 RS2) "Creators Update"
    Final 15063 (PC).used abbodi's script - "esd-decrypter-wimlib-28.7z" , option - 1 to create a standard iso image.

    2.Then did the W10UI(W10UI_1.8.zip) using the latest updates(kb4015583 & kb4018483) on all the respective four
    indexes.

    3.Deleted the "Updated" boot.wim file and copied the "Clean" boot.wim file from the iso image i created in Step 1
    in the sources directory.

    4.Now, whenever i boot the system i keep getting the same error.

    NOTE:

    1. I am proceeding using the standard setup and not using Murphy78's script.
     
  19. Enthousiast

    Enthousiast MDL Tester

    Joined:
    Oct 30, 2009
    Messages:
    35,567
    Likes Received:
    59,637
    Trophy Points:
    450
    That's what i said from the beginning. not updated boot.wim works always, uptodate x64 boot.wim doesn't work with standard setup, but works with murphy78's script, uptodate x86 boot.wim works fine with standard setup and script.
     
  20. Enthousiast

    Enthousiast MDL Tester

    Joined:
    Oct 30, 2009
    Messages:
    35,567
    Likes Received:
    59,637
    Trophy Points:
    450
    Install CU after enabling .net 35, the CU can have update components for .net 35. Best is to pre-enable dotnetfx on the mounted wim, and integrate the CU after that.