Hi orange109, I'm trying to reproduce this error, just a couple of questions. Are you using LAN or wireless? Also Win8.1 32 or 64bit? Thanks.
I'm using lan in this case and the Win 8.1 is 64 bit version.
Thank you, one more question, did you install legacy or uefi?
Not sure what do you mean by 'install' the legacy / uefi boots optiones were there in the bios interface.
Hi orange109, when you install an OS, you can do so by hitting F10 when the NUC boots up. When you do that you can select your USB/CD device (where the installer is) and choose either UEFI device or not, that is what I was referring to. If you don't hit F10 and just let the installer run, you can tell how your OS was installed by going into the BIOS (hit F2 on restart) and seeing where the "Windows Boot Manager" is under "Boot Order".
I tried to replicate your problem and I was able to access the headless NUC without a problem using Team Viewer. I'm still working on UltraVNC. Can you tell me what error you're getting when you try (a screen shot would be great if possible)? Just so you know the way I tried in Team Viewer, I sign in (on the right side) and add the remote computer to my list of "Computers and Contacts".
As for the install question, I use an image of Win 8.1 which sits on a USB flash. I press F10 and use Acronic True Image to burn the OS image on my SSD.
Not sure which one of them is it.
As for the Team Viewer, as I mentioned in the update part of my post - "Disabling the legacy showed better results in UltraVNC/Teamviewer. I was able to actually control the headless NUC but I couldn't modify the tiny resolution it gave me (400x600)"
I don't get any error message in either Team Viewer or UltraVNC, it's just that UltraVNC / teamviewer is very bad at 600x400 resolution scale.
Just to be clear, I disabled the legacy boot after I installed the image of the OS on the SSD.
Also, I tried doing all of the following on a fresh copy of Win 8.1 Home 64 bit since I thought there might be something wrong with my OS backup image, but it was the same on both.
Oh and could you supply some screenshots indicating what is the resolution you're getting in the remote access? both Teamviwer and VNC
I just wanted to let you know I haven't forgotten about you, I'm still working on replicating your problem. Another couple questions. What are you using to connect to the headless NUC, and what OS is it, also is it wired or wireless?
Yes, I saw that you could get TeamViewer to work if you disabled Legacy in BIOS (which is very strange, shouldn't have anything to do with it), but when Legacy isn't disabled what happens? Nothing at all, do you get an error?
Lastly, have you tried to use TeamViewer to start automatically when the NUC boots, and then login from your other machine? Not the way you described. I will upload a document tomorrow if you're not sure how to do that, I just wanted to let you know I hadn't forgotten about you.
1. The computer I connect with to remote access is a desktop PC (Intel Core i7-2600 CPU @ 3.40GHz) running Windows 10 Pro 64 bit.
I use UltraVNC or the latest Team viewer to try to control the NUC. The desktop PC is connected to the same home local network with a wire connection. Not that it matters because you get the same results either WiFi or if its a far away station.
2. When I left the legacy enabled and disabled the uefi boot I remember getting a bigger resolution but without any way to actually control the station. When both were enabled as it was in the default setting of the NUC bios, it just didn't work at all, I got a black screen.
3. The way I tried is to have team viewer start up when Windows boots as you suggest, otherwise I don't have a way to test it when I try to boot headless.
Just to be on the safe side, If I plug the screen off just a bit after doing a restart to the OS it would still work properly after booting back up. But when I shut down the NUC and turn it on again, then it won't work.
BTW, Some guy told me he managed to remote access the NUC with Windows remote desktop access, but I don't have Windows PRO on the NUC nor do I plan to purchase it just for the sake of remoting it.
It is surely a problem with Intel because VNC / Team viewer are cross platform products that work almost on any computer in the world. This also needs to work on these new NUC models while booting headless. Whether it should be a bios update or graphics driver update I don't know, but it should be fixed asap.
I have exactly the same problem as orange109 with my new NUC5PPYH which I'm using with Kodi as an HTPC. Once I turn off my HDMI connected display, and put the NUC to sleep then wake it up with the display off, Teamviewer shows the black screen as described in this thread. If I send ctrl-alt-del to the NUC, I get a corrupted display as described elsewhere. I have to physically turn on the display for Teamviewer to be able to function correctly.
If I leave Kodi running, put the machine into suspend, wake it up, then reconnect, Kodi will sometimes display, however, it doesn't function correctly. Trying to change to the Windows desktop or another application results in the black box syndrome. Alt-tabbing back to Kodi will show the display, however, mouse operation is funky and the mouse can't reach the bottom of the screen.
If, after turning the monitor on, I turn it back off, Teamviewer continues to function correctly. It's only when rebooting or awakening the NUC with the display off, do these problems develop.
Lastly, I have these issues running wireless and wired.
I have these software versions:
Windows 7 Ultimate SP-1 64-bit
Intel display drivers 10.18.14.4234
Headless boot / wake-on-lan / alt-tab out of Kodi after headless boot or wake-on-lan problem:
Sending Ctrl-Alt-Del when black box is shown:
Thanks for sharing.
Come on Intel! Don't leave us hanging! Fix the drivers/bios or what ever needs fixing so we could remote access headless.
It's obviously a driver issue as it was resolved in the big thread for the other NUC model. Why Intel didn't roll that out for the other models, I'm unclear. It's been over a year since this problem was discovered, and there's really no excuse for not having this patched for all NUC models by now.
Intel, can we get an update please? It's been two weeks since you've chimed in here.
attached is a screenshot of the headless nuc while remote accessed with UltraVNC while latest graphics driver installed.
It is not workable. I cant use the mouse & the keyboard - it only shows the desktop and thats that.
PLEASE FIX IT INTEL! WHY WOULD YOU RELEASE A NEW MODEL OF A NUC WHICH IS WORSE THEN THE PREVIOUS ONE?
same goes for the RealVNC. Don't know why cvare said he got it to work. If you got it to work please tell me how you did it because its not working for me at all. Tried enabling/disabling the legacy boot. Nothing seems to work
Like in UltraVNC, It is not workable. I cant use the mouse & the keyboard - it only shows the desktop and thats that.
Intel this is just unacceptable!! I am using the NUC for business purposes and you are really causing me damages. How can you release a model that won't work headless (besides the pricey Team Viewer) after there were so many complaints about this in the past??!
Also, I have posted this thread a month ago! why there hasn't been any progress since? new drivers?!
Please fix it already. If you found the cure for the previous Celeron based NUC to work with VNC headless why can't you do it for this one as well?
Look at the attached image