Error: Invalid Invalid WEP Key / Bug Reports / NetSetMan Support

NetSetMan Support

Search for already answered questions about NetSetMan (Pro) or ask new ones

You are not logged in.

Pages: 1

#1 2021-01-09 03:56

youraverageconsumer
New Member
Registered: 2021-01-09
Posts: 1

Error: Invalid Invalid WEP Key

  • Windows version (incl. x86/x64)
      Windows 10 x64

  • NetSetMan version
      5.0.2

  • Is the NSM Service activated? (Preferences > System Privileges)
      I can't find this option

  • Step by step description to reproduce the problem.

  Hi! I'm getting an error in WiFi Profiles whenever I make ANY changes to a profile and attempt to save it. I can make new profiles and they will successfully save initially, but after the initial save any attempts at modifying the profile yields the following error:

Error: Invalid Invalid WEP Key. Must be 5/13/29 ASCII or 10/26/58 HEX characters.

  This happens regardless of whether the particular profile even requires a password (as you can see in the uploaded screenshot, the Encryption option is Open). To clarify, this happens to all profiles; pre-existing and newly created profiles encounter the same error when modification after creation is attempted.

  1. Yes I have re-installed the program (multiple times)

  2. Yes I have restarted my computer

  3. Yes I have tried animal sacrifice over a ouiji board

  At this time, the only workaround I have found is to export the initial WiFi profile, modify it manually with a text editor, and import it back into NetSetMan. This is a burden. Please help.

Thanks!

Offline

#2 2021-01-09 16:23

NetSetMan Support
Administrator
Registered: 2005-08-06
Posts: 1,878

Re: Error: Invalid Invalid WEP Key

youraverageconsumer wrote:

Yes I have tried animal sacrifice over a ouiji board

That might be the problem. IT rituals require a computer mouse and motherboard instead. Please try again and post images for review.

youraverageconsumer wrote:

I'm getting an error in WiFi Profiles whenever I make ANY changes to a profile and attempt to save it.

We were able to reproduce the problem with "Open" encryption, exactly as in your screenshot and description. We will fix this for the next release.

However, you are saying that this error happens for all kinds of settings. We are unable to reproduce any other constellation with this problem. Please provide a step-by-step description (and screenshot) for a case with another type of encryption.

Offline

Pages: 1