VSS and Windows 10 May 2019 version1903
After installing Windows 10 version 1903, Acronis has stopped working. Log files follow
5/31/2019 2:01:14 PM: -07:00 19908 I00000000: -----
5/31/2019 2:01:14 PM: -07:00 19908 I00000000: ATI Demon started. Version: 23.5.1.17750.
5/31/2019 2:01:14 PM: -07:00 19908 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
5/31/2019 2:01:14 PM: -07:00 19908 I00640002: Operation SURFACEBOOK started manually.
5/31/2019 2:01:17 PM: -07:00 19908 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
5/31/2019 2:01:17 PM: -07:00 19908 I013C0000: Operation: Backup
5/31/2019 2:01:17 PM: -07:00 19908 I0064000B: Priority changed to Low.
5/31/2019 2:01:17 PM: -07:00 19908 I000B03F0: Create Backup Archive From: To file: E:\Backup\SURFACEBOOK_inc_b18_s3_v1.tib Compression: Normal Exclude: Files matching mask Match criterion: hiberfil.sys, pagefile.sys, $Recycle.Bin, swapfile.sys, System Volume Information, *.tib, *.tib.metadata, *.~, *.tmp, C:\Users\jimva\AppData\Local\Temp, C:\Users\jimva\AppData\Local\Microsoft\Windows\INetCache, C:\Users\jimva\AppData\Local\Mozilla\Firefox\Profiles\*\cache2, C:\Users\jimva\AppData\Local\Mozilla\Firefox\Profiles\*\OfflineCache, C:\Users\jimva\AppData\Local\Opera Software\Opera Stable\Cache, C:\Users\jimva\AppData\Local\Opera Software\Opera Stable\Media Cache, C:\Users\jimva\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\WINDOWS\CSC, C:\Users\jimva\OneDrive, C:\Users\jimva\Dropbox\, c:\jim, C:\Users\jimva\Desktop\Jim
5/31/2019 2:01:20 PM: -07:00 19908 I000101F8: Pending operation 173 started: 'Creating partition image'.
5/31/2019 2:01:20 PM: -07:00 19908 I00100000: Volume Tracker has failed to find changes on volume '\\?\Volume{985dfc66-83ea-4b6e-b6a2-cc3428696e57}\'.
5/31/2019 2:01:20 PM: -07:00 9948 I00640000: Writing incremental version to file: SURFACEBOOK_inc_b18_s4_v1.tib
5/31/2019 2:01:20 PM: -07:00 19908 I000101F8: Pending operation 173 started: 'Creating partition image'.
5/31/2019 2:04:12 PM: -07:00 19908 I00100000: Volume Tracker has failed to find changes on volume 'C:'.
5/31/2019 2:23:41 PM: -07:00 19908 I000101F8: Pending operation 173 started: 'Creating partition image'.
5/31/2019 2:23:41 PM: -07:00 19908 I00100000: Volume Tracker has failed to find changes on volume '\\?\Volume{1ba47fed-7dbc-4505-b42e-1b53dfece8af}\'.
5/31/2019 2:23:46 PM: -07:00 19908 I000101F8: Pending operation 173 started: 'Creating partition image'.
5/31/2019 2:23:49 PM: -07:00 19908 E000101F6: Error 0x101f6: Unable to create volume snapshot
| trace level: error
| line: 0x65b5eb7011094703
| file: c:\bs_hudson\workspace\790\processor\diskadm\da_commit.cpp:348
| function: DaProcessor::CommitImpl::OnDaError
| line: 0x65b5eb7011094703, c:\bs_hudson\workspace\790\processor\diskadm\da_commit.cpp:348, DaProcessor::CommitImpl::OnDaError
| $module: ti_demon_vs_17750
|
| error 0x70021: Unable to create volume snapshot
| line: 0xa5695862aaf8e69c
| file: c:\bs_hudson\workspace\790\core\resizer\backup\backup.cpp:831
| function: resizer::BackupImageBuilderImp::DoCommit
| line: 0xa5695862aaf8e69c, c:\bs_hudson\workspace\790\core\resizer\backup\backup.cpp:831, resizer::BackupImageBuilderImp::DoCommit
| $module: ti_demon_vs_17750
|
| error 0x10c449: Failed to lock the volume snapshot.
| line: 0x3fec04e376b8a236
| file: c:\bs_hudson\workspace\790\core\fdisk\win_snapshot.cpp:1344
| function: win_snapshot_core::CallSbLock
| line: 0x3fec04e376b8a236, c:\bs_hudson\workspace\790\core\fdisk\win_snapshot.cpp:1344, win_snapshot_core::CallSbLock
| $module: ti_demon_vs_17750
|
| error 0x9: Unknown status.
| line: 0x2aacb7b2ab852ac
| file: c:\bs_hudson\workspace\790\core\fdisk\ver2\arch\windows\win_errors.cpp:40
| function: Fdisk::AddKstatusError
| line: 0x2aacb7b2ab852ac, c:\bs_hudson\workspace\790\core\fdisk\ver2\arch\windows\win_errors.cpp:40, Fdisk::AddKstatusError
| code: 0x13
| $module: ti_demon_vs_17750
|
| error 0xfff0: The media is write protected
| line: 0xbd28fdbd64edb8f1
| file: c:\bs_hudson\workspace\790\core\common\error.cpp:307
| function: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8f1, c:\bs_hudson\workspace\790\core\common\error.cpp:307, Common::Error::AddWindowsError
| code: 0x80070013
| $module: ti_demon_vs_17750
5/31/2019 2:23:49 PM: -07:00 19908 E013C0005: Error 0x13c0005: Operation has completed with errors.
| trace level: error
| line: 0x9f2c53c72e8bcec0
| file: c:\bs_hudson\workspace\790\products\imager\demon\main.cpp:714
| function: main
| line: 0x9f2c53c72e8bcec0, c:\bs_hudson\workspace\790\products\imager\demon\main.cpp:714, main
| $module: ti_demon_vs_17750
Start: 5/31/2019 2:01:14 PM
Stop: 5/31/2019 2:23:49 PM
Total Time: 00:22:35


