Skip to main content

TI2020 causes "volsnap driver not found" error frequently, and the backup failed (in case of Acronis snapshot backup)

Thread needs solution
Forum Member
Posts: 14
Comments: 24

Today I upgraded to 2020 from2019, and set hourly backup for system disk.

It created the initial backup normally, but on next cycle it failed the backup (differential) and showed "volsnap driver not found". But it retried automatically and created the backup normally.

This error occurs on my 3 PC's with the same reason.

Until 2019, all backups worked normally and I never seen volsnap driver error!

 

New topics (2019/8/24)

I checked this error, and tried to install TI2019 on the newly installed Windows10 and executed 2 or 3 times acronis snapshot backups. After that, I upgraded to TI2020 after uninstalling TI2019.

Then this "volsnap driver not found" error message came  out and the backup was failed.

So this "volsnap driver not found" error is recrested when the upgrading from TI2019 to TI2020.

If someone knows how to uninstall the previous TI2019 and make the system completely clean?

1 Users found this helpful
Frequent Poster
Posts: 19
Comments: 508

Hello! 

Seems like that volsnap driver has some issues on your machine.

Here is a KB article that should help fix the issue permanently: https://kb.acronis.com/content/63024

Forum Member
Posts: 14
Comments: 24

I checked the registry, and fltsrv is normal. the same error occurs on my 3 PC with this "volsnap driver not found".

So I went back to 2019, and no trouble occurs and no volsnap driver error. It is very starnge and unusual!

Forum Hero
Posts: 207
Comments: 5062

It is an odd error. It was not reported during beta testing (at least no mention of it on the forum). It is possible that it was behind some of the record for which no information was given.

i hope you sent feedback via the in App feedback, including the system report, as that would be need Ed to investigate the issue further.

Forum Member
Posts: 14
Comments: 24

I have already contact to Japanese agent by sending system report and snapshots.

I am using TrueImage since its early version for about 20 years, and now I backup the system using "acronis snapshot" instead of VSS because VSS does not save Windows update information.

So today, I defined Acronis snapshot and VSS backup methods, and at first I tried acronis snapshot and it failed with "volsnap driver not found". After that, I ran VSS backup and it finished normally, and so I retried acronis snapshot again, and it successfully finished!!!

I also confirmed this procedure after PC power off and on, the same things happened (first acronis snapshot failed, Vss finished, and second and third acronis snapshot finished successfully.

I wonder the site test was done mainly for VSS backup, and test for acronis snapshot was not surficient.

Forum Hero
Posts: 207
Comments: 5062

Have you tried doing a repair installation - download the full installer from your account, then run as administrator and select repair rather than uninstall.

In the past doing a repair has fixed a wide range of problems.

Ian

Forum Member
Posts: 14
Comments: 24

Thanks for your comments.

I tried the repair install, but the result was same and acronis snapshot failed indicating no volsnap driver!

Forum Hero
Posts: 207
Comments: 5062

Thanks for the confirmation. Will need to keep a lookout for further instances of this happening.

Ian

Forum Member
Posts: 14
Comments: 24

One thing, I wonder why "volsnap driver not found" error comes out when TI2020 executes  Acronis snapshot backup instead of VSS backup? I understand that Acronis snapshot backup performs backup with Acronis own backup method and do not use Windows VSS system.

 

Forum Hero
Posts: 57
Comments: 9352

A few suggestions for volsnap:

 

Restart the Volume Shadow Copy service:  Open services.msc Locate Volume Shadow Copy Service, and then double-click on it to open its Properties box. Stop the Service and then Start it again. Or else right-click on it and select Restart.

Run the System File Checker utility:

Open and admin command prompt and type sfc /scannow.

Run check disk on volume C::

In Disk Management click on volume C: to select it then right click for a contest menu.  Select Properties from the menu.  Click on the Tools tab in the properties box then click on Check.  If errors are found they will be repair upon a Restart of the PC.

You might also fix it by updating all your storage controller drivers to the latest versions.

Lastly, run a test on your RAM to check for issues.  Bad RAM can cause volsnap errors.

 

Beginner
Posts: 0
Comments: 2

A few suggestions for volsnap

Thanks for your advice...
...but that didn't help...

 

Beginner
Posts: 0
Comments: 2

..

Forum Moderator
Posts: 242
Comments: 7052

Hello Everyone,

if you encounter the issue with backup failing with "No Volsnap driver was found", please contact Acronis support team and provide the following information

  1. Whether an earlier version of Acronis True Image worked fine and if backup started failing only after upgrading to (or clean installing) Acronis True Image 2020.
  2. Whether there is volsnap entry in the registry parameter UpperFilters in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71a27cdd-812a-11d0-bec7-08002be2092f}. See https://kb.acronis.com/content/63024
  3. System Report

