rhahgleuhargh Posted February 19, 2018 Author Share Posted February 19, 2018 Ce sera Lubuntu en 2019 pour mon vieux portable, pas envie de la changer pour ce que j'en fais. Il est probable que le reste de mon équipement suive, au moins en double boot, j'hésite encore pour la distribution à choisir. Quasiment pas de virus, tout ce qu'il faut pour le Web, le multimédia, la bureautique (pas encore aussi performante qu'Office pour la gestion des macros ou PowerPoint mais je n'ai pas trop cherché à creuser), de nombreux tweaks et thèmes pour rendre l'apparence moins austère, de quoi peut-on rêver de mieux ? Quote Link to comment Share on other sites More sharing options...
mooms Posted February 19, 2018 Share Posted February 19, 2018 Et il reste toujours le dual boot, Wine, et les machines virtuelles. Quote Link to comment Share on other sites More sharing options...
mooms Posted March 4, 2018 Share Posted March 4, 2018 J'ai màj le script vbs pour masquer les KB de télémétries avec KB2952664, et j'en ai profité pour ajouter les 16(!) KB Silverlight et celle de Skype (kbkb2876229) (oui ils ont mis deux fois "kb" dans le nom). Voici ce que ça donne: ' Maxpsoft May 30, 2013, 9:34:15 PM ' Edited by Rhahgleuhargh 2015, July 7 ' ' Original Mike.Moore Dec 17, 2012 on answers.microsoft but when ran it Hide everything so no good. ' Link to script: http://www.msfn.org/board/topic/163162-hide-bing-desktop-and-other-windows-updates/ ' You may freely use this script as long as you copy it complete and it remains the same except for adjusting hideupdates. ' If I need to change something then let me know so all may benefit. Dim WSHShell, StartTime, ElapsedTime, strUpdateName, strAllHidden Dim Checkagain 'Find more keep going otherwise Quit Dim hideupdates(22) 'TO ADD 1 EDIT THE (11) AND ADD another hideupdates(#) hideupdates(0) = "KB2952664" hideupdates(1) = "KB3021917" hideupdates(2) = "KB3068708" hideupdates(3) = "KB3080149" hideupdates(4) = "KB976932" hideupdates(5) = "KB2952664" hideupdates(6) = "KB2512827" hideupdates(7) = "KB2526954" hideupdates(8) = "KB2617986" hideupdates(9) = "KB2636927" hideupdates(10) = "KB2668562" hideupdates(11) = "KB2977218" hideupdates(12) = "KB3056819" hideupdates(13) = "KB3080333" hideupdates(14) = "KB3106614" hideupdates(15) = "KB3126036" hideupdates(16) = "KB3162593" hideupdates(17) = "KB3182373" hideupdates(18) = "KB3193713" hideupdates(19) = "KB4013867" hideupdates(20) = "KB4017094" hideupdates(21) = "KB4023307" hideupdates(22) = "kbkb2876229" Set WSHShell = CreateObject("WScript.Shell") StartTime = Timer 'Start the Timer Set updateSession = CreateObject("Microsoft.Update.Session") updateSession.ClientApplicationID = "MSDN Sample Script" Set updateSearcher = updateSession.CreateUpdateSearcher() Set searchResult = updateSearcher.Search("IsInstalled=0 and Type='Software' and IsHidden=0") Checkagain = "True" For K = 0 To 22 'Bing Desktop has 4, Silverlight has 5 If Checkagain = "True" Then Checkagain = "False" CheckUpdates ParseUpdates End if Next ElapsedTime = Timer - StartTime strTitle = "Windows 10 Upgrade required Updates Hidden." strText = strAllHidden strText = strText & vbCrLf & "" strText = strText & vbCrLf & "Total Time " & ElapsedTime intType = vbOkOnly 'Silent just comment these 2 lines with a ' and it will run and quit 'Set objWshShell = WScript.CreateObject("WScript.Shell") 'intResult = objWshShell.Popup(strText, ,strTitle, intType) 'Open Windows Update after remove the comment ' 'WshShell.Run "%windir%\system32\control.exe /name Microsoft.WindowsUpdate" Set objWshShell = nothing Set WSHShell = Nothing WScript.Quit Function ParseUpdates 'cycle through updates For I = 0 To searchResult.Updates.Count-1 Set update = searchResult.Updates.Item(I) strUpdateName = update.Title 'WScript.Echo I + 1 & "> " & update.Title For j = 0 To UBound(hideupdates) if instr(1, strUpdateName, hideupdates(j), vbTextCompare) = 0 then Else strAllHidden = strAllHidden _ & vbcrlf & update.Title update.IsHidden = True' Checkagain = "True" end if Next Next End Function Function CheckUpdates 'check for new updates cause Bing Desktop has 3 Set updateSession = CreateObject("Microsoft.Update.Session") updateSession.ClientApplicationID = "MSDN Sample Script" Set updateSearcher = updateSession.CreateUpdateSearcher() Set searchResult = _ updateSearcher.Search("IsInstalled=0 and Type='Software' and IsHidden=0") End Function Testé en MV, c'est un peu long mais ça fonctionne. Le script sous forme de SFX: Telemetry.exe Quote Link to comment Share on other sites More sharing options...
rhahgleuhargh Posted March 14, 2018 Author Share Posted March 14, 2018 (edited) Hello, Changelog du mois : Security Monthly Quality Rollup : KB4088875 remplace KB4074598 (common), KB2973351 et KB300436, et KB3101722 (x86) (classic) Telemetry Updates : KB2962664 v24 mise à jour. Tests en cours. Curieusement la mise a jour cumulative fait planter ma machine virtuelle classique x86 qui est devenue irréparable. Je vais retenter une installation. Edited March 15, 2018 by rhahgleuhargh Quote Link to comment Share on other sites More sharing options...
rhahgleuhargh Posted March 15, 2018 Author Share Posted March 15, 2018 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 ? Quote Link to comment Share on other sites More sharing options...
Thiersee Posted March 15, 2018 Share Posted March 15, 2018 I'll test it today; on my work-PC no issues. Quote Link to comment Share on other sites More sharing options...
mooms Posted March 15, 2018 Share Posted March 15, 2018 2 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 ? Du coup je n'ai pas vraiment envie de tester 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. Quote Link to comment Share on other sites More sharing options...
Thiersee Posted March 15, 2018 Share Posted March 15, 2018 Just installed W7 HP x86 in VirtualBox (updated ISO with KB4088875): no installing-issues or BSOD, but WU requested 4 old patches, the same I got after installing the March-Preview. Quote Link to comment Share on other sites More sharing options...
Thiersee Posted March 15, 2018 Share 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 Link to comment Share on other sites More sharing options...
rhahgleuhargh Posted March 15, 2018 Author Share 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 Link to comment Share on other sites More sharing options...
Thiersee Posted March 15, 2018 Share 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 Link to comment Share on other sites More sharing options...
Pink_Freud Posted March 15, 2018 Share 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 Link to comment Share on other sites More sharing options...
rhahgleuhargh Posted March 15, 2018 Author Share 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 Link to comment Share on other sites More sharing options...
mooms Posted March 15, 2018 Share 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 Link to comment Share on other sites More sharing options...
rhahgleuhargh Posted March 16, 2018 Author Share Posted March 16, 2018 @mooms Encore une brillante mise à jour ! Quote Link to comment Share on other sites More sharing options...
mooms Posted March 16, 2018 Share 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 Link to comment Share on other sites More sharing options...
rhahgleuhargh Posted March 16, 2018 Author Share 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 Link to comment Share on other sites More sharing options...
mooms Posted March 16, 2018 Share Posted March 16, 2018 Bon à savoir. J'en ferais un le mois prochain ! Quote Link to comment Share on other sites More sharing options...
Thiersee Posted March 16, 2018 Share 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 Link to comment Share on other sites More sharing options...
rhahgleuhargh Posted March 16, 2018 Author Share 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 Link to comment Share on other sites More sharing options...
Thiersee Posted March 16, 2018 Share 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 Link to comment Share on other sites More sharing options...
Thiersee Posted March 17, 2018 Share Posted March 17, 2018 I'm not alone.... MDL, post #10220 Quote Link to comment Share on other sites More sharing options...
rhahgleuhargh Posted March 17, 2018 Author Share 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 Link to comment Share on other sites More sharing options...
pussyfooter Posted March 17, 2018 Share 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 Link to comment Share on other sites More sharing options...
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...
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.