Re-adding PXE support to Configuration Manager Site

1 minute read

I already tweeted about that, but I thought this is worth a blog post, although I don’t have a solution yet.

When I try to add PXE support (or re-add it) to my Distribution Point, the following happens:

The SMS_DISTRIBUTION_MANAGER process starts the installation of all the components needed for PXE support.

  1. The vcredist are being installed
  2. WDS Server role gets installed
  3. PXE Provider is initialized
  4. WDS Service gets started and configured

Event ID 7000 : not a valid Win32 application

After all that I have a look at my fancy Server Manager in Windows Server 2012 and see that some services couldn’t be started (e.g. WDS services, WSUS service). The error in the eventlog is EventID 7000, stating that the application is not a valid Win32 application.


During my search for a problem I also booted my server and after reboot I was greeted with this message, which was totally new to me:


At first I chose to ignore this error and have a look myself and the message wasn’t wrong, there IS a file called program (no extension) on my Systemdrive. How could that happen?

image I opened this file in Notepad and saw that this file is actually a log file of the vcredist installation. How did that happen?

Digging for errors

A clue to why the log file was named “Program” is in the distmgr.log of ConfigMgr.


It looks like if the “” (quotation marks) were missing in the command line for the logfile path. Windows would then go and interpret the logfile as “C:Program”. The proof is in the “Program” file:


It clearly says: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is ‘c:program’.

I don’t know if this is a bug or has something to do with my environment, but it’s annoying ;-)

One can resolve this error by renaming the file to any other name you like. After that all the services are able to start like before.

Searching for this EventID 7000 I found the following Technet article:;en-us;Q325680


Leave a Comment