Well, yes I suppose that would be the nuclear optionTry left shift and hit Restart computer . Look fore Remove Windows update button . This should fix it back to previous update .![]()
Are you positive it's a Windows issue and not AMD? I've seen many threads on reddit about multi monitor issues with AMD GPUs. I suppose it isn't AMD if it worked fine before 24H2.Well, yes I suppose that would be the nuclear optionBut I do have to update at some point and find an alternate solution I think.
PS. my monitor doesn't sleep now once the screen is locked. Can't say if that is coincident with this update or a previous one, but another change in behaviour. Why does Microsoft keep screwing up sleep??
Well, good point. I haven't checked if something hasn't happened with AMD drivers behind the scenes. I didn't actively change AMD drivers but @sswilson was having driver changes he didn't want to have happen that he talked about in that other thread.Are you positive it's a Windows issue and not AMD? I've seen many threads on reddit about multi monitor issues with AMD GPUs. I suppose it isn't AMD if it worked fine before 24H2.
Well, good point. I haven't checked if something hasn't happened with AMD drivers behind the scenes. I didn't actively change AMD drivers but @sswilson was having driver changes he didn't want to have happen that he talked about in that other thread.
Worth me checking for sure.
Ah very good then. Perhaps I can go back to finger pointing at MS then24H2 has been such a major buggy mess from day one.
Heh..... I think I finally tracked that down to being my fault. Looks like the card's memory was probably not getting enough airflow and causing the driver to fail.... after a week or so of trying different things (including blocking drivers and setting high case fan profiles tied to GPU temps) "somebody"had a eureka moment and remembered that my vid card has a bios switch, and wouldn't you know it.... it was of course set to "quiet" as opposed to "performance".
Haven't had any issues since.![]()
Aside from the drivers it blocked, only the one ASUS one reported, and this oddity when running through the KVM I don't have other issues that I've noticed yet anyway.I have no issues with 24H2 but then again I use a single monitor and block optional updates in group policy.