diff --git a/SandboxiePlus/SandMan/Forms/OptionsWindow.ui b/SandboxiePlus/SandMan/Forms/OptionsWindow.ui
index e2fabbf2..22544996 100644
--- a/SandboxiePlus/SandMan/Forms/OptionsWindow.ui
+++ b/SandboxiePlus/SandMan/Forms/OptionsWindow.ui
@@ -7,7 +7,7 @@
0
0
835
- 575
+ 475
@@ -45,7 +45,7 @@
QTabWidget::North
- 6
+ 1
@@ -55,7 +55,7 @@
-
- 3
+ 2
@@ -1095,7 +1095,7 @@
-
- 1
+ 3
@@ -3028,6 +3028,50 @@ To specify a process use '$:program.exe' as path.
Access Policies
+
-
+
+
+ Apply File and Key Open directives only to binaries located outside the sandbox.
+
+
+
+ -
+
+
+ Apply Close...=!<program>,... rules also to all binaries located in the sandbox.
+
+
+
+ -
+
+
+ When the Privacy Mode is enabled, sandboxed processes will be only able to read C:\Windows\*, C:\Program Files\*, and parts of the HKLM registry, all other locations will need explicit access to be readable and/or writable. In this mode, Rule Specificity is always enabled.
+
+
+ true
+
+
+
+ -
+
+
+ Prioritize rules based on their Specificity and Process Match Level
+
+
+
+ -
+
+
+ Qt::Vertical
+
+
+
+ 20
+ 81
+
+
+
+
-
@@ -3042,6 +3086,19 @@ To specify a process use '$:program.exe' as path.
+ -
+
+
+ Qt::Horizontal
+
+
+
+ 638
+ 20
+
+
+
+
-
@@ -3049,33 +3106,7 @@ To specify a process use '$:program.exe' as path.
- -
-
-
- When the Privacy Mode is enabled, sandboxed processes will be only able to read C:\Windows\*, C:\Program Files\*, and parts of the HKLM registry, all other locations will need explicit access to be readable and/or writable. In this mode, Rule Specificity is always enabled.
-
-
- true
-
-
-
- -
-
-
- Prevent sandboxed processes from accessing system deatils through WMI
-
-
-
- -
-
-
- Some programs read system deatils through WMI(A Windows built-in database)
-instead of normal ways.For example,"tasklist.exe" could get full processes list
-even if "HideOtherBoxes" is opened through accessing WMI.Enable this option to stop these heavior.
-
-
-
- -
+
-
@@ -3089,14 +3120,7 @@ even if "HideOtherBoxes" is opened through accessing WMI.Enable this o
- -
-
-
- Prioritize rules based on their Specificity and Process Match Level
-
-
-
- -
+
-
The rule specificity is a measure to how well a given rule matches a particular path, simply put the specificity is the length of characters from the begin of the path up to and including the last matching non-wildcard substring. A rule which matches only file types like "*.tmp" would have the highest specificity as it would always match the entire file path.
@@ -3107,46 +3131,6 @@ The process match level has a higher priority than the specificity and describes
- -
-
-
- Apply Close...=!<program>,... rules also to all binaries located in the sandbox.
-
-
-
- -
-
-
- Apply File and Key Open directives only to binaries located outside the sandbox.
-
-
-
- -
-
-
- Qt::Vertical
-
-
-
- 20
- 81
-
-
-
-
- -
-
-
- Qt::Horizontal
-
-
-
- 638
- 20
-
-
-
-
@@ -4078,6 +4062,7 @@ The process match level has a higher priority than the specificity and describes
+ 75
true
true
@@ -4667,6 +4652,7 @@ This is done to prevent rogue processes inside the sandbox from creating a renam
+ 50
false
true
@@ -5080,8 +5066,8 @@ instead of "*".
0
0
- 75
- 16
+ 98
+ 28