Windows Sandbox issue finally resolved in Windows 10

Sep 2, 2019 11:46 GMT  ·  By

The most recent cumulative update released by Microsoft for Windows 10 version 1903 resolve a bug hitting Windows Sandbox after the installation of another update.

Specifically, Microsoft acknowledged a bug breaking down Windows Sandbox after installing cumulative update KB4505057, which was published by the company on May 20. Microsoft explained the following:

“Windows Sandbox may fail to start with "ERROR_FILE_NOT_FOUND (0x80070002)" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.”

The issue was finally corrected with the release of Windows 10 cumulative update KB4512941 on August 30, with the company explaining that Windows Sandbox should now works correctly on all devices, regardless of the changes made during the update process.

Windows Sandbox

Windows Sandbox is one of the key additions to Windows 10 May 2019 Update (version 1903), and it allows users to run apps and browse the web in a secure environment. More like a virtual machine, Windows Sandbox comes pre-loaded on Windows 10, so once installed it can be easily launched just like a typical application.

Running apps in isolation is essential for testing untrusted software, and Windows Sandbox is designed in such a way that every time you close it, everything is removed and its settings are returned to normal. In other words, every time you launch Windows Sandbox you find it completely clean, without any files that you previously launched in the secure environment.

The most recent cumulative update, however, might be causing high CPU usage on devices where it’s installed. Users report that after deploying this update, a process associated with Cortana records huge CPU spikes. Microsoft is yet to acknowledge this problem, albeit given the number of reports, there’s a chance the company is already looking into it.