Crash decrypting strings encrypted in different environment

[aarnold-sd68]

Please make sure to fill out this form completely, and attach your program logs (set to Debug setting). You can delete this line.

• Searched to see if this issue exists
• [ X] Completed below form
• [ X] Attached debug log file
• Copy output in File -> UPS Variable

**WinNUT Version: 2.3..9437.23054
**Windows OS Version: Server 2025

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to - Run on Server 2025 seems to crash, on first run.

Expected behavior
Program should load the GUI

Additional context
Add any other context about the problem here.

CrashReport_2025-11-10T10.56.20.txt

@gbakeman's Addendum

Exception

{
  "ClassName": "System.Security.Cryptography.CryptographicException",
  "Message": "Key not valid for use in specified state.
",
  "Data": null,
  "InnerException": null,
  "HelpURL": null,
  "StackTraceString": "   at System.Security.Cryptography.ProtectedData.Unprotect(Byte[] encryptedData, Byte[] optionalEntropy, DataProtectionScope scope)
   at WinNUT_Client_Common.SerializedProtectedString.Unprotect(String protectedString) in C:\Users\Glen\Repositories\nutdotnet\WinNUT-Client\WinNUT_V2\WinNUT-Client_Common\SerializedProtectedString.vb:line 75
   at WinNUT_Client_Common.SerializedProtectedString.ToString() in C:\Users\Glen\Repositories\nutdotnet\WinNUT-Client\WinNUT_V2\WinNUT-Client_Common\SerializedProtectedString.vb:line 84
   at WinNUT_Client.WinNUT.UPS_Connect(Object retryOnConnFailure) in C:\Users\Glen\Repositories\nutdotnet\WinNUT-Client\WinNUT_V2\WinNUT-Client\WinNUT.vb:line 370
   at WinNUT_Client.WinNUT.WinNUT_Shown(Object sender, EventArgs e) in C:\Users\Glen\Repositories\nutdotnet\WinNUT-Client\WinNUT_V2\WinNUT-Client\WinNUT.vb:line 250
   at System.Windows.Forms.Form.OnShown(EventArgs e)
   at System.Windows.Forms.Form.CallShownEvent()
   at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbacks()"

[aarnold-sd68]

hmm, uninstall re-install fixed the issue :).

[aarnold-sd68]

ahh and now I know what caused it. When you copy the user.config from another server it breaks the install.

[gbakeman]

ahh and now I know what caused it. When you copy the user.config from another server it breaks the install.

But it would load the next time OK with the same user config? Could you please provide that config file (with sensitive information redacted)?

[aarnold-sd68]

Once I copy the config from a working machine, WinNut no longer will load. The only way to fix it, is to uninstall it and re-install it. I did notice there was mention of a backup and restore function but I couldn't find it. I think I redacted everything I needed too.
*Edit - if I delete the the c:\users%username%\appdata\NUTDotNet folder it will also fix the installation.

user.config.txt

[gbakeman]

Hi @aarnold-sd68 ,

Thanks again for providing the previous info. It looks like it's a simple bug. I have the username and password encrypted using standard Windows APIs, and when this information is moved to a new machine, it throws an error that I didn't think to catch. Should be a simple fix too. I'm thinking I'll put a line in the GUI message log stating that the username/password is invalid and has been cleared/reset. Does that sound like a decent fix?

I also wanted to add: you're right that there is a settings import function, but that was only to bring over previous WinNUT configurations that were stored in the Registry. There is an issue open in #121 for a full export/import function, subscribe there for more info.

[aarnold-sd68]

That sounds like a good fix to me.