One big ask, sandbox compatibility

thmtrxhsu

New Member
What could this big ask be? Something that has plagued almost every nlite user surely. Getting the damn sandbox to work. Any magic is acceptable but must be disguised as “sandbox compatibility” option.

Should you choose to undergo this quest I shall provide guidance simply show willingness.
 
What could this big ask be? Something that has plagued almost every nlite user surely. Getting the damn sandbox to work. Any magic is acceptable but must be disguised as “sandbox compatibility” option.

Should you choose to undergo this quest I shall provide guidance simply show willingness.
Sure, I'm always open for expanding Compatibility options, if that's what you're aiming at.

Simply provide a preset that you expected to work, and tell me on what or with what to test the sandbox, is it a third party tool, an Edge isolation, Container etc.

Of course it must be confirmed working with all else the same, except removals.
 
Yes I can provide very precise instructions.
1. Get Rufus
2. Use the Image downloader feature part of Rufus and download 20H2, the December one, English, Education Edition.
3. Mount such image in NTLite, mount Education N, in particular.
4. Load the Lite-Safe99999 preset..
5. Process it.
6. Put it on USB, install in real machine (tested in real machine), Sandbox works.
ALL other presets fail, and most interestingly have a tendency to fail with new error codes, particular the last 5 presets with Lite-Safe99999 being the last. I interpret it as MS giving the middle finger, exploding the sandbox API(not the API but all the backbones) all over the place deliberately.

And rest assured Garlin that sandbox compatibility is not assured by "App Guard/Containers", like not even close.
It's annoying complicated, but I did greatly narrow it down turning a huge problem into a manageable one.
The preset before Lite-Safe999 was close to success. I know 100% it related to drivers for that preset, but did it only relate to drivers somebody only as knowledgeable as nuhi could answer easily.

Please remove the attachment once you have it in hand.
 
Last edited by a moderator:
Why did you remove the VHD drivers (vhdmp.inf, virtdisk.inf)?
An example of how VHD files are used is the Hyper-V feature in Windows 7, Windows Server 2008, Virtual Server, and Windows Virtual PC. These products use the VHD API to contain the Windows operating system image utilized by a virtual machine as its system boot disk.

NTLite can easily extend Containers or Hyper-V protection to cover kernel-mode drivers.
PS -- VSS (shadow copy) probably doesn't work w/o volsnap.inf
 
garlin

For critics to be valid, the critic must demonstrate first of all that they understand the whole message not just pieces they "choose" to understand.
On this you fail, and thus your critic fails.
The most essential part of what I said was "last five presets generate new and unique sandbox error messages." Somehow, you saw past the most essential part.

Why do we need sandbox compatibility option? Because any number of a few dozen things will cause it to fail at runtime.
My biggest problem with your critic is you need to make sense as a whole, not just in part.
You have a good point in part absolutely, but as a whole I can discard your whole message altogether.
Put another way, keeping referred drivers, containers and Hyper-V protection is extremely insufficient for ensuring the sandbox works.
This is a matter of fact, yours a matter of fantasy.
 
I feel like I'm being trolled. Read your last 4 presets, even diff'ed them; but your progression of system changes jumps around.
Frankly it's too much work to compare each image in a VM, due to the changelog.

Since you got this in the bag, reduce it to a test case of exactly which removals break Sandbox. Asking folks to review a pile of randomly different presets doesn't cut it -- Just surprise me.
 
are sandboxes more commonly used than VM's ?

dont think i know anyone personally who uses a sandbox, apart from the neighbours kid
 
Guys, let's show a bit more respect to a reported case.
Since there is a compatibility for Containers, he can post any preset that breaks it with that enabled, plus there is one that works as a bonus, for me that's enough.
All the other presets are a bit of a bloat, very easy to ignore.

Testing, haven't confirmed any of the claims yet, slow Sunday.
 
thmtrxhsu, one is the 'Storage Quality of Service (Storage QoS)' removal.
Adding that component to the AppGuard/Containers compatibility option.

Continuing tomorrow, found at least one more when loading all the presets at once.
 
Huh, Sandbox is using a lot of components, as it's a virtual machine with a remote desktop connection to it as far as I see.

These and more are needed from your presets:
"Storage Quality of Service (Storage QoS)"
"Network Adapter Multiplexor Protocol"
"Enhanced Storage"
"Remote FX"

But then retesting all at once, especially with Servicing Stack disabled, it does not work, needs more - especially earlier mentioned virtual drivers.
Continuing tomorrow, just wanted to note that I haven't given up, just testing takes long for these kind of scenarios.
 
I think it's done, sending you a test version for confirmation of the new Containers compatibility upgrade.

Thanks for your patience.
 
Back
Top