ZBEVPN ZBEVPN
ZBEVPN installation guide

Failed to install ZBEVPN? Windows installation requirements and troubleshooting

Use this guide when ZBEVPN does not finish installing, Windows blocks the setup, or the Microsoft Store installation appears to fail before the app is usable. If ZBEVPN is already installed but cannot sign in or connect, use the post-install troubleshooting guide instead.

Before you install: basic requirements

ZBEVPN for Windows installs a desktop application, a background Windows service, required Microsoft components, and VPN networking support. Because those changes affect the system, installation must be approved by an administrator.

Use a Windows administrator account

Windows may ask: “Do you want to allow this app to make changes to your device?” This is expected. Choose Yes only when the installer came from the official ZBEVPN source.

Use the official download or Store listing

Download ZBEVPN only from the official ZBEVPN portal or the official Microsoft Store listing. Avoid old copies, file-sharing links, and repackaged installers.

Keep enough free disk space

Keep at least 2 GB free on the Windows system drive, usually C:. The installer needs space for temporary extraction, application files, components, and logs.

Restart Windows if updates are pending

Windows Update, Microsoft runtime installers, and service changes can leave the system waiting for a reboot. Restart first if another installation or update recently ran.

Recommended clean installation steps

  1. Close ZBEVPN if it is already open. If two ZBEVPN windows are open, close both windows using the X button before continuing.
  2. Restart Windows, especially if you are upgrading from an older version or if the app window was open during the previous install attempt.
  3. Download or open ZBEVPN from the official source.
  4. Approve the Windows administrator prompt when the installer asks to make changes to your device.
  5. Do not close the Microsoft Store or installer window until setup finishes.
  6. After installation completes, double-click the ZBEVPN desktop icon, or open ZBEVPN from the Start menu.
  7. When ZBEVPN starts, choose Yes if Windows asks to allow the required ZBEVPN service component to run.
Important: this page is for installation and first-start failures. If the app opens normally but sign-in, location selection, or VPN connection fails afterward, the installation itself probably succeeded. Use the “Installed but not working?” guide for those cases.

First start after installation

After setup completes, start ZBEVPN by double-clicking the desktop icon or opening it from the Start menu. Windows may ask for approval to allow a required ZBEVPN service component to run. Choose Yes. This service component is required for the VPN client to operate correctly.

If two ZBEVPN windows appear

Keep only one ZBEVPN window open. If two app windows are visible, close both windows using the X button, wait a few seconds, then double-click the ZBEVPN icon once to start the app again. Running two app windows can confuse first-start approval and can keep old files locked during upgrades.

If the approval prompt does not appear

Close the ZBEVPN window, wait a few seconds, and start the app again from the desktop icon or Start menu. If the app still does not prompt and does not continue, restart Windows and open ZBEVPN again.

If the app is stuck on the login screen

Close ZBEVPN completely and start it again. If two windows are open, close both. Then double-click the ZBEVPN icon once and allow the required service component if Windows asks. If the login screen is still stuck after restarting the app, restart Windows and try again.

Installation problems and fixes

Most common

1. Administrator approval was not completed

ZBEVPN cannot install correctly without administrator approval because it installs under C:\Program Files, creates a Windows service, registers uninstall information, and installs networking support.

Fix: run the installer again and approve the Windows prompt. If this is a work, school, or managed device and you do not have administrator rights, ask the device administrator to approve the installation.

Upgrade issue

2. Previous ZBEVPN files are still locked

During an upgrade, Windows may still have the old ZBEVPN window, background service, or executable open in memory. This can lock files in C:\Program Files\ZBEVPN and stop the new installer from replacing them.

Fix: close ZBEVPN completely. If two ZBEVPN windows are open, close both with the X button. Then restart Windows and run the installer again before opening ZBEVPN or another VPN application.

Windows state

3. Windows is waiting for a reboot

Installation can fail when Windows is still finishing updates, another uninstall, a Microsoft runtime change, or service cleanup from a previous install.

Fix: restart Windows, sign back in, and start the ZBEVPN installation again.

Microsoft components

4. Required Microsoft components could not be installed

ZBEVPN setup may install or verify required Microsoft components, including the Microsoft .NET Desktop Runtime and Microsoft Visual C++ Redistributable. On some systems, these component installers are blocked by a pending reboot, Windows Installer state, security software, or device policy.

Fix: restart Windows and retry. If installation still fails, install the required Microsoft components from Microsoft, then run ZBEVPN setup again. Use the official .NET 8 download page and the official latest supported Visual C++ Redistributable downloads page.

Security policy

5. Antivirus, Smart App Control, AppLocker, or managed-device policy blocked setup

VPN applications install services and networking components. Some antivirus products, endpoint protection, Smart App Control, AppLocker, or corporate device-management policies can block service creation, runtime installers, VPN components, or executable files.

Fix: check Windows Security, antivirus alerts, or work/school device notifications. On a managed device, ask the administrator whether VPN client installation and Windows service creation are allowed.

Disk space

6. The system drive does not have enough free space

Setup needs space for temporary extraction, application files, logs, and required components. Very low disk space can interrupt the installer before it finishes.

Fix: free at least 2 GB on C:, empty temporary files if needed, restart Windows, and run the installer again.

Download or Store flow

7. Download or Microsoft Store installation was interrupted

If the Microsoft Store, browser download, or installer extraction was interrupted, Windows may keep an incomplete temporary copy.

Fix: restart Windows, download or open ZBEVPN again from the official source, and leave the installer open until it finishes.

Other network tools

8. Another VPN or network utility interfered with setup

Other VPN clients, security suites, packet filters, virtualization tools, or network adapters can sometimes interfere with VPN component installation or service startup.

Fix: disconnect other VPN clients, restart Windows, install ZBEVPN first, then reopen other network tools only after setup completes.

When to use the post-install troubleshooting guide

If installation finished and the ZBEVPN app opens normally, but the app cannot sign in, cannot connect, cannot reach the VPN location, or the VPN tunnel does not come up, use the separate post-install guide. Those problems usually involve network access, firewall rules, account state, proxies, local routing, or blocked VPN traffic rather than installer failure.

What to send to support

If installation still does not complete, send support these details:

  • Windows version and whether the device is personal, work, school, or managed.
  • Whether the Windows administrator prompt appeared and whether you were able to approve it.
  • The exact error message or a screenshot of the installer failure.
  • Whether this was a first install or an upgrade from an older ZBEVPN version.
  • How much free space is available on C:.
  • Whether antivirus, Windows Security, AppLocker, Smart App Control, or corporate endpoint software showed a warning.