This will help us to identify the root cause of the issue and properly fix it. Thank you!

Beginner
Posts: 0
Comments: 1

Ekaterina wrote:

Hello Everyone,

if you encounter the issue with backup failing with "No Volsnap driver was found", please contact Acronis support team and provide the following information

  1. Whether an earlier version of Acronis True Image worked fine and if backup started failing only after upgrading to (or clean installing) Acronis True Image 2020.
  2. Whether there is volsnap entry in the registry parameter UpperFilters in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71a27cdd-812a-11d0-bec7-08002be2092f}. See https://kb.acronis.com/content/63024
  3. System Report

This will help us to identify the root cause of the issue and properly fix it. Thank you!

I have the same problem since yesterday.

(1) is true

(2) is true There is a voldsnap entry in upperfilters

 

The wy the product is right now. I cannot do a backup and I cannot do a restore.  The whole thing started with 2020 but when going back to 2019, the problem does not disappear.

Forum Member
Posts: 14
Comments: 24

I am the first reporter of this problem and checked and tried in several ways and finally this problem has been fixed by the following update procedure;

Problem : Backup by acronis snapshot fails indicating "volsnap driver not found" (this message is my translation because I us Japanese version). VSS backup works normally.

my procedure:

1. Set "sytem restore" effective for sytem disk (C:) in the control panel

2. Check VSS using acronis VSSDoctor and fix the error

3. Uninstall previous TI2019 using acronic Cleanup tool

4. Clean up system using CCleaner and manually

5. Define backup target system disk C: only (exclude recovery partition, EFI partition,etc)

Then I could install TI2020 and backup in acronis snapshot successfully.

However I can not identify which procedure is effective and why this error occurs.

 

 

Forum Hero
Posts: 70
Comments: 8346

Jean, if you're needing to roll back to 2019, I'd suggest running the cleanup tool to remove all traces of True Image first.  Once it's done, reboot to clean up the registry.  Then install 2019 (make sure to get the most current file from your account - just in case). 

And, when you launch the cleanup tool and the 2019 installer, make sure to always right-click and "run as administrator" even if you're logged in with an admin account.

Cleanup tool is in my signature.

Forum Hero
Posts: 207
Comments: 5062

You should also save your settings before removing ATI 2020 and then restore them once you have reinstalled ATI 2019.

Ian

Beginner
Posts: 2
Comments: 9

The issue surfaced about a week ago.  Spend days/hours trying to fix, uninstall, re-install, registry cleaner, uninstall anti-virus (malwarebytes), etc to NO SUCCESS.

I did a baseline clean install of Win7, all software, created gold disk backup absolutely no issue as of yesterday.  Today my daily differential kicked off and "no volsnap driver was found" resurfaced.

I installed 2020_21400 specifically because release notes specifically said "volsnap driver" error was FIXED.
I was using 2018 previously, upgraded to 2020 in October when it came out. I NOW REGRET IT.

Beginner
Posts: 2
Comments: 9

Found VSS doctor, ran, no errors although 2 sections noted issues:
1)saying my system reserve drive is low on space (which I don't use for backups)
2)Event log entries (of course since I've had issues)

Same volsnap driver not found error.

I should note previously and currently I use cobian backup which uses shadow copy as well, never had an issue with it and 2018 worked fine alongside it as well.  Just thought if another utility can use shadow copy why can't TI2020.

Next will try install repair

 

Attachment Size
519592-176200.txt 18.48 KB
Legend
Posts: 110
Comments: 28791

Curtis, please see the post above from Ekaterina and submit the diagnostic data requested in that post to Acronis for investigation.

Beginner
Posts: 2
Comments: 9

Cleaned Registry (wisecare) and install repair, volsnap driver still fails, next unistall and reinstall.

Steve, I appreciate and will follow your advice, regretfully my experience with support is very tainted.  When I called on a recovery problem testing 2020 new install support's only guidance after an hour of chat was to boot off remote media as if they were just running off a script.  I figured out the issue within a couple hours and it was fairly simple.  I sent them the solution.  It's what happens with you have tier 1 support staff answering tier 2.

I will follow your guidance if I can't figure this out (although given it cropped up before I suspect I'll have to).

