https://www.displayfusion.com/Discussions/RSS/?TopicID=639e89f7-5f8d-47c9-be3c-ce2c36689431 DisplayFusion RSS: Bug with Windows Pro version 2004 - Show only monitor 1 Sat, 20 Jun 2026 06:03:26 GMT en hourly 1 https://www.displayfusion.com/Discussions/RSS/?TopicID=639e89f7-5f8d-47c9-be3c-ce2c36689431 https://www.displayfusion.com/Discussions/View/bug-with-windows-pro-version-2004-show-only-monitor-1/?ID=639e89f7-5f8d-47c9-be3c-ce2c36689431#2 Tue, 28 Jul 2020 20:35:42 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/bug-with-windows-pro-version-2004-show-only-monitor-1/?ID=639e89f7-5f8d-47c9-be3c-ce2c36689431#2 DisplayFusion We haven't run into anything like that before. If you can get it to happen again, does simply exiting DisplayFusion make it stop happening? ]]> https://www.displayfusion.com/Discussions/View/bug-with-windows-pro-version-2004-show-only-monitor-1/?ID=639e89f7-5f8d-47c9-be3c-ce2c36689431 Sun, 26 Jul 2020 19:14:18 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/bug-with-windows-pro-version-2004-show-only-monitor-1/?ID=639e89f7-5f8d-47c9-be3c-ce2c36689431 DisplayFusion I've found a bug that I think has to do with DisplayFusion. I have an iGPU and dGPU running into the same monitor for a dual boot (windows/mac) computer. When on Windows, I've previously used DisplayFusion to disable the iGPU monitor on boot. I just updated my computer set-up and installed Windows Pro version 2004, and there's a new option in Window's display settings to "show only on 1" to disable a second monitor.

This setting seems to seriously conflict with something in DisplayFusion, causing the iGPU to go in and out non-stop. I initially found this by trying to disable my iGPU through DisplayFusion. When I noticed the issue, I tried to enable it again and got the HR:31 error that is going around. The only thing that fixed the issue was to either enable both "monitors" (gpus) in Windows settings or to do a complete uninstall of DisplayFusion.

Just wanted to report this since it seems like the team has been running into this error. Might have to do with this new feature in Windows Pro 2004? ]]>