SCCM 2012 R2 + Surface Pro 1 PXE boot failure Windows Deployment Services error 0xc0000022 caused by Secure Boot

Question

_{Friday, September 12, 2014 12:51 PM | 2 votes}

This is less of a question and more of a posting for anyone else who runs into this problem, though I would love to know why this is happening.

Last week everything was working fine. The server was not changed since then.

When I PXE boot a Surface Pro 1 with Secure Boot enabled from our SCCM 2012 R2 server the boot process fails with a message displayed on the Surface Pro "Windows Deployment Services error 0xc0000022". Disabling Secure Boot allows the PXE boot and OS image to succeed. Secure Boot can then be reenabled after Windows 8.1 has been loaded.

I can PXE boot normally a Surface Pro 3 or any other computer we have, but multiple Surface Pro 1 tablets won't boot unless Secure Boot is disabled.

The last file pulled by the Surface Pro 1 before it errors out is: SMSBoot\x64\bootmgfw.efi.

The SCCM server is running Windows Server 2012 R2. The Surface Pros that I tested had a variety of firmware revisions, including the latest one from August 2014. It is possible that the ones that I imaged last week had really old firmware revisions, but I cannot guarantee this.

All replies (4)

_{Wednesday, October 1, 2014 9:35 PM}

Thanks for share your issues, the experiences and how solve them.

_{Wednesday, January 7, 2015 10:05 AM}

I just wanted to let you know that I had exactly the same problem and after disabling Secure Boot on the Surface Pro 1 (2 devices here so far) it worked as it did with all other systems I installed with Secure Boot enabled. Maybe this is a bug in the Surface 1 Firmware?

Thanks for posting the solution, this saved me quite some headaches! :-)

_{Thursday, August 13, 2015 7:05 PM}

I had the same issue on an older Surface.  Like you said, all my newer ones would PXE boot except for this one.  I resolved it by entering the BIOS and removing the installed keys.  After doing so, I am now able to PXE boot to my deployment server!

I too am running Server 2012R2.

_{Tuesday, October 27, 2015 6:19 PM}

Thanks for this post. I had the same issue and disabling secure boot allowed me to run the os install from WDS.