{"id":10298,"date":"2019-07-01T18:46:17","date_gmt":"2019-07-01T16:46:17","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=10298"},"modified":"2019-07-24T19:12:28","modified_gmt":"2019-07-24T17:12:28","slug":"windows-10-v1903-sandbox-fails-with-error-0xc0370106","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2019\/07\/01\/windows-10-v1903-sandbox-fails-with-error-0xc0370106\/","title":{"rendered":"Windows 10 V1903: Sandbox fails with error 0xc0370106"},"content":{"rendered":"

[German<\/a>]Users of the Windows Sandbox included in the Windows 10 May 2019 Update now get the error code 0xc0370106 displayed when calling it. Microsoft seems to have broken this feature again. This time we have probably to blame the latest Intel Microcode Update.<\/p>\n

<\/p>\n

Windows 10 Sandbox mode<\/h2>\n

\"\"Last year, in December, Microsoft introduced Windows Sandbox<\/a>, an isolated, temporary, desktop environment where users can run untrusted software without the fear of lasting impact to the system. Any software installed in Windows Sandbox stays only in the sandbox and cannot affect the host. Once Windows Sandbox is closed, all the software with all its files and state are permanently deleted.<\/p>\n

\"Optional<\/p>\n

Windows Sandbox is part of Windows 10 Pro and Enterprise and may be installed as a feature. Every time Windows Sandbox runs, it's as clean as a brand-new installation of Windows. Windows Sandbox has been introduced in Windows 10 Pro or Enterprise Insider build 18305 or later \u2013 so it's also part of Windows 10 Mai 2019 Update (version 1903).<\/p>\n

Windows Sandbox uses Hyper-V, which will be activated. So enabling the Sandbox mode will prevent VirtualBox and VMWare from running on the same computer.<\/p><\/blockquote>\n

No luck with Windows Sandbox<\/h2>\n

For users of a non-English Windows 10 V1903 the Windows Sandbox is a mirage. After the release of the Windows 10 May 2019 update (version 1903) German users found out that the Windows Sandbox crashed with the error 0x80070002 (a file could not be found).<\/p>\n

The issue was caused by the KB4497936 cumulative update that Microsoft released for this version of Windows. More details on this topic I had gathered in the blog post Windows Windows 10 V1903: Update KB4497936 breaks Sandbox<\/a>. Until July 1, 2019) there is no fix from Microsoft, which is why I could not use this feature.<\/p>\n

Windows Sandbox crashes with error 0xc0370106<\/h2>\n

Today I got this comment<\/a> from a German blog reader who has become aware of another problem in connection with the Windows Sandbox. The user wrote:<\/p>\n

I now get since 07\/01\/2019 the following: Error 0xc0370106. the computer or container was terminated unexpectedly.<\/p><\/blockquote>\n

The blog reader asks if there is more information. Yes, there is – here is briefly compiled together turned what I know so far. Error 0xc0370106 isn't new, 2017 it hit users of docker<\/a> containers when they installed Windows 10 Creators Update (V1703). But now we are talking about Windows 10 May 2019 Update (version 1903) and the Windows Sandbox, a completely different thing.<\/p>\n

But searching the internet shows that the bug seems to hit some people who are experimenting with the Sandbox in Windows 10 V1903. A search on the Internet for error 0xc0370106 showed me, that this error has been reported since the end of June 2019 (June 27-30, 2019) (here<\/a>, here<\/a> and here<\/a>). Also on reddit.com there is this contribution<\/a> to the error since some days.<\/p>\n

\"Windows<\/p>\n

The error code 0xc0370106 stands for ERROR_VMCOMPUTE_UNEXPECTED_EXIT, i.e. the virtual Hyper-V machine of the Windows sandbox is supported by an unexpected error. This is in accordance with the German error description that the user left as a comment.<\/p>\n

The usual repair mechanisms like dism \/scanhealth <\/em>etc. doesn't help. But since it is noticeable that this error code was reported at the end of the month, I guess that the cumulative update KB4501375<\/a> released on June 28, 2019 may causes this crash. I can't judge finally about that, because I fired up my German test machine within Windows 10 V1903, which has not been booted for a long time, I just activated and tested the sandbox again. There it crashed with the error 0x8007000002 described above (a file could not be found).<\/p>\n

I found this forum entry<\/a> from end of May 2019\/Start of June, who is claiming Microcode Update KB4497165 is causing this issue. The user noted, that the Windows Sandbox is crashing with error 0xc0370106 since than. The user was running OS build 18362.145 of Windows 10 V1903. This cumulative update KB4497935 has been announced<\/a> on May 24,\u00a0 2019 within Windows-Blog for Preview Build 18362.<\/p><\/blockquote>\n

\"Windows<\/p>\n

I then let the machine search for updates and was offered a .NET Framework 3.5 update KB4502584 and the cumulative update KB4501375. For further update searches the cumulative update KB4503293 was offered. But at the end of the day, after installing all updates, my machine drops error 0x80007057 \"wrong parameter\" \u2013 if I try to launch the Windows Sandbox.<\/p>\n

\"Windows<\/p>\n

In an additional step I change the machine's language to English, uninstalled the sandbox and installed it again. Then I ended with 0x80070002. I haven't the nerve to do a clean install with an English Windows 10 V1903. Software as a service, and I'm asking who is testing that stuff at Microsoft. It doesn't make really fun to use Windows 10.<\/p>\n

Blame Intel Microcode Update KB4497165<\/h3>\n

Addendum:<\/strong> It seems, that Microsofts Intel Microcode Updates for several CPUs is causing that crash in Windows Sandbox.\u00a0I had already mentioned it briefly in the above note: An old post came to my attention where a microcode update from May is mentioned as the cause. Also German blog reader Andr\u00e9 left a comment that points in this direction.<\/p>\n

Now I got a mail from a German blog reader who confirms my suspicion. He claims to have reported the bug on 05\/27\/2019 as a ticket to Microsoft.\u00a0The reason for the error is the installation of the microcode update \u00a0KB4497165<\/a>, but the May version (to be found in the Microsoft Update Catalog<\/a>). Microsoft re-released the microcode update on 06\/17\/2019 (without further details). According to the information, the blog reader left to me, Microsoft was able to reproduce the issue, but has no solution and does not document anything as a know issue. Uninstalling KB4497165 from May 2019 solves the issue with error 0xC0370106 described here. That makes sense (my machine did not get such updates).<\/p>\n

Addendum 2:<\/strong> It seems that Microsoft is testing a fix – see my blog post here<\/a>.<\/p>\n

Similar articles
\n<\/strong>Windows 10 V1903: Update KB4497936 breaks Sandbox<\/a>
\nWindows 10: Update KB4483214 breaks Sandbox mode<\/a>
\nWindows 10 gets Sandbox for applications<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

[German]Users of the Windows Sandbox included in the Windows 10 May 2019 Update now get the error code 0xc0370106 displayed when calling it. Microsoft seems to have broken this feature again. This time we have probably to blame the latest … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[22,1218,2],"tags":[2013,2011,1890,2012],"class_list":["post-10298","post","type-post","status-publish","format-standard","hentry","category-update","category-virtualization","category-windows","tag-error-0xc0370106","tag-update-kb4501375","tag-windows-10-v1903","tag-windows-sandbox"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/10298","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=10298"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/10298\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=10298"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=10298"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=10298"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}