System Image Error 0x81000036

Windows 10 Insider Preview error 0x81000036 with Create a system image
A solution to error 0x81000036 using Backup and Restore (Windows 7) in Windows 10 Insider Previews when trying to create a system image

Using Backup and Restore (Windows 7), I had been unable to “Create a system image” using Windows Insider Program builds going as far back as build 18850. I am currently running Windows 10 Insider Preview Build 18963 (20H1) on a Boot Camp partition on a MacBook Pro (Retina, 15-inch, Mid 2012).

Attempting to Create a system Image would bring up the dialog box, “Where do you want to save the backup” and it would fail with another dialog box with the text:

Windows could not find backup devices on this computer. The following information might explain why this problem occurred:

(0x81000036)

Close Windows Backup and try again.

I searched the Windows Insider Feedback Hub, googled the web and Microsoft forums and I didn’t find a solution until a few days ago. On the Feedback Hub, in a post with the title, “Cannot create System Image in build 18956 FIX IT!“, CJH suggested disabling Windows Sandbox and virtual machine.

Windows 10 Feedback Hub
Windows 10 Feedback Hub

After disabling Windows Sandbox (Control Panel/Programs/Turn Windows features on or off/Windows Sandbox) I was able to create a system image again. I initially disabled Hyper-V Manager but after re-enabling it, system image still worked.

MacFUSE file system is not available Error

I try to keep up with the latest Windows and macOSs by participating in the Windows Insider Preview program and the Apple Developer Program. I run both of these OSs on a Macbook Pro Retina (mid-2012). As of today, that is Windows 10 Build 16232.1000 and macOS 10.13 beta 2 (17A291m).

A lot of the time, things don’t work because I am running beta OSs with released apps.

One of the recent problems I encountered with macOS High Sierra (17A291j) was a kernel panic when I was using Paragon NTFS for Mac 15 with Dropbox (v30.3.14). I don’t know if it’s a good idea, but my Dropbox directory for both Windows and Mac is the same directory on an NTFS volume. Every time I started Dropbox, I would get a kernel panic. I opened a support ticket with Paragon Software and a few days later they sent me a new version that had the same problem.

For interoperability between the two OSs, read/write capability really helps. In the macOS (High Sierra), NTFS read/write capability is not native. I was very happy with Paragon NTFS for Mac 15 until I started getting kernel panics. On the Windows side, I haven’t found something that will read the Apple File System (APFS) in macOS 10.13.

With earlier versions of MacOS, I had used the open source NTFS-3g. When Paragon NTFS for Mac 15 stopped working in my situation with Dropbox, I decided to try the commercial version of Tuxera’s NTFS for Mac. This seemed to work ok until I installed the macOS High Sierra Developer Beta 2 Update 1 (17A291m).

On booting macOS, I would get the error message:

Aligned I/O enabled.
CBCIO enabled.
/System/Library/Filesystems/fusefs_txantfs.fs//Support/10.9/tufs/tufsfs.kext failed to load -… check the system/kernel logs for errors or try kextutil(8).
the MacFUSE file system is not available (71)

I traced this error to Gatekeeper in macOS 10.13. After I allowed the software, Tuxera NTFS for Mac started working again.

Allow software from Tuxera in macOS System Preferences Security & Privacy Setting
Allow software from Tuxera in macOS System Preferences Security & Privacy Setting