I've noticed this more recently than in the past. Unfortunately, I haven't fully traced it, but I have an issue where I will use the Advanced part of the program and enter in a command.. It shows up in the list and I've tested it by adding a key to the command. But for some odd reason, when I go to exit, it doesn't give me an option to save. I wind up exiting without the commands saved properly, so I have to go back and re-enter the commands again.
This becomes a bit annoying if I've entered a lot of commands and have to re-enter them. I'm unsure how the coding misses the need to save data, but could there at least be a manual save to prevent this. Or is there already one that I haven't seen?
Hopefully this explains enough, but send word if you need more information. I have often seen an error around the time this happens that has some sort of issue with keys that are undefined. It's often bypassed by telling the program to continue rather than close. It's not often enough for me to define it and I've had it happen without having this error, so I don't think it's linked.
** Actually, ending this post, I recreated the error when trying to remove a command that had no keys to assign listed and had ADown assigned to it.. The exact message I got was "Unhandled exception in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately." This is followed by "Argument 'Key' is not a valid value." And gives the options to Continue or Quit.
After selecting continue.. I don't get the box to remove, yes or no.. But upon deleting again, it does delete properly and go to the option to save when exiting.
Error Details:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentException: Argument 'Key' is not a valid value.
at Microsoft.VisualBasic.Collection.Remove(String Key)
at A.a561c42b03a3d37514b6458d610edd98.8776d27c77e2d3e436f7d6922a3b10dd(Object , EventArgs )
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
GCP_1
Assembly Version: 2.0.1.3
Win32 Version: 2.0.1.3
CodeBase: file:///C:/Users/Jeromy/AppData/Local/Temp/50413/GCP_1.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
ResourceAssembly
Assembly Version: 1.0.0.0
Win32 Version: 2.0.1.3
CodeBase: file:///C:/Users/Jeromy/AppData/Local/Temp/50413/GCP_1.exe
----------------------------------------
Microsoft.VisualBasic.Compatibility
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.4927
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic.Compatibility/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.Compatibility.dll
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Core
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.4926 built by: NetFXw7
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box. 
Sorry about this issue, we'll look into it.
In the meantime, there is a way to save manually.
In "full" mode, there is a button named "commands" in the "save" section to the top right. Click this. This will initiate the save process.
If that doesn't work (because the system has missed that it needs to save) you can force the process by editing a command. Hit add, give a name, then close the edit box and delete the command you just made.
Phil
Designer Of GameCommanderPro - www.GameCommanderPro.com
Designer Of KeyBlaster - www.keyblaster.com