• Guest, The rules for the P & N subforum have been updated to prohibit "ad hominem" or personal attacks against other posters. See the full details in the post "Politics and News Rules & Guidelines."

Question Acronis TI & Macrium Reflect No Longer Work

EXCellR8

Diamond Member
Sep 1, 2010
3,750
673
126
I am no longer able to make backups of my OS drive with either Acronis True Image 2019 or Macrium Reflect 7.2; the process of imaging does not seem to initialize or start. Reflect mentioned something about VSS failing to verify or something; Acronis just stays at 0% (calculating time remaining)--so I'm thinking the issue is related. Is anyone else using either piece of software with Windows 10 Pro (May Update 2004) and successfully able to image their disks? This is the first major problem I've encountered while trying to backup my OS installation, so any advice would be helpful.

Thanks in advance.
 

Z15CAM

Platinum Member
Nov 20, 2010
2,085
39
91
www.flickr.com
Have run into this problem after installing the July 7th Win10 v2004 online update KB4565503 ?

Lots of issues related to this latest MS System update.

Hope you have a Macrium Reflect WinPE backup image prior to this flaky update so that you can run it again without corruption happening.

Suggest you Download the Off line installs of :
windows10.0-kb4565503-x64_db6e183196b0c394a7fa3be6e8fd26544c6dc9ce.msu
windows10.0-kb4565627-x64-ndp48_a765b5e7b36d04b80565d097620218def98f1f9d.msu and
windows10.0-kb4561600-x64_c1b68e8ebc584fba22606561477bfd8d6ca553d6.msu

Go OFF LINE and over-write your present Win10 v2004 Boot Driver with a known clean image of the previous version and manually run the off line installer to update you system.

I ran into all sorts of issues with this latest MS Win10 v2004 forced install system update and so have many others.

Try re-installing Macruin Reflect or Acronis (Whatever your using on the present Updated system) to install the appropriate app drivers then make a Backup WinPE thumb - Honestly I would not trust that your present updated OS is not free off other corruption due to the Online Win10 v2004 update.

If you can't access your Backup Images and haven't run Disk Cleanup removing the previous OS you can try going off line and roll back to the previous OS then running the 3 Update files as mentioned - All off line.

Good luck
 
Last edited:
  • Like
Reactions: EXCellR8

EXCellR8

Diamond Member
Sep 1, 2010
3,750
673
126
Thanks for the info--the latest full image I have of the system is from the beginning of May, so that's my bad. I do have a differential created in June but not sure it will work.

As for the actual issue itself, it appears to be related to VSS. I downloaded Acronis' free VSS Doctor tool, which picked up on a few things--but nothing I'd be familiar with, or know how to fix.

2020-07-21 08:30:20 GMT-04:00
AcronisVSSDoctor-net45, 1.0.39.0, v4.0.30319
Microsoft Windows NT 6.2.9200.0, 4.0.30319.42000

===========================================================
VSS Services Configuration and Status

Status: OK
Description: All VSS-related services are configured correctly

Services:

Name: swprv
Title: Microsoft Software Shadow Copy Provider
Status: Stopped
ReferenceStatus:
NeedToFixStatus: False
StartMode: Manual
ReferenceStartMode: Manual
NeedToFixStartMode: False
IsOk: True
ExpectationDescription:
Exception:

Name: VSS
Title: Volume Shadow Copy
Status: Stopped
ReferenceStatus:
NeedToFixStatus: False
StartMode: Manual
ReferenceStartMode: Manual
NeedToFixStartMode: False
IsOk: True
ExpectationDescription:
Exception:

Name: EventSystem
Title: COM+ Event System
Status: Running
ReferenceStatus: Running
NeedToFixStatus: False
StartMode: Auto
ReferenceStartMode: Auto
NeedToFixStartMode: False
IsOk: True
ExpectationDescription:
Exception:



===========================================================
VSS Providers Configuration

Status: OK
Description: Only known VSS provider(s) found

Providers:

Id: b5946137-7b9f-4925-af80-51abd60b20d5
Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\{b5946137-7b9f-4925-af80-51abd60b20d5}
Name: Microsoft Software Shadow Copy provider 1.0
IsDefault: True



===========================================================
VSS Access Control Configuration

Status: OK
Description: Known VSS access control entries are configured correctly

AccessControls:

UserName: NT Authority\NetworkService
EntryExists: True
UserExists: True
IsActive: True
IsOk: True
StatusDescription:



