One is designed for a temporary disabling of D+ without requiring a restart. Drivers are still loaded (the reason a restart isn’t needed) because D+ may be re-enabled by the user at any time and it needs to be functional when it is re-enabled.
The other option for disabling permanently and will stop the drivers from loading. If the user wishes to re-enable D+ after using this option, it isn’t a quick process. A restart is required.
Well permanent is not permanent, from a users point of view, since it can be easily reversed within minutes. Or else eternity is a boot session…which I’d love to debate…
And one is a more complete than the other. Some restrictions (as well as some drivers) still remain with D+ slider set to disabled. Never experimented to find exactly which, but my observations with bugs suggest BO protection and manual sandbox (always sandbox) [Edit: and blocked files] at least.
Perhaps long-term disabling is a better choice of words than permanent?
And I never said it was an eternity. Simply that you can’t just re-enable D+ and expect it to be functional after using the permanently disable feature. A reboot is required.
Adding to Mouse1’s observations disabling D+ is not capable of undoing the injections of guardxx.dll in all running processes. Only the “Deactivate Defense+ permanently(Requires a system restart)” setting will disable the injection of guardxx.dll. That would be another reason the reboot is needed.
If slider is a temporary disable & deactivate permanently is a permanent disable then why slider is automatically set to disabled after restart when only deactivate permanently is checked which is only required to disable D+ permanently?