1-800-691-1991 | 9am - 8pm ET

Backups writing to C:\Windows\SysWOW64


In some cases, backup repositories automatically created by setup during upgraded from v5 may start writing data into C:\Windows\SysWOW64 if backup files used to reside in the root folder of the volume.


Root cause is still unknown but this KB will assist you in getting your jobs writing to the correct repository.  A patch will be released at a later date.


1) The repository for the backup job(s) will need to be deleted however you cannot delete the repository with jobs linked to it so what you can do is create another repository pointing to the same location.

2) Move the Veeam files (VBK, VRB, VIB, VBM) from the SysWow64 folder back into their original locations with the rest of the backup files for your jobs.

3) As long as you have a VBM file for each set of backups you can then simply go into Backup Repositories (under Backup Infrastructure) and re-scan the repositorie(s) that you just created.  Veeam should then see that the backup files reside in that directory.

4) Go into your Backup jobs and point back to the newly created repository and click the Map Backups link.  Your jobs should pick up where they left off and you shouldn't have this issue again.

5) Delete the original repository which should now have no jobs linked to it.

More information

If you have any issues with any of the above steps please log into and create a support ticket.
Veeam Backup & Replication
Last Modified:
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.


error icon

Oops! Something went wrong.

Please go back try again later.