Winbma stopped working

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Creating a 2nd Autheticator
2. Restarted Computer
3. WinBMA fail to launch. With the error (WinBMA has stopped working)

Problem signature:
  Problem Event Name:   CLR20r3
  Problem Signature 01: winbma.exe
  Problem Signature 02: 2.0.4331.27062
  Problem Signature 03: 4ebc2dbd
  Problem Signature 04: mscorlib
  Problem Signature 05: 4.0.0.0
  Problem Signature 06: 4ee9af8e
  Problem Signature 07: 3fea
  Problem Signature 08: b
  Problem Signature 09: System.IO.EndOfStreamException
  OS Version:   6.1.7601.2.1.0.256.1
  Locale ID:    18441
  Additional Information 1: 0a9e
  Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
  Additional Information 3: 0a9e
  Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Using Win 7 x64

Original issue reported on code.google.com by tommieto...@gmail.com on 18 Aug 2012 at 12:07

[GoogleCodeExporter]

Delete (or rename?) your winbma settings.cfg file.  This will remove all 
authenticator data from the app and should eliminate the app crash loop.  

If it is crashing then it's likely the file is corrupt or blank and your 
authenticator data is already lost anyways (unless you exported them to file 
prior).  You'll just have to go through the "I can't log in" stuff on 
battle.net to detach your authenticator and make a new one in WinBMA.

If you don't know where the settings.cfg file is, Windows 7 keeps it here:
C:\Users\%currentuser%\AppData\Roaming\WinBMA\settings.cfg

Original comment by nimb...@gmail.com on 22 Aug 2012 at 4:41

[GoogleCodeExporter]

Thanks for the suggestion to delete the settings.cfg
It also solved my problem that WinBMA would not start.

Original comment by JWeber...@gmail.com on 28 Jun 2013 at 6:26