Okay, I've managed to solve this myself.
As it turns out, the keyboard at boot is set to have NumLock enabled. Which, frankly, is kind of retarded.
So when I was typing the password 'admin', I couldn't tell since each of the five characters were obscured with '*', but MEBx was receiving 'ad05n'. Which is clearly wrong.
So the work around, in case anyone else experiences this, is to turn NumLock off (forcibly) as soon as you enter MEBx. Note that I'm using a Thinkpad USB keyboard.
Nice to know you got over the password issue in your system. Thank you for sharing this feedback.
Now, are you still seeing the other issue you mentioned in which you cannot get to the MEBx via Ctrl+P?
That's actually the same problem as well. The 'P' key is '*' when in NumLock. There must be a very tiny fraction of a second at boot, just before post, where the keyboard switches out of NumLock, and Ctrl-P worked for me that 1/100 times.
I find I can get into MEBx reliably if I very quickly but deliberately:
1) turn the NUC on
2) Wait for the Intel NUC logo
3) Quickly turn off NumLock
4) Press Ctrl-P
I remember in old school BIOS ~10 years ago there was an option whether to boot with NumLock on or off. It would be very nice if Intel Visual BIOS added that as a feature.
It would also be very helpful if the MEBx interface showed the character you typed for a split second before masking it with an asterisk. Or, if there was any sort of a scratch pad inside of MEBx so that I could see what characters I'm typing. I've seen others with similar problems, with UK or other non-US keyboards.
Alright, just wanted to confirm.
I will make sure your comment reaches the proper department for future consideration.
@diego_intel: My D54250WYK has just arrived, and first problem I experienced when installing Win7 Pro was when it asked me to type a User Name, then a PCname for network. I couldnt understand why the keys I was entering were incorrect, and also being echoed to both fields. In the end I had to putup with defining names I didnt want, just to continue the install. Once Windows install complete, I had the same problem when trying to Create a 'Drivers' folder to save the NUC drivers in. As the Windows DVD came from Germany, I wondered if it was not recognising my UK keyboard so sent them an email to ask if it is truly a UK DVD (and why the supplied KEY wasnt accepted!). It was only when next morning I had time to type out a keyboard mapping in Notepad, it dawned on me the numeric pad was mapped into the keyboard centre ! Maybe my system installs the last 15 years have been lucky, but I dont recall any of them booting with NUMLOCK set. Maybe in days of Win 3.1 seem to recall having to go into BIOS setup to disable the numlock. So I confidently think I have the answer and go into the NUC BIOS, but nowhere can I find a setting for it ! Google the web which brings me to this post to see I am not the first to ask where is the BIOS setting. I think this must trip a lot up, and its so yuck to have to manually disable numlock each time one switches on. It surely must be a tiny minority who use numloc, so it should be an easy update to your BIOS to just set the KB without numlock to cater for the majority, to save you having to introduce an extra UI feature ?
I've found the setting in BIOS. But not the tradiational way.
Up at the top, do a search for numlock. Then add it as a favourite.
Once added as a favourite, click the star (favourties) and you will see it there as Unknown>Intel Board > Numlock status. I had to click about 5-6 times then down arrow but finally it switch from ON to OFF. Saved the changes and rebooted. No more Numlock!