pennsylvaniaron Posted June 15, 2016 Posted June 15, 2016 1 hour ago, Thiersee said: At the moment my VM (installed with Conv-Rollup) searches since 1 hour.... I know this might be difficult to answer but I'm at my wits end. I am using an april 2016 win 7_64 updated ISO made by LEGO. I have incorporated the May 2016 updates from this thread. On some machines I cannot get windows update to find any new updates. It just keeps searching for hours. However on other machines it works fine. It worked on my VM (on my main computer) because I always test the new ISO I create. The latest machine I used it on yesterday still cannot get past finding any new updates. Initially this machine also failed sfc after I used all my silent installs, including mbam, ccleaner, cryptoprevent, GWX, adobe FP, reader dc, googletoolbar. However, sfc corrected the files. I ran sfc again and then it PASSED. I thought that was the reason for winupdate to not work but winupdate still searching. I then took another HD in this machine, did a new install with same ISO and immediately did an sfc (passed) and then checked for updates. It's still searching....grrrr When this iso works this is the scenario: 5 minutes after the installation if you manually go to win update there will be in my case about 12 or so updates ready to get installed. If after 5 minutes you manually go to win update and it wants you to search for new updates I know its futile. In addition I have tried literally a dozen fixes via google searches for a repair and nothing works. spent hours and am totally frustrated. I cant seem to get a working ISO. I wrote to lego and even he is stumped. using wtk 1.5.4.4.... regards.... Quote
pennsylvaniaron Posted June 15, 2016 Posted June 15, 2016 20 hours ago, rhahgleuhargh said: @pennsylvaniaron Yes it's due to the fact I putted " " in the name of the fisrt category, it causes a crash if you have checked "category as subfolder" option. Uncheck it or wait for the next UL release, I've corrected that. yes I unchecked subfolder and now it works. thanks. Now that I can see the files what are the first 2 "convenience" updates as compared to the "classic". From recollection these are new to me. Am I supposed to COMBINE both categories? In other words should I incorporate BOTH into my ISO? regards... Quote
rhahgleuhargh Posted June 15, 2016 Author Posted June 15, 2016 since 2 monthes, M$ servers are busy and saturated the 3 days following Patch Tuesday. Even on my Windows 10 installation it was very long to obtain the updates. My opinion : WU needs a fix or M$ should revise the manner to obtain updates. Quote
pennsylvaniaron Posted June 15, 2016 Posted June 15, 2016 6 minutes ago, rhahgleuhargh said: since 2 monthes, M$ servers are busy and saturated the 3 days following Patch Tuesday. Even on my Windows 10 installation it was very long to obtain the updates. My opinion : WU needs a fix or M$ should revise the manner to obtain updates. yes that theory at this point makes the most sense. It was even suggested in some of the blogs I visited when trying to repair. I'll check it out later. regards... Quote
rhahgleuhargh Posted June 15, 2016 Author Posted June 15, 2016 1 minute ago, pennsylvaniaron said: yes I unchecked subfolder and now it works. thanks. Now that I can see the files what are the first 2 "convenience" updates as compared to the "classic". From recollection these are new to me. Am I supposed to COMBINE both categories? In other words should I incorporate BOTH into my ISO? regards... Just be patient, this bug will be solved for next release. The 2 integration methods can coexist. In next release, all updates related to Convenience Rollup will be numeroted. Quote
Thiersee Posted June 15, 2016 Posted June 15, 2016 (edited) Half an hour ago I terminated the search in my VM, I didn't want to wait longer. Ten minutes ago I started the VM and the search again: I got immediately the list of requests! I started the installation and I wait and wait.... Edit: Just now finished.... @pennsylvaniaron The first category contains only the Convenience -Rollup the second contains the common patches for method 1 (with rollup) and method 2 (classic, like up to may) the third contains all the patches only for method 2 (classic). It means: if you are using the rollup-methode you need category 1 & 2 if you are using the classic-methode you need category 2 & 3 All other categories are related to both ways. BTW, I tested the Rollup-methode (Professional x64) with WTK 1.5.4.4 with this .INI and it works very good: rollup-pack (KB3125574) just before the patches for may Spoiler *AIO|v1.5.4.4|2016-06-13_21-20-PM #Silent Installs KB2533552::N/A (Not Needed);NO;9,23 MB;E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2533552-x64.msu;Always Installed #Updates E:\WUD_Convenience_Rollup\x64\ADD-Windows6.1-KB3064209-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3020369-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2670838-x64.msu E:\WUD_Convenience_Rollup\x64\ADD-Windows6.1-KB3102429-v2-x64.msu E:\WUD_Convenience_Rollup\x64\ADD-Windows6.1-KB3139923-v2-x64.msu E:\WUD_Convenience_Rollup\x64\ADD-Windows6.1-KB3140245-x64.msu E:\WUD_Convenience_Rollup\x64\ADD-Windows6.1-KB3156417-x64.msu E:\WUD_Convenience_Rollup\x64\RDP-Windows6.1-KB2574819-v2-x64.msu E:\WUD_Convenience_Rollup\x64\RDP-Windows6.1-KB2592687-x64.msu E:\WUD_Convenience_Rollup\x64\RDP-Windows6.1-KB2813347-x64.msu E:\WUD_Convenience_Rollup\x64\RDP-Windows6.1-KB2830477-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB971033-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2545698-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2547666-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2667402-v2-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2676562-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2698365-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2729094-v2-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2732059-v5-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2750841-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2761217-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2773072-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2834140-v2-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2862330-v2-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2894844-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2900986-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2919469-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2970228-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2984972-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3004375-v3-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3006137-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3059317-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3118401-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3123479-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3138378-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3138612-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3142024-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3145739-x64.msu E:\WUD_Convenience_Rollup\x64\WUClient-SelfUpdate-ActiveX-x64.cab E:\WUD_Convenience_Rollup\x64\WUClient-SelfUpdate-Aux-TopLevel-x64.cab E:\WUD_Convenience_Rollup\x64\WUClient-SelfUpdate-Core-TopLevel-x64.cab E:\WUD_Convenience_Rollup\x64\Windows6.1-kb3125574-v4-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3150220-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3153171-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3153199-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3153731-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3155178-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3156013-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3156016-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3156017-x64.msu E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3156019-x64.msu E:\WUD_Convenience_Rollup\x64\IE11\IE11-Windows6.1-x64-de-de.exe E:\WUD_Convenience_Rollup\x64\IE11\IE11-Windows6.1-KB3154070-x64.msu #Options Compatibility Check Enable CMD Force Unsigned Log Registry Changes Prepare Drivers Prompt Addons Prompt Drivers Prompt Gadgets Prompt Silent Prompt Themes Prompt Updates Prompt Wallpapers Rebuild Image Retry Updates Show Duplicates Edited June 15, 2016 by Thiersee Quote
pennsylvaniaron Posted June 15, 2016 Posted June 15, 2016 Thiersee plz excuse my newbieness on this subject but what is the "convenience rollups?". In addition are you saying when using WUD I should download EITHER the classics or the CONVENIENCE or download BOTH and incorporate them into my last months win 7_64 ISO? regards... Quote
pennsylvaniaron Posted June 15, 2016 Posted June 15, 2016 (edited) 3 hours ago, rhahgleuhargh said: since 2 monthes, M$ servers are busy and saturated the 3 days following Patch Tuesday. Even on my Windows 10 installation it was very long to obtain the updates. My opinion : WU needs a fix or M$ should revise the manner to obtain updates. I have to say I now disagree with this theory. I just tried updating again. my working computers are getting new updates for defender regularly. On a working computer if you do a manual check for updates and there aren't any win update informs you. on the non working one it just keeps CHECKING. It never ends. Win update is corrupted somehow on my ISO and I can't figure it out. This is no way to create an updated slipstreamed ISO. I am giving people a corrupted win 7 setup from the get go. somehow when all these updates get integrated something is amiss....very frustrating.. regards... Edited June 15, 2016 by pennsylvaniaron Quote
Thiersee Posted June 15, 2016 Posted June 15, 2016 (edited) 37 minutes ago, pennsylvaniaron said: Thiersee plz excuse my newbieness on this subject but what is the "convenience rollups?". In addition are you saying when using WUD I should download EITHER the classics or the CONVENIENCE or download BOTH and incorporate them into my last months win 7_64 ISO? regards... @pennsylvaniaron No, no, you misunderstood me (oder, better, I explained it to simply ) Convenience-Rollup is a package (KB3125574) released by MS on May 2016, containing almost all patches (but not all!) since release of SP1 though April 2016. This package has some prerequisite to observe. You can build an actual ISO in the way used up to May 2016 (WUD, Classic): you need category 2 (Common) & 3 (Classic) OR you can build it with this new package (Convenience Rollup): you need category 1 (Convenience Rollup Pack Update) & 2 (Common). This is the "basis"; if you need some other features (RDP 8.0 or 8.1, additional patches, IE11 and so on) it's up to you: for this purpose you can use the other categories of WUD. BTW, I don't know how do you build your ISO, but I don't think WUD-ULs are the right choice to implement some patches in your last month ISO. Regards, Thiersee Edited June 15, 2016 by Thiersee Quote
Thiersee Posted June 15, 2016 Posted June 15, 2016 @rhahgleuhargh It's courious: I just tried a deep cleaning on the VM I installed using the convenience rollup package and updated with the patches of june and it did not uninstall the replaced patches (it did not find anything to uninstall...). Quote
rhahgleuhargh Posted June 15, 2016 Author Posted June 15, 2016 (edited) @Thiersee EDIT : same observation for me. The only ones I had after deep-clean of my Convenience Rollup VM are usual KB2685811/13 and KB253411 (present in ISO). @pennsylvaniaron All my VM are OK with WU this evening. I don't understand why. I'm not sure WU is corrupted, but it seems regarding to abbodi1406 comments that the 3 old WUclient cabs are needed even if they are superseeded by KB3138612 (classic integration) and Convenience Rollup (newest WU Client, but KB3138612 still requested !). I putted them back in next UL release. Concerning Convenience Rollup, it's like a SP containing most important updates since SP1. Integrating it instead of classic method saves time, saves spaces in your final installation (1.5 Go). But some updates are still required, that's why I create the common Updates category. I'll update first post when I'll upload the new ULs. Edited June 15, 2016 by rhahgleuhargh Quote
pennsylvaniaron Posted June 15, 2016 Posted June 15, 2016 thiersee you have been very helpful. I didn't know anything about this convenience rollup. now I understand much more. so it does seem like its almost a sp2 for win 7? what I am doing as I write is using lego's april iso which I ASSume has the convenience rollup. not sure how he made it. I am not introducing anything update wise from may or june. its almost finished. it has my silent installs and some minor component removals, net 4.6, and some files I use placed on the desktop for convenience. I will do an sfc and winupdate and report back in a few minutes. regards... Quote
Thiersee Posted June 15, 2016 Posted June 15, 2016 @rhahgleuhargh Quote EDIT : same observation for me. The only ones I had after deep-clean of my Convenience Rollup VM are usual KB2685811/13 and KB253411 (present in ISO). I had KB2685811/813 on a try a couple of days ago: normally I install them later, but I forgot them in the list during integration, so I installed them twice.... KB2534111 was the only difference between W7SP1 RTM and W7SP1_u (Media Refresh); so if somebody uses the old ISO without media-refresh should not get it uninstalled. And indeed, deep clean depends on, how the system has been originally installed, classic- or rollup-way. Quote
pennsylvaniaron Posted June 15, 2016 Posted June 15, 2016 I just ran sfc on this april iso and it passes. I also ran win update on my main computer (using it to write this) and it took a little longer than usual but found 12 new updates which have to be the newest just released. The april iso using manual winupdate has the red X saying it has never been checked or run. Its still checking some 20 minutes or so... if my computer found 12 new updates then it cant be Microsoft servers. I believe lego is making a new iso. maybe that will solve the problem.... regards... Quote
bphlpt Posted June 16, 2016 Posted June 16, 2016 @pennsylvaniaron, The problems with WU/MU, especially with "older" OS such as Windows 7, have been going on for quite awhile and have been getting worse. My Windows 7 Ultimate x64 system was completely up to date with WU/MU on Monday, and would pass SFC with no errors. Running WU/MU today took well over an hour to "scan" before it came up with the list of available updates. Then it took well over another hour to install those same updates. In both cases it was just sitting there doing nothing most of the time. After restarting I double checked and it still passes SFC. I then let WU/MU rescan and this time it only took about 5 minutes to come back with info that there was a Security Essentials update and it took less than 5 min to install it, and less than 5 min for another rescan to confirm that WU/MU was now happy and completely up to date again. The situation of WU/MU taking an extremely long time for the initial scan and for the initial install at both the time of the initial Windows 7 OS install and then again after every patch Tuesday is now expected behavior for many people. Which updates that need to be installed first to "fix" this situation seem to vary and don't consistently work for everyone. After the first successful update session each month succeeding runs are better, but the first time is a real bear. If anyone can come up with a reliable solution that works for everyone it would really be appreciated. Cheers and Regards Quote
Legolash2o Posted June 16, 2016 Posted June 16, 2016 Installation of 3145739 before running Windows Update will speedup Windows Update. Quote
bphlpt Posted June 16, 2016 Posted June 16, 2016 KB3145739 was installed on my system 10 days ago, when I last reinstalled my OS, and is still in place. Having it didn't help my initial scan and install today after patch Tuesday. Unless you're saying that I should have uninstalled it and reinstalled it before today's updates? Or maybe that I should be happy with my experiences today because they would have been even worse if I didn't have KB 3145739 installed? LOL Glad to see you around Liam! [OT] @Liam, if I could please ask a favor. At this point anyone that installs Windows 7 probably wants to keep Windows 7 and doesn't want to upgrade downgrade to Windows 10. So the next time you make your updated ISO could you please NOT include the following KB's: KB971033, KB2952664, KB3021917, KB3035583, KB3068708, KB3080149, and KB3123862. Assuming that an install of your ISO passes SFC and can still be updated by the user with those updates or any other updates that come up in the future, then I think that your ISO would appeal to the widest audience possible. Thanks for considering my request. [/OT] Cheers and Regards Quote
rhahgleuhargh Posted June 16, 2016 Author Posted June 16, 2016 (edited) Hello, Changelog pour juin (identique x86 x64) : W10 / Telemetry Updates : KB3035583 v3 mis à jour ; KB2952664 passe en v18 (mai) Additional Updates : KB3080079 passe dans la catégorie "Classic integration Updates" (incluse dans le Convenience Rollup Pack et nécessaire pour KB3140245) RDP 8.1 : le prérequis KB2857650, KB2923545, KB3020388, KB3075226, KB3126446, et KB2923545 passent dans la catégorie "Classic integration Updates". Les 3 mises à jour restantes sont renommées 1-RDPWindowsxxx.msu. ATTENTION, les mises à jour RDP doivent être intégrées avant le Rollup ! Common Updates : KB3139923 v2 et KB3140245 deviennent prioritaires, KB3159398, KB3161561 remplace KB3156417 et KB2536275, KB3161664 remplace KB3153199, KB3161949 remplace KB2888049, KB3161958, KB3164033 remplace KB3140735, KB3164035 remplace KB3156013, KB3162835 remplace KB3153731 Restauration des fichiers .cab de l'ancien client WU, certains éléments ne sont pas remplacés par KB3138612 ou le Convenience Rollup Pack. IE 11 Updates : KB3060005 remplace KB3154070 Installateurs / Setup installer files : Ajout de KB2506143 Windows Management Framework 3.0 Deep-clean : nettoyage de KB2585542 et KB3072630 (classic integration updates) Les Uls donnent la possibilité d'intégrer soit par le Convenience Rollup Pack, soit par la méthode classique. Toutes les mises à jour liées au Rollup sont numérotées pour faciliter l'intégration (1- prérequis et RDP 8.1, 2- mises à jour pré Rollup, 3- Rollup, 4- mises à jour post Rollup, 5- Mises à jour RunOnce). Thiersee a demandé à ce que KB3020609 et KB2673808 soient intégrées par Wintoolkit dans les prérequis. Ceux qui veulent rester sur une intégration classique doivent intégrer les mises à jour communes (1-, 2-, 4-, 5-), et celles non numérotées. Toutes les mises à jour parues après le Rollup sont communes avec celles de l'intégration classique. rien ne change pour les mises à jour additionelles et W10. Ceux qui veulent masquer les mises à jour W10 après Rollup doivent utiliser le SFX Rollup au lieu du W10. You can now integrate updates via Convenience Rollup Pack or via classic integration method. All related Convenience Rollup updates are now numeroted, just select them if you prefer to choose this integration method (more faster) : 1- for prerequisites and RDP updates (Thiersee asked Legolash2o to move KB3020609 and KB2670838 in prerequiste category), 2- for updates before Rollup, 3- Rollup itself, 4- Post rollup updates. Those who prefer to stay with a classic integration should integrate common updates (1-, 2-, 4-, 5-), and all other Windows6.1xxx.msu updates. Nothing has changed for Additional and W10 related updates. If you want to hide W10 related updates after Convenience Rollup integration method, please use the Rollup SFX instead of the W10. Test de validation des ULs en cours, je les uploade dès que possible. Je pense que dorénavant je ne ferai plus que des tests via intégration par le Convenience Rollup Pack, je n'ai pas assez de temps libre et plus assez d'espace disque pour créer d'autres machines virtuelles ! Ceux qui veulent tester par intégration classique peuvent reporter les résultats de leurs tests, merci. Edited June 16, 2016 by rhahgleuhargh Quote
Thiersee Posted June 16, 2016 Posted June 16, 2016 (edited) 5 hours ago, rhahgleuhargh said: Hello, ....... RDP 8.1 : le prérequis KB2857650 passe dans la catégorie "Classic integration Updates". Toutes les autres mises à jour restent nécessaires, y compris via le Convenience ....... rien ne change pour les mises à jour additionelles, RDP 8.1 et W10. Ceux qui veulent masquer les mises à jour W10 après Rollup doivent utiliser le SFX Rollup au lieu du W10. ..... Nothing has changed for RDP 8.1.... @rhahgleuhargh Are you really sure? As I installed with the old list from 08-06-2016 (Convenience Rollup!) Deep Cleaning has uninstalled: KB2857650, KB2923545, KB3020388, KB3075226, KB3126446, for both x86 & x64. I wrote it already in a previous post (monday, page 53). I'll do another test. Thiersee Edit: The numbered files are very confusing (my opinion!) Edited June 16, 2016 by Thiersee Quote
rhahgleuhargh Posted June 16, 2016 Author Posted June 16, 2016 @Thiersee Yes, I can confirm it ! I made a test this morning in x86 with only prerequisite KB2574819, and the 2 other updates KB2830477 and KB2592687 : all others RDP updates except KB2857650, and 2 other old KBs related to RDP 8.0 were asked at my first WU as critical updates ! it wasn't the case with my previous test with may UL. All is OK with a new test integrating all RDP updates except KB2857650. I didn't reproduce the same test in x64, I included the 8 RDP updates. Quote
rhahgleuhargh Posted June 16, 2016 Author Posted June 16, 2016 (edited) 1 hour ago, Thiersee said: @rhahgleuhargh Edit: The numbered files are very confusing (my opinion!) Sorry I haven't found any better solution. The big advantage is that you can do the Rollup integration in one pass, the correct updates order is preserved. When using classic integration method you just have to catch all KBs with CTRL + A, and then unselect the rollup , ADD and W10 updates if not needed. An other solution is to check the option of creating folders for each category, but it is making the integrating task more difficult. Or create separated ULs for classic or Rollup integration ? too complex to maintain ! Edited June 16, 2016 by rhahgleuhargh Quote
Thiersee Posted June 16, 2016 Posted June 16, 2016 (edited) 41 minutes ago, rhahgleuhargh said: Sorry I haven't found any better solution. The big advantage is that you can do the Rollup integration in one pass, the correct updates order is preserved. When using classic integration method you just have to catch all KBs with CTRL + A, and then unselect the rollup , ADD and W10 updates if not needed. An other solution is to check the option of creating folders for each category, but it is making the integrating task more difficult. Or create separated ULs for classic or Rollup integration ? too complex to maintain ! I understand, but there is no relationship between category-number and download-number, and that's confusing me! I just finished one of my final installations (VM, x86) and I did NOT get any request regarding RDP! Could be eventually the sequence of integration or the presence of KB2813347? I integrated for RDP 8.1 Quote E:\WUD_Convenience_Rollup\x86\RDP-Windows6.1-KB2574819-v2-x86.msu E:\WUD_Convenience_Rollup\x86\RDP-Windows6.1-KB2592687-x86.msu E:\WUD_Convenience_Rollup\x86\RDP-Windows6.1-KB2813347-x86.msu E:\WUD_Convenience_Rollup\x86\RDP-Windows6.1-KB2830477-x86.msu BTW: 1) KB2813347 (in the UL) should have been replaced by KB3075220, but this one is needed only if RDP 8.1 is not installed http://catalog.update.microsoft.com/v7/site/ScopedViewInline.aspx?updateid=e31f669c-cc33-40a3-954c-47bd3c6fa68e (details) 2) KB2923545 has been replaced by KB3125574 (Rollup) http://catalog.update.microsoft.com/v7/site/ScopedViewInline.aspx?updateid=b3cd5165-7bda-468f-95fa-b8b2f36d085e (details) Thiersee Edited June 16, 2016 by Thiersee Quote
rhahgleuhargh Posted June 16, 2016 Author Posted June 16, 2016 (edited) Maybe it could be due to the presence of KB2813347, I don't remember why I didn't include it in my test. I don't know how the sequence of integration is changing anything, since you install first the prerequisites. So if you succeeded with this one, it's OK for me ! I'll move KB2923545 in the Classic integration category like the other prerequisite. ULs reuploaded and post edited. Edited June 16, 2016 by rhahgleuhargh Quote
pennsylvaniaron Posted June 16, 2016 Posted June 16, 2016 14 hours ago, bphlpt said: KB3145739 was installed on my system 10 days ago, when I last reinstalled my OS, and is still in place. Having it didn't help my initial scan and install today after patch Tuesday. Unless you're saying that I should have uninstalled it and reinstalled it before today's updates? Or maybe that I should be happy with my experiences today because they would have been even worse if I didn't have KB 3145739 installed? LOL Glad to see you around Liam! [OT] @Liam, if I could please ask a favor. At this point anyone that installs Windows 7 probably wants to keep Windows 7 and doesn't want to upgrade downgrade to Windows 10. So the next time you make your updated ISO could you please NOT include the following KB's: KB971033, KB2952664, KB3021917, KB3035583, KB3068708, KB3080149, and KB3123862. Assuming that an install of your ISO passes SFC and can still be updated by the user with those updates or any other updates that come up in the future, then I think that your ISO would appeal to the widest audience possible. Thanks for considering my request. [/OT] Cheers and Regards liam yes this is a good suggestion. july 29th is around the corner and no one knows what Microsoft is going to do with the "free" offer. just one client of many that I have dealt with wanted the free win 10. all others want win 7. NOTE: on the april iso (updated to may 18) having trouble updating in WU>>>>I left the clients computer on overnight. I changed the power options to HIGH PERFORMANCE" so it would not sleep. In the morning the little blue icon was showing near the clock indicating there were updates to be installed. There were only 2 (file validation and june malicious tool). So it seems that what others are saying about WU is true. The servers are slow et al. ISO is GOOD!! regards... Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.