Find your message below: its solution is right underneath.
Other pages:Windows: server, secure connection and deviceWindows: updates and diagnosticsWindows: settings, session and service
Request not sent or not confirmed in time
The WireGuard command could not be sent to the local VPN service.
What is happening: your request could not be sent to FuzeVPN’s VPN service, on your computer.
What to do (in order; stop as soon as it works):
Wait until FuzeVPN has checked the VPN status. If the connection or disconnection you asked for did not happen, go to the next step.
If FuzeVPN shows “Disconnect”, click it and wait until FuzeVPN shows “Not protected”. Disconnecting also removes the internet block that the kill switch keeps in place after a failure. If you asked to disconnect, stop here once FuzeVPN shows “Not protected”. If you asked to connect, continue with the steps below until FuzeVPN shows “Protected”.
If the internet stays blocked, open the “Diagnostics” page in the side menu and click “Diagnostics”. If “Complete disconnection” is offered below the results, click it. If you later need to contact support while this device is still offline, write from another connected device, such as a phone on mobile data.
If you asked to disconnect, stop here: “Not protected” confirms disconnection. If that confirmation is still missing, contact support. If you asked to connect, start the VPN connection again and wait until FuzeVPN shows “Protected”.
Quit FuzeVPN with “Quit FuzeVPN” in its icon’s menu near the clock, then reopen it with the same Windows account as usual. The cross only minimizes FuzeVPN near the clock. Accept the Windows prompt if it appears, and restart if Windows asks you to.
Switch to OpenVPN: disconnect the VPN, then choose OpenVPN in “Settings → Connection → VPN protocol”. In “Automatic” mode, FuzeVPN already switches to OpenVPN once if WireGuard does not start on your PC. Then connect again and check that FuzeVPN shows “Protected”.
Restart Windows, then try again.
If the message still comes back, send a report to support.
The OpenVPN command could not be sent to the local VPN service.
What is happening: your request could not be sent to FuzeVPN’s VPN service, on your computer.
What to do (in order; stop as soon as it works):
Wait until FuzeVPN has checked the VPN status. If the connection or disconnection you asked for did not happen, go to the next step.
If FuzeVPN shows “Disconnect”, click it and wait until FuzeVPN shows “Not protected”. Disconnecting also removes the internet block that the kill switch keeps in place after a failure. If you asked to disconnect, stop here once FuzeVPN shows “Not protected”. If you asked to connect, continue with the steps below until FuzeVPN shows “Protected”.
If the internet stays blocked, open the “Diagnostics” page in the side menu and click “Diagnostics”. If “Complete disconnection” is offered below the results, click it. If you later need to contact support while this device is still offline, write from another connected device, such as a phone on mobile data.
If you asked to disconnect, stop here: “Not protected” confirms disconnection. If that confirmation is still missing, contact support. If you asked to connect, start the VPN connection again and wait until FuzeVPN shows “Protected”.
Quit FuzeVPN with “Quit FuzeVPN” in its icon’s menu near the clock, then reopen it with the same Windows account as usual. The cross only minimizes FuzeVPN near the clock. Accept the Windows prompt if it appears, and restart if Windows asks you to.
On Windows, in Automatic mode, FuzeVPN switches to OpenVPN once, only if WireGuard does not start on the PC. If OpenVPN also fails, the OpenVPN message is shown, even if you did not choose OpenVPN. Switch to WireGuard in the meantime: disconnect the VPN, then choose WireGuard in “Settings → Connection → VPN protocol”. Then connect again and check that FuzeVPN shows “Protected”.
Restart Windows, then try again.
If the message still comes back, send a report to support.
The local WireGuard service did not confirm the operation within the expected time.
What is happening: FuzeVPN’s VPN service, on your computer, did not reply fully in time. Your request may still finish in the background.
What to do (in order; stop as soon as it works):
Do not start anything again straight away: wait until FuzeVPN has checked the VPN status. If the connection or disconnection you asked for did not happen, go to the next step.
If FuzeVPN shows “Disconnect”, click it and wait until FuzeVPN shows “Not protected”. Disconnecting also removes the internet block that the kill switch keeps in place after a failure. If you asked to disconnect, stop here once FuzeVPN shows “Not protected”. If you asked to connect, continue with the steps below until FuzeVPN shows “Protected”.
If the internet stays blocked, open the “Diagnostics” page in the side menu and click “Diagnostics”. If “Complete disconnection” is offered below the results, click it. If you later need to contact support while this device is still offline, write from another connected device, such as a phone on mobile data.
If you asked to disconnect, stop here: “Not protected” confirms disconnection. If that confirmation is still missing, contact support. If you asked to connect, start the VPN connection again and wait until FuzeVPN shows “Protected”.
Quit FuzeVPN with “Quit FuzeVPN” in its icon’s menu near the clock, then reopen it with the same Windows account as usual. The cross only minimizes FuzeVPN near the clock. Accept the Windows prompt if it appears, and restart if Windows asks you to.
Switch to OpenVPN: disconnect the VPN, then choose OpenVPN in “Settings → Connection → VPN protocol”. In “Automatic” mode, FuzeVPN already switches to OpenVPN once if WireGuard does not start on your PC. Then connect again and check that FuzeVPN shows “Protected”.
Restart Windows, then try again.
If the message still comes back, send a report to support.
The local OpenVPN service did not confirm the operation within the expected time.
What is happening: FuzeVPN’s VPN service, on your computer, did not reply fully in time. Your request may still finish in the background.
What to do (in order; stop as soon as it works):
Do not start anything again straight away: wait until FuzeVPN has checked the VPN status. If the connection or disconnection you asked for did not happen, go to the next step.
If FuzeVPN shows “Disconnect”, click it and wait until FuzeVPN shows “Not protected”. Disconnecting also removes the internet block that the kill switch keeps in place after a failure. If you asked to disconnect, stop here once FuzeVPN shows “Not protected”. If you asked to connect, continue with the steps below until FuzeVPN shows “Protected”.
If the internet stays blocked, open the “Diagnostics” page in the side menu and click “Diagnostics”. If “Complete disconnection” is offered below the results, click it. If you later need to contact support while this device is still offline, write from another connected device, such as a phone on mobile data.
If you asked to disconnect, stop here: “Not protected” confirms disconnection. If that confirmation is still missing, contact support. If you asked to connect, start the VPN connection again and wait until FuzeVPN shows “Protected”.
Quit FuzeVPN with “Quit FuzeVPN” in its icon’s menu near the clock, then reopen it with the same Windows account as usual. The cross only minimizes FuzeVPN near the clock. Accept the Windows prompt if it appears, and restart if Windows asks you to.
On Windows, in Automatic mode, FuzeVPN switches to OpenVPN once, only if WireGuard does not start on the PC. If OpenVPN also fails, the OpenVPN message is shown, even if you did not choose OpenVPN. Switch to WireGuard in the meantime: disconnect the VPN, then choose WireGuard in “Settings → Connection → VPN protocol”. Then connect again and check that FuzeVPN shows “Protected”.
Restart Windows, then try again.
If the message still comes back, send a report to support.
Kill switch or network protection not prepared
Windows could not prepare the kill switch before the VPN connection.
What is happening: an unexpected error stopped Windows from preparing the kill switch, the protection if the connection drops, before connecting.
What to do (in order; stop as soon as it works):
If FuzeVPN shows “Disconnect”, click it and wait until FuzeVPN shows “Not protected”. Disconnecting also removes the internet block that the kill switch keeps in place after a failure. If you asked to disconnect, stop here once FuzeVPN shows “Not protected”. If you asked to connect, continue with the steps below until FuzeVPN shows “Protected”.
If the internet stays blocked, open the “Diagnostics” page in the side menu and click “Diagnostics”. If “Complete disconnection” is offered below the results, click it. If you later need to contact support while this device is still offline, write from another connected device, such as a phone on mobile data.
If you asked to disconnect, stop here: “Not protected” confirms disconnection. If that confirmation is still missing, contact support. If you asked to connect, start the VPN connection again and wait until FuzeVPN shows “Protected”.
Quit FuzeVPN with “Quit FuzeVPN” in its icon’s menu near the clock, then reopen it with the same Windows account as usual. The cross only minimizes FuzeVPN near the clock. Accept the Windows prompt if it appears, and restart if Windows asks you to.
Try the other protocol: disconnect the VPN, then choose WireGuard or OpenVPN in “Settings → Connection → VPN protocol”. On Windows, Automatic mode uses WireGuard. It switches to OpenVPN once, only if WireGuard does not start on the PC. Then connect again and check that FuzeVPN shows “Protected”.
Restart Windows, then try again.
If the message still comes back, send a report to support.
Windows could not prepare or finalize WireGuard network protection.
What is happening: Windows could not set up or check the network protection for the WireGuard connection.
What to do (in order; stop as soon as it works):
If FuzeVPN shows “Disconnect”, click it and wait until FuzeVPN shows “Not protected”. Disconnecting also removes the internet block that the kill switch keeps in place after a failure. If you asked to disconnect, stop here once FuzeVPN shows “Not protected”. If you asked to connect, continue with the steps below until FuzeVPN shows “Protected”.
If the internet stays blocked, open the “Diagnostics” page in the side menu and click “Diagnostics”. If “Complete disconnection” is offered below the results, click it. If you later need to contact support while this device is still offline, write from another connected device, such as a phone on mobile data.
If you asked to disconnect, stop here: “Not protected” confirms disconnection. If that confirmation is still missing, contact support. If you asked to connect, start the VPN connection again and wait until FuzeVPN shows “Protected”.
Quit FuzeVPN with “Quit FuzeVPN” in its icon’s menu near the clock, then reopen it with the same Windows account as usual. The cross only minimizes FuzeVPN near the clock. Accept the Windows prompt if it appears, and restart if Windows asks you to.
Switch to OpenVPN: disconnect the VPN, then choose OpenVPN in “Settings → Connection → VPN protocol”. In “Automatic” mode, FuzeVPN already switches to OpenVPN once if WireGuard does not start on your PC. Then connect again and check that FuzeVPN shows “Protected”.
Restart Windows, then try again.
If the message still comes back, send a report to support.
Windows could not prepare or finalize OpenVPN network protection.
What is happening: Windows could not set up or check the network protection for the OpenVPN connection.
What to do (in order; stop as soon as it works):
If FuzeVPN shows “Disconnect”, click it and wait until FuzeVPN shows “Not protected”. Disconnecting also removes the internet block that the kill switch keeps in place after a failure. If you asked to disconnect, stop here once FuzeVPN shows “Not protected”. If you asked to connect, continue with the steps below until FuzeVPN shows “Protected”.
If the internet stays blocked, open the “Diagnostics” page in the side menu and click “Diagnostics”. If “Complete disconnection” is offered below the results, click it. If you later need to contact support while this device is still offline, write from another connected device, such as a phone on mobile data.
If you asked to disconnect, stop here: “Not protected” confirms disconnection. If that confirmation is still missing, contact support. If you asked to connect, start the VPN connection again and wait until FuzeVPN shows “Protected”.
Quit FuzeVPN with “Quit FuzeVPN” in its icon’s menu near the clock, then reopen it with the same Windows account as usual. The cross only minimizes FuzeVPN near the clock. Accept the Windows prompt if it appears, and restart if Windows asks you to.
On Windows, in Automatic mode, FuzeVPN switches to OpenVPN once, only if WireGuard does not start on the PC. If OpenVPN also fails, the OpenVPN message is shown, even if you did not choose OpenVPN. Switch to WireGuard in the meantime: disconnect the VPN, then choose WireGuard in “Settings → Connection → VPN protocol”. Then connect again and check that FuzeVPN shows “Protected”.
Restart Windows, then try again.
If the message still comes back, send a report to support.
The VPN connection does not start
The WireGuard tunnel service did not reach the active state.
What is happening: the WireGuard connection did not start, or Windows did not confirm that it was active.
What to do (in order; stop as soon as it works):
If FuzeVPN shows “Disconnect”, click it and wait until FuzeVPN shows “Not protected”. Disconnecting also removes the internet block that the kill switch keeps in place after a failure. If you asked to disconnect, stop here once FuzeVPN shows “Not protected”. If you asked to connect, continue with the steps below until FuzeVPN shows “Protected”.
If the internet stays blocked, open the “Diagnostics” page in the side menu and click “Diagnostics”. If “Complete disconnection” is offered below the results, click it. If you later need to contact support while this device is still offline, write from another connected device, such as a phone on mobile data.
If you asked to disconnect, stop here: “Not protected” confirms disconnection. If that confirmation is still missing, contact support. If you asked to connect, start the VPN connection again and wait until FuzeVPN shows “Protected”.
Quit FuzeVPN with “Quit FuzeVPN” in its icon’s menu near the clock, then reopen it with the same Windows account as usual. The cross only minimizes FuzeVPN near the clock. Accept the Windows prompt if it appears, and restart if Windows asks you to.
Switch to OpenVPN: disconnect the VPN, then choose OpenVPN in “Settings → Connection → VPN protocol”. In “Automatic” mode, FuzeVPN already switches to OpenVPN once if WireGuard does not start on your PC. Then connect again and check that FuzeVPN shows “Protected”.
Restart Windows, then try again.
If the message still comes back, send a report to support.
The OpenVPN tunnel could not be started.
What is happening: an unexpected error stopped the OpenVPN connection from starting.
What to do (in order; stop as soon as it works):
If FuzeVPN shows “Disconnect”, click it and wait until FuzeVPN shows “Not protected”. Disconnecting also removes the internet block that the kill switch keeps in place after a failure. If you asked to disconnect, stop here once FuzeVPN shows “Not protected”. If you asked to connect, continue with the steps below until FuzeVPN shows “Protected”.
If the internet stays blocked, open the “Diagnostics” page in the side menu and click “Diagnostics”. If “Complete disconnection” is offered below the results, click it. If you later need to contact support while this device is still offline, write from another connected device, such as a phone on mobile data.
If you asked to disconnect, stop here: “Not protected” confirms disconnection. If that confirmation is still missing, contact support. If you asked to connect, start the VPN connection again and wait until FuzeVPN shows “Protected”.
Quit FuzeVPN with “Quit FuzeVPN” in its icon’s menu near the clock, then reopen it with the same Windows account as usual. The cross only minimizes FuzeVPN near the clock. Accept the Windows prompt if it appears, and restart if Windows asks you to.
On Windows, in Automatic mode, FuzeVPN switches to OpenVPN once, only if WireGuard does not start on the PC. If OpenVPN also fails, the OpenVPN message is shown, even if you did not choose OpenVPN. Switch to WireGuard in the meantime: disconnect the VPN, then choose WireGuard in “Settings → Connection → VPN protocol”. Then connect again and check that FuzeVPN shows “Protected”.
Restart Windows, then try again.
If the message still comes back, send a report to support.
OpenVPN Core stopped before the network connection was opened.
What is happening: OpenVPN stopped before opening the connection.
What to do (in order; stop as soon as it works):
If FuzeVPN shows “Disconnect”, click it and wait until FuzeVPN shows “Not protected”. Disconnecting also removes the internet block that the kill switch keeps in place after a failure. If you asked to disconnect, stop here once FuzeVPN shows “Not protected”. If you asked to connect, continue with the steps below until FuzeVPN shows “Protected”.
If the internet stays blocked, open the “Diagnostics” page in the side menu and click “Diagnostics”. If “Complete disconnection” is offered below the results, click it. If you later need to contact support while this device is still offline, write from another connected device, such as a phone on mobile data.
If you asked to disconnect, stop here: “Not protected” confirms disconnection. If that confirmation is still missing, contact support. If you asked to connect, start the VPN connection again and wait until FuzeVPN shows “Protected”.
Quit FuzeVPN with “Quit FuzeVPN” in its icon’s menu near the clock, then reopen it with the same Windows account as usual. The cross only minimizes FuzeVPN near the clock. Accept the Windows prompt if it appears, and restart if Windows asks you to.
On Windows, in Automatic mode, FuzeVPN switches to OpenVPN once, only if WireGuard does not start on the PC. If OpenVPN also fails, the OpenVPN message is shown, even if you did not choose OpenVPN. Switch to WireGuard in the meantime: disconnect the VPN, then choose WireGuard in “Settings → Connection → VPN protocol”. Then connect again and check that FuzeVPN shows “Protected”.
Restart Windows, then try again.
If the message still comes back, send a report to support.
Windows could not complete the network configuration for the OpenVPN tunnel.
What is happening: a network setting for the OpenVPN connection could not be applied or checked.
What to do (in order; stop as soon as it works):
If FuzeVPN shows “Disconnect”, click it and wait until FuzeVPN shows “Not protected”. Disconnecting also removes the internet block that the kill switch keeps in place after a failure. If you asked to disconnect, stop here once FuzeVPN shows “Not protected”. If you asked to connect, continue with the steps below until FuzeVPN shows “Protected”.
If the internet stays blocked, open the “Diagnostics” page in the side menu and click “Diagnostics”. If “Complete disconnection” is offered below the results, click it. If you later need to contact support while this device is still offline, write from another connected device, such as a phone on mobile data.
If you asked to disconnect, stop here: “Not protected” confirms disconnection. If that confirmation is still missing, contact support. If you asked to connect, start the VPN connection again and wait until FuzeVPN shows “Protected”.
Quit FuzeVPN with “Quit FuzeVPN” in its icon’s menu near the clock, then reopen it with the same Windows account as usual. The cross only minimizes FuzeVPN near the clock. Accept the Windows prompt if it appears, and restart if Windows asks you to.
On Windows, in Automatic mode, FuzeVPN switches to OpenVPN once, only if WireGuard does not start on the PC. If OpenVPN also fails, the OpenVPN message is shown, even if you did not choose OpenVPN. Switch to WireGuard in the meantime: disconnect the VPN, then choose WireGuard in “Settings → Connection → VPN protocol”. Then connect again and check that FuzeVPN shows “Protected”.
Restart Windows, then try again.
If the message still comes back, send a report to support.
Windows could not configure DNS for the OpenVPN tunnel.
What is happening: the DNS setting for the OpenVPN connection could not be applied or confirmed. DNS is used to find the address of websites.
What to do (in order; stop as soon as it works):
If FuzeVPN shows “Disconnect”, click it and wait until FuzeVPN shows “Not protected”. Disconnecting also removes the internet block that the kill switch keeps in place after a failure. If you asked to disconnect, stop here once FuzeVPN shows “Not protected”. If you asked to connect, continue with the steps below until FuzeVPN shows “Protected”.
If the internet stays blocked, open the “Diagnostics” page in the side menu and click “Diagnostics”. If “Complete disconnection” is offered below the results, click it. If you later need to contact support while this device is still offline, write from another connected device, such as a phone on mobile data.
If you asked to disconnect, stop here: “Not protected” confirms disconnection. If that confirmation is still missing, contact support. If you asked to connect, start the VPN connection again and wait until FuzeVPN shows “Protected”.
Quit FuzeVPN with “Quit FuzeVPN” in its icon’s menu near the clock, then reopen it with the same Windows account as usual. The cross only minimizes FuzeVPN near the clock. Accept the Windows prompt if it appears, and restart if Windows asks you to.
On Windows, in Automatic mode, FuzeVPN switches to OpenVPN once, only if WireGuard does not start on the PC. If OpenVPN also fails, the OpenVPN message is shown, even if you did not choose OpenVPN. Switch to WireGuard in the meantime: disconnect the VPN, then choose WireGuard in “Settings → Connection → VPN protocol”. Then connect again and check that FuzeVPN shows “Protected”.
Restart Windows, then try again.
If the message still comes back, send a report to support.
The DCO adapter is open, but the server could not be configured in the driver.
What is happening: OpenVPN started preparing the connection, but the server could not be set up in the DCO adapter, a network driver used by OpenVPN.
What to do (in order; stop as soon as it works):
If FuzeVPN shows “Disconnect”, click it and wait until FuzeVPN shows “Not protected”. Disconnecting also removes the internet block that the kill switch keeps in place after a failure. If you asked to disconnect, stop here once FuzeVPN shows “Not protected”. If you asked to connect, continue with the steps below until FuzeVPN shows “Protected”.
If the internet stays blocked, open the “Diagnostics” page in the side menu and click “Diagnostics”. If “Complete disconnection” is offered below the results, click it. If you later need to contact support while this device is still offline, write from another connected device, such as a phone on mobile data.
If you asked to disconnect, stop here: “Not protected” confirms disconnection. If that confirmation is still missing, contact support. If you asked to connect, start the VPN connection again and wait until FuzeVPN shows “Protected”.
Quit FuzeVPN with “Quit FuzeVPN” in its icon’s menu near the clock, then reopen it with the same Windows account as usual. The cross only minimizes FuzeVPN near the clock. Accept the Windows prompt if it appears, and restart if Windows asks you to.
On Windows, in Automatic mode, FuzeVPN switches to OpenVPN once, only if WireGuard does not start on the PC. If OpenVPN also fails, the OpenVPN message is shown, even if you did not choose OpenVPN. Switch to WireGuard in the meantime: disconnect the VPN, then choose WireGuard in “Settings → Connection → VPN protocol”. Then connect again and check that FuzeVPN shows “Protected”.
Restart Windows, then try again.
If the message still comes back, send a report to support.
An unknown WireGuard error occurred. See the local diagnostic log.
What is happening: FuzeVPN did not recognize this WireGuard error. Its details are in the technical logs, which are included in the diagnostic report.
What to do (in order; stop as soon as it works):
Try another location or another network, then try again.
If FuzeVPN shows “Disconnect”, click it and wait until FuzeVPN shows “Not protected”. Disconnecting also removes the internet block that the kill switch keeps in place after a failure. If you asked to disconnect, stop here once FuzeVPN shows “Not protected”. If you asked to connect, continue with the steps below until FuzeVPN shows “Protected”.
If the internet stays blocked, open the “Diagnostics” page in the side menu and click “Diagnostics”. If “Complete disconnection” is offered below the results, click it. If you later need to contact support while this device is still offline, write from another connected device, such as a phone on mobile data.
If you asked to disconnect, stop here: “Not protected” confirms disconnection. If that confirmation is still missing, contact support. If you asked to connect, start the VPN connection again and wait until FuzeVPN shows “Protected”.
Quit FuzeVPN with “Quit FuzeVPN” in its icon’s menu near the clock, then reopen it with the same Windows account as usual. The cross only minimizes FuzeVPN near the clock. Accept the Windows prompt if it appears, and restart if Windows asks you to.
Switch to OpenVPN: disconnect the VPN, then choose OpenVPN in “Settings → Connection → VPN protocol”. In “Automatic” mode, FuzeVPN already switches to OpenVPN once if WireGuard does not start on your PC. Then connect again and check that FuzeVPN shows “Protected”.
Restart Windows, then try again.
Reinstall FuzeVPN with the installer from the FuzeVPN for Windows page, including if you installed it from the Microsoft Store. If “Repair” is offered, choose it. Your device and preferences are kept. Choose the installer for your processor, x64 or ARM64, shown in Windows Settings → System → About → System type.
Manual updates also keep your device and preferences.
You do not need to open the log yourself: send the diagnostic report to support instead. It contains the app’s technical logs.
An unknown OpenVPN error occurred. See the local diagnostic log.
What is happening: FuzeVPN did not recognize this OpenVPN error. Its details are in the technical logs, which are included in the diagnostic report.
What to do (in order; stop as soon as it works):
Try another location or another network, then try again.
If FuzeVPN shows “Disconnect”, click it and wait until FuzeVPN shows “Not protected”. Disconnecting also removes the internet block that the kill switch keeps in place after a failure. If you asked to disconnect, stop here once FuzeVPN shows “Not protected”. If you asked to connect, continue with the steps below until FuzeVPN shows “Protected”.
If the internet stays blocked, open the “Diagnostics” page in the side menu and click “Diagnostics”. If “Complete disconnection” is offered below the results, click it. If you later need to contact support while this device is still offline, write from another connected device, such as a phone on mobile data.
If you asked to disconnect, stop here: “Not protected” confirms disconnection. If that confirmation is still missing, contact support. If you asked to connect, start the VPN connection again and wait until FuzeVPN shows “Protected”.
Quit FuzeVPN with “Quit FuzeVPN” in its icon’s menu near the clock, then reopen it with the same Windows account as usual. The cross only minimizes FuzeVPN near the clock. Accept the Windows prompt if it appears, and restart if Windows asks you to.
On Windows, in Automatic mode, FuzeVPN switches to OpenVPN once, only if WireGuard does not start on the PC. If OpenVPN also fails, the OpenVPN message is shown, even if you did not choose OpenVPN. Switch to WireGuard in the meantime: disconnect the VPN, then choose WireGuard in “Settings → Connection → VPN protocol”. Then connect again and check that FuzeVPN shows “Protected”.
Restart Windows, then try again.
Reinstall FuzeVPN with the installer from the FuzeVPN for Windows page, including if you installed it from the Microsoft Store. If “Repair” is offered, choose it. Your device and preferences are kept. Choose the installer for your processor, x64 or ARM64, shown in Windows Settings → System → About → System type.
Manual updates also keep your device and preferences.
You do not need to open the log yourself: send the diagnostic report to support instead. It contains the app’s technical logs.
FuzeVPN component unavailable or invalid response
The OpenVPN DCO adapter could not be used.
What is happening: the OpenVPN DCO adapter, a network driver used by OpenVPN, could not be installed, opened or used.
What to do (in order; stop as soon as it works):
Quit FuzeVPN with “Quit FuzeVPN” in its icon’s menu near the clock, then reopen it with the same Windows account as usual. The cross only minimizes FuzeVPN near the clock. Accept the Windows prompt if it appears, and restart if Windows asks you to.
If FuzeVPN shows “Disconnect”, click it and wait until FuzeVPN shows “Not protected”. Disconnecting also removes the internet block that the kill switch keeps in place after a failure. If you asked to disconnect, stop here once FuzeVPN shows “Not protected”. If you asked to connect, continue with the steps below until FuzeVPN shows “Protected”.
If the internet stays blocked, open the “Diagnostics” page in the side menu and click “Diagnostics”. If “Complete disconnection” is offered below the results, click it. If you later need to contact support while this device is still offline, write from another connected device, such as a phone on mobile data.
If you asked to disconnect, stop here: “Not protected” confirms disconnection. If that confirmation is still missing, contact support. If you asked to connect, start the VPN connection again and wait until FuzeVPN shows “Protected”.
On Windows, in Automatic mode, FuzeVPN switches to OpenVPN once, only if WireGuard does not start on the PC. If OpenVPN also fails, the OpenVPN message is shown, even if you did not choose OpenVPN. Switch to WireGuard in the meantime: disconnect the VPN, then choose WireGuard in “Settings → Connection → VPN protocol”. Then connect again and check that FuzeVPN shows “Protected”.
Restart Windows, then try again.
Reinstall FuzeVPN with the installer from the FuzeVPN for Windows page, including if you installed it from the Microsoft Store. If “Repair” is offered, choose it. Your device and preferences are kept. Choose the installer for your processor, x64 or ARM64, shown in Windows Settings → System → About → System type.
Manual updates also keep your device and preferences.
If the message still comes back, send a report to support.
The secure OpenVPN component is unavailable.
What is happening: the part of FuzeVPN that prepares this PC’s secure OpenVPN identity is not available.
What to do (in order; stop as soon as it works):
Quit FuzeVPN with “Quit FuzeVPN” in its icon’s menu near the clock, then reopen it with the same Windows account as usual. The cross only minimizes FuzeVPN near the clock. Accept the Windows prompt if it appears, and restart if Windows asks you to.
If FuzeVPN shows “Disconnect”, click it and wait until FuzeVPN shows “Not protected”. Disconnecting also removes the internet block that the kill switch keeps in place after a failure. If you asked to disconnect, stop here once FuzeVPN shows “Not protected”. If you asked to connect, continue with the steps below until FuzeVPN shows “Protected”.
If the internet stays blocked, open the “Diagnostics” page in the side menu and click “Diagnostics”. If “Complete disconnection” is offered below the results, click it. If you later need to contact support while this device is still offline, write from another connected device, such as a phone on mobile data.
If you asked to disconnect, stop here: “Not protected” confirms disconnection. If that confirmation is still missing, contact support. If you asked to connect, start the VPN connection again and wait until FuzeVPN shows “Protected”.
On Windows, in Automatic mode, FuzeVPN switches to OpenVPN once, only if WireGuard does not start on the PC. If OpenVPN also fails, the OpenVPN message is shown, even if you did not choose OpenVPN. Switch to WireGuard in the meantime: disconnect the VPN, then choose WireGuard in “Settings → Connection → VPN protocol”. Then connect again and check that FuzeVPN shows “Protected”.
Restart Windows, then try again.
Reinstall FuzeVPN with the installer from the FuzeVPN for Windows page, including if you installed it from the Microsoft Store. If “Repair” is offered, choose it. Your device and preferences are kept. Choose the installer for your processor, x64 or ARM64, shown in Windows Settings → System → About → System type.
Manual updates also keep your device and preferences.
If the message still comes back, send a report to support.
The response from the local WireGuard service was invalid.
What is happening: FuzeVPN’s VPN service, on your computer, replied in a format the app does not understand.
What to do (in order; stop as soon as it works):
Quit FuzeVPN with “Quit FuzeVPN” in its icon’s menu near the clock, then reopen it with the same Windows account as usual. The cross only minimizes FuzeVPN near the clock. Accept the Windows prompt if it appears, and restart if Windows asks you to.
If FuzeVPN shows “Disconnect”, click it and wait until FuzeVPN shows “Not protected”. Disconnecting also removes the internet block that the kill switch keeps in place after a failure. If you asked to disconnect, stop here once FuzeVPN shows “Not protected”. If you asked to connect, continue with the steps below until FuzeVPN shows “Protected”.
If the internet stays blocked, open the “Diagnostics” page in the side menu and click “Diagnostics”. If “Complete disconnection” is offered below the results, click it. If you later need to contact support while this device is still offline, write from another connected device, such as a phone on mobile data.
If you asked to disconnect, stop here: “Not protected” confirms disconnection. If that confirmation is still missing, contact support. If you asked to connect, start the VPN connection again and wait until FuzeVPN shows “Protected”.
Switch to OpenVPN: disconnect the VPN, then choose OpenVPN in “Settings → Connection → VPN protocol”. In “Automatic” mode, FuzeVPN already switches to OpenVPN once if WireGuard does not start on your PC. Then connect again and check that FuzeVPN shows “Protected”.
Restart Windows, then try again.
Reinstall FuzeVPN with the installer from the FuzeVPN for Windows page, including if you installed it from the Microsoft Store. If “Repair” is offered, choose it. Your device and preferences are kept. Choose the installer for your processor, x64 or ARM64, shown in Windows Settings → System → About → System type.
Manual updates also keep your device and preferences.
If the message still comes back, send a report to support.
The response from the local OpenVPN service was invalid.
What is happening: FuzeVPN’s VPN service, on your computer, replied in a format the app does not understand.
What to do (in order; stop as soon as it works):
Quit FuzeVPN with “Quit FuzeVPN” in its icon’s menu near the clock, then reopen it with the same Windows account as usual. The cross only minimizes FuzeVPN near the clock. Accept the Windows prompt if it appears, and restart if Windows asks you to.
If FuzeVPN shows “Disconnect”, click it and wait until FuzeVPN shows “Not protected”. Disconnecting also removes the internet block that the kill switch keeps in place after a failure. If you asked to disconnect, stop here once FuzeVPN shows “Not protected”. If you asked to connect, continue with the steps below until FuzeVPN shows “Protected”.
If the internet stays blocked, open the “Diagnostics” page in the side menu and click “Diagnostics”. If “Complete disconnection” is offered below the results, click it. If you later need to contact support while this device is still offline, write from another connected device, such as a phone on mobile data.
If you asked to disconnect, stop here: “Not protected” confirms disconnection. If that confirmation is still missing, contact support. If you asked to connect, start the VPN connection again and wait until FuzeVPN shows “Protected”.
On Windows, in Automatic mode, FuzeVPN switches to OpenVPN once, only if WireGuard does not start on the PC. If OpenVPN also fails, the OpenVPN message is shown, even if you did not choose OpenVPN. Switch to WireGuard in the meantime: disconnect the VPN, then choose WireGuard in “Settings → Connection → VPN protocol”. Then connect again and check that FuzeVPN shows “Protected”.
Restart Windows, then try again.
Reinstall FuzeVPN with the installer from the FuzeVPN for Windows page, including if you installed it from the Microsoft Store. If “Repair” is offered, choose it. Your device and preferences are kept. Choose the installer for your processor, x64 or ARM64, shown in Windows Settings → System → About → System type.
Manual updates also keep your device and preferences.
If the message still comes back, send a report to support.
Send a report to support
Open the “Diagnostics” page in the side menu and click “Diagnostics”. If “Send” appears, click it to send the report. With automatic reporting turned on, the report is sent automatically. If an account is signed in, the report ID appears after sending. For a report still waiting to be sent, FuzeVPN makes up to 5 automatic attempts within 24 hours. “Try again” sends it again. If the service refuses the report, use email instead. Open “Complete diagnostic”, select its text, copy it and paste it into an email.
Then write to support at contact@fuzevpn.com, with the exact message and the report ID if shown. Copy the codes from the Diagnostics page: “Error code”, “HTTP”, “TLS” or “Windows code”. Also include the time, the FuzeVPN version if visible, and the location, protocol and network used. If you are not signed in, open “Complete diagnostic” and copy its text into your email to support. We reply within 72 hours, in your language.