Just received and installed a new Gigabyte Aorus RTX 2070 Gaming Box on a Skull Canyon NUC tonight. Wanted to share the experience, and ask a question.
First off, this is an external Thunderbolt 3 Graphics Box running an Nvidia RTX 2070 card. These boxes are nice, and a little smaller in size than the Razer external graphics boxes and the like, as this box is shorter in depth and tailored to the smaller card size.
- I should have predicted this, but in my single monitor setup there is now no graphics/no video in a preOS or pre-boot environment. For BIOS changes and updates, I'll have to reconnect the monitor to the main system to get any video to see what I am doing. It makes sense, as the Thunderbolt driver isn't loaded until Windows is up, but I just didn't foresee this.
- Currently running World of Warcraft at 1920x1080 with all max graphics settings. I'm not a 4k Monitor person yet, but this card is quite an improvement in performance over the integrated graphics on the same monitor I was using before.
- The odd thing, and probably the only question I have, is surrounding the monitor detection stuff in Windows. My only monitor is now connected to the external gaming box (via HDMI), and the Skull Canyon NUC has no monitor connected. Yet, somehow, when I get into Windows, Windows thinks the only monitor is Monitor #2, and there is an entry for a Generic Non-PNP Monitor showing up (as Monitor #1) connected to the Intel integrated graphics controller. It was a challenge to get the monitor configured as the Primary Windows Monitor, as all the controls kept popping up on the non-existent screen. I learned about this handy key stroke - Windows+Shift+Right Arrow. This makes your active window move to the next monitor in a multi-monitor setting. So I right-clicked to get 'Display Settings' then did that keystroke to make the settings window move over to Monitor #2. From there, I could then tell Windows that Monitor #2 is Primary.
So, back to my question: What the heck is the "Generic Non-PnP Monitor" that Windows "thinks" is connected to the Intel graphics subsystem (but really doesn't exist) - and takes over the Monitor #1 position, causing all sorts of downstream usability and setup issues? Cause it's a pain in the butt.
Have you installed Intel's drivers? The most important in your case are those three drivers (install them in the same order):
Management Engine driver: https://downloadcenter.intel.com/download/28219/Intel-Management-Engine-Consumer-Driver-for-Windows-... NUC6i7KYK?product=89187
All other drivers you may download here: https://downloadcenter.intel.com/product/89187/Intel-NUC-Kit-NUC6i7KYK
By the way, when I search the internet and this forum, I see several references to "Virtual Monitor" and "Generic Non-PnP Monitor" showing up with Intel devices running headless. Here's one thread, with some registry hacks to kill it.
I'd like to better understand why Intel does this with their graphics driver. What's the purpose in creating a "virtual display" when no monitor is plugged in?