- Se connecter pour poster des commentaires


Already checked backup locations.
Also did a repair install.
- Se connecter pour poster des commentaires

Jim, please download / run the Acronis VSS Doctor tool plus also do a restart of Windows if not tried already. (link in my signature)
- Se connecter pour poster des commentaires

Sorry, I forgot to mention I had already run the VSS Doctor tool 0 issues found.
- Se connecter pour poster des commentaires


The Windows error code in your log " Common::Error::AddWindowsError | code: 0x80070013" Indicates that your Windows update, presumably to version 1903, has failed. This is likely the reason for the " error 0xfff0: The media is write protected " and the " error 0x10c449: Failed to lock the volume snapshot." as well.
I would recommend uninstalling the latest Windows update or any updates that show as Failed in the Update & Security settings of Windows 10 then, try to reinstall them and see if that will fix your issue. Updates that show as failed in the Updates & settings of Windows 10 can usually just be run again to get them to install correctly. Click on Check for Updates to re-run.
- Se connecter pour poster des commentaires

The update installed fine, that is not the issue. Following is from a support ticket
As I understand you are facing issue while creating the backup as you are getting an error "Unable to create volume snapshot"
I will be glad to assist you.
I would like to inform you that latest update of Windows 10 creates a read only partition "Msft Virtual Disk 1.0" and will be named as "PortableBaseLayer" which will be hidden.
However to resolve this issue I suggest you to create a disk level backup.Please refer to the below Knowledge base article on how to create the disk level backup:
- Se connecter pour poster des commentaires

I would like to inform you that latest update of Windows 10 creates a read only partition "Msft Virtual Disk 1.0" and will be named as "PortableBaseLayer" which will be hidden.
Not seeing any such hidden / read-only partition on my Windows 10 #1903 system.
- Se connecter pour poster des commentaires

- Se connecter pour poster des commentaires

- Se connecter pour poster des commentaires

Jim, thanks for the screen images. The hidden 'disk' shows as a separate virtual disk of 8GB size which makes me wonder if this is only created on systems using UEFI or else with larger memory capacity? I am running on an older Dell laptop which is still legacy and only has 4GB memory where the new virtual disk isn't being shown / created.
- Se connecter pour poster des commentaires

My machine is a Surface Book 2 i7 with 16G of memory, it has UEFI.
- Se connecter pour poster des commentaires



Interesting, I have yet to upgrade to version 1903 and even when I do I probably would not face your issue because I do not use the Entire PC backup option as I prefer the full disk or file/folder options.
The Portable Base Layer Drive is a Virtual disk used by sandbox and is present to insure that your disk has enough space for update installs. It appears that you have sufficient disk space for updates so if you wish to use the Entire PC backup option you need to remove the Portable Base Layer drive. See this LINK
- Se connecter pour poster des commentaires

Seems to be the same problem I have posted weeks ago: I am using Carbonite Backup for backing up to the cloud. It creats a virtual drive and ATI seems not to be able to lock this drive when make a backup. So the only solution for me was not to choose „entire PC“ when making a backup.
https://forum.acronis.com/forum/acronis-true-image-2019-forum/acronis-tih-2019-and-carbonite-backup
- Se connecter pour poster des commentaires

I can confirm that only backing up C: fixes the problem.
- Se connecter pour poster des commentaires

Thanks for the confirmation.
- Se connecter pour poster des commentaires