SCCM Task Sequence Error Codes & Fixes

When performing a bare-metal image install in SCCM, occasionally an error will occur that will halt the initiation of a task sequence.  Below are a few errors I have experienced, which I have compiled with my own [brief] explanation and what to do to fix it.  This post will be updated as I come across new errors, explanations, alternate fixes, etc.

Error: 0x800701E7
Cause: Unknown.
Fix: Restart with boot CD or PXE.

Error: 0×80070032
Cause: No file system
Fix: Using command support, format (quick) the disk or recreate the disk using diskpart.exe

Error: 0×80070490
Cause: Failed to find driver for PCI\VEN device
Fix: Review SMSTS.log for driver info. Likely need to add the PCI\VEN into an .inf or txtsetup.oem file

Error: 0×80070241
Cause: Error during TS user interface caused in memory
Fix: Restart with boot CD or PXE.

Error: 0x80072EE7
Cause: IP address is not on a subnet that connect to the SCCM server
Fix: Change the port the Ethernet cable is connected on. Restart with boot CD or PXE.

  1. #1 by zx9hippo on May 10, 2011 - 1:56 pm

    0×80070490 = also attributed to trying to use a WIM image that does not specify OS bit-depth support (32/64). a.k.a. – using wim image 1 of 2 instead of 2 of 2 as the OS image.

  2. #3 by Karl on October 20, 2011 - 9:34 am

    0×80070570= Corrupted wim file

  3. #5 by AJ on February 14, 2012 - 4:52 am

    HI, i get a task sequence error (0×80070643) when runing a program from a list of advertised programs. can u please assist..

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

Join 39 other followers