Strange behavior with the Sonicwall NetExtender CLI

Posting this in case anyone else has run into this issue but after six months of troubleshooting I was able to determine why I would sometimes run into an issue I was experiencing. I am a technical consultant who has to VPN into many different customer systems and what I would notice from time to time is that whenever I used the NECLI.EXE to connect and disconnect I would run into some unexplainable issues where other VPN's would no longer work. The two that seem to consistently get clobbered are FortiClient and GlobalProtect. Rebooting would not help resolve the issue nor would uninstalling NetExtender or the other two. What I noticed was that I could go back and connect to the NetExtender customer using the GUI client and then everything would magically work again so I simply stopped using the Generic VPN setting in RDM or the NetExtender VPN (both do the same thing on the back end) and I would no longer have the issue.

Last week someone was finally able to identify root cause of this issue and it had to do with how the NECLI.EXE clobbers the following registry setting:
KEY: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections]
VALUE: DefaultConnectionSettings

Hopefully Sonicwall creates a fix for this but for now I can go back to using RDM to automate my connection and then add a single line to the NxDisconnect.bat file Sonicwall file uses to put the damaged key back to the pre-connection value. I wouldn't expect this would affect most users out there but I am passing this along in case other users found that their VPN stack was behaving weird after disconnecting from the client and provide a way to get back to a working system.