This is a public Forum  publicRSS


    Mark Bagshaw
    Can't upgrade Version 11 user profile to Version 12
    Topic posted October 2, 2012 by Mark Bagshaw, tagged Installation and Configuration Topics, Troubleshooting 
    946 Views, 5 Comments
    Can't upgrade Version 11 user profile to Version 12

    I have just purchased an upgrade of Dragon Naturally Speaking Professional Addition to upgrade from Version 11 to Version 12. When I try to upgrade my existing user profiles I get the message "Upgrades of this user profile type are not supported in this edition". Surely I don't need to start from scratch with a new user profile just because I have upgraded?




    • Graham Hendry

      A long shot - you do have the DNS Professional upgrade rather than Preferred?  With the DNS 11launch there were problems with some users receiving the Preferred rather than Professional version.



    • Neil Iosson


      I had a similar problem and went through Nuance phone support to get it fixed.

      Go to C:\ProgramData\Nuance\NaturallySpeaking11\Users\yourname

      (Worth noting that Program Data is a hidden folder and you need to enamble this using My Computer / Organise | Folder and Search Options and then select the "View" tab and then "Show hidden system folders and files".)

      The key was to:

      1) rename the "current" folder as something else e.g. "old"

      2) make a copy of the back-up folder i.e. "Copy of back-up"

      3) rename the copy to "current"

      and then re-run the upgrade tool (which is in the \DragonNaturallySpeaking12.0\ Dragon Naturally Speaking Tools folder from the start menu). 


      Best of luck, Neil

    • Larry Allen

      There is a setting in a few Release 11 user files with Dragon Pro 11, Dragon Legal 11, and possibly other versions which cause this error. 

      Adding the line:
      in the [Options] portion of the options.ini file for the Release 11 affected user(s) allows the files to be imported/upgraded to Release 12.
    • Brian Cragun

      Adding SpeakerLanguageID=0 worked for me.