Skip to main contentParsec logo

Changelog

last updated more than a week ago
Add RSS Feed

This changelog is the comprehensive history of Parsec's product changes. Some of the features listed have been deprecated or were changed in later updates. We thought, rather than changing old posts, it would be fun for everyone to see the whole history of the product's development. For a perspective on Parsec's product and our product philosophy, we wrote a blog post in December 2017 about the early history of the Parsec Game Streaming software.

  • May 7, 2025150-99

    150-99 will be rolled out over the next 7 days

    IMPROVEMENTS

    • [All] To better assist users on non-corporate networks, the -6023 error code related to a failed peer-to-peer (P2P) session will now include a secondary error code. This additional code is derived from the UPnP signal received when a connection attempt fails. We will be updating our -6023 error troubleshooting guide with solutions and workarounds as we continue to identify common network conditions causing these errors. Note that these supplementary error codes will not appear in Parsec for Teams audit logs.
    • [All] On routers that do not support temporary UPnP leases, we will now create a permanent UPnP lease.
    • [All] When Parsec is closed, or UPnP disabled inside the app, we are now more thorough with cleaning up Parsec UPnP records from the router.
  • April 4, 2025macOS Installers

    New macOS installers are available with support for macOS Sequoia

    IMPROVEMENTS

    • [macos] Updated installer to no longer require macOS Sequoia's monthly approval of Screen Capture permission when hosting is enabled.
  • April 2, 2025150-98

    150-98 will be rolled out over the next 25 days

    IMPROVEMENTS

    • [Windows host] When using “Use Client Resolution” and Parsec Virtual Displays, the client resolution will be dynamically added to the Virtual Display. Previously if you were using a non-standard display resolution on the client display, you would need to manually add the resolution to the host registry.
    • [Windows host] When using Privacy mode, Parsec will now automatically re-enable displays where the user had selected “Remove display from the desktop” using the Advanced Display Settings found in Windows 10/11 Enterprise. Disabling the display using this setting would break Privacy Mode.
    • [All clients] Display a banner in settings to make it more obvious when we have detected a hardware video decoder to be non-functional and offer the user a method to re-try using the decoder.
    • [Windows/macOS/Linux client] When “Automatically Open Additional Screens” is selected and you connect to a Windows host, Parsec will no longer open additional screens until after you have successfully logged into your Windows account on the host.
    • [macOS client] Parsec now uses more screen real estate in fullscreen on modern Mac computers with screen notches.

    BUGFIXES

    • [Windows/macOS host] Fixed a bug where the app only checks once for the host start port configuration, preventing it from being updated later or set correctly via App Rules if there is no internet connectivity on app start.
    • [Windows/macOS/Linux client] Fixed a bug where a guest connecting to a host owned by a different account could access the host user’s second or third screen unintentionally when enabling “Automatically Open Additional Screens”.
    • [All] Fixed a bug where it was possible for the Parsec app to stop talking to the Parsec backend when the app was running for a very long time.
    • [Windows host/client] Fixed a bug where the app configuration may get reset at app start.
    • [Windows host] Fixed a bug with capturing UAC prompts that primarily impacted Windows computers running ARM Architecture.
    • [Windows client/host] Fixed a bug where Parsec interprocess communication was slow on ARM Architecture.
    • [Linux client] Fixed a bug in various distros where if a dependency was missing that Parsec required, the app may deadlock.