===========================================================
VSS Components Availability

Status: OK
Description: VSS components are accessible



===========================================================
VSS Writers Status

Status: OK
Description: All VSS writers are working correctly

Writers:

Name: Task Scheduler Writer
Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
State: [1] Stable
IsOk: True
Error: No error

Name: VSS Metadata Store Writer
Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
State: [1] Stable
IsOk: True
Error: No error

Name: Performance Counters Writer
Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
State: [1] Stable
IsOk: True
Error: No error

Name: System Writer
Id: {e8132975-6f93-4464-a53e-1050253ae220}
State: [1] Stable
IsOk: True
Error: No error

Name: ASR Writer
Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
State: [1] Stable
IsOk: True
Error: No error

Name: Shadow Copy Optimization Writer
Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
State: [1] Stable
IsOk: True
Error: No error

Name: Registry Writer
Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
State: [1] Stable
IsOk: True
Error: No error

Name: MSSearch Service Writer
Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
State: [1] Stable
IsOk: True
Error: No error

Name: WMI Writer
Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
State: [1] Stable
IsOk: True
Error: No error



===========================================================
VSS Shadow Storages Status

Status: Warn
Description: Some VSS shadow storages are misconfigured

Storages:

ForVolume: C:\
OnVolume: C:\
Used: 0 B
Allocated: 0 B
Maximum: 3072 MB
Minimum: 320 MB
VolumeSize: 464 GB
Available: 355 GB
TargetMaximum: 46 GB
MaximumGreaterThenMinimum: True
MaximumIsEnough: False
MaximumIsNotReached: True
AvailableIsEnoughForMaximum: True
IsOk: False
Description: Recommended Maximum storage size is 10 percent of volume size

ForVolume: \\?\Volume{eeb26d2b-0000-0000-0000-100000000000}\
OnVolume: \\?\Volume{eeb26d2b-0000-0000-0000-100000000000}\
Used: 0 B
Allocated: 0 B
Maximum: UNBOUNDED
Minimum: 32 MB
VolumeSize: 499 MB
Available: 433 MB
TargetMaximum: 49 MB
MaximumGreaterThenMinimum: True
MaximumIsEnough: True
MaximumIsNotReached: True
AvailableIsEnoughForMaximum: True
IsOk: True
Description:



===========================================================
Disk Free Space Available

Status: Warn
Description: Some disks have insufficient free space. Perform a cleanup.

Volumes:

Name: C:\
DeviceId: \\?\Volume{eeb26d2b-0000-0000-0000-501f00000000}\
Size: 464 GB
Available: 355 GB
Minimum: 320 MB
IsOk: True
Description:
IsMounted: True

Name: D:\
DeviceId: \\?\Volume{72e07a53-0000-0000-0000-100000000000}\
Size: 1863 GB
Available: 1480 GB
Minimum: 320 MB
IsOk: True
Description:
IsMounted: True

Name: E:\
DeviceId: \\?\Volume{6eb129a3-ee23-4dc9-8e86-c17fabdc860f}\
Size: 3725 GB
Available: 1522 GB
Minimum: 320 MB
IsOk: True
Description:
IsMounted: True

Name: G:\
DeviceId: \\?\Volume{d9cd9f95-0000-0000-0000-100000000000}\
Size: 223 GB
Available: 94 GB
Minimum: 320 MB
IsOk: True
Description:
IsMounted: True

Name: \\?\Volume{eeb26d2b-0000-0000-0000-100000000000}\
DeviceId: \\?\Volume{eeb26d2b-0000-0000-0000-100000000000}\
Size: 499 MB
Available: 433 MB
Minimum: 32 MB
IsOk: True
Description:
IsMounted: False

Name: \\?\Volume{eeb26d2b-0000-0000-0000-f05074000000}\
DeviceId: \\?\Volume{eeb26d2b-0000-0000-0000-f05074000000}\
Size: 508 MB
Available: 55 MB
Minimum: 320 MB
IsOk: False
Description: Free space is below required minimum
IsMounted: False



===========================================================
Disk I/O Load

Status: Warn
Description: Some disks may be overloaded. VSS may behave incorrectly under such conditions. Stop heavy operations or wait until completion.

Disks:

