KB4512486 Security Only Quality Update for Windows 7 - Aug. 13

Brds7t7 said:

Was yours in the optional section or important section?.

It was in the important section, but unchecked. Does that make a difference?

Strange, I don't think I've ever had a .NET Framework version update (except for the .NET Security rollups/updates) appear in the Important section.

Is your Windows update set to "Give me recommended updates the same way I receive important"? If so, that might explain why it appeared in the important section. It would still come unchecked though.

Brds7t7 said:

Is your Windows update set to "Give me recommended updates the same way I receive important"? If so, that might explain why it appeared in the important section. It would still come unchecked though.

Yes, that is checked.

LevelBest said:

Yes, that is checked.

That's the reason then. The .NET version updates are actually classed as recommended and not important. If you uncheck that option it will move to the optional section. I always have that unchecked to keep a lot of unnecessary updates out of the important section.

The .NET Framework version updates will never come checked, unless it's flagged as an important update.

daliokas said:

looks like updates KB4512486 AND KB4512506 kills Windows 7 with nvme SSD drives. two out of ~100 pc's won't boot with these updates installed, and only these two has nvme SSD as boot drives.
tried to remove both and install separately - it's enough one of these patches to kill Windows 7 machine.

I have one machine too that got BSOD 0x0000007B INACCESSIBLE_BOOT_DEVICE after installing KB4512506, it uses a Samsung 960 EVO NVMe SSD.

I tried to use the latest Samsung NVMe driver instead of the Microsoft one bundled in KB2990941 but it did not help.

The fix described in KB2839011 for uninstalling a patch from the WinPE environment did work fine, as did restoring a previous recovery point.

What is strange is I have another workstation with a Samsung SM961 NVMe SSD that I held off to update until today when I could do a full backup but it went through without any issues!

Surprised that hasn't been mentioned in the known issues? Although, killing someone's ability to actually boot into their PC probably isn't on MS list of priorities!
I haven't installed the last 2 Security updates (except for the SHA-2 update). I decided to cut off the security updates 6 months early and save myself further hassle. Haven't got the patience anymore to be fixing MS shi* updates.

MS bork-ups know no bounds these days! And they want everyone to upgrade to Windows 10?? I'd rather tbh!

Per Hansson said:

daliokas said:

looks like updates KB4512486 AND KB4512506 kills Windows 7 with nvme SSD drives. two out of ~100 pc's won't boot with these updates installed, and only these two has nvme SSD as boot drives.
tried to remove both and install separately - it's enough one of these patches to kill Windows 7 machine.

I have one machine too that got BSOD 0x0000007B INACCESSIBLE_BOOT_DEVICE after installing KB4512506, it uses a Samsung 960 EVO NVMe SSD.

I tried to use the latest Samsung NVMe driver instead of the Microsoft one bundled in KB2990941 but it did not help.

The fix described in KB2839011 for uninstalling a patch from the WinPE environment did work fine, as did restoring a previous recovery point.

What is strange is I have another workstation with a Samsung SM961 NVMe SSD that I held off to update until today when I could do a full backup but it went through without any issues!

I have realized the problem is not with NVMe SSD drives, it is with UEFI boot mode, which is a requirement for NVMe but can be used with any other drive as well.
Now I know why the second machine accepted the patch without issues: it had the "Win7 post SP1 rollup" patch KB3125574 applied.
Contained in this rollup is the recommended update KB3133977 for Bitlocker.
That patch is what works as a workaround for the problem: if you have it installed the system can then accept this months patch Tuesday patches: KB4512486 or KB4512506.
Microsoft has updated the patch notes for the latter with that info too, however they have done nothing to stop PC's being bricked by the update still: as KB3133977 is still only listed as a recommended update!