SCCM 2012 R2 Won't import boot.wim

Over the weekend I have upgraded to SCCM R2 CU4 and today I am having issues with OSD, After the install of the client, the task just ends and does not continue to install the applications.
I checked: drivers, network access account, redistributed all content to DPs still the same issue. After some googleing I found this thread "Failed to get the environment key - SMSTS.log" Sorry not allowed to link yet.
My wim versions are 6.2.9200 so I figured I need to import new boot images, not a big deal.
I have ADK 8.1 Setup up on the server. exported the boot.wim from the adk but whem I attept to import the new boot.wim sccm gives me an error. So back to google. People have stated that MacAfee can cause errors, well we don't run MacAfee, we have
Symantec. For jokes sake I disabled that anyway, but still sccm fails to import the boot.wim, for any user, including the addmin user that was used to install SCCM. As well as from multiple network locations.
Any one have any idea. Any logs I can look at?

I've removed ALL drivers and all packages from SCCM, as well as task sequences pointing to driver packages. Still same issue.
I cannot add or remove drives from boot images. When attempting to add driver to a boot image. the dialog where I select the boot image is just blank and does not list any boot images that are in sccm console.
When attempting to update files on distribution points from the boot images that exist i get this error message.
Error: Boot image to update:
•   Microsoft Windows PE (x86)
Error: Actions to perform:
•   Add ConfigMgr binaries
•   Disable Windows PE command line support
Optional components:
•   Scripting (WinPE-Scripting)
•   Startup (WinPE-SecureStartup)
•   Network (WinPE-WDS-Tools)
•   Scripting (WinPE-WMI)
Error: The wizard detected the following problems when updating the boot image.
•   The SMS Provider reported an error.: ConfigMgr Error Object:
instance of SMS_ExtendedStatus
•   Description = "Failed to insert OSD binaries into the WIM file";
•   ErrorCode = 2152205056;
•   File = "e:\\qfe\\nts\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
•   Line = 4716;
•   ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
•   Operation = "ExecMethod";
•   ParameterInfo = "SMS_BootImagePackage.PackageID=\"SPS00004\"";
•   ProviderName = "WinMgmt";
•   StatusCode = 2147749889;
What else is there to try? I am running out of ideas.

Similar Messages

Thinkpad 10 SCCM 2012 R2 x64 WINPE OSD boot wim

Trying to inject drivers in to my CM12 x64 boot wim (ADK and MDT 2013 integration with CM12) for the new Thinkpad 10 Tablet. The x86 worked flawlessly and touch screen works on the x86 builds even my S1 Yoga. Errors galore with the x64 versions of the drivers from the SCCM pack. Being UEFI boot only both versions are needed and not all my locations will have the dock for using a keyboard so touch just needs to work.
Here is what successfully got added,the 2 display drivers and thats it. I started with all the drivers and worked in reverse by removing each driver after every error.
from SCCM:
Success: Drivers that will be included:
Realtek USB GBE Family Controller
Lenovo USB2.0 Ethernet Adapter
Intel(R) 5 Series 4 Port SATA AHCI Controller
Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller
Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller
Intel(R) C600 Series Chipset SATA AHCI Controller
Realtek USB GBE Family Controller
VMware Pointing Device
VMware USB Pointing Device
VMware PVSCSI Controller
VMware SVGA 3D
VMware VMCI Bus Device
vmxnet3 Ethernet Adapter
Intel(R) HD Graphics
ThinkPad Display 640x480
Realtek USB GBE Family Controller
Any help is appreciated and parkerj, as usual I am willing to be your huckleberry if needed. On a unrelated item any tips for removing the lenovo scup data from my wsus/scup environment? We had an issue and now i cannot publish the data. Whick makes me sad as I think the Lenovo SCUP catalog shows good progress. Primary issue is knowing what applies to what without publishing everything.