Name: 0 G:
DiskBytesPersec: 0
DiskReadBytesPersec: 0
DiskReadsPersec: 0
DiskTransfersPersec: 0
DiskWriteBytesPersec: 0
DiskWritesPersec: 0
PercentDiskReadTime: 0
PercentDiskTime: 0
PercentDiskWriteTime: 0
PercentIdleTime: 99
IsOk: True

Name: 1 D:
DiskBytesPersec: 0
DiskReadBytesPersec: 0
DiskReadsPersec: 0
DiskTransfersPersec: 0
DiskWriteBytesPersec: 0
DiskWritesPersec: 0
PercentDiskReadTime: 0
PercentDiskTime: 0
PercentDiskWriteTime: 0
PercentIdleTime: 99
IsOk: True

Name: 2 E:
DiskBytesPersec: 1569
DiskReadBytesPersec: 0
DiskReadsPersec: 0
DiskTransfersPersec: 0
DiskWriteBytesPersec: 1569
DiskWritesPersec: 0
PercentDiskReadTime: 0
PercentDiskTime: 0
PercentDiskWriteTime: 0
PercentIdleTime: 95
IsOk: True

Name: 3 C:
DiskBytesPersec: 11635058
DiskReadBytesPersec: 11573165
DiskReadsPersec: 593
DiskTransfersPersec: 601
DiskWriteBytesPersec: 61893
DiskWritesPersec: 7
PercentDiskReadTime: 11
PercentDiskTime: 11
PercentDiskWriteTime: 0
PercentIdleTime: 87
IsOk: False



===========================================================
NTFS Volume Access Control Configuration

Status: OK
Description: All volumes have correct access control configuration

Volumes:

Name: C:\
SystemHasAccess: True
SystemSid: S-1-5-18
IsOk: True
Description: "SYSTEM" account has "Full Control" access

Name: D:\
SystemHasAccess: True
SystemSid: S-1-5-18
IsOk: True
Description: "SYSTEM" account has "Full Control" access

Name: E:\
SystemHasAccess: True
SystemSid: S-1-5-18
IsOk: True
Description: "SYSTEM" account has "Full Control" access

Name: G:\
SystemHasAccess: True
SystemSid: S-1-5-18
IsOk: True
Description: "SYSTEM" account has "Full Control" access

Name: \\?\Volume{eeb26d2b-0000-0000-0000-100000000000}\
SystemHasAccess: True
SystemSid: S-1-5-18
IsOk: True
Description: "SYSTEM" account has "Full Control" access

Name: \\?\Volume{eeb26d2b-0000-0000-0000-f05074000000}\
SystemHasAccess: True
SystemSid: S-1-5-18
IsOk: True
Description: "SYSTEM" account has "Full Control" access



===========================================================
Event Log

Status: Warn
Description: Some VSS-related errors or warnings occurred during the previous day

Events:

Timestamp: 7/20/2020 10:02:35 PM
Type: Error
Source: VSS
Message: Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{eeb26d2b-0000-0000-0000-100000000000} - 0000000000000280,0x0053c008,000001CFDEB0A3B0,0,000001CFDEB0B3E0,4096,[0]). hr = 0x80070079, The semaphore timeout period has expired. . Operation: Processing EndPrepareSnapshots Context: Execution Context: System Provider
InstanceId: 12289
SearchLink: https://www.google.com/#newwindow=1&q=VSS+event+id+12289

Timestamp: 7/20/2020 10:02:35 PM
Type: Error
Source: volsnap
Message: The shadow copy of volume \\?\Volume{eeb26d2b-0000-0000-0000-100000000000} being created failed to install.
InstanceId: -1073348541
SearchLink: https://www.google.com/#newwindow=1&q=volsnap+event+id+3221618755

Timestamp: 7/20/2020 9:12:37 PM
Type: Error
Source: volsnap
Message: The shadow copy of volume C: took too long to install.
InstanceId: -1073348598
SearchLink: https://www.google.com/#newwindow=1&q=volsnap+event+id+3221618698

Timestamp: 7/20/2020 9:09:10 PM
Type: Error
Source: volsnap
Message: The shadow copies of volume C: were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.
InstanceId: -1073348583
SearchLink: https://www.google.com/#newwindow=1&q=volsnap+event+id+3221618713

Timestamp: 7/20/2020 8:03:51 PM
Type: Warning
Source: volsnap
Message: An unfinished create of a shadow copy of volume C: was deleted.
InstanceId: -2147090402
SearchLink: https://www.google.com/#newwindow=1&q=volsnap+event+id+2147876894

