Oblivion Desktop on Windows

1. Choose your Windows package

Desktop 3.11.0 lists Windows 10 or later as its minimum. Open Settings → System → About and check System type before downloading. A 64-bit processor running 32-bit Windows still needs the ia32 package.

Choose EXE for a normal installation. Choose ZIP to run the extracted application without the installer. Download the application package, not GitHub’s “Source code” archive. You can also compare all Windows downloads.

The 3.11.0 release is the latest stable release checked on 5 November 2026. The Desktop repository is archived; these requirements do not promise compatibility with every later Windows update. This guide covers Oblivion Desktop, not the separate Oblivion app.

2. Install the EXE or extract the ZIP

EXE installer

1. Disconnect and quit any running copy of Oblivion Desktop before installing or updating.
2. Open the downloaded oblivion-desktop-win-…exe. Follow the installer and choose the installation folder. A Windows permission prompt can appear during installation; approve it only for the package you intended to run.
3. Finish setup and open Oblivion Desktop from Start. You should reach the application window. If it does not appear, go to launch and permission errors.

ZIP archive

1. Right-click the ZIP and choose Extract All. Use a permanent folder you can write to, such as a folder inside your user directory.
2. Open the extracted folder and run oblivion-desktop.exe. Keep its neighbouring folders and files together.
3. Do not run it directly inside WinRAR or another archive viewer: that can launch a temporary extracted copy. For an update, extract into a new folder after quitting the old copy; do not mix files from two releases.

Portable does not mean “no files outside this folder.” Desktop copies helper components into its user-data directory, normally %APPDATA%\oblivion-desktop. Installed and ZIP copies can therefore interact with the same user data. Use one copy at a time; deleting an extracted folder is not a complete settings reset. File handling in 3.11.0

If SmartScreen or your antivirus blocks the download or launch, read the warning and confirm the release URL and filename before proceeding. For a removed or quarantined file, use the missing-component checks. Do not turn off protection to complete these steps.

3. Make your first connection

1. Check that ordinary internet access works before connecting. Temporarily disconnect another VPN if you have one running; you can reconnect it after the test.
2. Open Desktop and note the connection method and network mode. System Proxy sets Windows proxy settings for applications that use them; TUN uses a virtual network interface. Proxy / None alone requires configuring the receiving application. Leave advanced settings unchanged for the first attempt.
3. Press the main connection button once. In TUN mode, Windows may ask permission to start oblivion-helper.exe. Approve only if it belongs to the Desktop copy you just launched. Cancelling prevents that helper from starting; disconnect and retry when you are ready to approve it. This permission is separate from Add to Exceptions, which changes antivirus settings. Windows helper startup
4. Wait for the connected state, then open a website in the application you want to use. A connected indicator alone does not establish that every app is using the connection.
5. Disconnect in Desktop when finished. Confirm that normal browsing still works before quitting.

If the window opens but connection fails, open App Log and keep the first error with the lines immediately before it. If a local error below matches, resolve that first. Otherwise continue to connection help. If browsing stops after disconnecting, check for a leftover system proxy.

Network modes in the project documentation

“The warp-plus file is not found” or a blocked component

This means a required component is unavailable; changing endpoints will not restore it. Start with the filename and path in the log. A message mentioning WarpPlus can accompany a failure to run masque-plus.exe, as the 3.0.0 report #1105 shows.

1. Quit Desktop. For ZIP, confirm that the whole archive was extracted and its resources folder is still present.
2. Open Windows Security → Virus & threat protection → Protection history, or your antivirus’s quarantine history. Compare the detected file’s path and time with the failure. Detailed records may require administrator access.
3. If a file was blocked, keep its detection name and verify where the package came from. The project has reported false positives, but that does not prove every detected file is safe. Leave an uncertain file quarantined; ask your security administrator or antivirus vendor to review it.
4. If extraction was incomplete and no security block is recorded, download the matching complete package again from the release above, reinstall or extract into a fresh folder, and retry once. Do not obtain a loose warp-plus.exe from an unrelated download site.

Desktop may offer Add to Exceptions. This changes antivirus exclusions; it is not a connection permission. Do not accept it automatically. A persistent block needs review, not repeated reinstalls. If you previously allowed a detection, Microsoft explains how to undo that under Allowed threats in its Protection history guide.

Project’s missing-file guidance · 3.11.0 exclusion handling

PowerShell or “Command Failed: tasklist”

These errors concern Windows tools used by the app. First check whether Windows can find and run them. Open Command Prompt (cmd), without elevation, and run these read-only checks one at a time:

where.exe powershell.exe
where.exe tasklist.exe
powershell.exe -NoProfile -Command "$PSVersionTable.PSVersion"
tasklist.exe

The first two commands should show file paths; the next two should show a version and a process list. If a tool is “not recognized”, try its standard Windows location:

"%SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -Command "$PSVersionTable.PSVersion"
"%SystemRoot%\System32\tasklist.exe"

