Windows 10: Every single Windows 10 update causes my monitor to be undetected.

Every single Window 10 update that happened for the past 2 years or causes my external monitor not to be recognized. This has been happening since about autumn 2016.



The resolution takes several hours each time. I suspect that Windows 10 update corrupts my Nvidia Geforce driver. However, uninstalling the driver doesn't work, since Windows then installs another copy of a non-working driver. Altogether this is many many hours of productivity lost each year.


Since I have lost any hope that Microsoft will get its s--t together with Windows updates, I am considering another solution: disable Windows updates altogether. This should help me get by until I get myself a Mac. To be clear, my current Alienware Laptop is top of the line, it is the Operating System that is a piece of crap. I will not make the same mistake next time I buy a computer. Does anyone knows how to disable Windows updates? Thank you very much!

:)

 

Windows 10 KB3213986 Update Cripples Multi-monitor Gaming

The recent Cumulative Update for Windows 10 (KB3213986) cripples multi-monitor gaming, looking at the way Microsoft worded its "known issues" text. After the update is applied, users with multi-monitor setups could experience screen stuttering or clipped screens when running 3D apps on machines with more than one monitor. The only workaround Microsoft suggests for now entails running your 3D apps in non-fullscreen modes, such as windowed-maximized (pseudo-fullscreen) or windowed modes. Microsoft also goes as far as to suggest that people with multi-monitors could try starting their 3D apps with just one monitor connected.

"Users may experience delayed or clipped screens while running 3D rendering apps (such as games) on systems with more than one monitor," the change-log for the KB3213986 update reads. "To work around this issue please consider the following options: 1. Running the application in Windows mode (not full screen), or 2. Starting the application with only one monitor connected," it adds. The update effectively cripples multi-monitor gaming, using technologies such as AMD Eyefinity or NVIDIA 3D Vision Surround.





Source: Microsoft

 

Windows 10 dual monitor going back to single monitor display

HI,





To isolate the issue, we have some questions for you:

• 
  When you tried to turn it back to single monitor, were there any changes made before?
  
• 
  Have you checked if the drivers are up-to-date?
  
• 
  What changes did you make in the Display Settings?
  
• 
  Aside from what you have mentioned, what other troubleshooting steps have you done so far?
  

We'll be waiting for your response.



Regards.

 

[Windows 10] HDMI monitor becomes undetected and detected repeatedly if it's switched to other devices.

Everything works fine with Windows 7.

I have 3 monitors, 2 DVI and 1 HDMI and I use the HDMI one as my main monitor.

I also have a headphone "MDR-HW700DS" and it has a HDMI switcher(3-in/1-out).

My PC and my Xbox1 are connected to the HDMI input1 and input2 of the switcher.

After upgrading to Windows 10, My main monitor(HDMI) will goes off and on in 1 second but repeatedly about every 5 seconds when I switch to display the Xbox1.

Which means, my main monitor(HDMI) will be disappeared(undetected) from the display settings for 1 second and suddenly be detected and remains only about 5 seconds, then loop.

It's really annoying and I can't do any multi-task in this situation, because one of my secondary(DVI) monitors will blink every 5 seconds.

When the main monitor is undetected, all the desktop icons and active-windows on it will be pushed to my secondary monitor(it will become the main monitor automatically) and also causes it to blink(like the blink after you adjust your display settings).
And my main(HDMI) monitor will be detected in 1 second(all the desktop icons and active-windows will go back to main monitor), so the secondary monitor will blink again and remain steady for only 5 seconds, then the main(HDMI) monitor will be undetected again
and looping.

This never happened when I was using Windows 7.