Start your 3-day free trial
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.


When a VPN client still uses old settings after a profile update, the new file may have been saved without replacing the selected profile, or a different app, system service, or managed policy may still own the active tunnel. Prove each layer before deleting anything.
The complete VPN guide provides the broader model. This guide follows the update from source revision to stored profile, selected owner, running interface, routes, and verified traffic.
Scope: use only issuer-authorized workflows on the client and operating-system versions supported by its documentation. This guide follows the official documentation listed below; no complete end-to-end test was performed. Client-specific behavior must be checked against your installed version.
Key Takeaways
- Confirm that the source itself changed by using an issue time, version, profile label, or other non-secret marker.
- Identify the client or operating-system service that owns the active tunnel before importing again.
- Determine whether import replaces an existing profile, creates a duplicate, or requires an explicit reconnect or reload.
- Compare non-secret fields and runtime evidence; never post a private key, token, certificate, or complete configuration.
- Keep the last recoverable profile until the replacement connects and follows the intended path.
Begin at the source, not the client. Confirm the provider or administrator issued a new revision for the same intended account, team, device, or environment. Useful non-secret evidence includes issue time, expiry, profile display name, endpoint hostname or region, protocol, certificate validity dates, and a documented version identifier.
Do not compare complete configuration text in a public diff. Files can contain private keys, preshared keys, passwords, access tokens, certificates, internal routes, and identifiers. Compare only fields the issuer designates as safe. If you received the replacement through a file or URL, follow the secure VPN configuration import guide.
A new filename is weak evidence. A browser may append a number while downloading the same bytes, and an administrator may update the portal without regenerating the profile. Conversely, the same filename can deliver a new revision. Record provenance and metadata instead of relying on the name.
Many devices can hold several VPN definitions: a provider app profile, a system settings profile, an enterprise-managed profile, a browser extension, a command-line interface, or another VPN client. Importing into one store does not replace an object owned by another.
Before changing anything, record:
Disconnect through the current owner rather than force-killing unrelated services. If the profile is managed, the user may not have authority to replace it; contact the administrator instead of attempting to remove controls.
With AethoVPN, trust the profile issued under your own account: on Windows, Debian/Ubuntu x64 or Android the app connects after you continue with your email code, and on a Mac, iPhone or iPad the configuration comes from the official setup guide, which needs a Pro or Premium plan. On Windows, Debian/Ubuntu x64 and Android, compare the AethoVPN app's connection with the recorded owner; on Mac, iPhone and iPad, check the VPN client or system profile actually using the issued configuration. Disconnect only a confirmed old or unintended tunnel through its owner, with authorization and a known recovery path; do not disconnect the client using the intended configuration merely because it is another app.
An owner record alone cannot prove that the new settings are active or old credentials are revoked; use the runtime checks below and issuer confirmation for revocation. Download the current client for your device to start the check from the current build.
Import behavior is client-specific. For Windows .ocfg global configuration imports, OpenVPN Connect documents that an active VPN connection prevents import, and a contained profile or proxy with an existing name prompts replacement or retention.[1] This is not a universal rule for standalone .ovpn imports: another workflow may create a second entry, compare an internal identifier, or reject the import.
Look for two entries with similar names, suffixes such as “2” or “copy,” different modification times, or different endpoint labels. Do not assume the most recent item is selected. A duplicate can exist while auto-connect, a shortcut, or the operating system still points to the older object.
If the client explicitly offers replace, read what will be preserved or removed before confirming. Account credentials may be stored separately from the imported profile, while certificates or private keys may be embedded. Keep a recovery copy through the issuer’s approved channel until the new profile works.
Use a controlled sequence and make one state transition at a time:
For command-line WireGuard setups, the wg-quick manual documents down, up, and save, while strip can produce a configuration for reload patterns.[2] A careless save can write current runtime state back to the file, so use the documented workflow for the actual owner rather than copying commands blindly.
Microsoft’s Azure VPN Gateway documentation likewise describes downloading a new client profile after gateway configuration changes and applying it to clients.[3] This supports the general lesson that changing the server-side source does not automatically update every installed client; it is not a procedure for unrelated providers.
Distinguish failure to load from an old active profile. Record the previous and target core versions, actual configuration path, and redacted field error. For sing-box, consult the matching migration entry: the TUN inet4_address/inet6_address fields were merged into address in 1.10.0, and the old fields were removed in 1.12.0.[4][5] This is a version-specific example, not a rule to delete every unknown field.
Keep a private recovery copy, migrate only the affected settings, then use the target binary's documented sing-box check with the intended configuration; confirm its file-selection options before running it.[6] A passing check proves configuration acceptance, not connectivity. If checking fails, stop before replacing the active profile; restore the supported previous binary and matching configuration only when the security policy permits rollback. After acceptance, use the runtime checks below.
For sing-box specifically, the DNS configuration migration guide walks through moving legacy DNS servers to the typed format, checking bootstrap and keeping a matching backup.
Verify its official release history, security notices and maintainer statement first. A GitHub archive marks a repository read-only and no longer actively maintained; one broken download or a rumor does not establish that status.[7] Record the evidence date without assuming that another client or core is also abandoned.
Use the replacement's official distribution and issuer-approved configuration. Check protocol, TLS, UDP, route/DNS policy and credential-store compatibility rather than copying its private database. Reissue or revoke affected keys, tokens or device grants through the issuer when required, and verify old access is rejected where supported. Deleting the old app is not revocation. Keep only a policy-approved rollback pair; after compromise or a security-mandated revocation, obtain fresh recovery material instead of reusing the old credentials.
Use two kinds of evidence. First, compare non-secret configuration facts: profile label, documented revision, endpoint hostname or region, protocol, route scope, DNS policy label, certificate validity dates, or issuer-provided public identifier. Never disclose private keys or complete certificates merely to prove a difference.
Second, compare runtime facts after reconnecting: connection start time, active owner, selected profile, peer or endpoint label, route entries, and a bounded traffic result. The client’s “import successful” message proves only storage or parsing. A “connected” label does not by itself prove that the intended routes or DNS policy are active.
Use the VPN connection testing guide for layered path checks. Keep the test small and reversible. Do not change DNS, protocol, server, and profile simultaneously, because success would not identify which transition fixed the problem.
An auto-connect rule, managed policy, startup service, scheduled task, or second client may reselect the old profile. Record exactly when the reversion occurs: immediately after import, on connect, after app restart, after device restart, or after a network change. That timing identifies the likely owner.
Check the supported startup and policy controls for the app and operating system. Do not disable security software, remove device management, or edit system databases to win a configuration race. If a managed profile reappears, the management server is the source of truth and the administrator must publish the replacement.
Also distinguish cached display from runtime state. A screen can show an old label while the active endpoint changed, or show a new profile while a separate system tunnel remains active. Use both configuration and runtime evidence before concluding that settings reverted.
Remove the old entry only after the replacement is stored, selected, connected, and verified on the intended path, and after you know how to recover if the next restart fails. Preserve any administrator-required rollback period. If old credentials were revoked for security reasons, follow the issuer’s incident instructions rather than keeping a usable fallback.
Before removal, export nothing unless the provider approves it; exporting may create another secret-bearing file. Record the old profile’s non-secret name and owner, then remove it through that owner’s supported interface. If the profile cannot be removed, use the separate profile removal troubleshooting guide instead of escalating to destructive system edits.
Reconnect once after removal and, when appropriate, restart the responsible client to prove that no shortcut or auto-connect rule still references the deleted object. Stop if removal affects an unrelated managed or corporate tunnel.
Provide the device and operating-system version, client name and version, approximate import time, profile labels, source revision, when the old settings reappear, the exact non-secret error, and which layer you verified. Include a short transition log such as “disconnected owner A, replaced profile B, explicitly selected B, reconnected at 14:10, endpoint label remained C.”
Redact private keys, preshared keys, tokens, passwords, QR codes, subscription URLs, full configuration files, internal addresses, and account identifiers. Use only the official support channel and follow its secure-upload instructions if diagnostic bundles are required.
The client may use an internal identifier rather than the visible filename or may require explicit replacement confirmation. Compare safe metadata and select the intended entry instead of importing repeatedly.
Sometimes, but not universally. The active tunnel may belong to a system service, managed profile, or another client, and some settings load only after an explicit disconnect and reconnect.
That is risky unless the issuer requires immediate revocation and provides recovery. Normally, keep the last recoverable profile until the replacement connects and passes a bounded path test.
An auto-connect rule, startup service, managed policy, shortcut, or second VPN client may select the old object. The moment of reversion helps identify which owner is restoring it.
Compare issuer-approved non-secret fields such as profile label, revision, endpoint hostname or region, protocol, route scope, and validity dates. Never post complete files, private keys, tokens, or QR codes.
No. Confirm the selected owner and safe profile fields, then verify routes, DNS policy, and one bounded traffic path. A status label alone can reflect stale UI or another tunnel.
Identify its owner first. A provider app, operating system, or device-management service may control removal; use its supported procedure and do not bypass administrative policy.
Disclaimer: This guide provides general technical information. Profile ownership, import, reload, and management behavior vary by VPN client, operating system, provider, and administrator.
Sources:
OpenVPN Connect - Windows Global Configuration File Support — https://openvpn.net/connect-docs/windows-global-configuration-file-support.html
WireGuard Tools - wg-quick(8) Manual — https://git.zx2c4.com/wireguard-tools/tree/src/man/wg-quick.8
Microsoft Learn - Update VPN Client Profile for Point-to-Site Connections — https://learn.microsoft.com/en-us/azure/vpn-gateway/point-to-site-user-vpn-profile-update
sing-box - Migration — https://sing-box.sagernet.org/migration/
sing-box - Deprecated Feature List — https://sing-box.sagernet.org/deprecated/
sing-box - Configuration Introduction — https://sing-box.sagernet.org/configuration/
GitHub Docs - Archiving repositories — https://docs.github.com/en/repositories/archiving-a-github-repository/archiving-repositories
Sources checked 9 October 2026.
Related articles:
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.