- Problem:
When booting an "unknown" machine, the following error is shown at startup:
Windows Boot Manager
Windows failed to start. A recent hardware or software change might be the cause.
Status: 0xc000000f
- Cause:
boot.wim missing or corrupted at Site Server location:
C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\SBS\Images\WinPE 4_0 x64\x64\sources
please note the folder WinPE 4_0 x64 correspond to my custom WinPE x64 pre-boot configuration:
and NBS is set to respond to "unknown" computers using the WinPE 4_0 x64 pre-boot configuration:
- Solution:
Re-create the preboot environment and make sure bootwiz.exe is running at the site server for re-creating boot.wim
If bootwiz.exe does not start, troubleshoot bootwiz.exe:
http://www.symantec.com/docs/TECH211409
check boot.wim has been created or date and time have been updated:
If successful the client will then boot into Automation, register with the SMP and, in my example, launch "initial deployment" or run the next assigned task :
NOTE:
If you found the above information useful, please give this article a thumbs-up(top right of the post) or add a comment below. Your feedback will help the Symantec tech community – Thank you, Mauro