Sandbox totally broken


  1. Posts : 194
    Windows 10
       #1

    Sandbox totally broken


    So I wanted to test the Windows 10 Sandbox, which finally was "fixed" with KB4512941, so you can finally at leat open it.

    So... opening works now, and I get this:

    - Permanent 10% svchost.exe usage in Sandbox:

    https://i.imgur.com/Mfk66Gb.png

    - Search doesnt work, clicking into it does nothing

    - Task menu totally broken:

    https://i.imgur.com/1EhTv6I.jpg

    Missing icons in task menu:

    https://i.imgur.com/Pgwbaso.png

    - very slow

    - clicking on start menu button does nothing until you maybe click it 10 times

    - device manager shows lots of missing / broken devices:

    https://i.imgur.com/LJOhvVG.png
    https://i.imgur.com/2h8dRKH.png

    Is this a joke?
      My Computer


  2. Posts : 43,022
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #2

    Some of the known issues are mentioned here:
    Enable or Disable Windows Sandbox in Windows 10

    Note the prerequisites, the build-related comments, and limitations which may relate to some parts of your experience.

    Do you have Home or Pro? Which build?
    Not tried it myself.. but see below..
    Last edited by dalchina; 02 Sep 2019 at 06:35.
      My Computers


  3. Posts : 194
    Windows 10
    Thread Starter
       #3

    I have Pro, otherwise Sandbox wouldnt be included. Latest version 1903 18362.329. The link says
    • When Windows Sandbox is first installed and on every servicing event a setup process will run and trigger significant CPU and disk activity for a minute or so.



    But it seems this never goes away, whenever I open the Sandbox CPU usage is very high even nothing happens and it is very slow.
      My Computer


  4. Posts : 43,022
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #4

    I have Pro, otherwise Sandbox wouldnt be included.
    Enable Windows Sandbox Feature in Windows 10 Home Edition

    and of course virtualisation is enabled on your PC..
      My Computers


  5. Posts : 194
    Windows 10
    Thread Starter
       #5

    Yes VT-d and VT-x are on it is a 8750H CPU with 16GB RAM.
      My Computer


  6. Posts : 43,022
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #6

    My initial experience is that it seems hugely inefficient in terms of resource usage. It took minutes for CPU usage to settle below 30% after launching it:
    Sandbox totally broken-snap-2019-09-02-12.14.48.png

    and is hugely demanding when I launch Edge in the Sandbox (the only thing I bothered to try).

    Its tasbar and search box seemed fine.
    Sandbox totally broken-snap-2019-09-02-12.37.05.png
    (I edited and uploaded these with Sandbox running from normal Windows)

    Device Manager showed
    Sandbox totally broken-snap-2019-09-02-12.46.18.png
      My Computers


  7. Posts : 11,247
    Windows / Linux : Arch Linux
       #7

    Hi there
    Sandbox is a great idea but like most things Ms try at first its implementation is totally cackhanded. It's not fit for purpose at all since there's no "persistency" available --i.e anything you can actually do on Sandbox is lost the next time you re-boot the sandbox or re-start your PC.

    As a Proof of Concept idea -it's OK -- saves having to use a Virtual machine and can of course use Native hardware so you aren't using a "para- virtualised Virtual Machine system".

    However a lot of software and hardware test configurations requires a system re-boot (or a sandbox re-boot) -- and any changes done within the sandbox system are lost when you re-boot the sandbox --Note here I'm not talking about re-booting the main W10 Machine of course.

    So Ms instead of messing around with adjusting the eye candy on a few menu items on the main windows GUI or fiddling around with themes and icon sets - please concentrate on getting what could be great features like the Sandbox to work in a way where you can actually test some proper things on it.

    Cheers
    jimbo
      My Computer


  8. Posts : 194
    windows 10 Home / Latest version
       #8

    I completely agree with jimbo45 that MS screws up just about every new thing they come out with which then takes then months if not years to get it sorted if ever.....Just look at all the hoops you have to go through just to get the stupid thing turned on.....Unacceptable and ridiculous......But typical MS.

    Forget about the stupid MS sandbox and just install Comodo firewall which has a built in sandbox(Now called containment) and enjoy.....Works great on all versions and no hoops to jump through.....What more could you ask for and besides that you are getting,to me at least,the best firewall on the planet.
      My Computer


  9. Posts : 10
    Windows 10
       #9

    Greetings! I'm having the exact same issue and it's driving me nuts.

    Windows 10 Pro N 1909 (Also happened with 1903)
    i7 6700K
    GTX 1070
    VT-d enabled in UEFI
    Can't find a mention of VT-x though

    Beautiful images:
    https://i.imgur.com/96t06uA.png
    https://i.imgur.com/s0kQDf6.png

    In other news, Application Guard doesn't work either. Does it work for you, OP?
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 14:36.
Find Us




Windows 10 Forums