virtualbox.org

It is worth noting that this worked perfectly fine with my Debian 8 VM that I used previously. Also, suspending/resuming a Windows 7 VM works with no issues.

Basically, when I attempt to use the feature to save the machine's state, it shows the progress bar as normal, then jumps quickly to 100% and throws the following error message:
And the status changes to "aborted" instead of "saved." Obviously it fails to resume correctly from this state. The host is a computer running 64-bit Windows 10 Pro using version 5.1.26 of VBox with matching guest additions. Not sure what other information I need to include. Please let me know and I'll post what I can.

Can you post the VBox.log and the VBoxSVB.log VBoxSVC.log from such a failed attempt? Both of them zipped please...

EDIT: There is no such thing as a VBoxSVB.log, only VBoxSVC.log.

Did you mean VBoxSVC.log? Or is there VBoxSVB somewhere?

Yes, you are right, it was a typo, the correct one is VBoxSVC.log, thanks for pointing that out!

Now, to your problem. I can't see anything out of the ordinary in the VM or in the logs. The mystery is even greater because you say that other VMs do not have the same problem, like a Win7 VM and your previous Debian8. One thing that I noticed is that you resumed this VM from a saved state. Have you tried shutting it down completely from within the VM and see what happens? I have a feeling that I know the answer, I simply have to ask.

If no one else sees anything weird in the logs, I'd suggest that you should head to the bug tracker and either search for an appropriate bug, or open a new bug report where you'll attach your logs and other vital information.

If I shut down from within the VM, it takes a while to do several stop jobs but it does seem to shut down cleanly.

But I just attempted to start it up again so I could get a log from a clean shutdown and it gave me the error message from my original post when I was about to unlock the OS disk, which is encrypted. Went to "aborted" status again. I'm including the logs from that occurrence just in case they are of any help, and also the log from a successful shutdown, which I was able to do on my second try.

I would appreciate any help if anyone knows why this is behaving so strangely. I've been using VBox for quite some time and I've never come across something like this.