Oblivion Desktop
Releases and project status
See what changed, choose a build, and check whether an older guide still applies to your app.
Release and repository status checked on .
Latest stable release
v3.11.0
Released
Choose your downloadOriginal release notesRepository archived
What does that mean for you?
The Desktop repository on GitHub is archived and is no longer actively maintained. Published releases and download assets remain listed, but issues, comments and code are read-only. New issues cannot be filed there while it is archived.
The sources we checked do not establish a reason for archiving or a date for another release. Future fixes and security updates are not confirmed.
Archiving the repository does not uninstall or disable the copy on your computer. Whether it can connect still depends on your network and the services it uses.
Newest to oldest
Changes that matter in use
Selected changes from the original release notes. Open a version’s notes for its full changelog. “Pre-release” follows the GitHub label; an unlabelled release can still contain experimental features.
v3.11.0
Helper, proxy reset and startup
Release notes list fixes for Oblivion-Helper and Proxy-Reset processes, improved startup behaviour, and dependency updates. Start here when comparing an older build with a helper or startup problem.
Notes for v3.11.0v3.10.0
DNS resolution and waking from sleep
Notes list a new local DNS resolver, a fix for disconnection after sleep, proxy-mode initialisation fixes and updated helper components.
Notes for v3.10.0v3.1.3Pre-release
Masque hidden on 32-bit Windows
The Masque option was hidden on ia32 builds because Usque did not support that architecture. A missing option in a 32-bit build is not an endpoint error.
Notes for v3.1.3v3.0.0
Masque added
Introduced the Masque connection method and improvements to custom endpoint handling. This is the relevant milestone when an older guide shows no Masque option.
Notes for v3.0.0v2.106.5
TUN restored as the default
TUN became the default network mode again. The default changed over time; check the mode actually selected in your app.
Notes for v2.106.5v2.97.8
System Proxy temporarily became the default
Changed the default to System Proxy to address an initial Cloudflare connection problem. This was a change for this release, not a permanent rule for Desktop.
Notes for v2.97.8v2.68.0
Default changed to TUN
Changed the default network mode from System Proxy to TUN. Compare this with the later changes in 2.97.8 and 2.106.5 when following an old tutorial.
Notes for v2.68.0v2.64.9Pre-release
Windows updater introduced
Added an in-app updater for Windows. This did not introduce the same installation workflow on macOS and Linux.
Notes for v2.64.9v2.45.0
License tab removed
Release notes describe the License tab as temporarily removed. The tab remains unavailable in the checked 3.11.0 interface; “temporary” was not a return date.
Notes for v2.45.0v2.40.0
Automatic DNS setup for macOS TUN
Added automatic DNS configuration for TUN on macOS and removed TUN’s experimental label. Older instructions to set DNS manually may no longer apply; do not erase DNS settings required by your network administrator.
Notes for v2.40.0v2.0.2
First experimental TUN mode
Introduced an experimental full-system TUN mode using Sing-box and Oblivion-Helper. TUN was experimental even though this release is not marked as a GitHub pre-release.
Notes for v2.0.2
Check your version and update
Open About App from the app menu to see your installed version. Compare it with 3.11.0, then note your operating system and architecture before choosing a package.
- Windows: the app’s Update action can download and launch an installer for your architecture. Administrator approval may be needed. If that route fails, use the original Windows downloads and installation guide. The updater uses an EXE installer; if you use the ZIP version and want to keep that installation format, download the ZIP manually.
- macOS and Linux: the Update action opens the release download page. Download the matching package and install it using the method appropriate to that package. See macOS files or Linux files for architecture, package formats and requirements.
The Beta Update option is on the App settings tab, under More Settings. Scroll down to find it. It allows update checks to include pre-releases; it does not mean that a newer beta exists. Leave it off if you only want stable releases.
These instructions apply to v3.11.0. The update paths follow the versioned updater code; the complete update process has not been tested on every operating system.
Older versions and beta releases
Use the complete GitHub release list to find a specific tag, then expand Assets and select a file for your operating system and architecture. The Source code ZIP and tar.gz archives contain source files, not ready-to-run installers.
A higher position in an old guide does not make a build current. The newest listed pre-release is 3.10.5, published 5 November 2025; stable 3.11.0 came later, on 10 November 2025. Compare the version, release date and Pre-release label together.
An older build can lack later fixes. We have not verified downgrade compatibility or a safe rollback path for every version, and do not maintain a verified list of older builds for unsupported operating systems. Check the current requirements before downloading.
A release mentions my problem. Is it fixed?
Release notes describe the changes shipped. A closed issue or a listed fix does not show that every network or computer is affected in the same way. For example, 3.11.0 references helper and startup issue #1175; that is a reason to compare versions, not proof that every proxy-reset problem is resolved.
If a problem remains, record your version, operating system, connection method, network mode and the relevant log lines. Remove personal information before sharing logs. Use the connection checks for a connection failure, or the Windows guide for installer and helper problems. For a missing method, country selector or License tab, see connection methods and IP location.
Changing versions alone does not identify the cause. Check the selected network mode after an update, especially when comparing builds across the default-mode changes above.