Skip to main content

CAPI2 (Windows) Error Event

Thread needs solution

Windows 10 Pro x64, 16 GB RAM, 1 SSD (OS), 2 1TB HDs

First of all, I'd like to point out that I have no issues, as I've made backups and restored the system several times without a problem, but I tend to check and keep my Event Viewer clean and every time I go for an incremental backup, I get these two Windows Error Events:

CAPI2 513

CAPI2 513

Details: AddLegacyDriverFiles: Unable to back up image of binary Microsoft Link-Layer Discovery Protocol. System Error: Access denied.

There's another thread on this CAPI2 event but it's quite old and I couldn't find anything interesting information. Since I have an SSD, I disabled Windows System Protection (System Settings > System Protection > Protection Settings > Configure... > "Disable protection...")

I was wondering if that might cause the error event, or if you could shed some light on the matter.

Thanks for your work.

0 Users found this helpful

Doing a search on Google for the CAPI2 513 error gave the following hit from the Macrium Knowledgebase with the same details as you have reported.

http://knowledgebase.macrium.com/display/KNOW/Event+513+errors+in+Windows+8.1  this is described as being caused by the Windows Shadow Copy System Writer. If the permissions of the COM catalog folder are incorrect, this writer may not work properly.

Sorry to resurrect an old thread, but I wanted to add a bit to this.

I had recently changed my Files and Folders backups to use the Acronis Snapshot instead of VSS. The reason was that I was getting a new Generic Volume Shadow Copy (as seen in Device Manager) for every backup that was run. It appearead as though this would continue on until the storage space allocated for shadow copies was filled. Each entry was more stuff added in the registry. I do not know if there is an Acronis bug or not, but it seems as thought the shadow copies should not survive beyond the backup job.

After the change, I started getting the CAPI2 513 errors. My backup scheme that backed up from one drive only had one error. The scheme that backed up from two drives had two errors.

I researched the fix that Steve mentions to determine what to do and why. On my system, the fix is a bit different. It's not difficult, but now the CAPI2 errors appear to be gone. Time will tell.

Bruno, thank you for sharing your experience with snapshot methods. If you would like to help us investigating and fixing the issue with VSS snapshot, you can reproduce the problem, and use "Send feedback" feature to submit the system report with diagnostic information to us.

Regards,

Slava

Slava, I recently submitted a report on the problem of the VSS shadow copies accumulating on my system (case 02963294). I'm trying to avoid doing further testing on that since the only way I've found to get rid of those shadow copies involves losing all my restore points. I'll see what happens with this case, but also wait until Update 3 before trying it again.

Hello Bruno,

Thank you for opening a support case. There were similar issues in the past which we did not have an opportunity to fix as they occurred in specific user environments. Hopefully now we will get to the root cause of the problem with persisting shadow copies.

Regards,

Slava

BrunoC,

I did some digging and found that the CAPI2 513 error is related to Network Permissions strangely enough.  Looks to be a Windows upgrade problem where permissions do not carry over correctly for some reason.  Below is a link to a Mocrsoft article on the problem and a fix.  Be careful with the fix as apparently there can be differences between OS installs but the procedure to fix the issue does work including Windows 10 installs.  Hope this helps!

https://answers.microsoft.com/en-us/windows/forum/windows8_1-hardware/c…

Enchantech, I did get my fix from this link you have (or maybe another link with the same response). Before just willy-nilly changing anything, I analyzed the fix by looking at the SDDL language and closely analyzing it on my system. Mine is a bit different from what is posted, but just adding in the one part to my existing config did the trick.

Nice!  Glad that worked for you. 

For others whom may attempt this, make sure that you follow the instructions in the linked solution to the letter to properly apply the fix.  Not doing so coule create other problems some of which my not be recoverable.

Enchantech, thank you for doing the research and sharing the solution with others! It seems to be quite popular - there are 242 upvotes. Actually I recall using instructions from that Microsoft forums page one or two times.

Regards,

Slava