request: best practices tutorial for troubleshooting sandboxed installers/applications

sandb0xie

Member
(If this already exists, would love to get a link to it.)

Many times when attempting to install or run an application, the installation/app will fail without providing meaningful logs or trace entries.

Wonderful people like @DavidXanatos , @bastik-1001 and @offhub help to troubleshoot here, but obviously the more the user can ascertain independently, without having to take up others' time in troubleshooting, the better.

Is there a writeup or tutorial on the best, most straightforward ways to track down sandboxed installer/application issues such that the specific problems are quickly identified, understood and worked around or fixed? It would seem this would involve a list of commonly-used .ini tweaks and Sandboxie-Plus settings that help with a broad swath of applications; and then a list of tools (Xanatos TaskExplorer, ProcMon, etc.) and how to quickly use these to resolve the issues (perhaps IPC, COM, pipes, registry, etc.). without being a world-class expert in those issues.

As an example: Most of the installers from iZotope here will fail to install in a Sandboxie-Plus sandbox:

Trying, let's say, the installer for VEA: It just reports "an error." No logs are generated and, unless something is being missed, no useful traces are available. Many different common settings have been tried in Sandboxie-Plus, but these iZotope installers just fail. When basic Sandboxie-Plus settings alone do not achieve the desired results, what are the best methods to proceed and figure out the issues?
 
Back
Top