ProxiFyre 2.5.2
ProxiFyre 2.5.2 is a maintenance release that makes a confusing Windows UI startup failure clear and actionable.
What's improved
- If Windows permissions make the installation path unsafe for elevation, ProxiFyre now identifies the exact folder and permission that caused the UI to stop.
- The diagnostic includes the affected Windows identity, access mask, and whether the permission was inherited or explicitly assigned, helping administrators find the source on localized Windows installations too.
- Other payload-integrity failures continue to use a safe, generic error message.
- Automated regression checks cover the new diagnostics on x86, x64, and ARM64.
For the system reported in #169, a non-standard permission on C:\Program Files allowed authenticated users to modify or delete content. ProxiFyre now makes that condition visible immediately instead of reporting only a generic startup failure.
Security note
This release does not weaken or bypass the launcher's security checks. The elevated UI still refuses to load from a location where a standard user could replace application files before elevation, and ProxiFyre does not rewrite permissions on shared Windows directories.
If ProxiFyre reports an unsafe parent directory, ask a system administrator to restore that directory from the appropriate Windows or organizational permissions baseline. Avoid broad recursive permission resets on Program Files.
If ProxiFyre already starts normally, there is no change to its runtime behavior or configuration.
Download and upgrade
No configuration changes are required. Download and run the online setup that matches the native Windows architecture; it upgrades the existing installation while preserving configuration and logs.
| Windows architecture | Recommended download |
|---|---|
| 32-bit Windows | ProxiFyre-2.5.2-win-x86-setup.exe
|
| 64-bit Intel/AMD Windows | ProxiFyre-2.5.2-win-x64-setup.exe
|
| Windows on Arm | ProxiFyre-2.5.2-win-arm64-setup.exe
|
MSI packages are available for managed deployment after prerequisites are provisioned. ZIP archives contain the application payload only and are not offline installers. Every published artifact includes a matching .sha256 checksum file.
Setup can acquire the verified Microsoft Visual C++ runtime and Windows Packet Filter prerequisites when needed, but it does not install .NET Framework. x86/x64 require .NET Framework 4.7.2 or later; ARM64 requires .NET Framework 4.8.1 or later.
Addresses #169 through improved diagnostics. Implemented in #172.