Thank you for your prompt response and dedication.

Regular Poster
Posts: 4
Comments: 177

Curtis Matthes  For me it solved that concern  https://kb.acronis.com/content/63024  

 

Screenshot_3_0.png

Attachment Size
519621-176208.png 77.43 KB
Beginner
Posts: 2
Comments: 9

Well, I tried to just revert to TI2018 and still the volsnap driver issue.  On performance setting, I switched from VSS to Acronis snapshot and am no longer receiving the error.  Well there are two days of my time I'm never going to get back.

Forum Hero
Posts: 57
Comments: 9352

Curtis,

Sorry to hear that you have not resolved the issue.  I know you state that you "cleaned" the registry however, have you checked to see if the volsnap entry noted in the KB Article exists in the reg key as indicated?

The UpperFilters value is one which an uninstall of the product does not remove.  Therefore a subsequent install of the product will not overwrite that reg value and fix the problem.  This is why reverting to 2018 did nothing.

The use of Acronis snapshot works because it does not rely on the volsnap component of VSS to perform the snapshot function.  Using it is fine and al least makes the product usable for you.

 

Beginner
Posts: 2
Comments: 9

Enchantech, thank you so much for your effort.  It makes sense as my attempts after the base reload was each time restoring a baseline gold disk just after Win7 was installed so I had an absolutely clean register although I would note I even used the Cleanup Tool (ATIH 2010-2019) so I assumed it picked up everything.

Regretfully I had no success.  added the property under the key as instructed, volsnap error when I tried vss, acronis copy, etc.  I'm absolutely baffled and now am on my third day of dedication to this issue.  Next I'm going to try w/o vss.

Forum Hero
Posts: 57
Comments: 9352

Curtis,

Have a look at the link below for information on MS Volsnap.  Errors involving volsnap are discussed.  If you find this applies in your case you may need to take some action using MS vssadmin commands to clear out old snapshots to fix the problem. 

MS Volume Shadow Copy Service errors

Beginner
Posts: 0
Comments: 1

It looks like this still hasn't been resolved.

I still get the volsnap error message. 

But if i just start the backup again after it fails, after a random number of tries (5-10), eventually, it works!!!??

 

Forum Moderator
Posts: 242
Comments: 7052

Hello Donald, 

yes, I'm afraid the issue still reproduces on certain configurations. We can only recommend following the article 63024: Acronis True Image: unable to select a disk for new backup, already configured backups fail, if volsnap is missing from UpperFilters in the system registry

Forum Member
Posts: 14
Comments: 24

I am the original reporter of this problem.

Although TI2021 has just been released, is this problem solved, or no reproduction of this error?

Beginner
Posts: 2
Comments: 9

I would love to know the answer to this as well.  I've tried everything support has asked, spent hours on the issue and it has now dragged on for over 6 months.  Users who are struggling with this should get a free copy of 2021 to see if it solves the issue FINALLY.  One foot out the Acronis door!

Forum Member
Posts: 14
Comments: 24

I fully agree to your FREE copy present! I bought 2020, but I did not use it for 1 year, so Acronis should give us free license for 2021!

Now I have tested 2021, but the results were not good!

1) Still unknown error occured during backup (1 per 10 backups).

2) As far as my test, the volsnap error did NOT come out.

As my opinion and feeling, 2021 still has some problems and so I will postpone to buy this new product.

Forum Hero
Posts: 57
Comments: 9352

All users with this problem:

The volsnap.sys driver can be found in C:\Windows\System32\Drivers\

