I absolutely feel it is not ready for prime time. It's also not compatible with VMware. I had to uninstall it and revert the Windows Defender settings it changed to get my vm's to boot. Maybe I'll revisit it in the future but for now it's not worth my time. The current quality seems like it should be below Mixrosoft's standards to release it yet.
It's absolute garbage for me. What a POS app this is. And no it's not a firewall issue and I've Googled all possible suggestions to fix it with none of them working. It has no Internet connection whatsoever and it takes quite some time just to start up and and show all taskbar launchers before it can be used at all.
No. I don't know what the problem is yet. I'm not too concerned about it either. Maybe in due time Microsoft will improve it.
Then I dunno. My issue at first was that WS doesn't like OpenVPN one bit. I use TunSafe now and it's working great.
Hello. wat0114. In my case WS had no internet connection either and eventually found out that the Avast Firewall was somehow blocking it. The only way i could get my WS to connect with Avast Internet Security installed was to temporarily disable the firewall component. Then start up WS and i would now get internet connection in the WS. I hope Avast are working on this. Now in regards to VMware, if you're getting this message Then do the following 1. Run a command prompt in Admin mode 2. Run this "bcdedit /set hypervisorlaunchtype off" (without the quotes) 3. REBOOT 4. Now VMWare should boot This however has a side effect on my system in that Windows Sandbox will not boot while hypervisor is set to "off". Dont know if it will have the same effect on your system. However all is not lost. To reverse all of this run the following in a Command prompt in admin mode bcdedit /set hypervisorlaunchtype auto REBOOT and your system should be back to the way is was before. Hopefully between MS, VMW and Avast they can sort this all out......eventually.
Hi I have W10 64bit Pro and therefore the Windows sandbox. On my regular Os i can see that it is activated, but the sandboxed Os is - unactivated. Is that the way it should be or what is up?
To be clearer; my regular Os-version is activated but, the sandboxed Os-version says, in settings, that IT, is not. I thought that if the Os is activated, it is activated, sandboxed or not.
You can use it on Windows 10 Home easily with the info and script included here: https://www.tenforums.com/tutorials...-sandbox-feature-windows-10-home-edition.html
Just updated Win10 Pro to latest version containing Windows Sandbox. Think of switching to it and abandoning long time beloved Sandboxie. Have not played with WS yet. According to this article you can open a browser inside of WS, at least Edge. Author compared opening Edge inside of WS to "creating a sort of sandbox within a Sandbox". https://www.pcworld.com/article/3338084/how-to-use-windows-sandbox-microsoft.html Opinions, feelings? Thanks, Acadia
Well, it seems that it doesn't offer the same amount as options as Sandboxie. So it's up to you if you can live with that. It depends on if you need certain stuff of not.
Anything is possible but I have my doubts. If you want more features there are better tools for free (VirtualBox, Sandboxie, etc.).