Hi,
UEFI BIOS Version: GWET23WW (1.23)
I have managed to implement drivers in a different way. I have created a package containing all drivers and placed it in a part of task sequence running inside installed operating system instead of running in WinPE. There is a script inside a package looking like this:
Start /w .\win\Chipset\setup.exe -s
Start /w pnputil -i -a .\WIN\TXEI\INF\TXEI.inf
Start /w setup.exe -SILENT
Start /w .\WIN\Audio\setup.exe /s
Start /w .\WIN\Bluetooth\setup.exe /s
Start /w .\WIN\Fingerprint\WBF_SPI_DDK_Extended_Setup.exe /s
Start /w .\WIN\GPS\setup.msi /qn
Start /w .\HOTKEY\setup.exe /S /B /H
pnputil -i -a .\WIN\MONITOR\TPLCD.INF
Start /w .\WIN\NFC\setup.exe /s
Start /w .\WIN\PMDriver\setup.exe -S -SMS
Start /w .\WIN\WLAN\setup.exe -s
reg import .\OSFIXES\ALSOR\ALSOR_Apply.reg
For anyone interested just make sure you follow correct paths to executables as presented in this script.
After running it I am left with Security Device unrecognized in Device Manager so I have to add another task sequence for Restart and than another one with a line with a package for Security Device and runing this as a command: pnputil -i -a TXEI.inf
Using regular pre-driver deploy task sequence commands in WinPE enviorenment unfortunately didn't helped so I have ended with workarounds presented here.
If anyone can add something to this I will be more than glad to hear.

SCCM 2012 R2 Won't PXE Boot

I'm trying to get PXE booting to work on our SCCM 2012 R2 server and am getting the dreaded "PXE-E53: No Boot file Name Received." DHCP server is in same subnet on a different machine, so supposedly no DHCP options or ip helpers are necessary. I'm
testing using a client VM with the legacy adapter for the NIC, and that machine PXE boots fine from our SCCM 2007 server.
When I test, I've been shutting down the SCCM 2007 server so that the 2012 machine is the only PXE server on our network.
In a nutshell, I'm trying to deploy Windows 8.1 using
this as a guide. The x86 and x64 boot images are enabled for PXE distribution and I've deployed the task sequence for the 8.1 OS image to all unknown computers. The DP shows content for the OS image and the boot images. PXE on the DP is enabled
and checkmarked to listen for PXE requests on all interfaces and for unknown computer support.
For troubleshooting I've tried unchecking all the PXE settinging in the DP, which removes WDS and then putting it back, as well as removing the MP role and putting it back (see attached snippet of SMSPXE.LOG).
I feel like I'm missing something basic here. Can anyone help?
Thanks!

Thanks, Jason. Yes, the MAC addrss is the client I'm trying to PXE boot.
I've reviewed the health in the monitoring section. No issues in System Status, and in Content Status there is only one error regarding the DP trying to contact an old SCCM 2007 distribution point at a branch office. This
appears to be a leftover from the migration process from SCCM 2007. This old distribution point is no longer in use and I can't seem to find any references to it on my SCCM 2012 R2 installation. Not sure if this is significant or not.
I've attached a snippet of the error:

SCCM 2012 sp1 - can't add boot image - Only finalized boot images are supported.

so when i updated to sp1 i had to install the new assessment and deployment kit which i have done.
when i try to add a boot image to sccm now i get the error:
You can not import this boot image. Only finalized boot images are supported. For more information press F1.
i have searched technet and on old versions of sccm you could re-install waik to fix this issue, i have tried re-installing ADK and its still doing the same.
has anyone had this problem on 2012 sp1?

Hi,
It works to import x86 image of windows 8 and now I have some problems when I try to import x64 boot image of 8.1.
Where I can see errors in logs. Are sow many log files and I'm little confuse and I cant find error to see what is the reason of this error.
And the error is:
Error: Data Source
Information
• Source location:
\\xxx\yyy\X17-24269\sources\boot.wim
• Boot Image:
1 - Microsoft
Windows PE (x64)
Error: Package
Information
• Name: boot
Error: Errors
• You can not
import this boot image.
Only finalized boot images are supported.
For more information press F1.