Timestamp: 7/20/2020 7:54:59 PM
Type: Error
Source: VSS
Message: Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{eeb26d2b-0000-0000-0000-501f00000000} - 0000000000000230,0x0053c008,000001CB19909FE0,0,000001CB1990B010,4096,[0]). hr = 0x80070079, The semaphore timeout period has expired. . Operation: Processing EndPrepareSnapshots Context: Execution Context: System Provider
InstanceId: 12289
SearchLink: https://www.google.com/#newwindow=1&q=VSS+event+id+12289

Timestamp: 7/20/2020 7:54:59 PM
Type: Error
Source: volsnap
Message: The shadow copy of volume C: being created failed to install.
InstanceId: -1073348541
SearchLink: https://www.google.com/#newwindow=1&q=volsnap+event+id+3221618755

Timestamp: 7/20/2020 5:10:15 PM
Type: Error
Source: VSS
Message: Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{eeb26d2b-0000-0000-0000-501f00000000} - 000000000000022C,0x0053c008,0000014BD150A100,0,0000014BD150B130,4096,[0]). hr = 0x80070079, The semaphore timeout period has expired. . Operation: Processing EndPrepareSnapshots Context: Execution Context: System Provider
InstanceId: 12289
SearchLink: https://www.google.com/#newwindow=1&q=VSS+event+id+12289

Timestamp: 7/20/2020 5:10:15 PM
Type: Error
Source: volsnap
Message: The shadow copy of volume C: being created failed to install.
InstanceId: -1073348541
SearchLink: https://www.google.com/#newwindow=1&q=volsnap+event+id+3221618755
 

Steltek

Platinum Member
Mar 29, 2001
2,385
279
126
Have you run any tests on the system drive to ensure that it isn't failing? If it isn't failing, have you checked that there is no file system corruption with CHKDSK?

Since you are having problems with your recent backups, I'd run a read-only scan by entering CHKDSK c: in an elevated command prompt. If it finds a file system error, it won't fix it but will error out with a "cannot continue in read only mode" error. That way, you will know there is a problem and also have the opportunity to manually back up any important data since the last successful backup before running a full CHKDSK /f on the drive.

If you are absolutely sure the drive is ok and the file system is good, since your system is bootable you can also try to run a Windows repair install to try to fix your current install while retaining your current configuration.

Are there any VSS errors in the Windows system log?
 
Last edited:

EXCellR8

Diamond Member
Sep 1, 2010
3,750
673
126
My boot drive is a relatively new SSD, which tests good. I didn't run CHKDSK on it, but I did run Windows file system scan which found no integrity violations.

I don't have any drive related issues aside from this; never have before running W10.
 

EXCellR8

Diamond Member
Sep 1, 2010
3,750
673
126
Alright so I think part of the problem, or at least something possibly contributing to the problem, is that my PC can't create system restore points. I only discovered this after trying to update Visual Studio 2019. Sure enough, I can't manually create restore points either, despite VSS services running and CHKDSK finding no errors. Furthermore, the System Protection tab under System Properties is pretty much grayed out completely and the Protection Settings area always shows "Searching..." (and never actually shows anything else).

The PC otherwise runs totally fine, so I'm kind of puzzled. Disable System Restore also shows up as 'Not Configured' in the Group Policy Editor, which is default I believe.
 
Last edited:

Steltek

Platinum Member
Mar 29, 2001
2,385
279
126
The reason Windows System Protection isn't working is because of the VSS issues you found earlier. VSS is an essential component of the Windows System Restore utilities and Windows Backup as it creates file snapshots and backs up volumes even when they are in use. 3rd party programs such as Macrium and Acronis also use it, which is probably why they aren't working for you either.

You'll have to troubleshoot the VSS issue to get system protection working again and to resolve your backup problems. It might be as simple as starting the VSS service (it is listed under Volume Shadow Copy) in Services.msc, setting it to Automatic, and rebooting your system.

Here is a webpage with a few other things you can check to try to fix it.
 

Z15CAM

Platinum Member
Nov 20, 2010
2,085
39
91
www.flickr.com
Steltek: Good Call, but it's the crappy online MS Win 10 v2004 system update that caused the issue.

