Every time I attempt to make an image from my external BOOTCAMP volume, I get an error with Status: 88, and an incomplete (and unusable) image file.
(Related annoying bug: WinClone then pops up another dialog saying the clone has completed successfully - when it hasn’t.)
Yet, volume-to-volume cloning of the same volume works, which leads me to think there’s nothing wrong with my NTFS volume.
I have run chkdsk both at boot and with Windows running, and it finds nothing wrong. I ran dism and sfc to check for and fix Windows system problems, with no effect.
This is (as far as I know) unchanged for roughly the past year, so probably not related to Catalina. I only recently realized that my image file backups were useless.
Here’s the WinClone.log output that appears to be relevent:
2019-11-01T23:21:14+13:00:Archiving file data: 89 GiB of 89 GiB (99%) done 2019-11-01T23:21:15+13:00:[ERROR] File data was concurrently modified! Location ID: 4 Expected SHA-1: 1e6a20f51bccb063dcab47d1234bafbbb7be9ee4 Actual SHA-1: 5b9f2adb8a4bd82b2794b5dc1cd90b71c967fdd9 2019-11-01T23:21:16+13:00:ERROR: 2019-11-01T23:21:16+13:00:Exiting with error code 88: A file being added to a WIM image was concurrently modified. 2019-11-01T23:21:17+13:00:Executing "wimverify /Users/brsmith/Desktop/BOOTCAMP image.winclone/Windows.wim" 2019-11-01T23:21:17+13:00:Last message repeated 9 times 2019-11-01T23:21:17+13:00:Helper tool error: There was an error while file imaging. Please check the volume and try again. Status:88 2019-11-01T23:21:17+13:00:[WARNING] The WIM_HDR_FLAG_WRITE_IN_PROGRESS flag is set in the header of "/Users/brsmith/Desktop/BOOTCAMP image.winclone/Windows.wim". It may be being changed by another process, or a process may have crashed while writing the WIM. [WARNING] "/Users/brsmith/Desktop/BOOTCAMP image.winclone/Windows.wim" does not contain integrity information. Skipping integrity check. 2019-11-01T23:21:17+13:00:ERROR: Exiting with error code 84: The WIM file is incomplete. 2019-11-01T23:21:18+13:00:Helper tool error: The WIM file is invalid. Please check the file and try again. 2019-11-01T23:23:14+13:00:Setting the system to allow sleep...
Interestingly: The SHA-1 values (both expected and actual) are same for the last 4 times I’ve tried this, suggesting it might be one particular file triggering the problem. Could it be a particular bit of data that’s showing an error in the SHA-1 calculation?
I’m out of ideas. Any suggestions?
[A bit later:] For shits and giggles I tried imaging the copied volume from the successful volume-to-volume copy. It also fails at the same point, with the same error. I guess if the volume copy is block-by-block copy that would make sense, but if it’s a file copy that’d be a strong indication that it’s something in a file causing the problem.