I also just received my Razer Core and am experiencing similar issues with my NUC6i7KYK!
Rebooting didn't remove the Virtual Display for me. I was able to right click on the desktop and use the Microsoft (not Intel/Nvidia) display settings app under "multiple displays" to select "Show only on 2".
In Win 10, if some application shows up hidden on the virtual display, you can hold shift while right clicking on it in the taskbar, select move, then press any arrow key, then move the mouse onto your actual display, and it will bring the application window with it.
Have you been able to get the BIOS/POST to display through the Core at all? I get nothing with the BIOS set to "Auto" display, and even making "Thunderbolt" primary I still don't get a signal until Windows initializes the display. This double sucks, given my drives are password protected using ATA Security and I need to see the BIOS password prompt. I tried typing it in blind, but it didn't boot, so who knows what's going on :-(
1 of 1 people found this helpful
I have not been able to get BIOS/POST to display through the Core at all. I suspect this is not possible due to lack of loaded drivers at that point. Typing it in blind might work if you connect your keyboard with a wire to NUC's USB port. Wireless certainly won't work, and neither will Core's USB hub.
Yeah, I've been using a regular USB keyboard connected directly to the NUC. After typing my password in blind and the NUC just sitting there, I pulled the HDMI cable out of the Core, plugged it directly into the NUC, and hit Ctrl+Alt+Del, at which point it boot into Windows without asking for an ATA Password (it's normally stored across restarts), meaning it was something after the password was entered which prevented me from booting (I don't see any "Halt on..." stuff in the NUC BIOS?). So, for kicks, I plugged the HDMI back into the Core, cold booted, typed my password blind, hit Ctrl+Alt+Del, and it came up when Windows started! I still have no idea what could be keeping it from booting the first time around, but at least I have a workaround that doesn't involve swapping cables around.
I had been hoping to plug my USB keyboard+mouse into the Core, but given it apparently won't then be available at boot, plus the fact that I'm also experiencing the same USB problems as everyone else (which can apparently be worked around by disabling the Intel graphics adapter), I think I'll just get a Logitech Unifying wireless keyboard, as I have a travel one now, and they are paired at power-on before boot. I also have a couple StarTech Thunderbolt docks (TB3DK2DPW) coming, I'm starting to fear those might also suffer from not initializing a connected USB keyboard before Windows boots :-(
At least the "Show only on 2" thing seems to be working to keep the Intel Virtual Display from interfering now.
Thank you for joining the Intel communities.
To be clear the unit works fine when you connect the monitor straight to the Intel® NUC except when it is connected to the Razer Core, correct?
Could you please POST the model of the Razor Core you have?
Also, I will appreciate if you could attach the results for the Intel SSU (System Support Utility), you can download it here:
Install the tool, run it and then attach the results here.
Let me clarify. If you connect the monitor to Core, it fails to work properly on first boot after connecting the power plug of the NUC.
If you connect the monitor to your NUC (with Core attached), everything loads up fine. That being done, now you can restart the system with your monitor connected to the core. (You can't unplug the NUC from the power plug, even if it is shut down)
The problem is that it just doesn't work right without that weird procedure. I mean just coming home with all peripherals already attached to the Core and only NUC left to connect and turn on.
I can probably even make a video if you're interested.
As for the model, according to the box:
Model No.: RC21-0094
nuc.xml.zip 7.2 K
When I boot with my monitor connected directly to the NUC, Windows comes up correctly with it as a single display. When I boot with the monitor connected to the Core, Windows comes up in dual-display mode, showing both my monitor attached to the Core (as secondary display), but also an Intel Virtual Display (as primary display). Unlike for Pavel, rebooting does not cause my Virtual Display to disappear. As above, I have used the Windows display settings to disable the Virtual Display.
Razor Core Model No.: RC21-0094
ssu.xml.zip 7.1 K
By the way, did you update your thunderbolt drivers to version 18? And latest bios. Both of these have a relatively fresh version.
I have updated both, yes. I pretty much sit around all day hitting refresh on the NUC downloads page ;-)
I'm not using any of the "GPU Switching" utilities from Razor, as they only seemed intended for use with their own laptops. You didn't happen to try any, did you?
Nope. I tried to avoid any crapware from that company. I only needed the device from them, not a full suite of led blinking software in the cloud. They don't provide any drivers and their utility has no useful features at all.
Please allow me to further investigate on this.
Just to make sure you all have this driver installed, correct?
Also, I stumbled upon the same problem yesterday and managed to get to device manager. It showed a generic pnp monitor attached to the NUC (video accelerator shown as intel 580). There was no monitor attached to it in reality.
Do you have the INF file installed for this monitor?
If there is an .INF file available for your monitor/TV, installing it would add support for display resolutions, refresh rates, or color quality etc.
Usually there is an installation disc that came with your monitor or display device.
Also, you can check the website of your monitor manufacturer to see if a monitor driver or monitor .INF file is available for download.
I’m sorry that I did not mention this before
Monitor .INF FAQ for Graphics Drivers
Do you have the possibility to test different cable?
I just want to know this before doing further investigation on the issue.
Thank you for your patience!