Ever since upgrading to Windows 11 a few weeks ago, activating programs by clicking their icon in the taskbar has been erratic.
Usually you get an orange dot under the icon, and the program doesn't switch to the foreground.
Today I decided to diagnose the cause of this as it didn't seem like a common problem.
The culprit is SoftEther CPN Client Manager. I am using 9760, but it also occurs on 9745.
Closing the program in the taskbar corner area resolves the Windows 11 taskbar issue completely.
Anyone else able to replicate this?
VPN Client Manager and Windows 11 Taskbar
-
- Posts: 2
- Joined: Fri Nov 12, 2021 3:11 pm
Re: VPN Client Manager and Windows 11 Taskbar
Yes, I have the exact same issue. I thought it might have been my machine, so tried it on my laptop and get the same issue with that.
-
- Posts: 3
- Joined: Sat Nov 06, 2021 6:48 am
Re: VPN Client Manager and Windows 11 Taskbar
I'm happy to hear it's not just me! I've created shortcuts to connect/disconnect my VPN sessions instead of having the client manager always running and causing chaos with the Windows UI.
-
- Posts: 2
- Joined: Fri Nov 12, 2021 3:11 pm
Re: VPN Client Manager and Windows 11 Taskbar
That is brilliant MasterAnt - I hadn't even realised you could make shortcuts. I have now done the same, and no longer need to have the Client Manager running (unless I am making config changes).
Cheers :-)
Phil.
Cheers :-)
Phil.
-
- Posts: 3
- Joined: Sat Nov 06, 2021 6:48 am
Re: VPN Client Manager and Windows 11 Taskbar
Can't believe this still hasn't been fixed—7-months later—very disappointing!!
-
- Posts: 287
- Joined: Wed Nov 25, 2020 9:10 am
Re: VPN Client Manager and Windows 11 Taskbar
This issue has been fixed in the developer edition.
You can build from source from https://github.com/SoftEtherVPN/SoftEtherVPN or download from Azure nightly builds.
The latest release (5.02.5180) does not include this fix by the way.
You can build from source from https://github.com/SoftEtherVPN/SoftEtherVPN or download from Azure nightly builds.
The latest release (5.02.5180) does not include this fix by the way.