Using the TweakUI program for XP (unsandboxed) will turn on the X-Mouse feature(s) with sandboxed and unsandboxed windows.
But Sandboxie is blocking changes to "system parameters" by a sandboxed program, when you run TweakUI sandboxed.
So BSA and SandboxDiff do not record any Registry changes: because there were no changes to record. They were blocked.
If you turn on the Resource Access Monitor, before using the TweakUI program (sandboxed) to turn on the X-Mouse features, the resulting report will show the blocking of system parameters.
You can override the blocking of changes to system parameters, under Restrictions > Low-level Access, and allow changes to be made to system parameters.
But before you do that, you need to understand that these parameter changes will then be made to the "real" Registry, outside of the sandbox.
It's just the same as running the TweakUI program unsandboxed, as far as system parameters are concerned.
What it comes down to is: You cannot use Sandboxie and BSA, SandboxDiff, etc to track the changes that are made to these Registry settings.
They're either blocked or written outside of the sandbox.
Using the RegShot program (unsandboxed) to track Registry changes didn't give a complete result, either.
There's a change made to:
Activation On; window autoraise Off:
Activatation On; window autoraise On:
But, changing this one Registry value by itself still does not turn the X-Mouse features on or off.
There's something else that needs to be done, that I didn't find.
Win 10 64-bit - Zone Alarm Pro Firewall, Malwarebytes Premium A/V, Cyberfox, Thunderbird
Sandboxie user since March 2007