If you get PXE Error 0xc000000f then have a read of this as it may be the solution you have been looking for.

Here’s a good one: Today I came in to work only to be told that imaging had stopped working. When trying to PXE the computer would display the error of 0xc000000f and went on about Windows failed to start. File: \Boot\BCD

Here’s a screenshot of the actual error:


The first place I checked was the SMSPXE.log which is on the Config Manager server itself and can be found in the following location: C:\Program Files\SMS_CCM\Logs

The log didn’t help me out too much other than showing me a log full of errors. An Internet search revealed nothing of value either. Here’s what the log looked like:


My next port of call was checking the site system components in the Configuration Manager 2012 Administration console. (Select ‘Monitoring’ at the bottom left-hand column in the console, then expand ‘System Status’ and click on ‘Component Status’) When I did this I saw the following:


I then right-clicked SMS_MP_CONTROL_MANAGER that was shown to be in a critical condition, then from the pop-up menu selected ‘Show Messages -> Warning’ for the period ‘1 day ago.’

I was then presented with hundreds of the following warnings:


Now I was getting somewhere: The description told me that the ‘MP has rejected the request because…certificate had expired‘

I then went to the properties page of our distribution point…


… where the problem stared at me in the face:


We use a self-signed certificate and it had expired!

The solution:

I changed the expiration date of the self-signed certificate to a future date and restarted the config manager server. (Note: the restart is required)

Get my book:

ConfigMgr - An Administrator’s Guide to Deploying Applications using PowerShell