Sandbox/WDAG not opening on domain-connected machine RRS feed

  • Question

  • I have noticed that if I try to launch Windows Sandbox OR Windows Defender Application Guard on a machine that is connected to our domain it will not launch. However, if the machine stays off or leaves the domain these features return back to normal.

    When connected to the domain, this is what I get for the Sandbox:

    Windows Sadbox failed to start

    Error 0x80070569. Logon failure: the user has not been granted the requested logon type at this computer.

    Additionally, when I try to launch Windows Defender Application Guard (WDAG), I receive the following message:

    Application Guard has stopped working. Please try to open your work again.

    Error Code 0x80070569

    Extended Error: 0x00000001

    WDAG Report - Container: Error: 0x80070569, Ext error: 0x00000001; RDP: Error: 0x00000000, Ext error: 0x00000000 Location: 0x00000000

    I am logged in as an administrator both off and on the domain and no matter what machine I try the results are the same. My test machines are Dells with one running  Win10 Pro1903 (OS Build 18362.239) and another running Win10 Pro Insider Preview 1903 (OS Build 18932.1000 - rs pre-release 190628-1650

    Can anyone tell me if they have run into this issue, and if so, what you did to correct it?

    Friday, July 19, 2019 1:23 PM

All replies