Jump to content

rhahgleuhargh

Members
  • Posts

    1,328
  • Joined

  • Last visited

  • Days Won

    52

Posts posted by rhahgleuhargh

  1. @Thiersee,

    I tried to remove previous july rollup pack, but in x64 KB3172605 is still requested as optional update and the 2 superseeded updates by KB3172605 as important updates. After install of KB3172605 all is fine. so this update is superseeded only in x86. Strange for a "cumulative" rollup... I confirm that KB3162835 is superseeded.

    I'll change the UL's date in the link. It's simplier for me to keep the same name in Mediafire. Please wait for an hour to reDL updated ULs.

  2. 3 hours ago, Alpha_95 said:

    @rhahgleuhargh  Je sais bien mais pourquoi se retrouve t'il caché alors que de base, il ne le devrait pas... Ce n'est pas trop grave certes.

    edit: je viens d'avoir la KB3177723 en supplément et en facultatif, la KB3179573

     

    désolé mais je ne comprends pas ce que tu veux dire. Sur mes tests tout est OK. Caché où ? dans la fenêtre "restaurer les mises à jour masquées" ? cela peut arriver lorsqu'on édite mal le fichier .vbs (bug lié aux " "), toutes les mises à jour y compris les optionnelles comme Silverlight sont masquées ; dans ce cas, il faut juste refaire l'édition du script en utilisant les guillemets d'origine (un copier/coller de l'une des mises à jour fait l'affaire).

    Pour les autres mises à jour, elles sont sorties hier, j'attends plus d'infos avant de mettre les UL à jour.

  3. 21 hours ago, pennsylvaniaron said:

    I know we have gone over this before but just to be clear. When making a new win 7 iso every month (in my case classic) its BEST (but not necessary) to create it from a clean win 7 sp1 iso. Is this because there are superseded WU from the month before? In other words if I extract my 7/22/16 ul finished win 7 iso using wtk into a new folder and then download with WUD the latest aug. UL and then integrate them, I assume there are already integrated updates that have been superseded and may either cause a problem or its just not the cleanest way to do it? If that is correct can you simply do a deep clean after installation making it just like using a clean sp1 iso to start with?

    Obviously using the prior months iso is faster. If I use the clean sp1 iso with the new aug UL I still have to remember which updates are prerequisites and which updates belong in the SFX? If so are those 2 updates (don't have the kb's right now) still prereq's and are there still a few that go into the sfx?

    regards...

    As I wrote to you before, all is possible. Integrating latest UL updates in an untouched ISO is the cleanest way, but it's possible to only add new updates to the previous version : no need to readd the prerequisites since there are in your previous ISO, you'll only have to modify the WTK installer or setupcomplete.cmd folders with new MRT and/or updated DNF461 SFX. When there are not a lot of updates, it doesn't affect your new system (ie this month there were only 5 updates), but in case of a lot of superseeded updates, it's polluting it. Do as you want.

     

  4. Hello,

    Test des nouvelles ULs en cours !

    Changelog identique x86 x64 :

    IE 11 Updates : KB3175443 remplace KB3060005

    W10/Telemetry Updates : suppression de KB3035583, KB3123862, et KB3173040

    Common Updates : KB3178034, KB317725, KB3167679, KB3172605 ;  KB3161102 remplace KB3170735 et KB3155178 : j'ajoute cette mise à jour optionnelle de juillet car fortement recommandée par M$ (et permet de retirer 2 mises à jour). Pour ceux qui veulent quand même le journal de Windows, il peut être téléchargé ici.

    La migration gratuite vers 10 ayant pris fin, je vais également supprimer KB3035583, KB3123862, et KB3173040 des scripts.

  5. @pennsylvaniaron

    I just install KB2603229 and KB3046269 in RunOnce (I don't need KB2533552 no more as explained previously) and usually for my tests : icare's DNF461, MRT, icare RunOnce, and the script (W10 or Rollup depending the method). I limit the number of the programs to the strict minimum because it increases the installation process, and purpose of my test is just to check if updated ULs are correct. Updates hidden in the script are those by default (if you integrate KB2533552 you'll have to remove KB976932 in the .vbs script).

    Just 2 tips :

    - Beware to integrate KB3172605 that includes latest WU client, because the previous one induced some errors during the W10 scripts (too much memory used).

    - I allways place all RunOnce programs in the same folder, so it's easier to add the next one in the WTK installer list.

    About WTK installer : sometimes in the past I encountered some freezes with it, especially in x86, that's why I use setupcomplete.cmd method in this configuration. But (in my specific case) all is OK in x64.

    I'll make a new test for the next Patch Tuesday with the new VirtualBox version.

  6. @pennsylvaniaron

    If you encountered an error it's maybe because the .vbs file was not edited correctly.

    Spoiler

    Dim hideupdates(8)    'TO ADD 1 EDIT THE (11) AND ADD another hideupdates(#)

    hideupdates(0) = "KB2952664"
    hideupdates(1) = "KB3021917"
    hideupdates(2) = "KB3035583"
    hideupdates(3) = "KB3068708"
    hideupdates(4) = "KB3075249"
    hideupdates(5) = "KB3080149"
    hideupdates(6) = "KB3123862"
    hideupdates(7) = "KB976932"
    hideupdates(8) = "KB3173040"

    Be carefull to modify the first number in line  "Dim hideupdates(x)" when you add updates to hide : for example, if you add 2 updates to the original .vbs script the "x" number must be 10 instead of 8.

    Spoiler

    Dim hideupdates(10)    'TO ADD 1 EDIT THE (11) AND ADD another hideupdates(#)

    hideupdates(0) = "KB2952664"
    hideupdates(1) = "KB3021917"
    hideupdates(2) = "KB3035583"
    hideupdates(3) = "KB3068708"
    hideupdates(4) = "KB3075249"
    hideupdates(5) = "KB3080149"
    hideupdates(6) = "KB3123862"
    hideupdates(7) = "KB976932"
    hideupdates(8) = "KB3173040"

    hideupdates(9) = "KB......"

    hideupdates(10) = "KB...."

     

  7. @pennsylvaniaron

    Here are 2 screenshots : before running .cmd file (folder content after decompressing Hide_W10_KBs_Silent_SFX_maker.7z), and after running .cmd files : the Silent SFX are the .exe files (you don't need the .7z files, they're just a step before the silent SFX file). The icon specifies that they are SFX, you can't miss them. The only thing you have to do is to add W10.exe (classic integration) or Rollup.exe (Convenience Rollup method) in WTK installer list.

    I deleted previous files containing the created SFX because some people prefer to edit themselves the updates to hide. It was simplier to just upload the maker with default .vbs files. If you don't need to modify the .vbs scripts, just launch .cmd file and you're done.

    Image 1.pngImage 2.png

  8. @Thiersee

    I made a test long time ago, and if I remember good, adding KB2533552 in the .vbs list doesn't have any effect, you have to hide KB976932. But if you want to make the test, please report !

    For the translation, why not ? my german is not as good as before, and I don't speak italian.

    @pennsylvaniaron

    by default KB2533552 is masked in both Rollup and classic .vbs scripts. You need to create a silent SFX with the .cmd file to place it in your RunOnce program list.

×
×
  • Create New...