That libfuse.so error is a classic architecture mismatch headache—usually happens when the linker tries to grab a 32-bit lib for a 64-bit build (or vice versa). Double-check your library paths to make sure it's not pulling from a legacy directory.
On a side note, while I was cleaning up some of my own project scripts today, I came across this utility for SOAP to JSON conversion. I know it’s a bit of a tangent from the FUSE issue, but if any of you are dealing with older web services while modernizing your stack, it’s a total lifesaver.

If you're looking for a quick way to verify those files without running a full restoration test every single time, you can usually run a checksum comparison (MD5 or SHA256) against the original data.
For a more 'point and click' approach to double-check specific files or verify hashes quickly, I've used https://thetoolapp.com/utilities/file-integrity-checker/ before. It’s pretty handy for a quick integrity check if you aren't in the mood to mess around with the command line for every single backup set.

I've seen this happen after a BIOS update or if a CMOS battery starts failing. Sometimes the motherboard resets to 'Legacy' instead of 'UEFI' (or vice versa), and GRUB just loses its mind because it can't find the partition it expects. It’s worth a quick check in your firmware settings to make sure the boot mode and the drive order haven't shifted on you.

That is a frustrating loop to be in, especially with TrueNAS. Usually, when the VM fails to start after a change, it’s because XCP-ng is trying to pass through a PCI device (like an HBA) that isn't being released properly by the host.
Have you checked if the "hide" parameters in your grub config are still correct? Sometimes an update can reset those, and the host grabs the controller before the VM can. Another thing to try is toggling the BIOS/UEFI mode in the VM settings - TrueNAS can be picky about that depending on which version you’re running.

Setting up a solid backup strategy is always such a relief once it's actually dialed in. It's really helpful to see the different approaches laid out like this, especially for finding that balance between reliability and ease of use. This definitely gives some good food for thought for anyone looking to refine their setup.

Ugh, RDP freezing up on Windows 11 24H2? That's a pain! It sounds like you're not alone, though. There's been some chatter about RDP acting a bit wonky after the 24H2 update.
From what I've seen, it might be related to how it handles network stuff, especially when reconnecting. Some folks have found that tweaking the network detection settings on the server side can help. It's a bit techy, but it involves going into the Local Group Policy Editor (type gpedit.msc in the Run dialog) and messing with the "Select network detection on the server" setting under Remote Desktop Services. You'd enable it and then tell it to turn off the "Connect Time Detect and Continuous Network Detect" options.
Alternatively, some people have had luck by messing with the Remote Desktop Connection settings on the client side, like setting the "Experience" tab to "WAN" instead of "Automatic" or even disabling the desktop wallpaper. It sounds weird, but sometimes those visual things can cause hiccups.
There's also talk about recent Windows updates causing some of these issues, so making sure you're on the very latest updates might have a fix baked in. Keep an eye out for any new patches from Microsoft.

If none of these solutions work, you can follow for more details instruction below.
https://thegeekpage.com/rdp-freezes-or-hangs-on-windows-11-24h2-how-to-fix/