SCCM 2012 Non-MS License import issue.

Hi All,
I am trying to import non-ms licenses in SCCM 2012 but its not letting me to import. I amusing the attached sample csv. but every-time I am getting error that import failed.
Link for both CSV & Image as follows ... Changed Url as
http:// 1drv.ms/1g1LZaN

Hi, I am using the same sample CSV in same format, but no luck. EG Below.
Name
Publisher
Version
Language
EffectiveQuantity
Adobe Acrobat 4.0
Adobe
999999
Adobe Acrobat 5
Adobe
5
999999
Adobe Acrobat 7 Professional
Adobe
7.1
999999
Adobe Acrobat 7 Professional
Adobe
7
999999
Adobe Acrobat 8 Professional
Adobe
8
999999
Adobe Acrobat 8 Professional
Adobe
8.1
999999
Adobe Acrobat 9 Pro
Adobe
9.5
999999
Adobe Acrobat 9 Pro
Adobe
9
999999
Adobe Acrobat 9 Pro
Adobe
9.2
999999
Adobe Acrobat 9 Pro
Adobe
9.4
999999
Adobe Acrobat 9 Pro Extended 64-bit Add-On
Adobe
9
999999
Adobe Creative Suite 3 Master Collection
Adobe
1
999999
Adobe Creative Suite 4 Design Standard
Adobe
4
999999
Adobe Creative Suite 4 Master Collection
Adobe
4
999999
Adobe Creative Suite 5 Design Standard
Adobe
5
999999
Adobe Creative Suite 5 Master Collection
Adobe
5.5
999999
Adobe Creative Suite 5 Web Premium
Adobe
5
999999
Adobe Creative Suite 5.5 Design Standard
Adobe
5.5
999999

SCCM 2012 R2 PxE can't boot - your pc need to be repired.

Dear All,
These days, I upgraded SCCM 2012 to R2 , after that PxE can't boot , and shows a blue screen that your pc need to be repired, same issue like this:http://www.gerryhampsoncm.blogspot.ie/2013/02/sccm-2012-task-sequence-fails-with-bcd.html
And, i have also re-configed the pxe more times follow by this acticle , and still failed.
And, after I replace the \RemoteInstall\SMSTemp\2014.01.08.12.31.26.01.{xxxxxxxxx}.boot.bcd to \RemoteInstall\Tmp\x86x64{xxxxxxx}.bcd, and the PC can boot to the winpe well. that means the pc using Tmp folder's BCD store
to boot to WinPE, and not using SMSTemp's.
I check the PxE process:http://technet.microsoft.com/en-us/library/cc722358(v=ws.10).aspx
PXEBoot.com downloads Bootmgr.exe and the BCD store, and I think PXEBoot.com should download BCD store from SMSTemp folder, and should not be the Tmp folder.
So, my question is that why te PXEBoot.com download BCD from Tmp folder ? And how can I change it to download BCD from SMSTemp folder. ? I have been getting to crazy about this fucking problem.
Nemo

