I'd like to see if anyone has encontered the above error code. I'm attempting to create a USB Task Sequence Media. I made a single change to my task sequence where I'm adding an installpackage of 120MB. The error occurs immediately after the writing stage. The log indicates a space remaining of 52MB. What is strange to me is that if I disable the step I'm trying to add and successfully build the media, the USB drive (4GB) has approximately 988MB free. Below is the trailing content of the log file where the error occurs. -------------------------------------------CreateTsMedia4/28/2009 11:44:41 AM436 (0x01B4)Staging package GPS000DFCreateTsMedia4/28/2009 11:44:41 AM436 (0x01B4)Before executing state - fsVolumeSpaceRemaining= 130 MbCreateTsMedia4/28/2009 11:44:41 AM436 (0x01B4)Staging package GPS000DFCreateTsMedia4/28/2009 11:44:41 AM436 (0x01B4)After executing state - fsVolumeSpaceRemaining= 52 MbCreateTsMedia4/28/2009 11:44:41 AM436 (0x01B4)-------------------------------------------CreateTsMedia4/28/2009 11:44:41 AM436 (0x01B4)Writing volume 1CreateTsMedia4/28/2009 11:44:41 AM436 (0x01B4)Skipping writing to X:\ for calculate passCreateTsMedia4/28/2009 11:44:41 AM436 (0x01B4)Setting up new volumeCreateTsMedia4/28/2009 11:44:45 AM436 (0x01B4)WriteVolumeId()CreateTsMedia4/28/2009 11:44:45 AM436 (0x01B4)-------------------------------------------CreateTsMedia4/28/2009 11:44:51 AM436 (0x01B4)Staging package GPS000B8CreateTsMedia4/28/2009 11:44:51 AM436 (0x01B4)Before executing state - fsVolumeSpaceRemaining= 3622 MbCreateTsMedia4/28/2009 11:44:51 AM436 (0x01B4)Staging package GPS000B8CreateTsMedia4/28/2009 11:44:51 AM436 (0x01B4)After executing state - fsVolumeSpaceRemaining= 3541 MbCreateTsMedia4/28/2009 11:44:51 AM436 (0x01B4)-------------------------------------------CreateTsMedia4/28/2009 11:44:51 AM436 (0x01B4)Could not find extension in input path "X:\"CreateTsMedia4/28/2009 11:44:51 AM436 (0x01B4)Failed to create media (0x80070057)CreateTsMedia4/28/2009 11:44:51 AM436 (0x01B4)CreateTsMedia failed with error 0x80070057, details=""CreateTsMedia4/28/2009 11:44:51 AM436 (0x01B4)MediaGenerator::~MediaGenerator()CreateTsMedia4/28/2009 11:44:51 AM436 (0x01B4)

I have the same problems with R2 sp1Beginning media generation Failed to create media (0x80070057) CreateTsMedia failed with error 0x80070057, details="" MediaGenerator::~MediaGenerator()

if you try a different usb key, say 16gb does it still fail ? are you creating it on the same server as sccm or using a sccm admin console on windows 7 or similar ? My step by step SCCM Guides Follow me on Twitter

Yes, just tried 3 sticks.I am running the configmgr from a windows 7 enterprise client.When i try to make a bootalbe media (just that optie when de manager puts only the pe env. on the usb) is also fails. Size doesn't matter, i think

I got this error code (0X80070057) when trying to build a D630 dell laptop from SCCM. The issue I had was bad sectors on the destination drive. Gdisk reported a bad FAT table.

I had AVIRA V10 Guard activated and tried to make a bootable standalone media usbstick with Windows 7 64-Bit on a Windows 7 Computer. It failed also!=> I had deactivated the Guard and the USBStick could have been created! :-) The Guard had blocked the autorun or sth. else!If it's not your solution look at the logfile in the admingui Directory from SCCM KonsoleI hope it works! Bye HerbertHerbert Peil SCCM 2007 R2 with SP2 One Prim. Site 2008 Server SP2 64BIT 1100 Clients XP / Windows 7 SQL 2005 64BIT

I had the same problem and same error after researching this issue Windows 7 has a 100mb or 200mb unasigned drive for OS recovery this is where the problem lies. Go into Disk Management and assign that disk a drive letter like B:\ if there and then try the process again. It has worked for me now several times with different brands and sizes usb drives.

You must first use Diskpart on the USB stick http://technet.microsoft.com/en-us/library/cc766465%28WS.10%29.aspx

I doubt you care about this answer now Redkin, but for those that follow on after doing a search and finding this thread, do yourselves a favor and unmount any mounted drives you have attached to your system. That fixed it for me. net use * /delete /y If you need to remap them after this, create another batch script like I did, or log off and back on letting your login process remap them. Anything worth doing is worth doing right.

I doubt you care about this answer now Redkin, but for those that follow on after doing a search and finding this thread, do yourselves a favor and unmount any mounted drives you have attached to your system. That fixed it for me. net use * /delete /y If you need to remap them after this, create another batch script like I did, or log off and back on letting your login process remap them. Anything worth doing is worth doing right. did everything as mentionned, this last one only worked=) thanks for you answer! (how did you found that by the way?!)

I had the same problem and found this thread but not the answer. I then kept on digging and found a KB article by MSFT detailing the problem and the solution. I tried it because the resolution is simple enough and was happy that it worked. Now, I can't find the original KB, or I would definitely put a link in here about it and point all of you to it. You have to agree, its kind of off the wall and you wouldn't ever think to test this out without knowing first to try.Anything worth doing is worth doing right.

The reason seems to be because the Create Task Sequence wizard has to mount the image using imagex, and it gets confused as to what drive letter to choose when there's existing network drives. So it only works when no network drives exist. Can a mod mark TowedJumper's answer as correct?

Perfect! Dumb issue, Simple solution! I have seen this solution before when having issues in the past. This did not correct my issue when running the console form a Windows 7 box. I actually ran this from the server for speed sake and thought i was going ot have to revert to an XP machine again. Nope! Processing like a champ as we speak. Nice find. -ce