True Image hangs up at 300 mb

Hi, I have the same or possibly similar problem when running a backup in Acronis True Image (ATI) 2016. I have not renamed any of my backup files.

I am running Windows 10 Pro 64-bit.

When I try and run a backup, scheduled or manual, the backup starts, then hangs at anywhere between 20 MB and 250 MB. The backup refuses to stop without a system restart, or terminating TrueImageHomeService.exe.

Looking through Event Viewer, I see errors from CAPI2, event ID 513, that read:

Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.

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

System Error:
Access is denied.
.

The timestamps of these events correlate with times that I am attempting to run a backup in ATI 2016.

I found if I go into Task Manager and terminate the vss_requestor.exe process, the backup will resume immediately.

Of course, this is not an optimal fix and I have not verified if the backup validates correctly afterward, but if anyone has any other suggestions I would appreciate it.

Hi All,

I had the problem. The solution is to force Windows 10 to run Error Check / Disk Check. Windows 10 reports no errors, but force it to run. Once ran, Acronis completes without problems. You may need to Schedule to run the File System Error Checking. And reboot to run it.

Hello theCreator,

Your suggestion to run disk check is a good one.  I do that about once a week.

Is your suggestion to run against the "Source" drive or the "Destination" drive ?

I assume you mean to run the "Chkdsk with a /f option ?

Steve

Hi Steve,

Both if necessary, but usually the Source Drive only.

For me, using Windows 10,  open File Explorer. Click on This PC. Right click on the Source Drive, usually C:/. Click on Properties. Now click on the Tools Tab. Click on Check. Click on Scan drive. It scans the drive within the operating system. If no problems are found, no choice is given to Schedule to fix the problems. No Reboot is necessary. The Results of the scan is viewed in the Event Log / Application, if you clicked on Show Details.

Thanks for the reply, thecreator.

Unfortunately, running chkdsk did not resolve the issue for me.

I also tried fixing the CAPI2 error I was receiving by granting NT AUTHORITY\SERVICE read access to MSLLDP. While this eliminated the CAPI2 errors in event log when running ATI 2016, it did not fix the vss_requestor.exe hang during backup.

If I end the vss_requestor.exe process during a backup, the backup continues as normal, and verifies properly. Looks to me the issue is vss_requester.exe hanging up on something.

Hi Titan_X,

Try running sfc /scannow (corrected - Thanks) from the CMD window with Administrator Rights. Right-click Start and you will see both CMD choices.

No space after the / (sfc /scannow).

I've already done sfc /scannow. Found no integrity violations.

Titan,

Try disabling Windows VSS service and then run your backup and see if that helps.

Enchantech, I did that and it helped; backup ran and verified successfully. It's a workaround at the moment, but I do depend on System Restore so I don't want to leave Volume Shadow Copy service disabled.

As I stated, the problem definitely appears to be related to VSS. Whether this is a problem that Acronis can patch or if it's a problem with my Windows 10 Pro install at this point, I'm not sure - but the fact that I ran a system file check with no integrity violations leaves me inclined to the former.

Titan,

I understand completely.  As info, I have read that Windows 10 no longer relies on the VSS service for system restore purposes.  From what I read the VSS service was left in Windows 10 for applications that still use its features.  True Image uses snapman which is a snapshot manager to create backups but uses VSS to a degree and I think it only uses it as a way to register the writer to the system.

At any rate you might do some looking into this or experimentation with Windows system restore with VSS disabled and see what your results are.

Enchantech, I went into System Protection settings to look at System Restore, and I get alerted that the Volume Shadow Copy service is malfunctioning if I have the service disabled.

Mmm, that's interesting.  I'll need to see if I can locate the article I read about this and give it another read.  Possibly I missed something there.

What was your VSS service set at for startup, auto, or manual?  The default setting should have been auto.  You can try setting it to manual and then see if both Windows System Restore and True Image will work  successfully.   Just by the sounds of your issue here I suspect you're experiencing a conflict in VSS writers.  This could be a situation where another application or Windows itself is using the VSS service when TI attempts to use it and this results in a failure.

