Last week, I started seeing complaints pop up about a Windows update. People were saying their games kept crashing. Others said Windows Hello stopped working. I thought maybe it was a few unlucky folks with weird setups. Then I looked into it. Turns out, this one is a bit of a mess.
I think the update rolled out on August 11? Let me check. That sounds right. Anyway, Microsoft pushed KB5121003 as a security patch. They fixed over 420 vulnerabilities with it. That’s a huge number. One of them was a zero-day exploit called LegacyHive that attackers were already using. So the update matters. You don’t want that hole sitting open on your machine.
But here’s the thing. The patch broke stuff. Not just small stuff either. I’m talking game crashes, PIN resets, and weird display glitches. Embark Studios, the team behind Arc Raiders and The Finals, confirmed both games were crashing constantly after the update. Players were getting error messages like thread hangs and EXCEPTION_ACCESS_VIOLATION. You don’t need to know what those mean. Just know they’re bad. Your game quits. Sometimes your whole PC restarts.
So what went wrong? Microsoft didn’t actually break their own code. They changed something that messed with a third-party driver called inpoutx64.sys. It’s a kernel-level port access driver. That sounds technical, but think of it like this. Some games and anti-cheat systems rely on this driver to talk to your hardware. The update touched that conversation. And now the conversation doesn’t work anymore.
Embark’s temporary fix? Open Command Prompt as admin. Run a few lines to stop and delete the inpoutx64 service. Then remove the driver file from system32/drivers. I’ve seen similar advice for anti-cheat software too. Or you could just uninstall the update altogether. That works as well. But I’d be careful about that.
Here’s why. The update patches that zero-day exploit I mentioned. If you uninstall it, you’re opening that door again. I’m not saying you’ll get hacked tomorrow. But it’s a risk. A real one. Microsoft issued this patch specifically because attackers were already using LegacyHive. So maybe don’t rush to remove it if your PC is still functional.
Then there’s Windows Hello. That’s been a headache too. Some users report having to reset their PIN every single time they restart their computer. The credential key regenerates each time and gets corrupted. Others say the Hello container just won’t load at all. That means your face or fingerprint login stops working. It’s annoying. It’s more than annoying. It slows you down every time you boot up.
Display issues popped up as well. Refresh rate drops. Black screens. HDR acting weird. Windows Latest thinks these are tied to display changes bundled with the patch. I haven’t seen this one myself, but enough people are mentioning it that I believe it’s real.
So what should you do if you’re stuck in this mess?
For game crashes, try removing that inpoutx64 driver first. It’s the easiest fix and doesn’t require uninstalling the entire update. If that doesn’t work, you can remove KB5121003 from your system. But again, only do that if you really need to. If your computer still runs and you’re not playing those specific games, waiting might be smarter.
Microsoft hasn’t listed any known issues in their official release notes yet. That’s frustrating. They’re probably working on a fix behind the scenes. The next scheduled update is in September. I’d bet money they roll out a fix then. Or maybe they’ll push an emergency patch sooner if enough people complain. We’ll see.
I’m not running this update myself yet. I saw the reports and decided to hold off. That’s not always possible though. Windows forces updates eventually. And you shouldn’t skip them forever because security matters. But if I were already on it and my games were crashing, I’d try the driver removal first. It’s low risk and reversible.
Here’s what I keep coming back to though. Microsoft fixes 420 vulnerabilities in one go. That’s genuinely impressive. It’s also necessary. But breaking drivers and messing with PINs and displays? That’s not a good look. I get that third-party drivers are hard to test for. There are thousands of them out there. But inpoutx64.sys is not obscure. It’s used by a lot of software. They should have caught this.
To be fair, we don’t know the full story yet. Maybe it was a last-minute change. Maybe the driver vendor didn’t communicate properly. Software is complicated. I’ve broken things myself while trying to fix other things. It happens. But Microsoft is a massive company. Their QA process should be better than this.
I think the smart move here is to wait. If you’re already affected, try the workarounds. If you’re not, hold off on installing KB5121003 for now. Watch for updates. Watch Microsoft’s release notes. They’ll probably issue a fix before September if the backlash gets loud enough. Or they won’t, and we all have to wait a month. That’s how these things go sometimes.
I’ll keep an eye on this one. If they push a fix, I’ll test it and report back. Until then, I’m staying on the older build. My games run fine. Hello works. I don’t need the headache.
My neighbor’s kid had this happen to his gaming PC. He spent two hours trying to figure out why The Finals kept crashing. He almost reinstalled Windows. Then he found that thread about inpoutx64 and fixed it in five minutes. His words: “I was about to lose my mind.” That’s the thing. These updates are supposed to make things better. They usually do. But when they don’t, it’s a massive time sink.
Honestly, I’m not sure why Microsoft hasn’t pulled the patch yet. They’ve done it before when updates caused serious issues. Maybe they don’t think this is widespread enough. Or maybe they’re confident they can fix it with another patch quickly. Either way, the lack of communication is the worst part. A simple “hey, we’re aware of the issues and working on it” would go a long way. Instead, we get silence.
Alright, let’s wrap this up. If you’re on Windows 11 and you’re not having problems, skip this update. Wait for September. If you already installed it and your games are crashing or Hello is broken, remove that driver first. If that doesn’t fix it, uninstall the patch. But only if the issues are really bothering you.
I’ll update this post when Microsoft releases a fix. Or I’ll write something new. But either way, I’ll keep using it and see how it goes. Might change my mind next week. We’ll see.
