Word to the wise, it's popping up rather commonly in small groups but doesn't appear to be acknowledged was widespread yet (has been updated to mention in the release info https://support.microsoft.com/en-us/help/4512506/windows-7-update-kb4512506)

 

(yes, W7 is the devil and so on.. reality is some companies are still migrating out)

 

Seems 2 patches released on patch tuesday (aug 13?) and WSUS delayed release can have detrimental effects on what appears to be winload.efi and .exe if run in the wrong order
Or related to the SHA2 changes enforced this month on (https://support.microsoft.com/en-us/help/4472027/2019-sha-2-code-signing-support-requirement-for-windows-and-wsus)

 

Causing them to not verify or boot so goes into repair loop you can't get out of

 

I raised an eyebrow at 1 after user said they rebooted and struck it after update requirements. 2 days later that number increased

 

I'm yet to throw one of the effected on the bench and see if the DISM rollback works from WinPE

 

And not alone it seems

 

https://community.spiceworks.com/topic/2226822-patch-tuesday-august-2019-breaking-computers-auto-repair-loop