Titan_X wrote:

Enchantech, I did that and it helped; backup ran and verified successfully. It's a workaround at the moment, but I do depend on System Restore so I don't want to leave Volume Shadow Copy service disabled.

As I stated, the problem definitely appears to be related to VSS. Whether this is a problem that Acronis can patch or if it's a problem with my Windows 10 Pro install at this point, I'm not sure - but the fact that I ran a system file check with no integrity violations leaves me inclined to the former.

Hi Titan_X,

Don't disable , but leave Volume Shadow Copy on Manual. If you have an error with that, make sure that Remote Procedure Call (RPC) is functioning and not disabled. Volume Shadow Copy depends on Remote Procedure Call (RPC).

Thanks again for the reply, Enchantech. I appreciate the extra thought process, and hope we can tackle this issue.

Volume Shadow Copy service is set to Manual start by default. I tried running a backup in ATI 2016, and once the backup started, VSS service started, presumably called by the vss_requestor.exe process. The backup still stopped at 22.6MB processed.

Stopping the service did not allow the backup to continue, but terminating the vss_requestor.exe process did.

I did manually create a system restore snapshot successfully, so I know VSS is working correctly.

It sounds like either ATI 2016 isn't able to work with VSS in Windows 10 like there's some disconnect between the vss_requestor.exe process and VSS. The only other thing I can think of is another piece of software may be preventing vss_requestor.exe from working with VSS.

Thanks, thecreator. I appreciate the assistance.

I've verified RPC is running and startup is set to automatic.

VSS startup is set to Manual. It starts automatically as soon as I kick off a backup in ATI 2016.

Hi Titan_X,

With Acronis True Image being used,  I have System Restore turned off. Just faster doing Full Backup, and restoring those Backups. If you have System Restore on, each Restore Point has Files and the Image Backups will be that much larger. And sometimes when having McAfee installed, System Restores, usually fails.

Are you running just with Windows Defender or another Anti-Virus program?

 thecreator, I am using Kaspersky Internet Security 2016. I've tried a backup in ATI 2016 with KIS disabled and I still run into the same issue.

From an administrator command prompt run the following,  vssadmin list writers.   This will list all service writers, their current state, and last error.  Any having a last error showing have failed.  Report back your findings.

It looks to be stuck on "Waiting for responses. These may be delayed if a shadow copy is being prepared." I have nothing running a shadow copy that I'm aware of.

I've tried re-registering the DLLs related to VSS per this article: http://blogs.technet.com/b/sdoakes/archive/2006/02/03/418722.aspx

No dice.

I'm leaving vssadmin list writers running. Will reply if I get anything.

Hi Titan_X,

Suggestion: If you have a good Backup Image Copy, reformat and reinstall Windows 10 on the same partition. Use Build 10240. Also, I have the operating system on a separate partition from the Documents and Emails, so it is very easy for me to recommend this, cause I don't lose any information. And great for Beta Testing.

With that said, after Windows 10 is reinstalled, install Acronis True Image 2016 and see if you have any problems. Then add in your Anti-Virus and see what happens. Then keep adding programs and see what happens. Don't forget to add Comments to the Images, so you can identify them, later.

Make sense?

Note: When reinstalling Windows 10 Pro Build 10240, don't enter a Product Key, it will activate just fine.

Titan,

Ok, first, if you have not shutdown and restarted your computer lately I suggest you do so.  A shutdown and restart will often clear such behavior.

Next, I was going to suggest that you have a look at Windows Event Viewer at the Application messages for error messages related to VSS, Shadow Copy, or snapman.  If you find any messages these will give you Event ID codes and sometimes a Result Code or hr code.  These pieces of information can often pinpoint the cause of your VSS failure. knowing that can help in finding a solution.  Google these codes and you just might find a solution.

I was going to suggest that you attempt to re-register the VSS components as this will often clear up problems when nothing else seems to help.  I had a look at the blog you linked to.  I have another way of doing this if you care to give it a try.  Here's how:

