According to the fault file, the config file that VoiceAttack accesses for its settings is either hidden or read-only. You'll want to first close VoiceAttack, then go into this folder:
C:\Users\Farknocker\AppData\Local\VoiceAttack.com\VoiceAttack.exe_Url_4pinogugfc5ybs4qaajf3fqd3nbyp4lb\0.0.0.1\
Then, right-click on the user.config file. Click 'Properties' and then take a look at the 'Hidden' and 'Read-only' attributes on the General tab. If either of those are checked, make sure to uncheck them and click 'OK'. Launch VoiceAttack and see if things are back to normal. If neither of those are checked, there's something else going on in your setup - I would go ahead and move that user.config file off to a safe place (out of that folder), and then launch VoiceAttack to see if that file is properly recreated (note that you would then have to re-validate your registration if you are using the standalone version of VA, as that information is stored in user.config).
Normally, this file is freely writable. I don't know how or even if Defender affects that file when rules are changed.
Hope that helps!