@ Tonyb , this is a tad embarrassing. All those errors showing were red herrings. Although virtualisation showed as enabled, the error code and the VMICTimeProvider was not supported, I decided to boot to the hybrid BIOS/EFI on this old 2012 HP laptop has. Looking around this barren waste there was a setting to enable ' Virtual Technology', which I did - rebooted - re-enabled Sandbox -rebooted and is working now.
i will go see if there is anything in my Bios like that i know for a fact virtualization is on , but i will go have another look around this Bios.
i even checked with DISM nothing seems to be wrongi don't get it what else can i do.
Giving up on this dumb messed up joke of a idea from Microsoft if anyone has ideas how to get what i'm calling the biggest joke of the decade let me know, MS answer with paid support reinstall it so they did nothing, then they did a refresh nothing works, according to them it should work YEAH WRIGHT MS, back to the drawing board i think it needs to go. if any computer smart guys have a clue let me know i'm done racking my brain and paying for support for something that won't work.
this is what it looks like in task managerand this is what it looks like all the time for me.
Internet Connection Sharing must be set to Automatic, otherwise if set to manual Sandbox won't start.
how do i do that ?? were did they hide it in windows 10 pro ??
ok i found it in services i will see if it works now
I'm able to reproduce the exact same issue: Stalls in the blue screen and getting the error after about 7-10 minutes.
In services, this one too seems to be responsible for the bug. Plus the one mentioned above.
Hyper-V Remote Desktop Virtualization Service
They must be set to automatic. The message is from Sandbox.
Quote
