Has anyone received this error when trying to capture an image "Capture failed: cannot capture/append image cannot create a file when that file already exists"?

i have been able to capture multiple images before with no issues.  i am not sure if it's an issue with my image or the SDA.  there is an article about this on the Quest site, but it keeps telling me that i need permissions to see the article even though i am logged in with our companies quest account and we have an active license.

quest article: https://support.quest.com/kb/4294531/error-during-replication-job-cannot-create-a-file-when-that-file-already-exists  

update: 11/09/22 3:03PM. 

i was able to access the logs file from the SDA\petemp folder.  i am still not entirely sure why this error is coming up.  There is no file with the same name in the "SDA\petemp\captures" or in the "SDA\peinst" directory the where the SDA is putting the .wim file.    

2022-11-09 16:07:13-0800 [info] Klonewin - Start [Build: Sep 21 2021 15:38:27]

2022-11-09 16:07:13-0800 [info] ...Capture: True

2022-11-09 16:07:13-0800 [info] ...Deploy: False

2022-11-09 16:07:13-0800 [info] ...Direct to/from server: True

2022-11-09 16:07:13-0800 [info] ...ImageName: 1025

2022-11-09 16:07:13-0800 [info] ...ImageType: wim

2022-11-09 16:07:13-0800 [info] ...LocalDir: C:\

2022-11-09 16:07:13-0800 [info] ...TempDir:

2022-11-09 16:07:13-0800 [info] Capturing directly to server: tempDir=T:\captures\1025

2022-11-09 16:07:13-0800 [info] Capture Image - Start

2022-11-09 16:07:13-0800 [info] ...Original Capture Location: [C:\]

2022-11-09 16:07:13-0800 [info] ...Drive Size=487756, Space Needed=66872, Available=420884

2022-11-09 16:07:13-0800 [info] ...Creating temp dir: T:\captures\1025

2022-11-09 16:07:13-0800 [info] ...Capture Directory: C:\

2022-11-09 16:07:13-0800 [info] ...Image File: T:\captures\1025\C.wim

2022-11-09 16:07:13-0800 [info] ...Temp Directory: T:\captures\1025

2022-11-09 16:07:13-0800 [info] ...Compression Type: 1

2022-11-09 16:07:13-0800 [info] ...Verification: 0

2022-11-09 16:07:13-0800 [info] ...Capturing...

2022-11-09 16:09:09-0800 [info] Number of files applied/captured: 0

2022-11-09 16:26:35-0800 [error] Capture Image Error: C [err = 59]

2022-11-09 16:28:29-0800 [error] ...Cannot capture/append image: Cannot create a file when that file already exists.


2022-11-09 16:28:31-0800 [info] Klonewin - Done, exit code: -1

update: 11/06/2022 at 5:10pm

i reached out to Quest and they provided the article i had mentioned, but it has to do with "Recovery Manager for AD Forest Edition".  i'll provide an update if i find a solution. 

0 Comments   [ + ] Show comments

Answers (3)

Posted by: josed558 11 months ago
Senior White Belt

Sorry, just to update.  We upgrade our SDA version and then i was able to upload the image.    

Posted by: josed558 1 month ago
Senior White Belt

I think Ifigured out what was going on.   I am not 100%, but so far the issueseems to have disappeared when i follow the procedure below. 


We have multipleimages, Bulk, Loaner, and Developer images that i create using the samemachine.   Normally when i would get this error I would just drop mygold image back on the machine and try again.  That process would a take along time and sometimes i would get the same error.  


So now, when I go to drop mygold image back on the machine i open up a command prompt from the recoverymenu in the KBE environment, run DISKPART, select the disk (normally disk 0),and run the clean command on the disk.  this seems to have resolved the"Cannot capture/append image: Cannot create a file when thatfile already exists." issue for me. 


Maybe aftercreating an image, sysprepping, and uploading it to the SDA if Kace createsanother hidden partitions on the machine's local drive and temporarily storesthe Wim file before uploading it to the SDA?  I could not find anything onthe SDA settings or in the  \\SDA\peinstor petemp directories with the name of the image that I was uploading.     

Posted by: grvenega 1 year ago
Yellow Belt

Hello josed558, about this issue.


What version is your SDA running? / 9.0.146 recommended.

Are you capturing the image from a virtual machine? / This is a best practice.

Are you using kace tool to sysprep before attempting to capture the image? / these instructions will help if followed carefully https://support.quest.com/kace-systems-deployment-appliance/kb/4232511/how-to-system-image-sysprep-capture-and-deploy

Is this a clean image, or did you run Windows update on it? / it is recommended to avoid upgrading the Windows image, instead, deploy the latest Windows build you need, customize the image and capture it.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