Windows 10: Error, 0x80070003/0xC0370400 in Sandbox and WDAG

[German]Users of Windows 10 can be annoyed by two errors in versions 1903 up to 2004. Both the Windows Sandbox and the Windows Defender Application Guard (WDAG) are affected by errrors 0xC0370400 and 0x80070003. Microsoft has confirmed these issues as of July 24, 2020 and plans to release a fix at some point.


First of all: Both errors only affect the commercial versions of Windows 10, because the Windows Sandbox (for virtualization) as well as the Windows Defender Application Guard (WDAG) are not available in Windows 10 Home.

The error codes 0x80070003 and 0xC0370400

The first error code 0x80070003 stands for E_PATHNOTFOUND and is an error indicating incorrect path information. The second error code 0xC0370400 stands for ERROR_VSMB_SAVED_STATE_FILE_NOT_FOUND and also describes a state where a required file with a stored state cannot be found. Both errors should not actually occur in a cleanly implemented operating system environment.

Windows Sandbox and WDAG affected

The two error codes 0x80070003 and 0xC0370400 can occur both with Windows Defender Application Guard (WDAG) and when opening the Windows Sandbox, as Microsoft states in the support document Receiving an error message when attempting to open Windows Defender Application Guard (WDAG) or Windows Sandbox. The issues affects the following Windows 10 versions::

  • Windows 10 Pro Version 1903
  • Windows 10 Enterprise Version 1903
  • Windows 10 Pro Version 1909
  • Windows 10 Enterprise Version 1909
  • Windows 10 Pro Version 2004
  • Windows 10 Enterprise Version 2004

The relevant features such as the Windows Sandbox or the Windows Defender Application Guard (WDAG) cannot then be used, after the error occurs. Microsoft suggests restarting the system as a workaround. The developers are currently working on eliminating the causes of the errors and plan to provide an update in a future version.

The developers in this area probably do not have such a lucky hand. I recall the sandbox error 0xc0370106, which made the sandbox, which was recently introduced in Windows 10 version 1903, simply unusable for many users for months. And also the Windows Defender Application Gurad (WDAG) always had bugs that annoyed the users (see links at the end of the article). Since WDAG is touted as a security feature, the bug is doubly bitter. In my eyes, this is a no-go in an enterprise environment. (via)


Similar articles
Windows 10 V1903: Update KB4497936 breaks Sandbox
Windows 10: Update KB4483214 breaks Sandbox mode
Windows 10 gets Sandbox for applications
Windows 10 V1903: Sandbox fails with error 0xc0370106
Wrong language in Windows Defender Application Guard
Windows 10 Insider Build 17713.1002 breaks Defender Application Guard

Cookies helps to fund this blog: Cookie settings

This entry was posted in Windows and tagged , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *