Windows
VPN MFA would not complete until NetExtender was replaced and MFA was rebound
The user could not finish VPN MFA setup on the regular account because the existing VPN client setup was tied to an older account. The technician removed the old NetExtender install, installed the new version, and verified a successful VPN sign-in after MFA was bound to the correct account.
Killed once by someone from XL.net, on 2026-06-30.
Affects
Apps
- NetExtender
What you see
- VPN MFA setup could not be completed on the workstation.
- The user had been signing in with an older VPN account that already had MFA linked to it.
Why it happens
Likely An older NetExtender setup was still in place and MFA was linked to a different VPN account than the one that needed to work.
When it shows up
A Windows workstation can still open VPN but MFA is bound to the wrong account or the client needs to be refreshed before MFA enrollment will work.
You are in this case if:
- NetExtender is the VPN client in use.
- The issue is specifically with VPN MFA enrollment or binding rather than a general network failure.
1 fix below
The steps that killed it
The steps are behind a quick check
There are two ways in and both take a few seconds. Signing in opens the steps on every bug page; so does reading the picture.
Or answer this
Drawing a picture for you.
Can't read it? Sign in instead.
Someone from XL.net killed this on a Windows computer on 2026-06-30. It is written up from that one repair, so it cites no outside page.