If you navigate to the above folder and scroll to near the bottom of the list you should find the volsnap.sys file.  I just looked at my install having recently applied and in-place upgrade on this PC the file shows a date of 8/9/2020 and is 420KB in size.  To verify I compared file size to a new PC I built on 06/06/2020, they are identical  If your driver is of a different size chances are you have a bad file. 

I did a search using Explorer on my system for volsnap.sys.  I found several instances of the file. Not all instances were .sys or System files some were MUI files.  Looking at the .sys files I find on my system dating back to 3/19/2019 the volsnap.sys file in folder C:\Windows\WinSxS\amd64_microsoft-windows-volsnap_number string.  I found two of these folders and the volsnap.sys file appears in both of them.  One of the files is 420KB dated 08/09/2020, the other is 419KB dated 03/19/2019.

The Winsxs folder is used by Windows to store files that are needed for installation as well as backup and updates to these files.  Looking at any volsnap files found here specifically at file dates and sizes and comparing those with what you find in the System32\Driver folder should enable you to determine if the file in the System32\Driver folder is bad or possibly out of date. 

Once you determine that a problem is likely to exist with the volsnap file you can rename the volsnap.sys file in the System32\Driver folder by adding .old to the name, then copy the latest by date volsnap.sys file found of the correct size in the Winsxs folder to the System32\Driver folder.

Having replaced the volsnap.sys file the issue you have should be resolved.

 

Forum Star
Posts: 60
Comments: 2002

The best way to tell if volsnap is functioning on a system is open a command windows as administrator and enter the following line:

net start volsnap

If the volsnap service is working, you will see a message that the requested service has already been started. That means the service is running. If you see any other message, it means there is a problem with the service on the system. The volsnap service has a start value of 0 in the Windows registry. This means it is started very early in the boot process and should be running at all times.

It may not be a good idea to replace volsnap.sys in C:\WindowsSystem32\drivers. Rather than looking at file size and date, you should look at the version number of the file. Hover the mouse over the file in Explorer to see a pop-up that shows the version. The number should match the build number of the Windows system. In my case I see volsnap version 10.0.19041.1 and Windows OS build number 19041.450. Both show 19041 so they match.

Volsnap.sys has a corresponding file named volsnap.sys.mui. You will find the mui file at C:\Windows\System32\drivers\xx-XX. Where xx-XX represents the language of the Windows system. In my case it is en-US. The mui file should be for the correct version of the sys file. In WinSxS you will find the mui file in the xxxx.resources.volsnap folder.

 

 

Forum Star
Posts: 188
Comments: 1781

Are there any volsnap errors in the event log when these problems occur?

 

Beginner
Posts: 1
Comments: 4

I just wanted to update this thread with my experience. I never had a volsnap issue with True Image 2019 or 2020. I upgraded to 2021 in August (both updates) and everything remained normal for around 10 days. Then a I ran version 5.70 of CCleaner's registry fix. Once it ran and deleted some Acronis related entries (none involving volsnap though) that is when the error started happening during backups, where the Daily would have to try 5, 8, 10 times in order to work. These were the entries deleted:

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\SharedDlls]
"C:\\Program Files (x86)\\Acronis\\TrueImageHome\\GlobalSignR3.cer"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\SharedDlls]
"C:\\Program Files (x86)\\Acronis\\TrueImageHome\\GlobalSign.cer"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\SharedDlls]
"C:\\Program Files (x86)\\Acronis\\TrueImageHome\\DigiCert.cer"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls]
"C:\\ProgramData\\Acronis\\NGMP\\ngmp.zip"=dword:00000001

 

