virtualbox.org

After the latest Windows 10 Update (2019-09 Cumulative Update for Windows 10 for x64-based Systems, Version 1903 (KB4515384) ■ Build 18362.356), Event ID 131 occurs in the Event Viewer.

Metadata staging failed, result=0x80070057 for container '{D397268A-724C-B4EF-D641-C9234BA2948B}'
Metadata staging failed, result=0x8007000D for container '{00000000-0000-0000-FFFF-FFFFFFFFFFFF}'
Metadata staging failed, result=0x80070057 for container '{ED17222B-F1C7-537F-9546-745658ADE2E3}'

The problem occurs on Windows 10 (64-bit) Guest only. To isolate the issue, I have created a new VM on Windows 10 (64-bit) Host and launched Windows Update in the Windows 10 (64-bit) Guest.
There are no such events on Windows 10 (64-bit) Host and Windows 10 (32-bit) Guest.

VirtualBox version: 6.0.12.
The problem exists both with installed Guest Additions and without Guest Additions.

And why would that be a VirtualBox issue?

I'm not sure, but the problem is only present on the VirtualBox Guests (Windows 10, 64-bit).
If you (or someone else) use the same OS (Build 18362.356) on your guest and you see similar events in the Event Viewer, please let me know.
Thanks

New to this forum, but if you do a 'Google' search for "meta data staging failed" you'll find that it has been a relatively common Windows error on real hardware for several years. You should probably pursue the approach that you would do if it happened on a Windows Host installation and forget the fact that you are using a Virtual Machine.

2multiOS

1. The problem started only after the last Windows 10 Update (Build 18362.356) and only in the Windows 10 (64-bit) guest.
2. Windows 10 (64-bit) Host (on this PC) does not have this problem.
3. All of Google's suggestions regarding "Metadata staging failed" didn't help me solve this issue. I tried:
   1. I changed device installation settings (Turning off the updates)
   2. I changed the address devices metadata in the Registry from go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409 to http://dmd.metaservices.microsoft.com/dms/metadata.svc.

I just want to know if anyone else has this problem.

Just because an OS/program that runs in the context of VirtualBox has a problem, it doesn't make it a VirtualBox problem necessarily. You're having an issue that has most probably nothing to do with VirtualBox, so my suggestion would be to treat it as such, as a native problem with the guest OS, and start searching in the appropriate forums.

I don't have it on two Win10 VMs that I have, one 32- and one 64-bit...