-
Notifications
You must be signed in to change notification settings - Fork 29
Description
JASP Version
0.95.0
Commit ID
No response
JASP Module
Other
What analysis are you seeing the problem on?
Security Sandbox Failure Failed to activate Security Sandbox. Your system does not allow security sandboxing. Do you wish to continue with out is? (probably fine)
What OS are you seeing the problem on?
Windows 10
Bug Description
Bug Description (JASP – Security Sandbox Failure):
When attempting to run an analysis in JASP (e.g., Unidimensional Reliability), a pop-up error message appears stating:
Security Sandbox Failure
Failed to activate Security Sandbox. Your system does not allow security sandboxing.
Do you wish to continue with out is? (probably fine)
This prevents the engine of the module (e.g., Reliability) from initializing correctly, leaving the analysis window stuck at “Waiting for initialization (of the engine) of module”.
Steps observed:
Load dataset into JASP.
Select Reliability → Unidimensional Reliability.
Error message appears and analysis does not proceed.
Expected Behaviour
Expected Behaviour
When selecting Reliability → Unidimensional Reliability, JASP should initialize the Reliability module without errors. The analysis engine should start normally, allowing the user to select variables and compute reliability statistics (e.g., Cronbach’s alpha) without interruption or sandbox-related error messages.
Steps to Reproduce
Steps to Reproduce
Open JASP on Windows.
Load a dataset (e.g., .sav, .csv, or .ods).
Go to the top menu and select Reliability → Unidimensional Reliability.
The software shows the error message "Security Sandbox Failure – Failed to activate Security Sandbox. Your system does not allow security sandboxing."
The module stays in the state “Waiting for initialization (of the engine) of module: Reliability” and does not proceed with the analysis.
Log (if any)


More Debug Information
JASP 0.95.1.0
Final Checklist
- I have included a screenshot showcasing the issue, if possible.
- I have included a JASP file (zipped) or data file that causes the crash/bug, if applicable.
- I have accurately described the bug, and steps to reproduce it.