Thread Error: Invalid handle (6)

pkandera · 2021-01-08 19:05

Every time after waking up from sleep/hibernate when the place (network) is changed I get this error. Sometimes it is necessary press OK more times sometimes only once.

Windows 10 Pro 20H2 64bit, build 19042.685
NetSetMan Pro 5.0.2
NetSetMan Service is activated

Thanks.
BR
Petr

pkandera · 2021-01-15 18:45

Version 5.0.3 - error still persists... Today about 20 times.
Help please.
BR
Petr

NetSetMan Support · 2021-01-15 22:14

We haven't been able to reproduce it so far. It is still on our agenda, but we are currently focussing on fixing bugs that we can reproduce, then this bug will follow. Sorry, that we didn't reply sooner.

Based on your previous posts, you have recently started using the Ping condition in AutoSwitch. Maybe this problem is connected to this. Please disable AutoSwitch completely and keep an eye on this for the next few days. If the problem does not occur anymore, enable AutoSwitch again, and remove one type of condition completely (for example Ping from all profiles), then see if the problem comes back or not. If it does, disable another type of condition as well. Continue, until you found the reason, and describe in detail exactly what you have configured and how to reproduce this. Your initial post is already a good start, but we need more details (e.g. what exactly do you mean by "place (network) is changed"?).

pkandera · 2021-01-21 13:15

I found there is no problem without Autoswitch. I found that the problem occurs when I change location from office network (cable LAN) to home network (Wi-Fi). And sometimes on home Wi-Fi after laptop waking up. I usually used ping as one rule in Autoswitch. Now I changed the all ping rules to NLM test and it looks better.

But Autoswitch (rules analyzing) works very slow in this version. On 4.x version it took 5-10 seconds, on 5.03 version it takes couple of minute. In Autoswitch window I see all rules on left side as ok but not on right side.

NetSetMan Support · 2021-01-21 13:47

If the problem went away changing all Ping conditions to NLM then there might be a problem with the Ping threads. We will analyse that.

We didn't change anything relevant in the actual AutoSwitch process that could lead to longer delays than in the previous 4.x version. Your observation is probably just a coincidence.
Ping requests aren't constantly done, but only every minute or so, which might explain your delays as you haven't used Ping before. NLM information is used as soon as it is provided by Windows. Changing to a different network might require Windows 1-2 minutes to realize that. Only then NetSetMan receives a notification and can check AutoSwitch conditions and react accordingly.

If you are saying that the left side of the AutoSwitch overview shows all values up to date, but the right side doesn't reflect that, then please create screenshots to document that. If you don't want to post them publicly, you can just upload them without including them in your message. Explain the circumstances for each screenshot situation, then we can analyse it.

pkandera · 2021-01-22 23:57

I don't know what happened but now it works as I assume. I didn't change settings. So it looks as a problem with ping. With NLM it is OK. Thank you for your support.
BR
Petr

pkandera · 2021-01-26 18:59

Version 5.04 - two subsequent days problem with autoswitch. Delay 4-5 minutes. See uploaded picture - autoswicth should switch to Home Wifi.

NetSetMan Support · 2021-02-20 12:05

We have implemented a couple of improvements regarding AutoSwitch for the next version so recognizing network changes should now be quicker and more reliable. We have also found what could potentially cause the error message you initially descibed and are now catching it internally without displaying it.
After the next release, please let us know if your problems are now solved.

NetSetMan Support

#1 2021-01-08 19:05

Thread Error: Invalid handle (6)

#2 2021-01-15 18:45

Re: Thread Error: Invalid handle (6)

#3 2021-01-15 22:14

Re: Thread Error: Invalid handle (6)

#4 2021-01-21 13:15

Re: Thread Error: Invalid handle (6)

#5 2021-01-21 13:47

Re: Thread Error: Invalid handle (6)

#6 2021-01-22 23:57

Re: Thread Error: Invalid handle (6)

#7 2021-01-26 18:59

Re: Thread Error: Invalid handle (6)

#8 2021-02-20 12:05

Re: Thread Error: Invalid handle (6)