Reinstalling WDS and the PXE was not the answer, at least not for me, but I dunno about the original poster as he kept quiet.
For now I am trying to get SCCM2012 R2 running as this is the topic for my final projekt.
But I am stuck here, the problem is the same as the original poster mentioned.
Even thougt DHCP options are set to my CM and smsboot\x86\wdsnbp.com, pxe keeps loading boot\... and fails.
Making a copy from smsboot to boot and renaming the file fixes it in a dirty way.
The WDS-service has never been configured manually, after rolling back to a fresh Server and installing CU1 first nothing changed about that (PXE worked at all at least) und reinstalling the living dead out of the roles and features fixes nothing.
The remoteinstall folder gets populated everytime, with the SMS related stuff and the wds related stuff, I guess (boot, SMSboot, ...).
I tried various variations of the start path, TFTP still loads from boot instead smsboot.
The Images have been temporarily replaced with the one from our old site.
I renewed the whole site, this bugs me since 2012 R1 and R2 is the second site too.
I would really appreciate it if someone could help with an working solution.
Let me know if you need some more informations, site is described below.
In case this should get another Thread, let me know.
Thank you guys :)
Hyper-V Environment, Windows Server 2012 R2 Standard on all three Hosts (Gen 2),
Followed mainly the MS TLG for SCCM2012 for this, supported by windows-noob.
Have a nice day.
Little Edit right here: renaming the file only helps with the 89 error thing, but it doesn't help booting the sccm image.

SCCM 2012 - Hardware Inventory Registry Import not working - Windows in the name of the Registry key

I downloaded the Reg to MOF tool and compiled some of our custom Registry Keys which worked fine. There was particular Key that didn't work and after some testing and messing around I realized why it isn't working:
The key I am using is: HKLM\Software\MyCompanyWindows
Because the key has the name Windows in it, it fails to import. I get the generic check the formatting for your MOF file error.
The MOF file you tried to import could not be compiled. Ensure that the MOF file contains valid data. You can use the command line mofcomp utility to test the data.
But if I run a MOFCOMP against the MOF I am trying to import it checks the syntax successfully.
If I change the key to MyCompanyWin or MyCompanyW it imports with no problem.
We have rolled out this key to almost every device in our organization and connected it to other inventory agents so there is no possibility of changing the key.
Is there any way to disable the validation check that SCCM is performing?

Hi,
If possible, could you please upload the MOF file to SkyDrive?
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SCCM 2012 OS deployment fails post loading.WIM

I am trying to install an image on a laptop - I get the PXE boot and it downloads the NBP file and starts loading the files for the .wim - it does this (I suspect) and after about 30 minutes of doing that (loading files.....) it goes to a login screen but
it is not the new image, it is what came with it.
How do I troubleshoot this.
In the smspxe.log it shows that it is looking for the bootimage HQ200005 (which corresponds to my x64 boot image) then I get some Begin validation of certificate and completed validation of certificate and then that's all.

Also, it's always a good rule of thumb to make sure you've got all your content properly distributed, boundaries and boundary groups setup and good to, and a network access account created.

SCCM 2012 R2 CU3 - Driver Import Fails

Hi,
We're having an issue importing new drivers, we can import drivers for Windows 7 fine but receive the following error when it's for Windows 8/8.1, 'The selected driver is not applicable to any supported platforms.' We've imported drivers before so it could
be the recent upgrade to CU3. Anyone else on CU3 able to import Windows 8.1 drivers successfully. Installing the driver manually on the client works fine.
Thanks
Ben

Hi,
We're trying to add drivers so I'm not sure if this would matter. It seems very similar to
http://support2.microsoft.com/kb/961105,
http://support2.microsoft.com/kb/979492 and
http://support2.microsoft.com/kb/978754. The first one mentions the Manufacturer in the inf file. We found a similar post
http://www.windows-noob.com/forums/index.php?/topic/1590-error-when-importing-win-7-drivers-inf-files-solution/. If we modify the following line:
[Manufacturer]
%Intel% = Intel, NTamd64.6.3, NTamd64.6.3.1
and change it to the below it imports fine.
[Manufacturer]
%Intel% = Intel, NTamd64.6.3.1
I believe it's a bug and MS need to get their act together and fix it :-)
Ben

SCCM 2012 report/data for importing software metering rules..

