If #Microsoft vibe coding means spending six hours of diagnosing a system that will not boot after Tuesday’s software update,
HARD NO.
Discussion
Loading...
@dexter
But Michael, it does boot. You just need to go into the BIOS and tell it to boot from the USB stick on which you've put an image of FreeBSD 14.3! It works EVERY time.
The running theory is that the update pushed new firmware signing certs, which rendered Secure Boot unusable and the system unbootable.
Disabling Secure Boot makes the system bootable, but the fallout was unsustainable.
Azure accounts in Outlook would fail to authenticate, regardless of if from Outlook new, Classic, OR THE EDGE WEB BROWSER.
The sign-in PIN failed and its remnants could not be removed, despite three or so approaches using regedit or the group policy manager.
The machine shipped with no option to create a local user, unless the user missed that step.
This is bullsh*t and I really, really do not want to grow the skills to mitigate this, minus the whole virtualize it with GPU pass-through with VDI fallback…
Bah. Is that what vibe coding in action looks like?
Oh look!
[Secure Boot] Starting with this update, Windows quality updates include a subset of high confidence device targeting data that identifies devices eligible to automatically receive new Secure Boot certificates. Devices will receive the new certificates only after demonstrating sufficient successful update signals, ensuring a safe and phased deployment.
WAS THIS VIBE CODED?