Also noticed this while running 3.5.2, FWIW. Happened directly after system restart.
Reentering reg info fixed issue.
My first thought was to be incredibly embarrassed for not having purchased a copy of DT3, as I was well aware of all the incredible work that went into the betas. And the tremendous post-launch efforts to make further adjustments moving form 3.0 to 3.5.
Fortunately, email records revealed the registration info! It took all of 2 minutes to fix. Just a glitch folks! If you’re curious as to what the excellent DT team does to improve the product, please consider reading the release notes. It gives a glimpse of the serious effort to make this an outstanding product for a range of users.