May 2012


Desktop Boards — Keyboard prompts during boot process POST

Here’s this list for function keys during POST for Intel boards.

During the boot-up process, before the operating system loads, you can press certain Function keys and Control key combinations to launch different tasks.

Function key or Control key Purpose
F2 Accesses the BIOS Setup program.
F7 Initiates a BIOS update process where the update files are stored on a USB thumb drive. For instructions on this BIOS update method, seeInstructions for F7 BIOS Flash update.
F8 Opens the Windows* boot option menu which allows you to boot into safe mode, enable boot logging, perform restore tasks, and more.
F9 Launches the Remote PC Assist Wizard. This function is only available when the board supports Intel® Remote PC Assist Technology (Intel® RPAT).
F10 Accesses the boot menu and displays all bootable devices to select from.
F12 Allows you to boot to a network; generally used to install an operating system from an image on the network.
Control-I Opens the Intel® Rapid Storage Technology option ROM user interface.  This prompt is available on boards that are configured for and support RAID.
Control-M Opens the Marvell RAID option ROM user interface. This prompt is available on boards that are configured for and support Marvell RAID.
Control-P Opens the Intel® Management Engine (MEBx) Configuration user interface. This prompt is only available on certain boards that support the Intel® Management Engine.

Desktop Boards — Keyboard prompts during boot process POST.


Windows could not complete the installation (after sysprep).

This got me going again…
New Member
Join Date: Feb 2011
Posts: 1
Thanked: 0
Here’s what I did to solve it for myself (I had run sysprep /generalize /oobe to move my machine from an AMD to an Intel platform):
1) Get the command prompt with Shift-F10.
2) Run services.msc and turn anything that you disabled yourself to Automatic (use your head here, for example Nero’s NMIndexService can stay off), in case you’ve done services tweaking like I did.
3) Ensure the sptd service is disabled if you have it installed (used for virtual CD/ISO-mounting apps), you do this with regedit, it’ll be in HKLMSystemCurrentControlSetServices I believe.
4) Reboot
5) Command prompt again, cd to WindowsSystem32oobe and run msoobe
6) Create a new user and go through the steps.
After the OOBE part was done, I just got a black screen instead of going to desktop. Just sat there, so I powered off and rebooted. After reboot, it logged me into the new user I had created.
7) Log back into your old user, all should be fine now.
Hope this helps someone out there.
Reply With Quote

New Member
Join Date: Feb 2011
Posts: 1
Thanked: 0
Thanks Gypsy. I tweaked your post a bit and did the following:
After getting the command prompt:
I ran MMC > Add Remove Snap In > Computer Management > System Tools > Users to change my Administrator password to meet the requirements.
Add Remove Snap In >Group Policy Object > Local Computer >Computer Configuration > Windows Settings>Security Settings>Local Policies>Security Option and changed “Accounts: Administrator Accounts status” to enabled. From there a restart and “bob’s your uncle”!