[N150RF] External monitor not detected after Windows update

As per title, after a Windows update yesterday, my HDMI monitor is no longer being seen.

System: Metabox N150RF, i7-6700HQ, GTX965M, Win10

I have tried:

• Display switching with Win-P
• Display detection in settings
• Uninstalling the updates
• Removing and reinstalling Intel drivers
• Removing and reinstalling Nvidia drivers
• Disabling/Enabling GPU switching in BIOS

Windows does play the notification sound when I plug/unplug the HDMI cable. But no display is detected.

What I will try after work:

• Another HDMI cable
• Installing older video drivers from the OEM disc

Has anyone else had issues after the Windows update this week?

(Apologies if there is a thread I should be posting in. Couldn't find an N150 owner's lounge.)

 

Is there some kind of setting on the monitor that maybe needs to be changed, like the input? Might be completely coincidental, but maybe it got switched from HDMI to another input?

Are you leaving the monitor plugged in while you have been making all those changes? It might be worth doing some of the updates or changes without it plugged in, restart and then plug it in?

 

Yep, I was doing a ballet of all plugged / not plugged options, and power cycling. Nada. Just now I got home from work, fired it all up, and it was working again.

I'm happy it's working, but I hate being in the dark about how or why!

 

Yeah, those moments are always odd. But I would keep an eye on it and try to take notice if you adjust any settings if it goes off like that.

 

Huh... Well, good!─ but like Pat said, definitely keep an eye on it. Test it a few times; reboot and try again, power down, cold boot, and try again, move the cable around a bit, etc. Make sure it's consistently working.

It could have just been a glitch in the Matrix.

 

Maybe there was some dust or something on either the connector on the monitor or laptop?

 

Microsoft released a security update a few weeks ago for Windows 10 that caused an issue with Secure Boot and it forced Windows to output display via the CPU for certain CPU/GPU configurations. I never heard if they released a patch. However from what I experienced on a few client devices, rebooting multiple times eventually solved the problem. That led me to believe the GPU was skipped over on the EFI Secure Boot Check, and after multiple reboots it finally passed and rewrote the verified signature to the OS. Again, this is all based of work related experiences and nothing confirmed from Microsoft.

 

It might not be something MS recognizes as an issue, but trial and error still is useful for finding a solution even if it isn't the official one. Hopefully that info might be useful to someone that might have the same issue though. Thanks!