Windows 11: Errors and Failures After Patch KB5070311

The latest optional November Update is causing errors for many users.

The latest Windows 11 update, KB5070311, is supposed to bring several improvements, but is causing errors for many users. Affected features include Dark Mode, login issues, and Intel graphics drivers.

Microsoft says the new KB5070311 update (Build 26200.7309) is here to deliver minor improvements to file operations and system stability. Sounds harmless enough, right? Well, some users can't even install the thing. Instead, they are greeted with the ever-mysterious error code 0x80070306, which tells you absolutely nothing except that something went wrong.

No one seems to know why it is happening, but the usual tech-support rituals apply: check your system files, sacrifice some time to manual installation, and hope for the best.

Dark Mode Users Get a Free Flashbang

If the update does install, congratulations - now File Explorer might try to blind you. With Dark Mode enabled, switching folders or tabs may trigger a sudden white flash, like Windows briefly forgetting it's supposed to be edgy and moody.

Even dialog boxes like Copy or Move can flare up, which is… fantastic… if you enjoy unexpected strobe effects in a pitch-black room.

Password Login: Now You See It, Now You Don't

Another charming quirk: on the login screen, the password option might simply vanish. Users who rely on PINs and need to switch methods are discovering that the password icon is still there - it is just invisible.

Yes, you read that right. Microsoft assures everyone that nothing is missing; you just have to click the invisible button. Because guessing where your password field is totally enhances the Windows experience.

Intel Arc Owners, Brace Yourselves

If you are using an Intel Arc GPU, things get even spicier. Reports after installing the update include crashes, black screens, angry warnings in Device Manager, and games refusing to launch. Some systems are turning into beautifully lit paperweights upon boot.

For many, the only fix is rolling back to an older driver - or pretending this update never happened.

about author