Hi,
I have a customer who would like to start using software metering. The plan is to create the rules manually, since I guess it would be overkill and/or have an huge performance impact to enable it for all...? We might be talking about 100-300 applications.
To do it manually, a powershell script can be used for creating these based on a txt file containing the following information.
Productname, FileName, OrginalFileName, FileVersion
The customer has then asked for a report/csv file showing these information for all .exe files, so they can pick what they want to have metered. The data amount will for sure be huge and unmanageable.
Anyone has a good approach for this challenge? :-)
Thanks in advance.
Best regards
Thomas

The approach is to say NO, what they are asking for is huge in the range of 100,000 different exes, there is no way anyone will go the list. Instead, look at the build in report for count of installed software products and sort from largest count
to smallest. Then create SWM rules for those applications that have a cost and not everyone has. Aka why would you crate a SWM rule for WORD or EXCEL? But it does make sense to create a rule for Visio or AutoCAD.
Also why create a rule for two different version of Visio? Do you need it, why? Are you sure?
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

SCCM 2012 - Boot Import failed

Hi,
I am trying to import boot.wim in to my prod environment, since it was not created as part of primary server installation. I tried creating from ADK deployment tool.
I tried using the preproduction SCCM boot image and also tried with MDT boot image. But I get the below error for all the steps. Please help
Log:
　Error: Data Source Information
Source location:
\\XXXXXXXX\SMS_Boot\OSD\boot\x64\boot.wim
Boot Image: 1 - Lite Touch Windows PE (x64)
　Error: Package Information
Name: boot
　Error: Errors
You can not import this boot image. Only finalized boot images are supported. For more information press F1.
Regards, Pratap

I'm having this problem at the moment Pratap. I'm carrying out a migration from ConfigMgr 2007 for a large bank. McAfee is preventing all DISM related activities (items 1 & 2 above involve DISM). This is quite a common problem.
The customer is very security conscious and refused to let me disable the services until I produced the official McAfee recommendation. See it here - temporary solution - disable McAfee
https://kc.mcafee.com/corporate/index?page=content&id=KB76867&actp=LIST
Note that you don't have to abandon the product altogether. Just be aware that you have to temporarily disable it when carrying out activities like these.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

How to resolve BADMIFS file in SCCM 2012

Hi,
I am trying to resolve Hardware inventory issue on the machines which is not reported more than 10 days in SCCM 2012.
I found there are BADMIFS files created in the below location.
How to resolve the issue on the machines which is under below each BADMIFS folders. Do we have any troubleshooting steps for each folder?

For troubleshooting hardware inventory import, you can check below link
https://sccmfaq.wordpress.com/2013/10/16/sccm-2012-troubleshot-hardware-inventory-import/
For Resolve-cleanup BadMIFs, you check below script
https://gallery.technet.microsoft.com/scriptcenter/SCCM-2012-bad-hardware-0bec0ee0
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"Mai Ali | My blog:
Technical | Twitter:
Mai Ali

SCCM 2012 R2 Boot WIM DISM - Drivers Failing -hr:0xc0000135‏

Hello OSD Experts,
I have upgraded my SCCM 2012 RTM to SP1(Not installed any Cumulative updates) then to SCCM 2012 R2 Successfully... I did not get any errors.
Before Upgrade my SCCM 2012 RTM/SP1 Images are removed from DP Targets.
Now my next high priority task is I wanted to integrate my Hardware models NIC & Mass Storage Drivers to my Boot Images, So that my OSD will work without any issues. But am getting errors, when I try
to add by DISM command to the Boot Images.
I have taken Default boot.wim file from SCCM 2012 R2 and copy pasted to my work location and ran the DISM command... however I am not successful in this for integration.
Has anyone have already have solution for this let me know.
<<<AV is in Disabled state during DISM.. Still no Luck>>>
<<<<<I tried to ran the DISM on Windows 8 & Windows 2008 R2>>>>>
Attached my DISM.Log @OneDrive... http://1drv.ms/1gdUi6w
Failed to create Dism Image Session in host. - CDISMManager::LoadImageSession(hr:0xc0000135)
DISM Manager: PID=3200 A problem ocurred loading the image session. Retrying... - CDISMManager::CreateImageSession(hr:0xc0000135)
DISM.EXE: Unable to start the servicing process for the image at 'E:\Boot_WIM\SCCMR2_WIMS\X86\Temp'. HRESULT=C0000135
<<< I have already checked this link but no luck... http://social.technet.microsoft.com/Forums/en-US/6b9facc4-9174-4ae7-a8a0-98d88d7f8a95/dism-error-0xc0000135-when-attemptign-to-add-drivers-to-mounted-2012-image?forum=mdt
>>>
Thank you In Advance,
HunBoy Started learning from this page