I followed the resolution instructions from the recommended article (https://kb.acronis.com/content/63024) and this has seemed to resolve the problem; two days of backups without errors.

 

Legend
Posts: 110
Comments: 28791

I have never known the default settings of CCleaner to remove any Acronis shared dll's, so am puzzled as to why it would do so on your system, and have to ask if you have modified the way CCleaner works by adding in extra definitions for areas to be cleaned by using one of the special .ini files as described in the CCleaner documentation?

Making such changes should always be tested in a safe environment before applying to any system where ATI is being used to protect your important data.

Forum Star
Posts: 60
Comments: 2002

I did some checking on a system with TI 2021 installed that had never had TI installed before. Yes, the registry does show the three shared dll entries you list. However, those files don't exist at the location specified. It's very understandable why CCleaner deleted the entries from the registry. They saw entries for files that didn't exist.

I manually deleted the three entries and then ran a backup. It worked fine. My best guess is that those files existed in a pervious version of TI and Acronis programmers didn't remove them from the list of files to be shown in the registry. Or maybe the entries are there because cloud backup needs them. The backup I tested without the entries was a local backup.

Forum Member
Posts: 14
Comments: 24

I wonder CCleaner relates to the unknown backup error of TI2020 (TI2021 also). Because CCleaner does not automatically clear the rregistry, it is manually cleaed.

This unknown backup error occurs sometime during continuos backup (every hour), for example. I can not decide that CCleaner relates to this error!

Beginner
Posts: 0
Comments: 1

Hello ,

I have the same problem "volnap driver not found"
in the version 2021. I'm back to 2020,
then TI works sometimes, but often aborts the backup.
 I've already tried everything, except for the manual entry
 into the registry, which I won't do either. I think I'll get another backup program 
now.

 

 
SAP
Beginner
Posts: 4
Comments: 4

Had similar issue with Volsnap error. Tried:

https://kb.acronis.com/content/63024

This seems to have fixed it. Will have to try couple of backups / verifications to see if this works.

 

Beginner
Posts: 1
Comments: 6

Mustang wrote:

The best way to tell if volsnap is functioning on a system is open a command windows as administrator and enter the following line:

net start volsnap

If the volsnap service is working, you will see a message that the requested service has already been started. That means the service is running. If you see any other message, it means there is a problem with the service on the system. The volsnap service has a start value of 0 in the Windows registry. This means it is started very early in the boot process and should be running at all times.

I had the "volsnap file " issue.

I ran the command indicated above (net start volsnap) and Windows told me that volsnap was already running. However this solved my problem for this time.
To be watched for the next automatic backups.
Thanks Mustang!

Beginner
Posts: 1
Comments: 2

Hi,

   Please add me to the list of Acronis users experiencing the "no volsnap driver found" error.

Am still in progress of trying suggestions noted above.  

Some specifics for my system:

The file version of (as taken from the file properties)
 c:\computer\windows (C:)\windows\system32\drivers\volsnap.sys   
is 6.1.7601.17567    SIZE: 289KB (296,320 bytes,  299,008 bytes on disk)
Dated: 12\8\2014 3:17am    digital signature: sha1

The Acronis version: 2020, build 25700

Regards....

 

Legend
Posts: 110
Comments: 28791

Matthew, your volsnap.sys version number and date stamp look to be far too old to be provided by ATI 2020. 

I don't have a system with ATI 2020 installed available but looking at ATI 2021, the volsnap.sys file version is 10.0.19041.488 with a date of 11/09/2020, so I find it hard to believe that the 2020 version would only be 6 with a date from 2014!

Please do a Repair Install of ATI 2020 followed by a restart of Windows then check if the volsnap details have been updated as expected.

See KB 60915: Acronis True Image: repairing program settings - for details of doing the Repair.

Beginner
Posts: 1
Comments: 2

Yes, the volsnap.sys file(s) resides in/on a WIN7  (gasp!)  partition of a Dual Boot (Win7/Win10) workstation.

After some investigation I noticed the WINSXS folder did NOT have the volsnap directories contained therein

(as noted post #31).  I looked further into the WIN10 partition and did see the volsnap directories in the

WINSXS folder.

SO....   I installed Acronis to the WIN10 partition and everything started working....     ((imagine that!)).

...and promptly UNinstalled Acronis from the WIN7 partition.  (whew!)

  FOR ME AND MY SYSTEM:  The guidance offered by KB Article#63024 (source Ekaterina)

((insert volsnap into UpperFilters))  caused my system to become unbootable and forced me to

revert to a previous registry instance; maybe that article helped others by for me was catastrophic.... 

--> I don't dare insert klbackupdisk as suggested elsewhere.

 

   As I am migrating AWAY from WIN7, as far as I am concerned, this issue has been resolved.

Hope it helps!!  

Thank you for your assistance...  I appreciate it.

Regards.