Tweet
Hi there 
As I'm sure you are aware DT Pro uses a hardware key for activation purposes.
When the hardware is changed (in my case, a new 2nd monitor, and change of RAM size), DT Pro requires reactivation.
It will not alert you to this until you attempt to run DT Pro.
However, DT Pro's shell integration seems to make Windows Explorer crash while DT Pro is in a "requires activation" state.
It was very hard to tie this down to DT Pro, but as soon as I ran the program and reactivated, Windows Explorer ceased crashing.
Can anyone else verify this bug?
As I'm sure you are aware DT Pro uses a hardware key for activation purposes.
When the hardware is changed (in my case, a new 2nd monitor, and change of RAM size), DT Pro requires reactivation.
It will not alert you to this until you attempt to run DT Pro.
However, DT Pro's shell integration seems to make Windows Explorer crash while DT Pro is in a "requires activation" state.
It was very hard to tie this down to DT Pro, but as soon as I ran the program and reactivated, Windows Explorer ceased crashing.
Can anyone else verify this bug?