Windows 10: GRB for Second Monitor is not detecting After 7/7/20 Security Intelligence update microsoft...

When I attempted to start my morning remote office work day I got a prompt that a security update had been performed. then I noticed my Second monitor was not working. I checked the cables for power and it had power. I checked the GRB cable and no issues when connecting to another system. even tried multiple monitors. tried to see if my driver was out of date its up to date with no roll back option. checked troubleshoot option on Microsoft and no resolution.

My wifi dual monitor will still work but again I need help getting my grb to detect my second monitor. thanks for any help.

:)

 

Second monitor not detected after update

Hi Tom,

There are several reasons that could have caused the issue you are experiencing. One of these is the update you previously performed in Windows, either it was not configured properly by the system or the update components were corrupted. Kindly answer the
following questions for clarification:

• Have you tried updating the monitor and display drivers?
• Have you tried to use another user profile to check if the issue re-occurs?

Furthermore, we suggest that you add the other monitor manually. This is to ensure that the second monitor is still connected after the update. Here are the steps:

• Type connected devices and open Connected Devices on the
  Windows Search bar.
• Click Add devices.
• Select the Second screen.
• Pick one of the 3 options: Duplicate, Extend, and the Second screen only.
• The Duplicate option will duplicate the primary display to secondary display.
• The Extend option will unite two monitors so you can use them both as one.
• The Second screen only option will, obviously, disable primary and use only the secondary monitor.
• Once you’ve chosen the preferred mode, save changes.

We're looking forward to your response.

 

Windows 7 Ultimate (64) Security updates not installing.

I have been having problems in installing the updates that I have listed below. For each update I attempted to install them individually but they would not install. I also downloaded the SURT 6.1 KB947821 v27. The problem has been going on now for about 2 months. (whenever the issue with the updates comes to mind I am never near my pc). Thank you in advance.


Cumulative Security Update for Internet Explorer 9 for Windows 7 for x64-based Systems (KB2838727)
Security Update for Windows 7 for x64-based Systems (KB2757638)
Security Update for Windows 7 for x64-based Systems (KB2785220)
Security Update for Windows 7 for x64-based Systems (KB2790113)
Security Update for Windows 7 for x64-based Systems (KB2813170)
Security Update for Windows 7 for x64-based Systems (KB2813430)
Security Update for Windows 7 for x64-based Systems (KB2839894)
Update for Windows 7 for x64-based Systems (KB2726535)
Update for Windows 7 for x64-based Systems (KB2773072)
Update for Windows 7 for x64-based Systems (KB2786400)
Update for Windows 7 for x64-based Systems (KB2798162)
Update for Windows 7 for x64-based Systems (KB2808679)

 

Microsoft Botches Up UEFI Support for Windows 7 on ASUS Motherboards



Microsoft suggests updating to Windows 10 to patch Windows 7

• 
  
  
• Chris Merriman
• 
  @ChrisTheDJ
• 05 May 2016

• Tweet
• Facebook
• Google plus
• Send to

9 Comments

MICROSOFT HAS confirmed a potentially lappy-borking problem that it won't be fixing, because Windows 7.

Woody Leonhard, the respected Windows columnist, points to a problem involving Asus motherboards, which also appear rebadged in a variety of other manufacturers' machines, and the activation of UEFI Secure Boot for Windows 7 in a patch KB3133977.

Short version: install update, welcome to Borksville, population you.

Both Asus and Microsoft acknowledged the problem. Microsoft entitled the article "BitLocker can't encrypt drives because of service crashes in svchost.exe process in Windows 7 or Windows Server 2008 R2", but we prefer to just call it "Trevor for brevity."

The firm's advice was that it's an optional update, leave well alone, you'll be fine, or alternatively turn secure boot off.

Then Microsoft did a silly, silly thing.

It moved the update from 'optional' to 'recommended' and anyone who reads this site regularly will know what happens when Microsoft does this. That's right boys and girls - it makes it automatically install, unless you've specifically told your machine not to.

So now, if you have one of the affected motherboard and you keep your security updates automatic like wot Microsoft recommends, then your machine will stop working properly.

We should add it's not permanently bricked, but it will take some mucking about in the BIOS to fix and that's a pain even for an experienced computer user.

Microsoft has, by offering a workaround, suggested heavily that it won't be fixing the problem, though we have asked the question, so expect a response in about a fortnight.

But the real kicker is this piece of advice: "Note The Secure Boot feature is supported in Windows 10. To learn more about the security advantages of this feature and about the upgrade path from Windows 7 to Windows 10, go to the following Windows website"

Holy toledo, this company really knows how to rub people up the wrong way.

After all - if the advice is to manually avoid the update or move to a version of the operating system where there's virtually no control over updates, then Microsoft is dealing in massive contradictions.

A more cynical site would suggest that it's yet another example of Microsoft running Windows 7 into the ground and adding built in obsolescence to encourage quicker updates. But we're not that sort of site.

Its the patching to force secure boot that is the problem win 7 does not support secure boot
hence it borks systems and well microsofts answer is Cactus >your Asshole > insert

from the inquirer