• The full path works, but the short name does not: check Path in Edit the system environment variables → Environment Variables. Save its existing entries first. Add only the missing directory for the affected tool: %SystemRoot%\System32 or %SystemRoot%\System32\WindowsPowerShell\v1.0. Preserve every other entry. Reopen Command Prompt and Desktop, then repeat the checks. Restore your saved entries if you need to undo the edit.
• The full path also fails: keep the exact message. A missing file, access denial and an organisation’s policy block need different remedies. For missing or damaged Windows files, follow Microsoft’s repair procedure: in an administrator Command Prompt, run DISM.exe /Online /Cleanup-image /Restorehealth; after successful completion, run sfc /scannow. Retest the tools afterward. Do not download replacement system executables or override a managed PC’s policy.
• Both tools run: record the full command that fails in Desktop. Installing PowerShell 7 is not a substitute for checking powershell.exe; do not change script execution policy merely because a message contains “PowerShell”.

PowerShell opens, but Desktop reports a module error? PowerShell module error detected or a message that Start-Process was found in Microsoft.PowerShell.Management but could not load points to a separate module problem. In Command Prompt, run powershell.exe -NoProfile -Command "Get-Command Start-Process". It should identify the command. If module loading fails, keep that error and use the Windows repair route above or your administrator; adding a PATH entry alone will not repair the module. Desktop’s module-error handling · Microsoft: Get-Command

Project tasklist guide · Microsoft: where

Socket permissions or an occupied port

For An attempt was made to access a socket in a way forbidden by its access permissions, note the address and port in App Log. Close duplicate Desktop instances and disconnect other proxy tools you recognise, then retry once.

The default proxy port is 8086. System Proxy also uses a PAC port equal to the proxy port plus one: normally 8087. A conflict on either can matter. If you change the local proxy port in Desktop’s network settings, record the old value, choose an unused port with the next port also available, and update any manually configured client. Disconnect before changing it; restore both settings if the test does not help. Ports used by Desktop

An access-permission error does not by itself identify the process or rule responsible. The older socket wiki proposes restarting Windows HNS. That affects virtual networking: ask your administrator to investigate it when the simple checks fail, rather than stopping Windows services as a routine fix.

EPERM, Access denied, or no window after an update

Check the operation after the error code:

If no window appears, check the notification area for Desktop first. Quit it there. If it is stuck, use Task Manager to end the clearly identified Desktop process, then open one copy. Check whether the shortcut still points to an older installation. If needed, restart Windows and retry once before reinstalling the matching complete package.

A log sequence showing spawn UNKNOWN, binary deletion or copying, then relaunch describes a recovery loop. It does not prove the binary was corrupt. Keep the first error and stop repeated retries; follow the component checks. Do not delete resources or the whole AppData folder as a startup fix, and do not make “Run as administrator” a permanent workaround.

These symptoms were reported in different versions, including 2.0.6: unlink, 2.42.0: spawn and 2.64.9: rename. They identify what to inspect, not a single confirmed cause in 3.11.0.

VBScript error, or no internet after quitting

vbscript process reported unknown error code 1 while setting or disabling System Proxy concerns Windows proxy configuration. It can occur even when the connection engine starts; changing the endpoint does not address that local failure. This distinction is visible in the Windows 11 report #469.

Disconnect and quit Desktop. Open Settings → Network & internet → Proxy and record the current values. If Desktop left a local proxy or setup-script address behind, restore the settings you used before connecting. If you previously used no proxy, turn off only the Use a proxy server or Use setup script entry you can identify as Desktop’s. Keep work or school settings intact. Test ordinary browsing again. Microsoft’s proxy settings guide

For a recurring VBScript error, check that the extracted application still has its bundled vbs resources and ask your administrator to check Windows scripting availability or restrictions. Do not enable scripts by registry edits or download .vbs repairs from third parties. The 3.11.0 release notes mention helper, Proxy-Reset and startup fixes; they do not establish a universal VBScript fix.

Windows 7/8 and “Entry Point Not Found”

Desktop 3.11.0 is not a Windows 7, 8 or 8.1 release. The ia32 download means 32-bit architecture, not support for those systems. An error mentioning DiscardVirtualMemory or KERNEL32.dll can mean the required Windows API is unavailable even though the DLL exists. Replacing a system DLL is not the solution; use a system meeting the release requirements.

Windows 7 report #404 · Electron’s Windows 7/8/8.1 support change

Still stuck? Keep these details

Keep the Desktop version, Windows version/build, system type, full package filename, EXE or ZIP, selected method and network mode, and the first error with its nearby log lines. If the window never opens, capture the Windows error dialog instead. Remove usernames, public IP addresses, license keys and other personal details before sharing a log.

To look for a saved log, paste %APPDATA%\oblivion-desktop\logs into File Explorer’s address bar and open main.log if it exists. Copy the relevant part before another connection attempt, which can clear previous connection logs. If the folder is absent, keep the error dialog; a very early startup failure may not have produced a log. Desktop’s log paths

If Windows shows a blue screen (BSOD), stop repeated connection attempts. Record the stop code, any named driver and whether you were using TUN. Have the crash investigated before trying again; a blue screen is not an endpoint-selection problem.

Use connection help when the app opens but cannot connect, the release notes to compare versions, or the archived issue history to match an older symptom. The archived repository does not accept new issue reports.

For a settings backup, a reversible reset or full removal, follow the recovery and removal guide.