I have the same issue. Did a clean install and didn't paid attention that they already put in 24H2 as download. And by the look of several threads it seems like Microsoft has to fix this, since updating/reinstalling Nvidia drivers doesn't help. I hope they are aware of it and it will arrive with the bug fix patch in November.
Black screen issues on Windows 11 24H2 when ALT+TABing?
So as the title suggests, when I ALT+TAB from a game both of my screens go black for about 4-5 seconds and then work normally.
Is anyone else having this issue and if so, is there a solution?
Edition Windows 11 Pro
Version 24H2
Installed on 01-Sep-24
OS build 26100.1591
Experience Windows Feature Experience Pack 1000.26100.18.0
Latest NVIDIA drivers 560.94 for MSI GeForce RTX™ 3080 SUPRIM X 10G
Latest BIOS 5404 for Asus ROG Strix B450-F Gaming II
Thank you in advance!
Windows for home | Windows 11 | Display and graphics
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
73 answers
Sort by: Newest
-
Anonymous
2024-10-23T20:22:51+00:00 -
Anonymous
2024-10-20T22:03:55+00:00 when this happens do you get any nvlddmkm errors in the event viewer?
-
Anonymous
2024-10-20T20:00:40+00:00 Yeah, I cant understand it either. I downgraded to 23h2 until they fix it, and even though it is supposed to be the opposite, it seems like my system works really better overall on 23h2 than on 24h2, but eventually, when it has ben out for a longer time, ill go back to it and see, for now, ill stick with 23h2
-
Anonymous
2024-10-20T18:35:48+00:00 I have no idea at least Microsoft has confirmed it and will fix it sometime in November 🫤
-
Anonymous
2024-10-20T18:28:10+00:00 Having the same issue on two machines (somewhat identical) with RTX 3080's with the latest GPU Drivers installed. Have tested DDU (removing the drivers) and install again.
Rolling back to the previous version of windows resolved the issue.
Updating back to the NOW RELEASED!? 24H2 has brought the issue back.
How does something like this pass and make it into the actual release?