Standalone Windows 7 Deploy Error 0x330021

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 5
Comments: 14

SnapDeploy4:
Standalone Utility booted via USB thumb drive or CD:

I can image a Dell Latitude E5510 laptop with Windows XP and I can image with Windows 7.
Problems arise when I attempt to put Windows XP over Windows 7 on the same machine.

So, XP to 7 works fine, but going from 7 back to XP does not.

Tried multiple images and multiple E5510's and each results in the same error.

Sometimes I can re-image XP and immediately use that to deploy to overwrite Windows 7 but then after a use, that XP image will not work either. I have three XP images that work fine UNLESS I attempt to deploy them over Windows 7.

Attachment Size
imag0251.jpg 1.11 MB
Thu, 07/21/2011 - 16:45
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 5
Comments: 14

Follow up:
I completely wiped the disk clean before re-trying to deploy and still no luck. I think the key is in the new photo attached... The main partition is identified as having 0 bytes free. This is unique to these Windows XP images that have been previously deployed to overwrite Windows 7. For some reason, I can use the image once, and thereafter it reports back a 0 byte free status on the main "C" drive. These are 500GB SATA drives.

Attachment Size
71199-96556.jpg 940.8 KB
Thu, 07/21/2011 - 17:28
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 88
Comments: 4769

Hello Eric,

Thank you for posting. I will do my best to help you.

I would recommend to contact our Support team so that we can investigate and resolve this issue.

If possible, please collect Acronis Report 51 from source and target machines.

Please let me know if you have additional questions.

Thank you.

Fri, 07/22/2011 - 09:38
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 5
Comments: 14

Hi Bart,
I cannot remember to be honest! I believe this error was due to the SATA mode differing. In BIOS, change to AHCI mode and retry. Not totally sure, but I think that was it. I do need to re-invest in some "Acronis time" because I need a network solution and right now, I am running machine to machine using freeware to image machines. (I honestly gave up on Acronis due to this error and not enough time to research). Not very efficient... I would be interested to know if you get past this error though. I may recontact Acronis to get another trail, if possible, now that I have more time. I do believe the Acronis solution is the right one, but it seemed a bit too complicated for us at the time.

Tue, 12/11/2012 - 15:30
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 0
Comments: 1

I just encountered the same also...

i have setup a Acronis Snap Deploy 4 Server, create a master image on Lenovo E430 and successfully created the image.

Now i saved in Acronis Snap Deploy and Enabled PXE...
i also create a bootable media to deploy the Image and Create the image.

Both PXE booting and Snap Deploy "Stand Alone " are not successfully loading the Image...

In the PXE booting.. yes the machine was able to detect the server and even start the deployment process.. it just start in a very quick and after again it restart the machine all over again.

In deploying Stand alone Image.. upon booting thru shared network and external HDD where is image is saved snap deploy are unable to load the image successfully. and showing "Error 0x330021"

although it does pertains to SATA configuration... i tried both Compatibility and AHCI but still this error is occurring all over again and unable to load the image successfully.

i also tried to re image the laptop for how many times thinking that there is something wrong on the image and its one of the suggestion on the error code... that may be the image is not successfully image.

Still Snap Deploy 3 is working fine... kindly highlight this issue... Snap deploy 3 also can image Windows 8.1 as i have tried...

but hope that snap deploy 4 is much more better and perfectly designed for windows 8 as well.. although the same hiccups encountered on snap deploy 3 when taking image and loading image but "You just need to set the SATA Config on BIOS to compatibility" and after successfully loading the image "Change it to AHCI" to load the Image success fully...

Additional info just want to share....

when taking and image in Windows XP and Windows 7 - Set the SATA Configuration on BIOS using Compatibility - so that it will detect the HDD

And when successfully loading the image using Windows 7 - Change the SATA Configuration on BIOS using "AHCI"
Note that if you forgot to change this and still compatibility is set "The Machine will always boots up in Blue Screen"

Thanks,
Andro Ruan

Sun, 01/19/2014 - 09:40