No actividad detectada en el seguimiento de actualizaciones del sistema operativo.
No actividad detectada en el seguimiento de actualizaciones del sistema operativo.
The message highlights a recent update challenge where the firewall unexpectedly blocked new content it hadn’t handled before. Eventually, I decided to apply the W10 22H2 Patch Tuesday for February. After reading the notification "Windows is Preparing your PC for Updates...", the video display on the port stopped appearing. It took several days to regain any video output because I overlooked that my 1080ti monitor uses DVI, along with other cables and connections.
For context, the system setup includes an Asus X570 Prime-P with a Ryzen 3900x processor (cooled by NH-D15), an Aorus 1080ti Xtreme Edition, G.Skill Trident-Z Neo 3600-CL16, Samsung 970 EVO 1TB drive, and an Asus VG248QE monitor. I’ve kept the cable bundle intact since gaining partial DVI support.
I attempted to fix driver issues with Nvidia, but no changes worked—settings remained stuck at "Display 1 isn't active." This setting controls the DP connection for display output. My main concern is finding more troubleshooting steps. I suspect a configuration change from the Windows update might be responsible, possibly linked to the DP functionality being disabled between my card and monitor.
Additional notes: The issue isn’t limited to Windows; without DVI support, even basic startup screens or UEFI menus aren’t visible. The DP port on both my card and monitor is completely inactive. I’m looking for advice on how to isolate the problem further or identify what might have changed after the update.
It seems you're facing a complex setup with limited testing options. You might consider using another system during spring break to evaluate performance and power usage, especially since you're planning to add Windows there. Installing Windows on your custom Void Linux server could complicate things further. With only one monitor available, it's hard to verify compatibility without more tools. Tracking changes in updates is challenging without clear changelogs or commit history, which would simplify troubleshooting and understanding modifications. The secrecy around specific changes might be for security reasons, but transparency could help with maintenance and future development.
It took some time, but you can reverse the change by navigating to: Start > Settings > Windows Update > Update history > Uninstall updates; then verify the DP connection. I’d even reinstall the update to test its functionality... It really works the second time.