Microsoft has graced us with yet another delightful batch of Patch Tuesday updates for Windows 11, and as usual, they’ve introduced some improvements—you know, the kind that can make your PowerShell scripts throw tantrums.
So, What’s the Drama?
Enter KB5132061, the latest update that aims to enhance security. However, in a classic Microsoft move, this security tweak may actually disable your PowerShell scripts instead. If you've got scripts relying on older coding that barely squeaked by in the past, you might want to hold your breath.
What Changed?
Microsoft decided that PowerShell script signing and signature verification needed a makeover. They’ve clamped down on text-encoding validation, which means if your script has any funky, invalid characters, Windows will reject it faster than you can say “PowerShell is awesome.”
Before this update, Windows played nice and replaced invalid characters for you. But now? It’s all about that strict life, rejecting anything that doesn't pass the UTF-8 smell test. Running a perfectly good script might now leave you staring at a NotSigned status instead of the warm, fuzzy feeling of tech victory.
What Are the Fixes?
Fear not, dear user! Microsoft has graced us with a support document to help you navigate this mess. They recommend saving your scripts with valid UTF-8 encoding, throwing in a byte order mark (because why not add more acronyms to the mix?), and signing them anew. Easy peasy, right?
If you’ve got a bunch of scripts to fix, Microsoft has also rolled out a shiny PowerShell repair tool. This little helper can scan your files for encoding mishaps and try to patch things up—without deleting your originals, of course. Just keep in mind: not every script is a fixer-upper. Some might be beyond help, much like that old car in your driveway.
And It’s Not Just Windows 11!
Oh, and by the way, this lovely feature isn’t just a Windows 11 exclusive. The guidance also applies to Windows 10 Enterprise LTSC 2021 and some Windows Server versions, because if we’re going to break things, let’s make it a group effort!
Final Thoughts
If you find that some of your beloved PowerShell scripts are sulking in the corner, this update might be the reason. Just remember, with enough patience and Microsoft’s helpful documents, you might get everything back on track—at least until the next update rolls around. Cheers!
