Windows 10 Hotfix Repository

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

  1. burfadel

    burfadel MDL EXE>MSP/CAB

    Aug 19, 2009
    2,627
    3,855
    90
    #2081 burfadel, Mar 23, 2016
    Last edited by a moderator: Apr 20, 2017
    actually it's for any w10 build after 10240 including insider previews

    Code:
    assembly version: 4.0.10608.16393
    files version   : 4.6.1532.0
    [/QUOTE]

    It says it's not applicable to insider preview build 14291, even if installed manually. The files version is 4.6.1528 on the insider preview though, not sure of the assembly version. I guess maybe the code is different in the Redstone Insider preview than TH2 Windows 10.
     
  2. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    12,918
    62,566
    340
    The 'any w10 build' is a theoretical sentence, based on update.mum applicability info

    since that latest 14xxx previews already include 4.6.2 (regardless the older version), it won't need this
    just like 10586 including 4.6.1

    as for assembly version, i'm sure it's like 4.0.14291.1001, so it takes precedence
     
  3. burfadel

    burfadel MDL EXE>MSP/CAB

    Aug 19, 2009
    2,627
    3,855
    90
    True, and we'll probably get files 4.6.1532.0 or newer in the next build anyway.

    People, don't forget to recompile runtime targets after installation of the update. This can be done easily with the Easy Ngen runner in my sig.
     
  4. farukkaraca

    farukkaraca MDL Member

    Sep 27, 2009
    169
    96
    10
  5. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    12,918
    62,566
    340
    .net 4.x is not part of win7 to have it as .cab update, it only can be installed with the .exe
     
  6. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    12,918
    62,566
    340
  7. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    38,284
    66,552
    450
    Don't need it, will test it ;):D

    But for now i'm already watching for 24hrs your Win7MUI2 script integrating alle 34LP's into a x86 en-us starter/enterprise install.wim/boot.wim and winre.wim :D Expect questions about dotnet461 lp's later ;):D
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. armond

    armond MDL Addicted

    Jun 16, 2008
    679
    223
    30
    Thanks so much, for another useful script. Just waiting for a possible Adobe Flash Player update to test it.
     
  9. Mr Been

    Mr Been MDL Senior Member

    Feb 24, 2008
    262
    69
    10
    #2089 Mr Been, Mar 25, 2016
    Last edited: Mar 25, 2016
    @abbodi1406

    First, thank you for your effort to help.

    But I can't manage to run this script. What I do ....

    1.) I set my target = F:\111 (extracted .ISO)
    2.) My 2 UPDs (.MSU) are in the same folder as 'W10UI.cmd' (c:\222)
    3.) DISM is in c:\windows\system32

    I press '0' to start, and the script immediatly closes.

    I've tried to mount an .ISO with Ultraiso to M:\ , same result.
    I've extracted Boot.wim and Install.wim to F:\111 , same result

    and the script should detect whether it's a Cumulative or a Service Stack update?

    Sorry, NoGo
     
  10. burfadel

    burfadel MDL EXE>MSP/CAB

    Aug 19, 2009
    2,627
    3,855
    90
    On my phone at the moment, will check it out when I get back. However, it's difficult to know what the update applies to by the file name alone, in terms of TH1, TH2, and likely RS1. If the update isn't relevant, it won't apply.
     
  11. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    12,918
    62,566
    340
    #2091 abbodi1406, Mar 25, 2016
    Last edited by a moderator: Apr 20, 2017
    I just replicated similar situation, all good

    how did you set the target? i mean through options or did you edit W10UI.cmd?

    in either way, or when pasting the path, don't use quotes marks ""
    at least not both after = mark
    wrong
    Code:
    set target="F:\111"
    correct
    Code:
    set "target=F:\111"
    set target=F:\111
    wrong
    Code:
    Enter the path for one of:
    .
    .
    
    "F:\111"
    correct
    Code:
    Enter the path for one of:
    .
    .
    
    F:\111
    you could open admin cmd in the script folder, then type W10UI.cmd to run it
    this allow to see the error messege without closing cmd window

    Cumulative update is treated as any normal update, it will be integrated to all wim files
    that applies to dynamic updates like KB3142588

    special updates are:
    servicing stack (installed first for all)
    adobe flash player (will no be integrated to boot.wim/winre.wim), example kb3144756
    .net 4.6 (will not be integrated to boot.wim/winre.wim), example KB3120830 or KB3102495
    oobe (will not be integrated to boot.wim/winre.wim), example KB3116278
    dynamic updates for setup media (will not installed at all), example KB3140744
     
  12. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    12,918
    62,566
    340
    true
    it's not even enough to check the version in .manifest files
    because some updates have different assembly version, yet applicable for different build version
    like .net 4.6.2 / 10608 -> applies to 10240 or 10586
    or rsat / 10514 -> applies to 10240 or 10586
     
  13. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    12,918
    62,566
    340
  14. Mr Been

    Mr Been MDL Senior Member

    Feb 24, 2008
    262
    69
    10
    #2095 Mr Been, Mar 25, 2016
    Last edited: Mar 25, 2016
    @abbodi1406
    how did you set the target? (I mean through options or did you edit W10UI.cmd)
    I did it through options 1. -- after starting the script.

    Enter the path for one of:
    .
    F:\111

    so I did .... The result is : 1. Target (x86): "F:\111"

    I'll try the new version later this evening.

    THANK YOU
     
  15. burfadel

    burfadel MDL EXE>MSP/CAB

    Aug 19, 2009
    2,627
    3,855
    90
    I know :). People don't realise that though! Can't even use KB number ranges, seeing as the same KB article applies to different OS variants. The best thing to do is keep your Windows 10 updates up to scratch and then the likelihood of any issues is greatly reduced. In other words, if people use WHDownloader and use the updates that apply to their OS as listed in there, as long as they apply the updates for 10586 on TH2, and only 10240 on TH1 (the RTM release) then it should be okay.

    On a separate note, what are the intentions for WHDownloader when Redstone is released? Redstone 1 in a couple of months or so, and Redstone 2 early next year. Will you update all releases as updates are available, or begin dropping 10240 once RS1 is released? People seem to already have lost track with two Windows 10 released, let alone three or four...
     
  16. burfadel

    burfadel MDL EXE>MSP/CAB

    Aug 19, 2009
    2,627
    3,855
    90
    #2097 burfadel, Mar 26, 2016
    Last edited by a moderator: Apr 20, 2017
    It is possible to do an applicability check for these, it just requires a few extra lines :).
     
  17. drew84

    drew84 MDL Expert

    Mar 13, 2014
    1,085
    1,664
    60
  18. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    12,918
    62,566
    340
  19. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    12,918
    62,566
    340
    Since w10 updates will be always a few for each build, i'll keep all official builds until further notice
    at least until they stop support for 10240 editions (other than LTSB)

    Yes it's possible, but it's not worth to complicate script for :D
    they are feature packs for rare cases and easy to install, not most to have or regular updates