F5F Stay Refreshed Hardware Desktop Error code 0x81000037 occurred during a backup attempt when accessing a shadow copy on a volume.

Error code 0x81000037 occurred during a backup attempt when accessing a shadow copy on a volume.

Error code 0x81000037 occurred during a backup attempt when accessing a shadow copy on a volume.

T
Toodaloo_246
Senior Member
Find
439
09-09-2024, 06:34 PM
#1
I rely on Windows 7 Backup & Restore in Windows 11. I've encountered problems with the newer version and it doesn’t capture system images for important drives as I need. This has been happening for about three weeks now, and none of my attempts have resolved it. The guidance from Microsoft doesn’t seem relevant to my case. It appears to be having trouble with my Games SSD; the drive it’s attempting an image of pauses at 97% completion, then waits while the target reaches 100%, and stops abruptly with an error. Any suggestions for fixing this? Could be a hardware issue—CrystalDisk isn’t showing any issues on either drive.
Reply
Reply
T
Toodaloo_246
09-09-2024, 06:34 PM #1

I rely on Windows 7 Backup & Restore in Windows 11. I've encountered problems with the newer version and it doesn’t capture system images for important drives as I need. This has been happening for about three weeks now, and none of my attempts have resolved it. The guidance from Microsoft doesn’t seem relevant to my case. It appears to be having trouble with my Games SSD; the drive it’s attempting an image of pauses at 97% completion, then waits while the target reaches 100%, and stops abruptly with an error. Any suggestions for fixing this? Could be a hardware issue—CrystalDisk isn’t showing any issues on either drive.

Reply
Reply
C
Cramie
Member
Find
238
09-09-2024, 06:34 PM
#2
Sharing an update since I think I uncovered something unexpected. What I thought was resolved didn’t turn out that way. Others might face similar challenges and become confused without a clear debugging path. The problem started after I downloaded files from MEGASync, which seemed to function normally at first. They ended up corrupting certain folders on my E: drive, but I didn’t investigate further. After removing these problematic directories, everything worked perfectly for the backup. I had created many backups during this time and cleared them all. Now I’m trying a fresh clean setup to confirm the fix. I spent several days carefully restoring files, testing each folder step by step. Looking back, I realized my mistake was assuming the issue was on my G: drive when it was actually MEGASync’s files. I learned that Windows Backup prioritizes file backups before system images, which can cause confusion if a backup fails. Also, registering services from a drive triggers system image creation. The solution involved narrowing down the problematic folders through a methodical process, almost like a search. In the end, I narrowed it all down to one folder and managed to fix it. This experience taught me that rushing without understanding can waste time and money. It’s better to focus on clarity and take your time to reproduce the issue properly.
Reply
Reply
C
Cramie
09-09-2024, 06:34 PM #2

Sharing an update since I think I uncovered something unexpected. What I thought was resolved didn’t turn out that way. Others might face similar challenges and become confused without a clear debugging path. The problem started after I downloaded files from MEGASync, which seemed to function normally at first. They ended up corrupting certain folders on my E: drive, but I didn’t investigate further. After removing these problematic directories, everything worked perfectly for the backup. I had created many backups during this time and cleared them all. Now I’m trying a fresh clean setup to confirm the fix. I spent several days carefully restoring files, testing each folder step by step. Looking back, I realized my mistake was assuming the issue was on my G: drive when it was actually MEGASync’s files. I learned that Windows Backup prioritizes file backups before system images, which can cause confusion if a backup fails. Also, registering services from a drive triggers system image creation. The solution involved narrowing down the problematic folders through a methodical process, almost like a search. In the end, I narrowed it all down to one folder and managed to fix it. This experience taught me that rushing without understanding can waste time and money. It’s better to focus on clarity and take your time to reproduce the issue properly.

Reply
Reply