content/posts/windows-backup/index.md

   1 ---
   2 title: "Windows Backup fails with 0x81000037? Check your filesystem"
   3 date: 2023-08-17T17:58:49+02:00
   4 ---
   5 # The Problem
   6 Yesterday, in preparation for a "downgrade" to Windows 10 from 11, I was trying
   7 to make a backup of my Windows files *(using the Windows 7 Backup and Restore
   8 control panel)*. Not long after it actually started copying the files, it spat
   9 out this error:
  10
  11 `Windows Backup failed while trying to read from the shadow copy on one of the
  12 volumes being backed up. Please check in the event logs for any relevant
  13 errors.`
  14
  15 The error code listed was `0x81000037`, and the first thing I did out of
  16 instinct was look this code up. The [official Microsoft support
  17 topic](https://support.microsoft.com/en-us/topic/windows-backup-or-restore-errors-0x80070001-0x81000037-or-0x80070003-e63576a2-22c9-8e90-bdde-e51a9e8e1893)
  18 stated that this error is caused if a reparse point *(Windows slang for
  19 symlink)* points to a FAT volume or is located on a volume containing compressed
  20 files. The listed workaround for this error is to delete the offending reparse
  21 point, and to locate it the topic suggests using the command `dir /al /s`, which
  22 is roughly equivalent to `find -type l` in Unix-like systems.
  23
  24 The first roadblock occurred when I found out that there is no offending reparse
  25 point which could cause this error, so I consulted `eventvwr` and found out that
  26 Windows Backup leaves some logs at `%WINDIR%\Logs\WindowsBackup`. It seemed to
  27 me that there are certain cache files that caused it to fail, so I deleted them
  28 and tried again. The backup again failed and I tried doing this a few more
  29 times, but as nothing helped I eventually gave up.
  30
  31 # The Solution
  32 Having been unable to fix Windows' backup utility, I decided to just copy the
  33 files to the backup drive and copy them over back after the "downgrade". This is
  34 when the actual solution to my problem becomes visible: Windows Explorer
  35 errored, I forgot the exact message by now but it went something like *"The file
  36 XYZ is not available at the location"* or something, searching for the exact
  37 message is as pointless as always.
  38
  39 This usually indicates filesystem errors, so I ran `chkdsk C:` and,
  40 unsurprisingly, it found errors on the filesystem. Besides others, it mentions
  41 the files XYZ that couldn't be copied to the backup drive. I ran `chkdsk /scan
  42 C:`, rebooted through the filesystem error notification that popped up right
  43 after *(`chkdsk /f C:` and reboot will work as well)* and let it fix the errors.
  44 Once it rebooted, the backup completed without errors. After installing Windows
  45 10, restoring the backup was a breeze *(I only had AppData to back up,
  46 everything else was already on other drives)* and so I was quickly up and
  47 running, then amazed by how fast and snappy Windows 10 is compared to its
  48 "successor", but that's worthy of a separate post.
  49
  50 (I don't expect to get around to writing such post anytime soon though.)
  51
  52 # *"Why are you writing about this?"*
  53 As you may know, Microsoft stuff is notorious for being not very well documented
  54 and it's entirely possible *(even if very unlikely)* that someone else encounters
  55 the same issue I have and is left helpless thanks to Windows' lack of a
  56 **proper, easy-to-use, centralized and well-written technical documentation
  57 system** *(think of `man`'s sections 4, 5, 7 and 8 for an idea of what I mean)*,
  58 not to mention countless YouTubers that parrot the same solutions as mentioned
  59 on the web many times before. I hope that this article will be useful to the one
  60 or so person with the same issue that may stumble upon it.
  61
  62 TLDR: Nobody seems to have mentioned this before *(please correct me if I'm
  63 wrong)*, so might as well help the potential other person stuck in the same boat
  64 as me.