Thiersee Posted March 25, 2018 Share Posted March 25, 2018 (edited) On 16.3.2018 at 5:19 PM, Thiersee said: Now the last report from me: After installing with the February-UL I do not get KB4088875 requested anymore, I don't know why. 1) After install, restart and search I get only KB4075211 (Preview, released on 22.02.2018) requested. 2) I install this one and after restart and new search I get sometimes KB4091290 ("repair" of KB4075211 and released on 01.03.2018) plus KB4088875, sometimes KB4091290 plus 4 old patches: only after installing this 4 patches I get finally KB4088875 requested. As I said: I do not really know why ! BTW: DeepCleaning after this procedure almost 1GB! @rhahgleuhargh After two days of intensive testing I got the explanation! With the actual version of MSE-definition-updates the AV.reg (QualityCompat) is not installed anymore, at least since 6th of march (my 2nd oldest definition update for MSE)! 1) Fresh install with February UL (but with updated MSE!): no requests from WU for newer update, only 4 old patches for windows and 2 for FW, look at picture 1. 2) Manually inserted QualityCompat-REG, restart (not really necessary), new search: ONLY the actual preview kb4088881, MRT and eventually MSE definition updates, look at picture 2 & 3; deleting reg-key, same requests like point 1). 3) Fresh install with March UL, old MSE (up to 6th of March): ONLY the actual preview kb4088881, MRT and eventually MSE definition updates, look at picture 2 & 3. 4) I decided to integrate the QualityCompat-Key per Tweak in WTK, fresh install with today's definition updates for MSE: ONLY the actual preview kb4088881, MRT and eventually MSE definition updates, look at picture 2 & 3; again, deleting the key from registry: same requests like point 1). So, let us wait for what MS will do in the April -rollup.....; anyway the reg-key is now necessary for new installs with an updated MSE. Have a nice week ! Edited March 25, 2018 by Thiersee Quote Link to comment Share on other sites More sharing options...
rhahgleuhargh Posted March 26, 2018 Author Share Posted March 26, 2018 @Thiersee Thanks for these tests. So it's still needed to add the keyreg ! This key is present in the icare's RunOnce silent SFX, but those who don't use it will need to add it. Have a nice week too ! Quote Link to comment Share on other sites More sharing options...
Thiersee Posted March 30, 2018 Share Posted March 30, 2018 Again a patch for a patch for a patch...... KB4100480, released 29.03.2018, only x64! Happy Easter & Joyeuses Pâques! Quote Link to comment Share on other sites More sharing options...
mooms Posted March 30, 2018 Share Posted March 30, 2018 Thanks Thiresee, to you too. https://www.ginjfo.com/actualites/securite-informatique/windows-7-et-kb4100480-une-mise-jour-critique-de-securite-se-deploie-20180330 https://www.bleepingcomputer.com/news/microsoft/microsoft-issues-out-of-band-security-update-for-windows-7-and-windows-server-2008/ Ils corrigent une vulnérabilité introduite par leur patch Meltdown, ça concerne W7 et 2008 en 64 bits. Quote Link to comment Share on other sites More sharing options...
Thiersee Posted March 30, 2018 Share Posted March 30, 2018 The problem will be in WinToolkit: it integrates this patch first and then the monthly rollup... Quote Link to comment Share on other sites More sharing options...
rhahgleuhargh Posted March 30, 2018 Author Share Posted March 30, 2018 (edited) @Thiersee I've uploaded updated UL with KB4100480. Does the fact that WTK integrates it before monthly rollup induce some problems ? The only solution is to integrate it in RunOnce until WTK will be updated. Or wait for next patch tuesday (new rollup will certainly include it). Edited March 31, 2018 by rhahgleuhargh Quote Link to comment Share on other sites More sharing options...
Thiersee Posted March 30, 2018 Share Posted March 30, 2018 I don't know, sorry! We should know if this patch closes an already present hole or if it prevents that such an hole opens ....... Quote Link to comment Share on other sites More sharing options...
rhahgleuhargh Posted March 30, 2018 Author Share Posted March 30, 2018 Just now, Thiersee said: I don't know, sorry! We should know if this patch closes an already present hole or if it prevents that such an hole opens ....... To be or not to be, that is the question ! Happy Easter ! Quote Link to comment Share on other sites More sharing options...
abbodi1406 Posted March 31, 2018 Share Posted March 31, 2018 Integration order has no affect for 4100480 the new 4099950 is not integratable rhahgleuhargh 1 Quote Link to comment Share on other sites More sharing options...
Thiersee Posted March 31, 2018 Share Posted March 31, 2018 And again a patch for a patch for a patch.... KB4099467 Quote Link to comment Share on other sites More sharing options...
ikon Posted March 31, 2018 Share Posted March 31, 2018 4099950 no problem with integrate Quote Link to comment Share on other sites More sharing options...
abbodi1406 Posted April 1, 2018 Share Posted April 1, 2018 7 hours ago, ikon said: 4099950 no problem with integrate It can be integrated, but it will not fix the issue (if present) just like KB3046269 and KB2603229 although in KB4099950 case, if latest rollup is integrated offline before installing the OS, the NIC issue will not occur Quote Link to comment Share on other sites More sharing options...
Thiersee Posted April 2, 2018 Share Posted April 2, 2018 On 1.4.2018 at 6:44 AM, abbodi1406 said: ...... although in KB4099950 case, if latest rollup is integrated offline before installing the OS, the NIC issue will not occur It means the patch is not necessary? Anyway, it would be interesting what MS means with this Info on KB4099950 Quote More information Important: This update must be installed prior to installing KB408875 or KB408878 The most people have set Windows to update automatically. Quote Link to comment Share on other sites More sharing options...
rhahgleuhargh Posted April 2, 2018 Author Share Posted April 2, 2018 @Thiersee In my VMs (fresh installs with KB408875 integrated offline) KB4099950 is proposed as optional update. Quote Link to comment Share on other sites More sharing options...
abbodi1406 Posted April 3, 2018 Share Posted April 3, 2018 KB4099950 contain PCIClearStaleCache.exe which can be executed on live OS only it checks pci.sys version and clear the registry cache for NIC (if exist) if KB4088875 is integrated offline, the stale cache will not exist, and KB4099950 will just ran and installed without fixing anything Quote Link to comment Share on other sites More sharing options...
rhahgleuhargh Posted April 10, 2018 Author Share Posted April 10, 2018 (edited) Hello, Voici ce que donne le Patch Tuesday de ce mois-ci : Security Monthly Quality Rollup : KB4093118 remplace KB4088875 et KB4100480 (x64) Common Updates : KB4099950 (RunOnce) passe prioritaire Telemetry Updates : KB2952664 v24 mise à jour Je ferai les tests d'ici la fin de la semaine. Edited April 11, 2018 by rhahgleuhargh Quote Link to comment Share on other sites More sharing options...
mooms Posted April 10, 2018 Share Posted April 10, 2018 Chez moi KB4099950 ne m'est pas proposée, mais je suppose que c'est normal puisque d'après l'article de la KB : Quote Important This update must be installed before you install KB4088875 or KB4088878. Du coup on se demande comment corriger le problème rencontré pour tous les gens comme moi qui ont installé les màj via WU dès leur sortie...Et aussi si elle servira à quelque-chose si installée en intégration via RunOnce... (C'est KB2952664 pour la télémétrie ). Quote Link to comment Share on other sites More sharing options...
Thiersee Posted April 10, 2018 Share Posted April 10, 2018 From the MS-article KB4088875: Quote A new Ethernet Network Interface Card (NIC) that has default settings may replace the previously existing NIC, causing network issues after you apply this update. Any custom settings on the previous NIC persist in the registry but are unused. This issue is resolved by KB4099950 which will be automatically applied when installing this update Just yesterday I updated my 2nd W7-installation on work-pc and observed this WU-behavior: 1) WU requested KB4074598; I installed it and after restart and one or two new search 2) WU requested KB4099950 and 4100480; I install them and after restart and one or two new search 3) WU requested finally (and not earlier!) KB4088875; I installed it, then restart WU did not request other patches. May be MS means KB4088875 will not be asked until the other have been installed. Then, of course, today KB4093118; in the same article MS says this one corrects the problems of KB4088875 and the reg-key QualityCompat is not necessary anymore. Quote Link to comment Share on other sites More sharing options...
rhahgleuhargh Posted April 11, 2018 Author Share Posted April 11, 2018 @mooms, KB4099950 m'a été demandée sur toutes mes machines virtuelles bien que j'aie au préalable déjà installé KB4088875 (la première version) via WU. Après est-ce que ça marche ou pas, si installée après, bonne question ! Si on doit lancer plusieurs rounds de redémarrages avant d'installer des mises à jour cumulatives, je pense qu'on n'a pas fini ! Erreur typo corrigée sur KB2952664. Quote Link to comment Share on other sites More sharing options...
Thiersee Posted April 11, 2018 Share Posted April 11, 2018 Tested x86-integration of KB4093118 instead of KB4088875, KB4099950 under silent-installers: no issues or requests from WU. The REG-key (QualityCompat) is still necessary, otherwise WU will ask for 4 old update for windows and 2 for NET-FW: have a look to the pictures in my post from March 25 This page or the previous one). May be tomorrow I can test x64. Quote Link to comment Share on other sites More sharing options...
rhahgleuhargh Posted April 12, 2018 Author Share Posted April 12, 2018 Testé en x64 avec KB4099950 en RunOnce : RAS. Quote Link to comment Share on other sites More sharing options...
rhahgleuhargh Posted April 13, 2018 Author Share Posted April 13, 2018 Uls mises à jour et uploadées. Quote Link to comment Share on other sites More sharing options...
mooms Posted April 13, 2018 Share Posted April 13, 2018 Elle sont datées du 1er Avril, ça ressemble à un poisson Quote Link to comment Share on other sites More sharing options...
rhahgleuhargh Posted April 13, 2018 Author Share Posted April 13, 2018 Oui, j'ai vu ça ! problème de 0 corrigé ! Quote Link to comment Share on other sites More sharing options...
pennsylvaniaron Posted April 17, 2018 Share Posted April 17, 2018 Guys I was away on vacation for 12 weeks. Tried following the last page or 2 of posts, but difficult without actually doing tests on a VM. I will be using the April UL's. I only make the x64 version of home premium. I'll also be incorporating ricktendos NFW 4.7.1 (1/13/2018) in my silent list. I'll be using WTK1.6.0.1. I see that there is a WTK v.1.6.0.5 on the public page, but I get an error every time I start it. Is this a known problem? Will I have to add the AV.REG file to WTK tweaks? Is that regfile still necessary to continue to get future WU? Anything else to be on the lookout for? regards... Quote Link to comment Share on other sites More sharing options...
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.