Not a big thing as compared to the general progress that seemingly makes things run even more smoothly, especially after 'blitz'-fixing the Chromium-browsers closing-issue with v1.07. If I decline an error-message will pop up that the connection to the driver has somehow failed and there is no Sandboxie-service available. When entering OK the boot-sequence will continue as normal. 1/3 of cases of boot-up or re-boot the UAC will be triggered.

Not exactly sure when it actually started but somewhere in the v1.0x-range. There is one minor issue though I'm observing with increased frequency - at least since v1.06, probably since v1.05 or even before that. So thanks again and congratulations for the effort. So far I'm quite happy with this latest build. removed OpenToken as it is only a shorthand for UnrestrictedToken=y and UnfilteredToken=y set together.fixed KmdUtil sometimes not properly terminating the driver #1493.fixed SandMan issue with reused process IDs.fixed issue causing Chromium browsers not closing properly #1496.fixed issue with file renaming in open paths introduced in 1.0.6.fixed memory leak in driver (conf_user.c).

Win32k hooking is now compatible with HVCI #1483

reworked syscall invocation code in the driver.

added option 'LingerLeniency=n' to solve issue #997.

added option to set a custom ini editor in the Plus UI #1475.

Note: This template requires RuleSpecificity being available to work properly

added new template 'DeviceSecurity' to lock down access to device drivers on the system.

added option 'DisableRTBlacklist=y' allowing to disable the hardcoded runtime class blacklist.

added experimental option 'CreateToken=y' to create a new token instead of repurposing an existing one.

This build fixed various issues with the previous build and adds some new functionality

Sandboxie 64 bit windows 7