<?xml version="1.0" encoding="utf-8" ?>
<?xml-stylesheet type="text/xsl" href="RSS_xslt_style.asp" version="1.0" ?>
<rss version="2.0" xmlns:WebWizForums="https://syndication.webwiz.net/rss_namespace/">
 <channel>
  <title>ASRock Forums : Stop Ctrl+P at Post -How To</title>
  <link>https://forum.asrock.com/</link>
  <description><![CDATA[This is an XML content feed of; ASRock Forums : Intel Motherboards : Stop Ctrl+P at Post -How To]]></description>
  <copyright>Copyright (c) 2006-2013 Web Wiz Forums - All Rights Reserved.</copyright>
  <pubDate>Sun, 21 Jun 2026 09:31:12 +0000</pubDate>
  <lastBuildDate>Thu, 28 Jul 2016 13:15:26 +0000</lastBuildDate>
  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
  <generator>Web Wiz Forums 12.04</generator>
  <ttl>360</ttl>
  <WebWizForums:feedURL>https://forum.asrock.com/RSS_post_feed.asp?TID=3124</WebWizForums:feedURL>
  <image>
   <title><![CDATA[ASRock Forums]]></title>
   <url>https://forum.asrock.com/forum_images/web_wiz_forums_black.png</url>
   <link>https://forum.asrock.com/</link>
  </image>
  <item>
   <title><![CDATA[Stop Ctrl+P at Post -How To :   gkar wrote:Hi,I have an older...]]></title>
   <link>https://forum.asrock.com/forum_posts.asp?TID=3124&amp;PID=15330&amp;title=stop-ctrl-p-at-post-how-to#15330</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://forum.asrock.com/member_profile.asp?PF=74">parsec</a><br /><strong>Subject:</strong> 3124<br /><strong>Posted:</strong> 28 Jul 2016 at 1:15pm<br /><br /><table width="99%"><tr><td class="BBquote"><img src="forum_images/quote_box.png" title="Originally posted by gkar" alt="Originally posted by gkar" style="vertical-align: text-bottom;" /> <strong>gkar wrote:</strong><br /><br /><font color="#333333"><span style=": rgb255, 255, 255;"><font color="#000000"><font color="#FFFFFF">Hi,<br><br>I have an older Fata1ty H87 Performance board. <u><b>Not sure when this started, but am certain it was fine when I updated BIOS to latest -2.60, some months back.<br></b></u><br><u><b>Now, my bootup, past POST is delayed by a request to enter MeBX using Ctrl+P. </b></u>Finally worked out I HAD to set a new strong password to access MeBX, but nothing of consequence (at least, I can't find any hidden values) to deactivate it. Can't find any BIOS settings relevant to cancelling it at POST.<br><br>Also, in my attempts, I now find sometimes I have no monitor (55" LG LED-TV) signal until near drivers' loading. Once loaded, the OS operates fine. I tried installing the earlier 2.50 BIOS, thinking it would prevent the activity <u><b>(as BIOS 2.60 stated 'added NVMe support')</b></u> which was the Intel ME component, but to no avail. So reflashed to 2.60.<br><br><u><b>Can anything inside the OS -Win10 x64- have any bearing on what is happening prior to the OS boot? ie. could an Intel update be the cause of this recent advent?</b></u> Why is there no switch(es) inside the BIOS to prevent/bypass this activity?<br><br>I hope someone can assist. I can easily reinstall a recent backup OS image (via True Image) if required. It is not critical HTPC operation, just a PITA. Thanks. </font><br></font></span></font></td></tr></table><br><br>So you're saying that you think UEFI 2.60 might have caused the prompt to start MEBX during startup, but that did not start happening until months after you changed to 2.60? You did mention the Windows update possibility too.<br><br>This prompt should time out, you should not be required to enter Ctrl+P. That is an <i><b>option</b></i> to start MEBX, or should be. That prompt should appear for only a few seconds.<br><br>Intel calls the switch or option in the UEFI/BIOS to enable MEBX, <i><b>Intel AMT</b></i>. I don't see any option like that in your board's manual, but it could have been added later on.<br><br>The obvious places for this option would be, in the <i><b>Advanced</b></i> screen, either the <b>CPU Configuration</b> screen, or the <b>Chipset Configuration</b> screen. A long shot guess, the <i><b>VT-d</b></i> option in <b>Chipset Configuration</b>.<br><br>Or it could simply be the <i><b>AddOn ROM Display</b></i> option in the <b>Boot</b> screen. That is normally enabled by default. The <i><b>Full Screen Logo</b></i> option on the same screen must be enabled for the <i><b>AddOn ROM Display</b></i> option to work.<br><br>My only other <i><b>theory</b></i> is a UEFI/BIOS clear happened for some reason, and an option was reset to its default that caused that prompt to appear.<br><br>Could a Windows 10 update be the cause? Given its automatic, no choice updates, in this case it is possible. I doubt you have the <b>Intel SBA</b> (Small Business Advantage) software installed, since it is not listed as a Windows 10 download.<br><br>This Intel MEBX user's guide contains a list of the software components required for MEBX to work. Check chapter 2 for that:<br><br><a href="http://www.intel.com/c&#111;ntent/dam/support/us/en/&#100;ocuments/motherboards/desktop/sb/intel_mebx_user_guide_for_7series.pdf" target="_blank" rel="nofollow">http://www.intel.com/content/dam/support/us/en/documents/motherboards/desktop/sb/intel_mebx_user_guide_for_7series.pdf</a><br><br>I would check the list of installed software in Windows 10, and see what might be there that might be the cause.<br><br>The addition of NVMe support in 2.60 is not at all related to MEBX or IME. NVMe is a new storage protocol used by PCIe SSDs.<br><br>Your H87 chipset supports Intel SBA, which is why the related features like MEBX can work with it. It may be a Fatality board, but its H87 chipset has more influence on what features it supports. Most of the Intel non-Z chipsets support SBA.<br><br>Using a TV as a monitor (via HDMI) will not be the same as a monitor. The 1080 resolution is supposed to be the same, but there is more to it than that. Nvidia's Control Panel utility has two resolution lists, one for PCs, the other just called Ultra HD, HD, SD. Those are for TVs. No idea what video source you use, but if it has software, try changing the resolution to a non-PC option, if possible.<br>]]>
   </description>
   <pubDate>Thu, 28 Jul 2016 13:15:26 +0000</pubDate>
   <guid isPermaLink="true">https://forum.asrock.com/forum_posts.asp?TID=3124&amp;PID=15330&amp;title=stop-ctrl-p-at-post-how-to#15330</guid>
  </item> 
  <item>
   <title><![CDATA[Stop Ctrl+P at Post -How To : Hi,I have an older Fata1ty H87...]]></title>
   <link>https://forum.asrock.com/forum_posts.asp?TID=3124&amp;PID=15322&amp;title=stop-ctrl-p-at-post-how-to#15322</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://forum.asrock.com/member_profile.asp?PF=3499">gkar</a><br /><strong>Subject:</strong> 3124<br /><strong>Posted:</strong> 28 Jul 2016 at 10:15am<br /><br /><font color="#000000"></font><font color="#333333"><span style=": rgb255, 255, 255;"><font color="#000000">Hi,<br><br>I have an older Fata1ty H87 Performance board. Not sure when this started, but am certain it was fine when I updated BIOS to latest -2.60, some months back.<br><br>Now, my bootup, past POST is delayed by a request to enter MeBX using Ctrl+P. Finally worked out I HAD to set a new strong password to access MeBX, but nothing of consequence (at least, I can't find any hidden values) to deactivate it. Can't find any BIOS settings relevant to cancelling it at POST.<br><br>Also, in my attempts, I now find sometimes I have no monitor (55" LG LED-TV) signal until near drivers' loading. Once loaded, the OS operates fine. I tried installing the earlier 2.50 BIOS, thinking it would prevent the activity (as BIOS 2.60 stated 'added NVMe support') which was the Intel ME component, but to no avail. So reflashed to 2.60.<br><br>Can anything inside the OS -Win10 x64- have any bearing on what is happening prior to the OS boot? ie. could an Intel update be the cause of this recent advent? Why is there no switch(es) inside the BIOS to prevent/bypass this activity?<br><br>I hope someone can assist. I can easily reinstall a recent backup OS image (via True Image) if required. It is not critical HTPC operation, just a PITA. Thanks. <br></font></span></font>]]>
   </description>
   <pubDate>Thu, 28 Jul 2016 10:15:49 +0000</pubDate>
   <guid isPermaLink="true">https://forum.asrock.com/forum_posts.asp?TID=3124&amp;PID=15322&amp;title=stop-ctrl-p-at-post-how-to#15322</guid>
  </item> 
 </channel>
</rss>