[voip-ninja]

Well, this sucks. Even after going back to FW026 it is still not powering on. Intel must have changed something with the CIR in FW027 that survives even rollback of the BIOS version.

So those of you running OE might not want to update to this new BIOS.

I'm running my D34010 with 27 and power on from the remote is working for me. I recently installed openelec on it (got sick of Windows as my OS for XBMC) and the mouse didn't work at all until I went to the 27 bios. I then went into the input settings in xbmc and checked the option for the remote to send mouse commands.

Power on, power off, all functions work perfectly from my RC6 remote.

Thanks for taking the time to respond. I have a little update on this.

Got frustrated enough that I tapped into the SATA port on the NUC and installed Win 7 x64 Pro onto a full size 3.5" HDD I had lying around. No change. Still could not get the thing to power up but once in Windows the device was recognized and would work.

I added a 2nd Windows Media Center device to my Harmony One and still no luck. I then (after spending hours scouring around trying to learn something) added a Microsoft Windows Media extender device to my Harmony and just like magic it started working. Power up and power down worked fine with Windows and when I put the SSD back in it continues to work with OE.

So, I can surmise a few things.... as this had been working completely fine now for a really long time;

1. FW 27 includes some new FW/setting for the Nuvoton CIR that is built into the Haswell NUC...
2. Once this FW/change happens the device will no longer power up from some older IR profiles like "Windows Media Center".
3. Does work with Windows media extender and probably several other IR profiles.
4. Rolling back FW does not fix the problem because, I assume, the new FW and/or settings stick even when the older FW is reinstalled.

I still have a couple of minor outstanding issues;

1. After going through all of this I re-built my activity as I had it before, trying to use "Microsoft Media Keyboard" device to shortcut some actions in XBMC. For some reason these are no longer working... although they had been working (from same device) when they were being used in a different activity. Not sure what is going on with this one... I have "remote sends keyboard presses" selected... turning it off doesn't change anything either.

2. I was getting some audio dropouts for a while. I suspect that at some point with all of the messing around the HDMI display device was changed from "HDMI1" to "default" and possibly that is related to the audio dropouts. I will have to test with some other files to see if the issue is really resolved now that I have changed it back to "HDMI1".

3. I don't even know if 27 fixed the issue I was originally trying to squash... random power-up of the NUC... have to monitor that.

All in all this has been a huge PITA. I feel like my part time job is nursing this NUC into doing what I want... it's even more frustrating because half the stuff I run into, nobody (but me) gives a crap about.