New
#20
Quite interesting:
On three of my Insider machines, Sandbox works only on one of them, an i5 Asus laptop. On that laptop, it works perfectly on 18305.1000.
However, after yesterdays CU (KB4483214) which upgraded the build to 18305.1003, Sandbox does no longer work. To be sure, I've repeated this now several times:
- 18305.1000, run Sandbox. It works.
- Update to 18305.1003
- Sandbox does not work
- Revert to 18305.1000 by uninstalling CU
- Again, Sandbox works
- Update to 18305.1003
- Sandbox does not work
Anyone else with same issue?
Kari
Sandbox married to IE, and now they broke that bond?
Jokes aside, I'll test this when I have time.
Thanks for confirming this.
Tweet
— Twitter API (@user) View on Twitter
(@TheRealHariP is from Sandbox team, I just mentioned him to get his attention.)
Tweet
— Twitter API (@user) View on Twitter
Kari
Last edited by Kari; 21 Dec 2018 at 13:15.
I used PowerShell to enable the Sandbox, option two in the tutorial on this version of W10:
After rebooting couple of times, there were couple of changes. One is that the network card had been disabled, showed up on the taskbar with a red x. The VMware player also lost connection to the Internet and would not start the virtual system. There are probably ways to enable the network connection, but I couldn't get the network card working
On the other hand, disabling the SandBox via PowerShell worked flawlessly. Great tutorial Brink...
is this out yet in windows version 1809 OS build 17763.379 ??