Starting September 25th, hosts running old versions of parsecd.exe and pservice.exe will stop functioning and will report their certificate is invalid. Update your out of date Windows computers now to avoid outages.
About the update
On April 2023, we updated our signing certificate and pushed updates out for parsecd.exe and pservice.exe. These are the Parsec Loader and Service.
On June 21st 2023, we released 150-88. Any Windows computers running the updated Loader and Service (released April 2023) are able to update to 150-88.
On September 25th 2023 any Windows computer that is not running the updated Loader and Service (released April 2023) will show a message that Parsec is either out of date or corrupt.
Typically, updates to the Parsec Loader and Parsec Service happen automatically when the computer has restarted, or Parsec has been fully quit and started again. However, if you have long running hosts in your environment, they may not have updated.
How to discover out of date hosts
Admin Dashboard
As a Teams Admin, you can see which Windows computers are out of date by visiting this page. At the top of this page, you will see a notice with a link to a CSV. This file will contain a list of computers that have reported loader with a version less than 8, and either no service reported (-1) or a service version less than 7.
Please note: macOS hosts may be represented on this list, but no action is needed for macOS hosts or clients. There also may be duplicate hosts reported in this list. You can use last_online, name and online fields to figure out which are duplicates.
From the computer itself
The app will report its version to be 150-87 followed by a letter, if it is outdated. You can find the build of the app in the Parsec settings, at the top-right.
How to discover out of date clients
From the computer itself
The app will report its version to be 150-87 followed by a letter, if it is outdated. You can find the build of the app in the Parsec settings, at the top-right.
How to update out of date hosts and clients
Restart the computer
Typically, restarting the computer should update the loader (pservice.exe) and service (pservice.exe), and subsequently allow the Parsec app to update to 150-88 or later.
Force stop the app and service
You can force stop pservice.exe and parsecd.exe to stop using task manager or scripting, and then start the Parsec service. Doing so will allow the loader (pservice.exe) and service (pservice.exe) to update, and subsequently allow the Parsec app to update to 150-88 or later.
Use a custom installer
We have created a custom installer that specifically updates pservice.exe, and parsecd.exe without modifying any other parts of your Parsec app. Running this on the computer should correct the issue and allow the computer to update to 150-88 or later.
Use our regular installer with a special flag
The latest version of the Parsec for Windows installer has an additional command flag below to perform the same action as the custom installer. Running this on the computer should correct the issue and allow the computer to update to 150-88 or later.
parsec-windows.exe /programfiles
Confirm the update was successful
If the host has updated correctly, the app will show version 150-88 or later in the settings menu. If the app has hosting enabled, it will no longer be displayed on the list of out of date hosts on the admin dashboard.