Today when I went to launch DNS (I think v15.6 but hard to tell given the non-DPI aware "About" with tiny fonts) it popped up a dialog telling me that it can't open my profile.

That profile exists and is located here:

C:\Users\dan\AppData\Local\Nuance\NS15\Users\DanMain_DgnRenamed

I take a rolling backup of this directory for the most recent two weeks, so I have a backup from Tuesday. However, the most recent DNS backup is from August, so I don't want to restore that.

What is the best way to approach this? Maybe create a new profile and copy the backup folder to this new profile folder?

TIA

Dan

We suspect your tiny font has to do with how you set your Windows Display settings. You could try increasing the Scale size

We can also see that your user profile has been corrupted twice. When Dragon successfully rescues your profile, it adds _DgnRenamed to your username but consider this a red flag. This is most often caused by Shutting down your computer before it has finished saving your profile. Sometimes just exiting Dragon can cause corruption. This is why we do not allow Dragon to automatically save our profile. If you would like to change this miserable default feature back to Dragon asking you if you would like to save your user profile (when exiting), look up “hack” in the Quick Tips, at the top of the page. Getting back to your issue…

The message is telling you to Launch Restore but this doesn't always work. You will find a legacy manual approach in the Quick Tips when you look up “switching” as in switching to your backup user profile. After you finish, you might also consider making a monthly manual backup

Change "No" to "Know" w/KnowBrainer 2022
Trial Downloads
Dragon/Sales@KnowBrainer.com 
(615) 884-4558 ex 1

Lunis, thank you for these suggestions.

The scale size is already at 200%, so I don't think it's this. As far as I can see, the whole of the app is DPI-insensitive, including the script editor (whose font is so small as to be unusable), so I'm putting this down to a simple lack of awareness, effort, or competence on the part of the developers.

With regard to the hack you mention, I have edited options.ini as suggested in Quick Tips, so hopefully that will reduce such problems going forward.

I have also set a reminder for regular manual backups.

Finally, the manual approach in Quick Tips didn't work - I got exactly the same error - but I went for a full restore and that did work, so there was no need to pursue the issue further.

All's well that ends well, I hope!

Regards,

Dan