Hi,
You could use SCCM console to add these drivers. From the SCCM console, go to Operating Systems -> Drivers. Right click and select Import Drivers and follow the wizard. Or go to Operating Systems -> Boot Images -> Right click the boot image in question
-> select Properties. Select the Drivers tab and click on the add button on the right and then select the NIC drivers.
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SCCM 2012: PXE deploy: import boot images?

Hi,
We fully configured sccm 2012 and did osd via bootable media. Now we want to configure PXE.
We enabled it (http://prajwaldesai.com/deploying-sccm-2012-part-14-build-and-capture-windows-7-64-bit/).
My questions:
*Is that all that needs to be done?
*It seems to me we need to import boot images in WDS?
*If we do, which to import then (both x86 and x64 probably) + there is a winpe and a winpe.....wim made by sccm, which one to import then?
*on DHCP we change the boot server hostname but what about the bootfile name, what is the path of that? \boot\x64\wdsnbp.com?
Please advise.
J.
Jan Hoedt

I keep on getting TFTP open timeout
I find in smspxe.log that it reaches to the SCCM-server but then something goes wrong. Not sure what.
How can I troubleshoot find more info, please advise?
00:51:55:2A:5C:C5, 0A190A42-FFDe6-5e69-9e41-70e481B852E3: device is not in the database.   SMSPXE   21/03/2014 16:10:08   2720 (0x0AA0)
Getting boot action for unknown machine: item key: 2046820352   SMSPXE   21/03/2014 16:10:08   2720 (0x0AA0)
CLibSMSMessageWinHttpTransport::Send: URL: oursccmserver.prod.ourcompany.be:80 GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX   SMSPXE   21/03/2014 16:10:08   2720 (0x0AA0)
CLibSMSMessageWinHttpTransport::Send: URL: oursccmserver.prod.ourcompany.be:80 CCM_POST /ccm_system/request   SMSPXE   21/03/2014 16:10:08   2720 (0x0AA0)
Jan Hoedt
Note: what I also can see:
Client IP Address: 000.000.000.000
Your IP Address: 000.000.000.000
Server IP Address: 000.000.000.000
Relay Agent IP Address: 000.000.000.000

SCCM 2012 R2 Boot Image won't load in Windows XP

I'm using ADK 8.1, MDT 2013, x86 Boot image w/ PE 5. Deployed a TS to Windows XP SP3 computer with a single task: Reboot Computer to PE
Getting this: Executing command line: "C:_SMSTaskSequence\WinPE\SMS\bin\i386\bootsect.exe" /NT60 SYS /MBR TSManager 10/31/2013 9:49:27 AM 3000 (0x0BB8)
Failed to install boot image. is not a valid Win32 application. (Error: 800700C1; Source: Windows)
More detailed smsts.log below:
<![LOG[Captured settings for adapter 1]LOG]!><time="09:33:52.197+420" date="10-31-2013" component="OSDNetSettings" context="" type="1" thread="5368" file="netsettings.cpp:99">
<![LOG[OSDNetSettings finished: 0x00000000]LOG]!><time="09:33:52.197+420" date="10-31-2013" component="OSDNetSettings" context="" type="1" thread="5368" file="main.cpp:192">
<![LOG[Process completed with exit code 0]LOG]!><time="09:33:52.307+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="commandline.cpp:1123">
<![LOG[Installing boot image to hard drive]LOG]!><time="09:33:52.353+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="bootimage.cpp:621">
<![LOG[Backing up existing boot system before trying to set up new boot system]LOG]!><time="09:33:52.353+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856"
file="bootimage.cpp:644">
<![LOG[BootLoader::backup: C:\, C:\_SMSTaskSequence\backup]LOG]!><time="09:33:53.213+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="bootloader.cpp:85">
<![LOG[BootLoader::restore: C:\_SMSTaskSequence\WinPE, C:\]LOG]!><time="09:33:54.479+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="bootloader.cpp:382">
<![LOG[Saving bcd store to C:\_SMSTaskSequence\WinPE\boot\BCD]LOG]!><time="09:33:57.057+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="bootconfigimplbcd.cpp:703">
<![LOG[Executing command line: "C:\_SMSTaskSequence\WinPE\SMS\bin\i386\bootsect.exe" /NT60 SYS /MBR]LOG]!><time="09:33:57.166+420" date="10-31-2013" component="TSManager" context="" type="1"
thread="4856" file="commandline.cpp:827">
<![LOG[CreateProcess failed. Code(0x800700C1)]LOG]!><time="09:33:57.182+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="commandline.cpp:1018">
<![LOG[Command line execution failed (800700C1)]LOG]!><time="09:33:57.182+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="commandline.cpp:1245">
<![LOG[Failed to install boot image.
is not a valid Win32 application. (Error: 800700C1; Source: Windows)]LOG]!><time="09:33:57.182+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="bootimage.cpp:681">
<![LOG[Failed to install boot image UCI00073.
is not a valid Win32 application. (Error: 800700C1; Source: Windows)]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="engine.cxx:840">
<![LOG[Failed to reboot the system. Error 0x(800700c1)]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="engine.cxx:953">
<![LOG[Failed to initialize a system reboot.
is not a valid Win32 application. (Error: 800700C1; Source: Windows)]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="engine.cxx:577">
<![LOG[Fatal error is returned in check for reboot request of the action (Restart in Windows PE).
is not a valid Win32 application. (Error: 800700C1; Source: Windows)]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="engine.cxx:273">
<![LOG[An error (0x800700c1) is encountered in execution of the task sequence]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="engine.cxx:348">
<![LOG[Set authenticator in transport]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="0" thread="4856" file="libsmsmessaging.cpp:7734">
<![LOG[Task Sequence Engine failed! Code: 800700C1]LOG]!><time="09:34:45.920+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="tsmanager.cpp:919">
<![LOG[****************************************************************************]LOG]!><time="09:34:45.920+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856"
file="tsmanager.cpp:953">
<![LOG[Task sequence execution failed with error code 800700C1]LOG]!><time="09:34:45.920+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="tsmanager.cpp:954">
<![LOG[Cleaning Up.]LOG]!><time="09:34:45.920+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="tsmanager.cpp:675">
<![LOG[Removing Authenticator]LOG]!><time="09:34:45.920+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="tsmanager.cpp:686">

See the "Workaround" section of this post for an example of downgrading bootsect.exe:
http://social.technet.microsoft.com/Forums/en-US/6e934990-999a-4367-860a-3ce4e5eda956/sccm-2012-r2-error-0x800700c1?forum=configmanagerosd
It is not the version of WinPE that is the problem here, but the version of bootsect.exe that gets injected into the boot media.
Nash Pherson, Senior Systems Consultant
Now Micro -
My Blog Posts
<-- If this post was helpful, please click "Vote as Helpful".
This workaround worked in my environment. Fixed my in-place upgrades from XP to Windows 7, and as a bonus, fixed imaging XP as well. yeah, I have to keep XP for awhile. :-(

SCCM 2012 R2 Won't import boot.wim

Similar Messages

Maybe you are looking for