Windows 10 interprets me as having three displays.
Windows 10 interprets me as having three displays.
So this is a weird one that I have never seen before. After turning on my computer this morning my computer made the sound for new hardware being connected but nothing happened. I went to device manager to see if anything was there and noticed that I had a 3rd monitor showing up as generic non pnp monitor. I went to my display properties and sure enough it was showing a tiny little monitor off to the side with a low res. I have 2 other monitors hooked up but thats it. I went back to device manager and disabled it and it no longer lets me move windows to the non existent monitor but it still shows up in my display properties. I used ddu to uninstall my drivers and reinstalled with the same problem. I noticed an updated driver on AMD's site and downloaded that and did ddu again and installed those and its still there. Not sure whats going on or how to get rid of it.
Check if a reboot is needed. Open PowerShell and run "shutdown /r /t 5" to schedule a restart in 5 seconds.
Also no resolution, size, or orientation was adjusted. Did you verify the display adapter settings?
Sure, I attempted a complete reboot. Even turned off the power and reset the BIOS to defaults just to be sure everything was normal. The only thought that comes to mind is I might be on an insider fast track, and perhaps an update while I was away yesterday caused this issue. It isn’t causing any problems now after I disabled it, but it feels strange. This morning I looked up the problem and saw a few others on various Windows versions, but no solutions were available.
It must be an insider matter since I faced major problems with the monitor and sound while using it, so I switched back to just checking the creators' updates.
I didn't consider any hardware modifications until now. Something new occurred this morning when I attempted to start my computer: the screen displayed a message indicating Windows failed to boot, likely because of recent changes. After turning it off and back on, it immediately launched normally. Initially, I assumed the issue was with my motherboard due to overclocking, as it often struggles to boot from a cold start.