Reported by noshark on 2013-09-04 16:37
Despite the fact that the user is asked to confirm deletion of a configuration profile, the trigger for that profile is not removed from nvda.ini until the whole configuration is saved.
If automatic saving of configuration on exit is not active, the user could easily restart NVDA with an entry in nvda.ini to trigger a non-existent profile. Indeed, a warning is sounded when switching to the application concerned.