I replaced my failed external hard drive that I use only for daily backups. Now when I run Macrium Reflect Free, I get an error message, even though Reflect was running fine before I installed the new hard drive.
This is the error message that I get, and a Google search shows that many people have been getting this message for many years. Anyone know how to fix this error? Creating Volume Snapshot - Please Wait ERROR: COM call "m_pVssObject->BackupComplete(&pAsync)" failed. - Returned HRESULT = 0x80042301 - Error text: VSS_E_BAD_STATE Gathering Windows Events - Please Wait ---------------------------------------------------------------------- Backup aborted! - Failed To Create Volume Snapshot. Result Code: 0x8004231f
It could be a problem of a non-standard sector size on the new external drive. See this link. Did you possibly replace the old drive with a drive more than 2 TB in size?
QUOTE: It could be a problem of a non-standard sector size on the new external drive. See this link. Did you possibly replace the old drive with a drive more than 2 TB in size?
Dave
The new 1 TB drive replaces a 1 TB drive (which worked with the same Reflect XML file), and the new drive has the correct bytes/sector size of 512.
Have you run a CHKDSK on the drive(s) you are planning on backing up since the drive swap? It could be just coincidence that the problem is showing up after the swap.
QUOTE: Have you run a CHKDSK on the drive(s) you are planning on backing up since the drive swap? It could be just coincidence that the problem is showing up after the swap.
Dave
I ran CHKDSK /f on the drive that I have since replaced, and I cancelled it after it had been running 21 hours. I will run CHKDSK (no /f parameter) on the new drive and on my C: drive, but I don't think it will detect anything. Many people have reported the same Macrium Reflect error, so I think the problem is with Reflect.
NEWS!!! I just discovered this information on the Internet, but I can't verify it until my Microsoft system backup finishes:
"The MSR partition is required to boot Windows 7 and later operating systems. Ordinarily, this partition does not have a drive letter assigned to it. If a drive letter is assigned then this can cause problems with Microsoft Volume Shadow copy Service (VSS).
If you receive the following error (or similar) when the MSR partition is included in a disk image then removing the drive letter association should resolve the issue:
Backup aborted! - Failed To Create Volume Snapshot Result Code: 0x8004231f
1. Start the Windows Disk Management Console. Click 'Start', type 'diskmgmt.msc' (without quotes) and press ENTER."
There are more instructions, but I'm hoping this will solve the Macrium Reflect problem.
I'll post the result of my test, just in case anyone else is having the same problem.
Glad to hear it. However, do you know how the drive letter came into existence? From your post, it appears the problem only started when you switched removable drives. That simple operation should not have caused any changes to your existing fixed drive table settings.
#7. "RE: Macrium Reflect Free Error" In response to dtellier (Reply # 6) Sat Jan-10-15 03:27 PM by spencercat
Quote:
QUOTE: Glad to hear it. However, do you know how the drive letter came into existence? From your post, it appears the problem only started when you switched removable drives. That simple operation should not have caused any changes to your existing fixed drive table settings.
Dave
The 'offending' drive letter had been there ever since I built the computer 4 years ago. I believe it was created when I installed Windows 7, and since it was a small partition, 100 MB, and I didn't know its purpose, I just left it alone.
Regarding the MSR partition, I found the following on the Internet; I don't know if it's true: "It's a placeholder invented by Microsoft. It doesn't contain any meaningful data and it's there just in case you'd ever need to create some additional partition for special uses. In that case, Windows will shrink the Reserved partition and create a new one in the recovered place. Deleting it shouldn't do any harm now, but you may face some problems in the future." Note the last clause regarding "...may face some problems in the future".
As to why the problem didn't exist with the previous external hard drive, I don't know. One of Life's many mysteries.
