Windows 11 24H2 Update Causing Black Screen for several seconds when using alt-enter

GrahamNZ

New member
I recently updated Windows 11 with the 24H2 update and subsequently rolled it back. The reason being that when using alt-enter to switch to/from full screen, there is now a delay of some 5-10 seconds when the screen is black. I waited for a 24H2 update that came yesterday but this made no difference. I therefore rolled Windows 11 back and all is well again.

Also I have the perception that TRS22 is running slightly slower. On some changes of camera, the train takes several seconds to appear and then it is running on a route with no track which may not appear for a further interval.

I do use the highest ultra definition but the system has always handled this up to now. Has anybody else seen this problem? There is little in the update of interest anyway.
 
This more proof there is problems with 24H2. Ubisoft titles have issues with it too, not all but at least five or more. Also, Black Ops 6 (Call of Duty) has issues with 24H2. DirectX errors causing crashes and freezes is the symptom for those. Same solution is rolling back to previous version, 23H2. Too bad nobody can figure out what is really causing the problems in 24H2, what has changed or what is so different.
 
Yes, I've noticed this - there is a black screen when switching views (though in my case it's only 1-2 seconds, so not something I was too worried about. But if it's actually slowing TRS22 down that's a different matter.....)
 
I've decided to stick with 23H2 for the time being and give 24H2 a whirl every now and then to see if there is any progress. There is nothing in the update that is of any particular interest.
 
The simple fix is to run full-screen but windowed. You can still see everything and you can switch to other applications without using Alt-Enter.
Thank you John for your suggestion. I thought I had been using full-screen, however the lower part of the window was being hidden thus I could not see the stops and waits properly. So I swapped between the real full screen and the one with the task bar as needed. I have now discovered that I had been using a minimised screen that had been sized to a full screen. I have now switched to the correct full screen window and the stops and waits are showing in full now, Yes, it is helpful to have the task bar showing. I still think that there should not be a black screen when using alt-enter. I'll reinstall 24H2 and see if the new patch has made any difference. I just hope that 24H2 has not slowed the computer as some people have suggested.
 
Thank you John for your suggestion. I thought I had been using full-screen, however the lower part of the window was being hidden thus I could not see the stops and waits properly. So I swapped between the real full screen and the one with the task bar as needed. I have now discovered that I had been using a minimised screen that had been sized to a full screen. I have now switched to the correct full screen window and the stops and waits are showing in full now, Yes, it is helpful to have the task bar showing. I still think that there should not be a black screen when using alt-enter. I'll reinstall 24H2 and see if the new patch has made any difference. I just hope that 24H2 has not slowed the computer as some people have suggested.
My experience was 24H2 didn't slow it down the computer, it just created DirectX errors.
 
My experience was 24H2 didn't slow it down the computer, it just created DirectX errors.
Thank you. I know nothing about DirectX apart from that it is needed. Would such errors be to do with Windows or with the application program? Does anybody monitor this sort of thing?
 
What video card do you have? This may have something to do with that because I am able to switch fine using Alt-Enter.

Trainz is a very GPU intensive program and if your card and drivers aren't capable of handling the swapping that can cause this kind of problem. It could also be that the computer is busy switching screens and that process is taking a "long" time, or much longer than expected.
 
Hello
Thanks for contacting me again. My apologies for the delay, I have been away on holiday.

To your question: the video card is NVIDIA GeForce GTX 1070.

I reinstalled 24H2 to see if the black screen is still there after the recent TRS22 upate and it is. I have since uninstalled 24H2 because a setting has been changed such that part of my home network drives are disconnected. It doesn't affect TRS22. I spent some time looking at resolving the disconnect with no luck so have reverted. I just wish Microsoft would leave things alone. I continue to use the full screen as you suggested, thanks again for that.
 
Last edited:
Hello
Thanks for contacting me again. My apologies for the delay, I have been away on holiday.

To your question: the video card is NVIDIA GeForce GTX 1070.

I reinstalled 24H2 to see if the black screen is still there after the recent TRS22 upate and it is. I have since uninstalled 24H2 because a setting has been changed such that part of my home network drives are disconnected. It doesn't affect TRS22. I spent some time looking at resolving the disconnect with no luck so have reverted. I just wish Microsoft would leave things alone. I continue to use the full screen as you suggested, thanks again for that.
This is such a lovely update from Microsoft! I just read about the black screen the other day while researching an audio issue where sound just fades away.
 
This is such a lovely update from Microsoft! I just read about the black screen the other day while researching an audio issue where sound just fades away.
Here's a novel idea. Why not keep Windows 10 free for those who want some stability in life and have Windows 11 for those who would like more adventure? For some of us, there is life outside trying to work around Microsoft's continual changes.
 
Here's a novel idea. Why not keep Windows 10 free for those who want some stability in life and have Windows 11 for those who would like more adventure? For some of us, there is life outside trying to work around Microsoft's continual changes.
They won't because they can't make any money doing that. I had other issues with Windows 11 on a PC I setup strictly to run a Roland LX17 digital grand piano. The PC I had with Windows 11 had so many constant interruptions that it caused latency between the sound drivers and instrument. This caused major hiccups and stalling and kept killing the ASIO4ALL interface, making playing impossible due to major pauses and stutters.

I now have the instrument connected to a PC running Windows 10. Overall, this works better but I have to disconnect it from the network while I use it and disable the antivirus (Defender) because the PC is constantly interrupting Pianoteq I use for recording and playback.

The Windows 10 issue came about after Microsoft announced that Windows 10 is now in EOL after they made it run like crap by putting in Windows 11-like features that aren't necessary. I disabled or removed a lot of them but it's still an issue.
 
Well, I just hope that Microsoft doesn't put in updates that rely on 24H2. It would be nice to think that they will take note of the issues.
 
Back
Top