After Windows 10 update to 18362.86 (Windows 10, Verson 1903) a few days my Macrium Reflect v6.3 backups have started failing with Error code=9. 
I did do a chkdsk of both the drive being backed up as well as the destination disk with no errors.

Here is my VSS log.

Image ID - B8291CB5EC67DF35

--------------------------------------------------------------------------------
Imaging Summary


--------------------------------------------------------------------------------
Backup Definition File: c:\users\craig\documents\reflect\my backup(1).xml
Auto Verify: N
Maximum File Size: Automatic
Compression: Medium
Password: N
Intelligent Copy: Y
Power Saving: N
Email On Success: N
Email On Failure: N
Total Selected: 161.36 GB


--------------------------------------------------------------------------------
Retention Rules
Rules will be applied to all matching backup sets in the destination folder

Full: Retain full images for 26 Weeks
Linked incremental and differential images will also be deleted

Backup Sets: 4 sets found
Nothing to delete

Differential: Retain differential images for 4 Weeks
Linked incremental images will also be deleted

Differential Backups: 2 found
Nothing to delete

Incremental: Retain incremental images for 14 Days
The oldest incremental images may be consolidated

Incremental Backups: 0 found



--------------------------------------------------------------------------------
Destination:
Backup Type: Incremental
File Name: Append to recent image in directory 'n:\backup\'
n:\backup\B8291CB5EC67DF35-26-26.mrimg


--------------------------------------------------------------------------------
Operation 1 of 5
Hard Disk: 3
Drive Letter: N/A
File System: NTFS
Label: Recovery
Size: 300.0 MB
Free: 20.0 MB
Used: 280.0 MB


--------------------------------------------------------------------------------
Operation 2 of 5
Hard Disk: 3
Drive Letter: N/A
File System: FAT32 (LBA)
Label: NO NAME
Size: 96.0 MB
Free: 69.1 MB
Used: 26.9 MB


--------------------------------------------------------------------------------
Operation 3 of 5
Hard Disk: 3
Drive Letter: N/A
File System: Unformatted
Label:
Size: 128.0 MB
Free: 0 B
Used: 128.0 MB


--------------------------------------------------------------------------------
Operation 4 of 5
Hard Disk: 3
Drive Letter: C
File System: NTFS
Label:
Size: 222.61 GB
Free: 62.08 GB
Used: 160.53 GB


--------------------------------------------------------------------------------
Operation 5 of 5
Hard Disk: 3
Drive Letter: N/A
File System: NTFS
Label:
Size: 450.0 MB
Free: 39.4 MB
Used: 410.6 MB