Copy the following commands into Notepad then save the file with a {.bat} extension. Run the .bat file by opening an admin command prompt and entering the .bat file name.

cd /d %windir%\system32
net stop vss
net stop swprv
regsvr32 /s ole32.dll
regsvr32 /s oleaut32.dll
regsvr32 /s vss_ps.dll
vssvc /register
regsvr32 /s /i swprv.dll
regsvr32 /s /i eventcls.dll
regsvr32 /s es.dll
regsvr32 /s stdprov.dll
regsvr32 /s vssui.dll
regsvr32 /s msxml.dll
regsvr32 /s msxml3.dll
regsvr32 /s msxml4.dll
vssvc /register
net start swprv
net start vss

After each of the recommendations above see if each one helps or fixes the problem before moving on the the next one.

Post back your results.

thecreator, I'll have to do this when I have more time.

Enchantech, I ran vssadmin list writers this morning first thing after a cold boot of my PC and it ran successfully.

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {c59e3018-4076-4a4d-a8e4-53bdf021915b}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {5e228f1f-5c30-4fc2-ab73-823309e22413}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {42b7b09c-3078-41f1-bb85-fb6f4e11c636}
   State: [1] Stable
   Last error: No error

Writer name: 'MSSearch Service Writer'
   Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Writer Instance Id: {aec60695-0c03-4b20-b107-31e3326d6632}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {2c9dc4a0-678d-4cb6-a197-d7702bc108fd}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {a89cc187-623e-4ab3-a5ea-f498ce15ba72}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {6748b902-c615-475d-9559-972ce7483f08}
   State: [1] Stable
   Last error: No error

I did exactly what you outlined in your post, creating a batch file to re-register those components.

It seems once Kaspersky protection activates, VSS writer breaks. Hmm...

I decided to uninstall KIS 2016 and leave my computer running for 15-20 minutes then try vssadmin list writers, and it still works just fine. I tried running a backup in ATI 2016 and ran successfully without intervention.

So now my head is turned towards Kaspersky. My plan of attack for now is:

1. Reinstall KIS 2016 and see if the VSS problem resurfaces.
2. If the problem resurfaces, reach out to Kaspersky to see if they are aware of the problem and have a fix.

I'll report my findings.

I did a quick Google search and nothing came up regarding VSS errors and KIS 2016.

Titan,

At least now you are headed in the right direction and you know what is causing the issue.  The best of luck to you in getting it resolved.

Here's an update. I reinstalled KIS 2016. Problem returned after updating to the latest build.

If I run 'vssadmin list writers' just after startup, it lists the writers without a problem. I can repeat this command over and over for a minute or so before it starts getting stuck on 'Waiting for responses. These may be delayed if a shadow copy is being prepared.' I did this and looked at event log and in the reports section of KIS to try and narrow down what is causing the problem. Neither produced any conclusive evidence.

Here's where it gets frustrating - the problem doesn't happen with every boot. Sometimes when I reboot, running 'vssadmin list writers' works fine and doesn't stop working, thus ATI 2016 backs up my machine without a problem. At the next reboot, running 'vssadmin list writers' hangs and the ATI 2016 backup hangs as well. I haven't been able to find any pattern with it.

I loaded up a fresh copy of Windows 10 Pro in VMware, installed KIS 2016, ATI 2016, and Google Chrome. I duplicated all settings, but I was unable to replicate the issue I'm having on my PC.

Chkdsk finds no errors, sfc finds no integrity violations, dism finds no problems, drivers and BIOS are all correctly installed and updated.

I'm thinking the trouble lies elsewhere outside than with KIS or ATI, but KIS definitely seems to be the catalyst.

For now, I've turned Fast Startup back on (was having an issue with a previous build of KIS 2016 and Fast Startup, but looks like that's been fixed.) and VSS looks to be working without any issues. I'm sure next time Windows Updates come out and my machine reboots, I'll run in to the same issue, but for now ATI 2016 is working just fine.

Titan,