My system borked and crashed with that July 7th online Win10 v2004 update after Disk Cleanup twice corrupting Windows Update, Defender, Disk Cleanup (Really big issue) and my Audio assignments and who knows what else. I had to over-write my system with a prior clean version using a Macrium WinPE image from a thumb and start over ;o(

I recommend he over-write with his prior CLEAN version of Win 10 and manually install the v2004 update off line and hope it takes. Who knows what other corruption and problems he may have with his present system.

Why spend the time and afford attempting repairs on a corrupt system - Especially when he has a CLEAN prior version of a Win 10 backup.

This is the main reason why you run a 3rd party backup like Macrium Reflect , Acronis or DOS GHOST.EXE. Hey! Being hit by Ransomware ain't any worse then being sabotaged by Microsoft.

I personally love a DOS GHOST.EXE boot Vs a Win Boot such as Macrium Reflect and Acronis for backup images but today Main Board Mfgr's Bios's tend to kill DOS emulation to recognize attached Network drives for crap RGB Bios space.

In which case a DOS GHOST.EXE boot still see's your entire Boot Drive (as Microsoft can't rid DOS from their Boot drive. What do think CMD and Power Shell is in Win GUI ?) but due to some shit Mfgr's BIOS's a DOS Boot will not see satellite network drives for you to lock on to and backup ;o(

ASUS BIOS's are noted for this shit - I talked to an ASUS Tech for over an hour about this issue and all he said that he switch to Acronis - Makes me want to go back to a Gigabyte platform - LOL

Can anyone here hack the latest ASUS Bios to allow a DOS emulated pass through which reads network drives - Would love it - I'm sure our "Rusky" Geeks have already did it ?

I'm tempted to Peril it with a Hex Editor and Rom Comply but alas Asus MB's have no backup BIOS Chip = Very "Risky" ;o)

Why would I consider backing up a computerized system whether MS Win10 VSS works or not !!!!!

Win10 is unreasonably complicated compared to Win7; however, you owned Win7.

I suppose the Poster is worried about loosing accumulated personal Info and updated apps if he runs a prior clean Image - Well just copy your present personal files to a another drive or a thumb and update your apps accordingly after installing the v2004 update and prey it's solid . I never keep any personal files on my boot drive an that includes Downloads, Outlook Mail and keep a daily protected update copy of my Firefox bookmarks.json file. Just about everything personal goes to a Raid-0 Scratch Pad or a Playground Drive - Then I sort and keep what I want to a secure drive. By a secure drive I don't mean MS Bit-locker but a Hot Plug drive through Bios. Understand that latest July 7th Win10 v2004 MS forced update could have a corrupted Bit-locker. Bit-locker only works if your OS is working.

I really don't care how bad I'm hit because I will be back up and running with a clean system in less then 20 minutes whether its Windows, Linux or BSD and Microsoft has nothing to do with it.

Yes; I'm running the July 7th's Win 10 v2004 update right now and through all the crap that came with it where it appears to be stable and working. Hopefully non-corrupted and with no time bombs - I still don't trust it.

With all due respect other then for MS having full control, I will update Win 10 Off-Line, Defender DISABLED with the appropriate KB system updates on a prior CLEAN version of a Win 10 image, preying the out come is solid and not corrupted ;o)

Seems to me MS is intentionally gouging us for money through their support administration amidst this Covid-19 pandemic.

Enough of my ramblings; but do not trust updating your Win 10 system using the forced MS Online Windows Update site - PERIOD !

Trust your reading this Larry - I'm outta WINd ;o)
 
Last edited:

EXCellR8

Diamond Member
Sep 1, 2010
3,750
673
126
Unfortunately, I think the only thing that can help me at this point is a repair install or clean install of Windows... as I've tried just about everything I've come across to fix it but nothing has worked. My last full image is also too old at this point so I'll likely just end up with a broken install anyway. The only other thing I can think of is to wait it out and hope Microsoft addresses it with the next update--but that could be grasping at straws. Seeing as the the system functions fine outside of this issue though so I don't absolutely need to repair it at the moment.

Appreciate the help and support though, and there isn't really any sensitive data on my boot drive save for a few things that I can just manually back up.

[UPDATE]

Ran the Media Creation Tool for version 2004 to do a repair install of the OS; I think it did the trick. After it ran through, which took about 25-30 minutes, I was able to manually create a system restore point! I was also able to create a new full image of the System disk using Macrium Reflect 7.2 so I think I'll be okay now--at least until Microsoft breaks me again.

Thanks for the input and information.
 
Last edited:

ASK THE COMMUNITY