Done and dusted - took a while to get it installed (~15 minutes?)
Wary of my previous encounter (here) I did double check C:\WINDOWS\System32\DriverStore\FileRepository folder:
I did check carefully that all files impacted by this CU in there - especially INF files - are not empty, and they're not, so need to assume that all is well.
Updated today! Took a while on my pre-Vista laptop, which is normal. Ran SF and DISM no errors. So far, all is good.
So here's my experience with the last 21H2 update, incl the preview which I started with.
After updating with the preview, which I assume was this regular update yesterday, I had no video, in fact my laptop an older HP would just shut down when it was doing the usual "getting your system ready, don't turn off " what I found after messing around is this "preview" update just removed my AMD driver altogether, even the intel 3000 graphics driver and when it got to a certain point with the restart updating, the laptop would just shut down altogether, I restarted it several times but it kept doing the same thing. So ok, I figured maybe its the "preview" issue, and I'll hold up until the actual WU shows it as a normal update. Which I did yesterday, well it did the exact same thing, I ended up having to recover the system with a full system backup which I did a couple days ago anticipating this.
So now I guess I won't be able to go past build 1348 on this HP laptop with this AMD/intel 3000 graphics system.
Its just crazy that MS comes out with updates like this, I'm sure there are many people that are still on old machines using W10 that have no idea what wrong with their machines now and unable to figure out what happened, why in the world would they code an update to remove a driver instead of just ignoring it if it was different??? This is insane to disable someone's machine like this.
I think I read someone' else had this sort of issue a week or so ago, but at the time I was waiting for the final WU to arrive before I added my issue. Not sure if there's any way other than just not updating that would fix this. Maybe MS will see this, but who knows.
Thanks for reading
Updating M$ remains being a big risk for everone , only working medicin is ; backup first, backup, backup , etc. before updating !
This way you avoid severe damage and you will keep your Windows for a very long time ( mine is about 5 years old ,without formatting , still a very fine machine )
See option 2: Enable or Disable Driver Updates in Windows Update in Windows 10
Yours is an example of why I don't want M$ messing with my drivers.
its not a driver that's being updated, its the regular cumulative WU for the system. if it was just a AMD driver showing up I'd know to not install it because only the old w8 AMD Driver works with this old card, 2670 XT.
note looked at that enable/disable driver updates, will try the disable one and see what it does.
I added this to reg file:
Code:Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Device Metadata] "PreventDeviceMetadataFromNetwork"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DriverSearching] "SearchOrderConfig"=dword:00000000
Well the Edge zealots at M$$ have done it again: Yesterday’s Patch Tuesday quietly rolled out EdgeDeflector block to all Windows 10 and Windows 11 users
My system auto updated this CU this morning. I forgot to pause updates after the last CU like I usually do. I wasn't aware of the update until the message popped up stating the restart was waiting. I can always remove it or restore the system image from after the last CU.
Quote