I did some digging and found an support center post that you might find interesting, I know I did!  Link below:

https://www.storagecraft.com/support/forum/windows-10-and-vss-errors

your post is very interesting. i wonder if Acronis can craft a patch to fix/bypass the MS VSS problem.

my backups in windows 10 still hang (forever) and resume after end Acronis' VSS process.

one workaround i tried with some success was loading acronis removeable media to usb flash drive and leaving in computer then reboot to flash drive periodically for backup (outside of windows).

for me, not automatic = not ideal :(

i'm hoping acronis will patch a fix

Why don't you simply disable VSS. When you use the recovery media, VSS is not used. TI will function in Windows without VSS. I see you set VSS startup to Manual. That did nothing. TI requested VSS to start and it did. Set VSS startup to Disabled, reboot and try again.

RTMxp,

If you wish to leave VSS enabled so that Windows restore points are created during normal usage of your machine you can do so.  When you want to run a backup task simply disable VSS so the backup will run and then start the VSS service again after the backup completes.

I know this is less than optimal and not possible if backups are scheduled so, if you wish to know more about VSS here is a link to the Microsoft VSSadmin commands.

https://technet.microsoft.com/en-us/library/cc754968%28v=ws.10%29.aspx

You should check that your system has sufficient shadow storage space available as if not enough space is allocated this can cause hangs.  You can check this with the (vssadmin list shadowstorage) command.  In general it is recommend that 3% to 5% of total system data be set aside for restore point shadow copies.  To allocate more shadowstorage space the command is:

(vssadmin resize shadowstorage /For=C: /On=C: /MaxSize=xxxMB or GB)

You should also consider removing or clearing restore points that are no longer needed.  You can delete all of the currently stored ones and start anew or you can select them individually.  Use (vssadmin delete shadows) command to do this.

Since it seems that Windows 10 VSS service has some growing pains at present all of this may be of no help in fixing your issue.

RTMxp, the problem is virtually resolved on my computer after turning Fast Startup back on (Start Menu > Power Options > Choose what the power button does, Click "Change settings that are currently unavailable", then make sure "Turn on fast startup (recommended)".

Really all this does is if the computer starts up and VSS is running just fine, it will keep VSS running just fine until the next reboot, after which the problem may recur.

I did this and ATI has been working just fine.

A few tidbits about Windows 10 Fast Startup:

http://www.tenforums.com/tutorials/4189-fast-startup-turn-off-windows-1…

It could be that an improper power setting such as hibernate being disabled is causing the issue with VSS.

A read through the posts of the attached link reveal some interesting things with older hardware as well.

i have disabled vss and ati seems to be working again. i disabled hibernate awhile back and that may have been when the ati problem started. i have also disabled system restore choosing to rely on daily incremental ati backups.  i tried system restore a few times a long time ago in other versions of windows and it didn't seem to work while good disc images are more reliable and just as fast (seems to me). freefilesync (for data backup with versions) also uses some kind of shadow copy and it still works (ffs always worked).

if in the future i find a need for vss or hibernate i can just turn them back on.

many thanks to all

If you have any other programs that need VSS, you can leave the VSS start type set to Manual and use pre and post commands in True Image to automatically disable VSS during a backup and enable it after the backup completes. You enter the pre and post command in the Advanced Options tab.

Create a bat file for each command:

Pre command named Disable_VSS.bat

sc config vss start=disabled
sc stop vss

Post command named Enable_VSS.bat

sc config vss start=demand

Now I ask you. where else can you get such  knowledgeable, personalized help from a volunteer!

you guys were great and i really appreciate all the help.

i just got the following information from acronis tech support after telling them what you had told me and what i did to fix the problem.

Hello Randy,

Thank you for your response.

I would like to inform you that as you have enabled both the Volume shadow copy service and Microsoft Shadow copy service it had a conflict. Both of these services are used for the same purpose to create a snapshot of the drive. If both of these are enabled you may have a conflict.

I n those rare cases you can disable one of the these service and set one as automatic which you have done to resolve the issue.