Tried it on my w7 64 bit system, and it worked fine.
Interestingly (though perhaps not to many in this forum) avast autosandbox got in before D+.
D+ didn't kick-in until the attempt to modify the registry (when I clicked the Modify System button in the red border box).
OK, so now I ran the test on my xp machine.
The autosandbox kicked in as expected, the box with Modify System came up in a red border when I accepted the Recommendation.
This time though, when I clicked Modify System, D+ didn't kick in to warn of an attempt to modify registry.
I am a bit confused (not uncommon) by the difference betweeen the W7 and xp system responses, but I wonder if the autosandbox on my W7 64bit machine is a bit leaky, whereas on xp it is watertight?
(otherwise why should D+ see an attempt to modify registry by a program that is running in a sandbox?)
Any thoughts?
Edit:
I set D+ to allow, and no system change was actually made (no text file added to C and no registry entry).
So, whilst I am still not quite sure what was going on with D+, the autosandbox seems to work fine!
Further Edit:
Looking a bit more closely I see that D+ was actually alerting on the attempt to modify the sandbox registry entry aswSnx privatestorage, not the entry that the tool asked us to check.