Thiersee

I think so too: I just installed the same VM with the last month ISO and they are requested too (not last month....).

Hi, tested on VM x86: the same old updates are requested by WU ! Have a nice (long) week end!

Hi Nemo_G, 1.6.0.9 is a test-build ! Thiersee

1.6.0.7 does not have the issue.

Hi Liam, both versions shows this warning on loading preset and the number of selected tweaks is wrong. In 1.6.0.7 and before is OK Same preset in both cases. Regards

This bug exists already since a looooong time!

NO!

Please, post your preset.ini. I get exactly those requests, if I don't integrate the AV.reg too 2534111 is normal; the other two will be not deepcleaned, if you integrate them as RunOnce; this is anyway a very old matter. Sometimes needs WU 1 or two restart and a bit time to realize they are not necessary....

Yes, it is! Have a look to my last post .

I don't think so: earlier versions were high-compressed in the same way, but they were working. And this is not the first time, WTK has this kind of crash... Be patient and wait that Lego has a look at this thread.

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.

From the MS-article KB4088875: 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.

To integrate the NVMe-driver in the installation-media is not enough! If your BIOS does not support to boot from a PCIe-drive, you have only two possibility: 1) modding the BIOS to insert a NVMe-module 2) to use the clover-system to boot. Both methods can you find on win-raid.com. Direkt link for point 2): https://www.win-raid.com/t2375f50-Guide-NVMe-boot-without-modding-your-UEFI-BIOS-Clover-EFI-bootloader-method.html I'm using this way on an ASUS MB A88X-Pro without any issues.

It means the patch is not necessary? Anyway, it would be interesting what MS means with this Info on KB4099950 The most people have set Windows to update automatically.

Or, if you install with an USB pendrive, you can simply delete the file ei.cfg within the folder "sources" on the pendrive. If you use WinToolkit there is a possibility too to delete the ei.cfg.

And again a patch for a patch for a patch.... KB4099467

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 .......

The problem will be in WinToolkit: it integrates this patch first and then the monthly rollup...

Again a patch for a patch for a patch...... KB4100480, released 29.03.2018, only x64! Happy Easter & Joyeuses Pâques!

@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 !

And you will not find it! There is no x86.

I'm not alone.... MDL, post #10220

@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.

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!

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.