Thiersee Posted March 15, 2018 Posted March 15, 2018 2 hours ago, mooms said: ....Par contre sur ma machine réelle (7x64) le nettoyage des màj obsolètes a été très très long au redémarrage. I can't confirm this issue: DeepCleaning tokes a short time (I did it last month too) and only the monthly-rollup from february was found. Quote
rhahgleuhargh Posted March 15, 2018 Author Posted March 15, 2018 Bug corrigé ! Il faut activer l'option "PAE/NX" au niveau du processeur de l'ordinateur virtuel. Ce n'est pas un bug de Virtualbox, mais de M$ : la mise à jour KB4088875 cause un souci avec la carte réseau virtuelle, plus d'infos ici. Quote
Thiersee Posted March 15, 2018 Posted March 15, 2018 (edited) I installed today 2 VMs (VirtualBox) with the UL from February and observed a strange behavior: on both WU did NOT ask for the March-Update KB4088875! On a working laptop, which I didn't update yet, KB4088875 is not requested by WU anymore, only the preview KB4075211 ! Can be possible, MS has token this patch from WU? I think I'll wait with the update of my ULs until there is a sure information from MS. Edited March 15, 2018 by Thiersee Quote
Pink_Freud Posted March 15, 2018 Posted March 15, 2018 (edited) 11 hours ago, rhahgleuhargh said: Bug confirmé : en machine virtuelle x86 avec la dernière mouture de Virtualbox, KB4088875 entraîne un écran bleu de la mort BSOD, que ce soit en mise à jour manuelle ou directement avec un ISO à jour (l'installation se passe bien, mais au premier redémarrage, boum !). Ce bug vient d'être reporté par quelqu'un sur le forum de Virtualbox, pour le moment pas de réponse. Je vais essayer de récupérer la version précédente de Virtualbox et retenter l'installation. Quelqu'un a-t-il eu le même souci ? 2 hours ago, rhahgleuhargh said: Bug corrigé ! Il faut activer l'option "PAE/NX" au niveau du processeur de l'ordinateur virtuel. Ce n'est pas un bug de Virtualbox, mais de M$ : la mise à jour KB4088875 cause un souci avec la carte réseau virtuelle, plus d'infos ici. Installed Win 7 Pro x64 in VBox (latest) with KB4088875 integrated & without "PAE / NX" option enabled... installed successfully, no BSOD after several reboots. Spoiler Edited March 15, 2018 by Pink_Freud Quote
rhahgleuhargh Posted March 15, 2018 Author Posted March 15, 2018 @Pink_Freud The BSOD occurs only with x86 configuration. I had no problem with x64 too. Activating PAE/NX option solved the problem. I'll upload updated ULs tomorrow. Pink_Freud 1 Quote
mooms Posted March 15, 2018 Posted March 15, 2018 3 hours ago, rhahgleuhargh said: Bug corrigé ! Il faut activer l'option "PAE/NX" au niveau du processeur de l'ordinateur virtuel. Ce n'est pas un bug de Virtualbox, mais de M$ : la mise à jour KB4088875 cause un souci avec la carte réseau virtuelle, plus d'infos ici. Je suis tranquille du coup, j'active tjrs cette option. Par contre mon W7 délire complet: après le deep clean il m'a proposé des màj de 2016... Quote
rhahgleuhargh Posted March 16, 2018 Author Posted March 16, 2018 @mooms Encore une brillante mise à jour ! Quote
mooms Posted March 16, 2018 Posted March 16, 2018 Du coup je n'ose plus faire un nouveau deepclean, à tous les coups ils ont encore merdé et ça va les nettoyer/réinstaller en boucle Quote
rhahgleuhargh Posted March 16, 2018 Author Posted March 16, 2018 6 minutes ago, mooms said: Du coup je n'ose plus faire un nouveau deepclean, à tous les coups ils ont encore merdé et ça va les nettoyer/réinstaller en boucle En général, ça se calme au bout de quelques jours ! Quote
mooms Posted March 16, 2018 Posted March 16, 2018 Bon à savoir. J'en ferais un le mois prochain ! Quote
Thiersee Posted March 16, 2018 Posted March 16, 2018 (edited) 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! Edited March 16, 2018 by Thiersee Quote
rhahgleuhargh Posted March 16, 2018 Author Posted March 16, 2018 (edited) @Thiersee Since a few monthes, at each cumulative update some old updates are requested, but if you ignore them and redo a search some days later, all is OK. Maybe it's due to the time needed to fix WU queries ? All my machines are updated with KB4088875, so I can't test, I don't have any info if this update was deleted (it doesn't at this time). At my work all computers have been updated with it yesterday (Windows 7 enterprise). Updated ULs uploaded. I left previous february ULs in case of ! Edited March 16, 2018 by rhahgleuhargh Quote
Thiersee Posted March 16, 2018 Posted March 16, 2018 @rhahgleuhargh My Work PC (from the beginning installed with ConvP-method) is updated with KB4088875 without issues, on my wife's laptop (HP factory installation, from the beginning updated with WU), WU requested KB4075211 and I updated it today in that way I describe in my previous post (KB4075211, KB4091290, KB4088875), I was forced to do so. Anyway I can't remember, if it was so since the patch-day or if it has changed. I didn't reach my brothers in Italy yet to update their PCs, so I can't say, how is the situation there. All my new installed VMs or real HW have the "strange" behavior. Because of my wife I do not have at the moment the possibility to test 4-5 hours undisturbed, so it will take a couple of days until I can do intensive test again. Thanks for the new ULs and have a nice weekend. Quote
rhahgleuhargh Posted March 17, 2018 Author Posted March 17, 2018 (edited) 1 hour ago, Thiersee said: I'm not alone.... MDL, post #10220 Yes, that's why I left previous UL in first post. Once again, a wonderfull update ! Edited March 17, 2018 by rhahgleuhargh Quote
pussyfooter Posted March 17, 2018 Posted March 17, 2018 Same situation here win7 x64. Update KB4088875 was proposed earlier this week. I didn't install it yet. Now I recheck WU and get the KB4074598 (2018-02 Security Monthly Quality Rollup) presented. Quote
Thiersee Posted March 25, 2018 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
rhahgleuhargh Posted March 26, 2018 Author 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
Thiersee Posted March 30, 2018 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
mooms Posted March 30, 2018 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
Thiersee Posted March 30, 2018 Posted March 30, 2018 The problem will be in WinToolkit: it integrates this patch first and then the monthly rollup... Quote
rhahgleuhargh Posted March 30, 2018 Author 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
Thiersee Posted March 30, 2018 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
rhahgleuhargh Posted March 30, 2018 Author 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
abbodi1406 Posted March 31, 2018 Posted March 31, 2018 Integration order has no affect for 4100480 the new 4099950 is not integratable rhahgleuhargh 1 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.