--------------------------------------------------------------------------------
Starting Image - Monday, May 06, 2019 18:18:00
Initializing
Destination Drive: Backup (n - Free Space 2.38 TB
Free space threshold: Delete oldest backup sets when free space is less than 5.00 GB

Creating Volume Snapshot - Please Wait
Volume Snapshots Created
Analyzing file system on volume
Analyzing file system on volume
Analyzing file system on volume C:
Gathering Windows Events - Please Wait


--------------------------------------------------------------------------------
Unknown error. - Error code = 9

Macrium published this KB article about this issue when it first appeared in a Windows Insider build for the release that would eventually become Windows 10 1903.  It appears that the Microsoft bug that Macrium describes there may have made it into the final release.  As noted in the article, Macrium provided a hotfix for Reflect V7, which has since been incorporated into the regular V7 code base, but no equivalent fix was provided for V6, presumably because V6 has been unsupported since February 2018 (a year after V7's launch), which predates this issue by several months.  As a test, you could try uninstalling V6 and installing V7 Free to see if it works properly.  If so, you might need to upgrade Reflect to keep using it on newer versions of Windows -- or hope that Microsoft issues an update to fix the bug that Macrium describes.

(Side note: The log you posted is the job log, not the VSS log, the latter of which is a separate child item in the Log tab of Reflect -- but the job log you actually posted is typically more useful anyway.)

Very helpful. Thanks very much. I'll look at upgrading and applying the hot fix.

Happy to help! You won’t have to apply the hotfix if you upgrade to V7 though, because the current version of V7 is a lot newer than that hotfix release and it already has that hotfix built in.

+x

 

crog62 - 7 May 2019 12:38 AM

After Windows 10 update to 18362.86 (Windows 10, Verson 1903) a few days my Macrium Reflect v6.3 backups have started failing with Error code=9. 
I did do a chkdsk of both the drive being backed up as well as the destination disk with no errors.

Here is my VSS log.

Image ID - B8291CB5EC67DF35

--------------------------------------------------------------------------------
Imaging Summary


--------------------------------------------------------------------------------
Backup Definition File: c:\users\craig\documents\reflect\my backup(1).xml
Auto Verify: N
Maximum File Size: Automatic
Compression: Medium
Password: N
Intelligent Copy: Y
Power Saving: N
Email On Success: N
Email On Failure: N
Total Selected: 161.36 GB


--------------------------------------------------------------------------------
Retention Rules
Rules will be applied to all matching backup sets in the destination folder

Full: Retain full images for 26 Weeks
Linked incremental and differential images will also be deleted

Backup Sets: 4 sets found
Nothing to delete

Differential: Retain differential images for 4 Weeks
Linked incremental images will also be deleted

Differential Backups: 2 found
Nothing to delete

Incremental: Retain incremental images for 14 Days
The oldest incremental images may be consolidated

Incremental Backups: 0 found



--------------------------------------------------------------------------------
Destination:
Backup Type: Incremental
File Name: Append to recent image in directory 'n:\backup\'
n:\backup\B8291CB5EC67DF35-26-26.mrimg


--------------------------------------------------------------------------------
Operation 1 of 5
Hard Disk: 3
Drive Letter: N/A
File System: NTFS
Label: Recovery
Size: 300.0 MB
Free: 20.0 MB
Used: 280.0 MB


--------------------------------------------------------------------------------
Operation 2 of 5
Hard Disk: 3
Drive Letter: N/A
File System: FAT32 (LBA)
Label: NO NAME
Size: 96.0 MB
Free: 69.1 MB
Used: 26.9 MB


--------------------------------------------------------------------------------
Operation 3 of 5
Hard Disk: 3
Drive Letter: N/A
File System: Unformatted
Label:
Size: 128.0 MB
Free: 0 B
Used: 128.0 MB


--------------------------------------------------------------------------------
Operation 4 of 5
Hard Disk: 3
Drive Letter: C
File System: NTFS
Label:
Size: 222.61 GB
Free: 62.08 GB
Used: 160.53 GB


--------------------------------------------------------------------------------
Operation 5 of 5
Hard Disk: 3
Drive Letter: N/A
File System: NTFS
Label:
Size: 450.0 MB
Free: 39.4 MB
Used: 410.6 MB


--------------------------------------------------------------------------------
Starting Image - Monday, May 06, 2019 18:18:00
Initializing
Destination Drive: Backup (n - Free Space 2.38 TB
Free space threshold: Delete oldest backup sets when free space is less than 5.00 GB

Creating Volume Snapshot - Please Wait
Volume Snapshots Created
Analyzing file system on volume
Analyzing file system on volume
Analyzing file system on volume C:
Gathering Windows Events - Please Wait


--------------------------------------------------------------------------------
Unknown error. - Error code = 9

Thanks for posting.

We've just release v6.3.1865 to handle this problem with Windows 10 1903. To update, take 'Other Tasks' > 'Check for updates' in Macrium Reflect. 

We do recommend that v6 customers update to v7 for continued Windows 10 support.

Kind Regards

Nick

Macrium Support

See our reviews on

Hi,
Was this fix added to 6.3.1865 for Reflect Workstation x64 edition on Windows 10 Enterprise as well? I just started getting this error for a full image to local disk (USB) backup job on my work computer which runs Workstation and Enterprise Edition.

Whereas on my home PC running Win 10 Pro, I was getting this error but updating to 1865 resolved that.

Let me know, thanks.
-t

The Reflect update wouldn’t have been specific to certain editions of Windows 10, and I can’t imagine that Windows 10 itself would be different across editions in a way that would lead to this behavior. If you haven’t already, you might try running CHKDSK /R against the partition you’re having a problem imaging (/R can take quite a while, FYI). Otherwise, if this is a managed system, any chance your IT department might have pushed a new or updated anti-malware solution or something like that? It might be interfering with Reflect.

+x

 

jphughan - 8 August 2019 3:10 PM

The Reflect update wouldn’t have been specific to certain editions of Windows 10, and I can’t imagine that Windows 10 itself would be different across editions in a way that would lead to this behavior. If you haven’t already, you might try running CHKDSK /R against the partition you’re having a problem imaging (/R can take quite a while, FYI). Otherwise, if this is a managed system, any chance your IT department might have pushed a new or updated anti-malware solution or something like that? It might be interfering with Reflect.

I guess I'm more asking whether someone can confirm if this fix was integrated into the Workstation 1865 build. I don't know if it's a 'given' that any bug fix in the Home version would also be integrated in the Workstation version in the same time frame.
-t

Ah ok, it wasn’t clear that your home PC was running different editions of both Windows and Reflect. Some home users run Reflect Workstation. Anyhow, if you go to the Help menu in Reflect, you should be able to view the release notes for the version you’re running to see if that fix is mentioned. I suppose it’s technically possible that even the release notes are incorrect if Workstation somehow didn’t get the actual code update even if it was supposed to, though. Hopefully Macrium can provide positive confirmation.

+x

 

jphughan - 8 August 2019 4:39 PM

Ah ok, it wasn’t clear that your home PC was running different editions of both Windows and Reflect. Some home users run Reflect Workstation. Anyhow, if you go to the Help menu in Reflect, you should be able to view the release notes for the version you’re running to see if that fix is mentioned. I suppose it’s technically possible that even the release notes are incorrect if Workstation somehow didn’t get the actual code update even if it was supposed to, though. Hopefully Macrium can provide positive confirmation.

Looks like the RN does claim this is fixed in my Workstation verison.

Would be nice if someone from Macrium can confirm/validate that, as I was not getting this error earlier but now it happens every time I run this particular backup job, so seems there is some case where it's not addressed.

I'll run a chkdsk when I get a chance.
-t