Windows Sandbox is a feature bundled with Windows 10 version 1903 and newer, and it allows users to operate another demonstration of the operating-system which makes it possible to test apps and services securely.
A lot more like an online machine that comes with Windows 10, the separate OS instance runs in a sandbox, and never only that all system files are protected, but all changes are automatically reset once the application is closed.
Needless to say, Windows Sandbox addresses a lot of users’ need of a secure testing environment and makes deploying apps like VirtualBox and others fairly unnecessary.
But as it sometimes happens in the Windows world, you will find things that occasional break down, and this time, it’s Windows Sandbox’s turn to hit this issue. Fortunately, there’s an easy fix for users encountering this, so continue reading to discover everything about this latest bug within the Windows world.
Based on Microsoft itself, there’s now a launch error that affects both Windows Sandbox and Windows Defender Application Guard, or WDAG. Quite simply, if you try to operate any of these two, you end up with an error preventing you against using them.
The issue happens on the following Windows 10 versions (keep in mind that Windows Sandbox debuted in Windows 10 version 1903, so any versions of the operating system that are over the age of this won’t include the feature built-in):
Worth noting would be that the issue is also experienced on Windows 10 version 2004, the most recent feature update that Microsoft rolled out it. This version is currently being made available to users in phases, but part of those who have already received the update might thus struggle to run Windows Sandbox or WDAG.
And also the error which you may experience, as explained by Microsoft in a support document spotted by TechDows, reads the next:
ERROR_VSMB_SAVED_STATE_FILE_NOT_FOUND (0xC0370400)” or “E_PATHNOTFOUND (0x80070003)
There’s only one workaround available right now, based on Microsoft, and it’s actually much easier than you’d expect it to be. And all you have to do is reboot the computer.
“To mitigate this problem after receiving one of the above error messages, you will have to restart your device,” Microsoft says.
As for a complete fix, the software giant explains that it’s already working on it, which you ought to participate a future update. At this point, however, no specifics have been provided on the ETA s to once the patch may go love users.
Important to note, however, is that the next Patch Tuesday cycle takes place on August 11 – this is actually the date when Microsoft will release new cumulative updates for those Windows 10 versions, and likewise to security fixes, the organization also typically resolves some non-security problems too. Right now, however, we don’t have a confirmation the August Patch Tuesday is supposed to resolve this problem.
Windows Sandbox is only on Windows 10 Pro and Enterprise SKUs, therefore if you’re running the Home version, the feature isn’t there. Users also need to enable it manually on Windows 10 Pro and Enterprise in the optional features screen in the operating-system.
However, users can also manually enable Windows Sandbox in Windows 10 Home too using a custom batch file that needs to operate on a tool running at least version 1903.