Ahh this is more than annoying, first NUC deployment equals epic fail.
Just hit this same issue. Attempting to use ScreenConnect 4.4 over WAN. Same ScreenConnect installation hosts over a 1K unattended remote devices or just about every hardware configuration under the sun, that you could imagine, without issue.
D54250WYK, Intel mSATA SSD, Corsair RAM, W7 Pro x64 SP1 fully updated, fully updated drivers and BIOS as of today.
I just dropped off a computer at a remote site, that I absolutely needed remote access to tonight, only to find that it doesn't work?
I spent way more on the Intel brand, than I would have for other similar device that would have met my needs. Went with Intel as this is something I need rock solid reliability on, and just assumed by going to directly to the hardware source I would have less issues and higher reliability.
Planned on deploying many more of these for similar functions, where I mange remote client networks. Considering I never have these issues, EVER. That's a pretty serious black eye on this product or driver.
FYI, device worked fine headless via RDP locally. ScreenConnect over WAN, black screen, that fills in gibberish if you move the cursor around.
9+ months without a resolution to this issues seems insane, I feel like an idiot for not realizing this was an ongoing issue before deploying this.