<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>UEFI | KC's Blog</title>
	<atom:link href="https://www.kjctech.net/tag/uefi/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.kjctech.net</link>
	<description></description>
	<lastBuildDate>Tue, 24 Jan 2023 18:21:02 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://i0.wp.com/www.kjctech.net/wp-content/uploads/2016/12/cropped-KC-Logo.png?fit=32%2C32&#038;ssl=1</url>
	<title>UEFI | KC's Blog</title>
	<link>https://www.kjctech.net</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">24634607</site>	<item>
		<title>MDT &#8211; Failure (5616) 31: Verify BCDBootEX</title>
		<link>https://www.kjctech.net/mdt-failure-5616-31-verify-bcdbootex/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=mdt-failure-5616-31-verify-bcdbootex</link>
					<comments>https://www.kjctech.net/mdt-failure-5616-31-verify-bcdbootex/#comments</comments>
		
		<dc:creator><![CDATA[Kent Chen]]></dc:creator>
		<pubDate>Sun, 13 Jun 2021 06:33:35 +0000</pubDate>
				<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[BIOS]]></category>
		<category><![CDATA[MDT]]></category>
		<category><![CDATA[UEFI]]></category>
		<guid isPermaLink="false">https://www.kjctech.net/?p=4639</guid>

					<description><![CDATA[<p>I was deploying a new Windows 10 installation on an old box via MDT the other day and it was failed. A quick Google search tells me that this is something to do with UEFI boot. It makes sense since it&#8217;s an old box. So, I created another sequence that only formats and prepares the disk for BIOS legacy boot [&#8230;]</p>
The post <a href="https://www.kjctech.net/mdt-failure-5616-31-verify-bcdbootex/">MDT – Failure (5616) 31: Verify BCDBootEX</a> first appeared on <a href="https://www.kjctech.net">KC's Blog</a>.]]></description>
										<content:encoded><![CDATA[<p>I was deploying a new Windows 10 installation on an old box via MDT the other day and it was failed.</p>



<figure class="wp-block-image size-large"><img fetchpriority="high" decoding="async" width="600" height="298" src="//i0.wp.com/kjctech.net/wp-content/uploads/2021/06/image-600x298.png" alt="" class="wp-image-4640" srcset="https://i0.wp.com/www.kjctech.net/wp-content/uploads/2021/06/image.png?resize=600%2C298&amp;ssl=1 600w, https://i0.wp.com/www.kjctech.net/wp-content/uploads/2021/06/image.png?resize=450%2C224&amp;ssl=1 450w, https://i0.wp.com/www.kjctech.net/wp-content/uploads/2021/06/image.png?resize=250%2C124&amp;ssl=1 250w, https://i0.wp.com/www.kjctech.net/wp-content/uploads/2021/06/image.png?resize=768%2C382&amp;ssl=1 768w, https://i0.wp.com/www.kjctech.net/wp-content/uploads/2021/06/image.png?resize=700%2C348&amp;ssl=1 700w, https://i0.wp.com/www.kjctech.net/wp-content/uploads/2021/06/image.png?resize=520%2C259&amp;ssl=1 520w, https://i0.wp.com/www.kjctech.net/wp-content/uploads/2021/06/image.png?resize=360%2C179&amp;ssl=1 360w, https://i0.wp.com/www.kjctech.net/wp-content/uploads/2021/06/image.png?resize=100%2C50&amp;ssl=1 100w, https://i0.wp.com/www.kjctech.net/wp-content/uploads/2021/06/image.png?w=1235&amp;ssl=1 1235w" sizes="(max-width: 600px) 100vw, 600px" /></figure>



<p>A quick Google search tells me that this is something to do with UEFI boot. It makes sense since it&#8217;s an old box. So, I created another sequence that only formats and prepares the disk for BIOS legacy boot and also applied the <a href="https://support.microsoft.com/en-us/topic/windows-10-deployments-fail-with-microsoft-deployment-toolkit-on-computers-with-bios-type-firmware-70557b0b-6be3-81d2-556f-b313e29e2cb7" target="_blank" rel="noreferrer noopener">hotfix</a> that fixes the issues with BIOS type firmware. But no luck, the deployment still fails right after the OS installation phase.</p>



<p>Guess what, to be able to deploy a Windows 10 installation on an old computer that doesn&#8217;t have the UEFI boot option, I will have to prepare a USB bootable disk with the BIOS boot option and boot from it.</p>



<p>Once I boot from it, it went through without any further errors.</p>The post <a href="https://www.kjctech.net/mdt-failure-5616-31-verify-bcdbootex/">MDT – Failure (5616) 31: Verify BCDBootEX</a> first appeared on <a href="https://www.kjctech.net">KC's Blog</a>.]]></content:encoded>
					
					<wfw:commentRss>https://www.kjctech.net/mdt-failure-5616-31-verify-bcdbootex/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">4639</post-id>	</item>
		<item>
		<title>How To P2V Windows Server 2012 with UEFI and a GPT Disk</title>
		<link>https://www.kjctech.net/how-to-p2v-windows-server-2012-with-uefi-and-a-gpt-disk/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=how-to-p2v-windows-server-2012-with-uefi-and-a-gpt-disk</link>
					<comments>https://www.kjctech.net/how-to-p2v-windows-server-2012-with-uefi-and-a-gpt-disk/#respond</comments>
		
		<dc:creator><![CDATA[Kent Chen]]></dc:creator>
		<pubDate>Mon, 14 Mar 2016 05:07:01 +0000</pubDate>
				<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[GPT]]></category>
		<category><![CDATA[P2V]]></category>
		<category><![CDATA[Server 2012]]></category>
		<category><![CDATA[UEFI]]></category>
		<category><![CDATA[virtualization]]></category>
		<guid isPermaLink="false">http://www.kjctech.net/?p=2873</guid>

					<description><![CDATA[<p>If you try to run a physical-to-virtual (P2V) conversion on a Windows Server 2012 R2 machine with UEFI, you’ll receive the error “There is no BCD boot device found in the source machine, noticing that the conversion of an EFI boot machine is currently not supported.” In this article, I’ll show you how to bypass that error by converting the [&#8230;]</p>
The post <a href="https://www.kjctech.net/how-to-p2v-windows-server-2012-with-uefi-and-a-gpt-disk/">How To P2V Windows Server 2012 with UEFI and a GPT Disk</a> first appeared on <a href="https://www.kjctech.net">KC's Blog</a>.]]></description>
										<content:encoded><![CDATA[<p>If you try to run a physical-to-virtual (P2V) conversion on a Windows Server 2012 R2 machine with UEFI, you’ll receive the error “There is no BCD boot device found in the source machine, noticing that the conversion of an EFI boot machine is currently not supported.” In this article, I’ll show you how to bypass that error by converting the server to a VM with Disk2vhd and how to repair the boot record so you don’t get a black screen with a blinking cursor.</p>
<p>//via <a href="https://4sysops.com/archives/how-to-p2v-windows-server-2012-r2-with-uefi-and-a-gpt-disk/" target="_blank" rel="noopener">4sysops</a></p>The post <a href="https://www.kjctech.net/how-to-p2v-windows-server-2012-with-uefi-and-a-gpt-disk/">How To P2V Windows Server 2012 with UEFI and a GPT Disk</a> first appeared on <a href="https://www.kjctech.net">KC's Blog</a>.]]></content:encoded>
					
					<wfw:commentRss>https://www.kjctech.net/how-to-p2v-windows-server-2012-with-uefi-and-a-gpt-disk/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">2873</post-id>	</item>
	</channel>
</rss>
