I've been trying to get Sandboxie to run a 2nd instance of Stronghold Kingdoms, like shown here https://www.youtube.com/watch?v=3nKGNvDaTEk. When I select "Run Sandboxed" from the right click menu, the game starts up and when it come time to load the 3d window I get "There is a problem with Directx, please contact support.I know it works because my friend uses it to do the same thing.
Win 10 (fresh install and up to date drivers)
FX-9370
HD 7850
Directx Error
Moderator: Barb@Invincea
-
- Sandboxie Support
- Posts: 27
- Joined: Tue Oct 04, 2016 4:05 pm
Re: Directx Error
@tekgeek
What version of Sandboxie do you have? Are you running one instance outside of sandboxie and another instance within?
What version of Sandboxie do you have? Are you running one instance outside of sandboxie and another instance within?
Re: Directx Error
I think Chris might be correct here, assuming I'm thinking the same thing he was.
All of this is only relevant if you are running one instance unsandboxed to start with however. If it's a matter of running two sandboxed then it is not something you would eventually see a fix for as this would more likely be related to an intentional restriction by the games devs and Sandboxie will not attempt to hide its presence or that of other processes running on the computer.
There is currently an issue that involves the Anniversary update of Windows 10, SBIE and some newer drivers. While the title implies it is only an NVIDIA issue, it has also been seen with some AMD GPUs [Not with mine apparently, it's the same driver so what's up with that? It does occur on my kids Win10 PC though...which happens to have an NVIDIA card] and Curt was nice enough to let us know a few of the more specific details:Are you running one instance outside of sandboxie and another instance within?
I'm still confused as to how an older driver works fine if it's a MS change but I expect he has a better understanding than I do on the matter! I'm more inclined to blame the newer drivers with what I have seen :P /me inserts random thought...what if it's linked to the new SHA2 rules [or more likely the timestamp shift?] for the AU and follows a different routine if the driver is so signed after that point? That might explain it but it's pure [and likely wrong] drunken guesswork on my part.It is not an Nvidia problem per se (though their driver has a lot of other issues). It is a DirectX problem and affects a lot more than just games. In the Win 10 anniv. update, MS changed DirectX to use a lot of "Immersive" controls & dialogs, which currently cannot be loaded in Sandboxie because they use RPC to communicate outside the sandbox.
All of this is only relevant if you are running one instance unsandboxed to start with however. If it's a matter of running two sandboxed then it is not something you would eventually see a fix for as this would more likely be related to an intentional restriction by the games devs and Sandboxie will not attempt to hide its presence or that of other processes running on the computer.
Goo.gl/p8qFCf
Who is online
Users browsing this forum: No registered users and 1 guest