--- title: "1.10.x" slug: "110x" updated: 2026-11-03T14:45:42Z published: 2026-11-03T14:45:42Z canonical: "docs.telosalliance.com/110x" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.telosalliance.com/llms.txt > Use this file to discover all available pages before exploring further. # 1.10.x ### Version 1.10.17 10/30/2026 > [!WARNING] > 11.10.17 versions have been removed because of some recently discovered license issues where keys may be inadvertently removed after update. **If you are already running this version you do not need to downgrade** - On a backup cluster node, the key9 preparatory block has been cleaned up to reflect only those that need to be added in key9 rather than those that need to be addressed on the primary node of the cluster. - The NTP warning banner that appears when no time servers are configured or the clock is not synchronized now runs across the full width of the page, so it is easier to notice. It has a close button, and a "Don't show this again" link that hides the banner on every page for that browser. ### Version 1.10.16 10/30/2026 > [!WARNING] > 1.10.16 versions have been removed because of some recently discovered license issues where keys may be inadvertently removed after update. **If you are already running this version you do not need to downgrade** - - Fixed a bug which only occurs on clusters of 3 or more nodes where an internal cluster function could continue to report that not all nodes were online, even though the Cluster page showed every node as fully synchronized. This could happen when two nodes finished synchronizing at the same time as a race condition. This could cause removals to be catalogued when they did not need to be. - Fixed an issue introduced in 1.10.10 where in a cluster where the secondary was a full license rather than a backup license, both licenses could appear on both servers. This could cause incorrect license counts and invalid license errors which were cosmetic. They did not affect functionality. This version fixes that and cleans up the residue from the problem. ### Version 1.10.15 10/28/2026 [Version 1.10.15 (R2 Platform - 1RU)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.15_r2-bank.pfc_upd) [Version 1.10.15 (X13 Platform)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.15_x13-bank.pfc_upd) [Version 1.10.15 (Virtual Machine)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.15_vm-bank.pfc_upd) > [!NOTE] > WARNING > > This version contains critical bug fixes affecting all versions between 1.10.5 and 1.10.15. See notes below. - Updated the Operating System with latest package updates for security and features. This also includes the PHP2Shell fix introduced in 1.10.14. - CRITICAL BUG FIXES: Bug introduced in 1.10.5 through 1.10.14 - Startup Hang due to ntp shift: With 1.10.14, some customers were reporting a hang on one of the stages during startup, especially after a restart. This could leave their system in a state where it was not fully booted and it would look like the configuration was not there. This was tracked down to a bug in the language framework we use to compile and execute the PathfinderCore PRO code. We moved to a newer version of that framework in 1.10.5 and the bug has existed since then. This version moves to a newer version of the framework that fixes the problem. The problem happens when the hardware clock and the time obtained by ntp differ significantly causing the clock to jump back by a significant amount of time during the boot. The framework had a regression bug that was making timers using utc rather than monotonic. This would cause timers in the application to hang while the time caught up which could be as long as the time jump. And usually the watchdog might restart the services first or that could lead to an hours long startup hang. Note that this does not affect daylight savings time shifts. Those will still work as they are offset expressions of the main UTC clock which ntp adjusts. - Fixes - This version updates the application execution framework to a version where this is fixed. - It also fixes a bug in the Set Time from PC option on the time web page which was setting local time to the hardware clock instead of UTC - Changed the ntp config so it continues to correct time even after a large jump. - Added a startup script that syncs time to ntp before starting the Pathfinder application - could add anywhere up to 15 seconds to the startup time if the ntp server is not responsive. This also sets the hardware clock. - Added a warning banner if ntp is configured but the ntp clock is not synced. - What to do if you are in the hung state: - If your system is hung on one of the startup stages, go to the advanced options, set the Supervisor startup delay to 60, save, and reboot. That should get the system started as it delays the pathfinder code startup for 60 seconds so that the ntp clock has a chance to settle. Then you can update to 1.10.15 and set that setting back to 0. If this does not work - contact support. - Notes: - For vm users pay attention to the recommendations of your chosen hypervisor manufacturer related to time for a Linux vm. So for example Vmware will seed the host on startup with UTC time, but windows hosts with local time. These are adjustable settings. Pathfinder should get seeded with utc. One of the things we saw in customer logs was the NTP clock jumping back 2 hours on every boot. While this version will attempt to fix that with ntp before starting Pathfinder, that is indicative of of a configuration problem. - Startup Hang during Stage 1 removal list fix: We had one customer where they were using device emulators as generic listeners where the connecting device was connecting and disconnecting in a Rest API fashion. When that was occurring when all nodes were not available, each of those connects/disconnects were incorrectly writing a cluster removal record. Added to that there was a bug that was rewriting the entire removal file on each record load during startup. This was causing a hang on startup longer than the watchdog timeout. This would be a very rare occurrence but repeatable once the file reached a certain size. Since those removal items were also held as objects in ram it also caused a memory leak. This would happen when one of the cluster nodes was offline, but then the file would retain its size after affecting subsequent reboots. - Fixes: - The connecting clients should never have been considered as synchronizable removal items. That is fixed so the removal records would not get created. - We fixed the bug that was causing rewrites during the load - that was the crux of the startup hang. - We added code to cleanup the incorrect records and get the file back down to a reasonable size. - Improved how the removal file gets written to better handle a power failure while the file is being written. - Startup hang during stage 0: This is theoretical and not been seen in the field but analysis showed a situation where a certain error on initial device connections might cause the stage to hang on startup. This has been fixed by properly catching the error. - Added information during the stage 3 service startup on the system page to show which services are still outstanding in the startup sequence. This allows you to see if there is a problem starting one of the services and if so which service. Note the Logic flows is usually the last one to start and can take some time if there are a lot of flows. - Added additional logging to the startup process to help troubleshooting and diagnosis. - Fixed an issue with the watchdog where a ntp time change could affect how it determines when the pings expire. - Moved key9 licensing log data to its own file to stop polluting the supervisor file. ### Version 1.10.14 10/22/2026 [Version 1.10.14 (R2 Platform - 1RU)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.14_r2-bank.pfc_upd) [Version 1.10.14 (X13 Platform)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.14_x13-bank.pfc_upd) [Version 1.10.14 (Virtual Machine)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.14_vm-bank.pfc_upd) - Implemented a critical security patch for PHP. Updated PHP to patch the critical PHP2Shell remote-code-execution flaws (CVE-2026-109618, CVE-2026-109619). - Updated the Linux operating system and kernel to keep packages and kernel up to date with newer improvements and security changes. ### Version 1.10.13 09/28/2026 [Version 1.10.13 (R2 Platform - 1RU)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.13_r2-bank.pfc_upd) [Version 1.10.13 (X13 Platform)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.13_x13-bank.pfc_upd) [Version 1.10.13 (Virtual Machine)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.13_vm-bank.pfc_upd) - Fixed a bug: The eight service projects that Supervisor references no longer copy their standalone.txt into build output, so publishing Supervisor can't overwrite its own startup file anymore. The VM build script also restores Supervisor's overlay files, including the default standalone.txt so VM ISOs ship the correct copies. ### Version 1.10.12 08/29/2026 [Version 1.10.12 (R2 Platform - 1RU)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.12_r2-bank.pfc_upd) [Version 1.10.12 (X13 Platform)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.12_x13-bank.pfc_upd) [Version 1.10.12 (Virtual Machine)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.12_vm-bank.pfc_upd) - 26224: Fixed a bug introduced in 1.10.7 when working on the newer translation style with Legacy Panels where buttons were launched in the down state by default instead of the up state. This only applies to customers that are still using Legacy panels with Pathfinder Core PRO. - WARNING: From the day version 1.0 of PathfindeerCore PRO was released almost 10 years ago the manual clearly stated that the use of Legacy Panels with PathfinderCore PRO was designed to be a temporary solution while customers migrated: - From the manual: “Prior to Pathfinder Core PRO’s HTML 5 Panels, User Panels could be created using a variation of PanelDesigner from the original Pathfinder PRO product. As this functionality is deprecated, we would urge all users to migrate to the much more powerful HTML5 Panels.” - This “temporary” solution has been available for almost 10 years but will be removed in the upcoming 2.0 version. The code base which the legacy panel application runs on can no longer be maintained, was written in a language for which support was removed in 2008, and can no longer be built, maintained for security patches, or tested for compatibility. - Please work with Telos support and/or your systems integrator to migrate any existing panels to HTML5 panels as soon as possible. - 25996: Made additional fixes to the simple tree not always opening and placing object paths into the correct branch when editing an existing flow. - 26107: Fixed a UI bug in logic flows where the drop down was not displaying the route IO value when a route point was selected in the flow. - 26213: Implement additional Quasar/Pulsar feature support including: - Pulsar device type support - Hot Keys - Additional program metering options - Vmix pan and phase support - DateMs, Date, Heartbeat support - rarely used and does not poll. Added for completeness. - recmode_enbl - FaCH/LwCH support of ON_LAMP and OFF_LAMP. Please note this overrides default behavior in ways that are not desirable in most situations. Only use if you really know what you are doing and accept the behavior differences. - FaCH/LwCH support of amix, amwg, icom_src, and label. - 26262: Fixed an issue where recmode_stat in AppControl in Quasar advertised swap as an option but it was not working. - Improved log rotation - Fixed an issue where a clean logs script might rotate logs and not retain as much as specified by the advanced options. This script originally primarily ran during restarts to force logs into a specific size for legacy cf card units. But in later versions it was often executed as part of the cron jobs therefore cleaning up logs more frequently than desired or specified. - Removed a misleading dmesg log message. - Added a phased log deletion which is more sensitive to when logs need to be removed and cleaned up based on age and tries to retain at least one copy of certain critical logs even if they have not changed in longer periods of time. - Added additional cross-checks for client cleanup to floating IPs when the IP moves as well as additional checks for moving the floating IP when the active node changes. - Added support for Key9. - IMPORTANT NOTE: We will update here when we are ready to start processing license updates. Currently only select beta testers will go through this process. So wait for confirmation before that we are ready to accept from a broader audience. - IMPORTANT NOTE: Starting with an upcoming 2.0 version all licensing will be switched to Key9 licensing in order to align Pathfinder’s licensing with the rest of the Telos portfolio. In order to update to 2.0 you will need to first update to a 1.10.12 or later version within the 1.10.x versions. This version presents a UI that will allow you to add Key9 licenses. More information will be available here as we finalize the process via support/sales for converting your existing license to key9. This version will not actually use the Key9 licenses yet, but they must be installed and validated using this version before the upcoming 2.0 version will allow you to update. New installs starting with 2.0 will only have the Key9 licensing. Also note that while you will be able to update to 2.0 at no cost when it becomes available, subsequent feature updates will require an active SLA. Reach out to your sales channel for information on how to obtain an SLA for your product. If you are interested in beta testing 2.0, let us know. - You do not need to update your license to key9 to use this version - you only need to convert it before upgrading to the 2.0 version when it becomes available. - If your Pathfinder is a hardware instance, it must have at least temporary access to the internet to activate the hardware key9 license. - If your Pathfinder is a VM and does not have access to the internet (air-gapped), you need to work with our support team to make sure there is a Telos license proxy or Telos OnPrem license server available. - Clicking on licensing from the System page will provide additional information regarding your Key9 status: - ![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/image-W4G0NG4E.png?sv=2026-02-06&spr=https&st=2026-11-07T02%3A40%3A19Z&se=2026-11-07T03%3A40%3A19Z&sr=c&sp=r&sig=QMC1kbDBRoV%2FXaHDsqsN%2Byi5me6OSijI1ZCzc8B%2FuJM%3D) - Provide your existing licenses to support and/or contact sales to add SLA support as well. (Note we are still working through the full process for doing this so stay tuned. This is mostly posted here to support select beta users.) Support will then return the corresponding Key9 licenses. Click on Key9 Licenses to add your licenses: - ![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/image-O4O5J76C.png?sv=2026-02-06&spr=https&st=2026-11-07T02%3A40%3A19Z&se=2026-11-07T03%3A40%3A19Z&sr=c&sp=r&sig=QMC1kbDBRoV%2FXaHDsqsN%2Byi5me6OSijI1ZCzc8B%2FuJM%3D) - Note that the Telos license server must be reachable to activate the key9 license. For air gapped systems, work with support to use a license proxy or on prem license server. ### Version 1.10.11 08/27/2026 - Not released - internal testing only ### Version 1.10.10 08/26/2026 - Not released - internal testing only ### Version 1.10.9 07/06/2026 [Version 1.10.9 (R2 Platform - 1RU)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.9_r2-bank.pfc_upd) [Version 1.10.9 (X13 Platform)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.9_x13-bank.pfc_upd) [Version 1.10.9 (Virtual Machine)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.9_vm-bank.pfc_upd) - Includes all changes from 1.10.8 and 1.10.7. - Added an option in the Advanced option to delay primary Pathfinder application start for a number of seconds after startup. This is protected with numerous warnings related to it only being used in consultation with support. We had one VM install that was having an issue with the start process hanging at one of the stages. We believe this was a one-off related to some specifics on the deployment hardware, but delaying the supervisor start seemed to address it. Hopefully this will never be needed beyond this one system. - Addressed some theoretical situations that could leave startup hung at a specific stage. Note: none of these have ever been seen in production or development. - Added some protection for a theoretical race condition during startup that could hang the startup at stage 00 Connecting to Devices. - Added protection for a theoretical situation where if someone deleted a device during stage 00 of the startup and that device was the last device in the setup, it could leave the startup stuck at stage 00 until the system was rebooted. - Added a catchall to make sure startup progresses beyond stage 00. - Added a catchall to handle a situation where all service starts occur within the first 5 seconds that could leave startup stuck in stage 3. - Added additional try/catch code in numerous places in the service manager loading processes to more elegantly handle any errors. - Fixed an actual bug where the service start stage was not actually waiting for all services as it was based on a constant number of service replies when more services now exist. This has been made more intelligent to prevent such problems in the future. In certain large systems, this could theoretically allow the system to progress farther into the boot process and clustering than it technically should have. - Enabled the keep alive bit on Tcp Listener accepted sockets in DeviceEmulators and the port 9600/2 API. This cleans up connections that were not properly closed after a period of time defined by the operating system. Note this does not affect the web page (panel) connections as those use websockets which already have connection loss detection built in at the websocket protocol level. This is specifically for Tcp listeners. If for example someone was connecting over a VPN to a Tcp listener in Pathfinder and the VPN silently dropped the connection without a proper closure of the socket, and the client was not subscribed to any changes that caused Pathfinder to send any data to the failed connection, it might not get detected and could stick around indefinitely. This turns on the keepalive bit on those accepted sockets to detect these issues. However a better choice involves making sure your application’s use of these connections has application level pings and/or subscriptions that semi-regularly return data. This is what Pathfinder does to detect failed connections to devices and between Pathfinder systems. ### Version 1.10.8 06/11/2026 (Not released) - Improved startup performance surrounding combiner input state validation - Changed initial startup state cross checks of uninitialized combiner input states to use a keyed hashmap instead of a for loop to greatly improve performance during that phase of the startup. - Added a ping with transaction id to the end of the initial translation state gets during startup to better determine completion of that work in the startup state and for use by the combiner input cross checks. - Consolidated multiple timers into a single timer and queue to reduce core utilization during this portion of the startup - Changed a metering rate constant to reflect the normally overridden value. - Fix several rare case potential bugs and race conditions in metering clients. - Fixed a bug with chrome shortcuts introduced in 1.10.x versions. ### Version 1.10.7 05/31/2026 Warning: This version pulled from the site. 1.10.8 will be available shortly. We found a one line code issue in the new metering code which could potentially lead to an async thread pool exhaustion problem. 1.10.8 will have all of the same fixes below when available. - 26005/25616/25435: This version attempts to fix several reports of problems with silence alarms and device connections within the alarms section of the code. Reports of alarms returning to level present without the requisite wait time, and devices losing their metering and silence alarm connections and not re-obtaining them without a reboot. While we were never able to reproduce the symptoms, we found a couple places in the code where race conditions were possible. Those have been fixed to more strictly enforce order of operations in this module. Warning: a lot of code changes in this area. Please report any issues you may encounter. - 25999: Attempted to fix an issue that was reported but not reproduced where deleting a subpage would still show the subpage in the UI. - 26000: Attempted to fix an issue that was reported but not reproduced where after saving a panel the page will hang and not properly reload the editing dialog. - 25990: Fixed an issue with the button color changes specifically with opacity settings when switching disabled on and off. - 25646: Fixed an issue with cloning panel pages where internally pointed logic was not repointed in the clone. - 25920: Fixed an issue introduced by changes in the translator conversions with legacy panel support. Please note that customers should migrate away from legacy panels (old PathfinderPC panels) soon as support is usually not tested and may be dropped in future versions. - 25494: Added mon talk property support for Quasar to Pathfinder. - 25991: Version 1.10.6 attempted to fix an issue with the BFMO/BMFO property in Altus. However this introduced a retrograde issue. Previous products like QOR and iQx and IQs used the previous incarnation, and it was only changed to the more correct version in later versions of Altus. This fix uses the correct BMFO versus BFMO depending on the product type. ### Version 1.10.6 04/16/2026 [Version 1.10.6 (R2 Platform - 1RU)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.6_r2-bank.pfc_upd) [Version 1.10.6 (X13 Platform)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.6_x13-bank.pfc_upd) [Version 1.10.6 (Virtual Machine)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.6_vm-bank.pfc_upd) - Fixed an issue with Altus/iQs/Qor in LwcpSs where the backfeed mode property was using bmfo instead of bfmo. - 25806: Fixed an issue with hardware mapped buttons where a press could be detected by both servers in a cluster sending mouse down changes both dierctions in the cluster. If the down time of the button was short and/or the servers behaving sluggishly this could result in a double press getting acted upon in the logic. This should be fixed in this version. - 25646: Added code to try and repoint internal bindings in a panel when it is cloned so that it points to the newly cloned panel items rather than the previous panel items. - Note: there is still an issue with the LocalChangePage property not getting repointed. This will get fixed in the next build. ### Version 1.10.5 03/15/2026 [Version 1.10.5 (R2 Platform - 1RU)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.5_r2-bank.pfc_upd) [Version 1.10.5 (X13 Platform)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.5_x13-bank.pfc_upd) [Version 1.10.5 (Virtual Machine)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.5_vm-bank.pfc_upd) - Updated the Linux operating system and kernel to keep packages and kernel up to date with newer improvements and security changes. - Updated the code framework from 8 to 10 to include language improvements and optimizations regarding memory usage and CPU performance. - Be prepared to revert to an earlier bank and report issues if these changes cause any problems with your workflow. ### Version 1.10.4 03/12/2026 [Version 1.10.4 (fanless engine)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.4-bank.pfc_upd) [Version 1.10.4 (R2 Platform - 1RU)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.4_r2-bank.pfc_upd) [Version 1.10.4 (X13 Platform)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.4_x13-bank.pfc_upd) [Version 1.10.4 (Virtual Machine)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.4_vm-bank.pfc_upd) - 25685: Fixed a bug introduced in 1.10.3 in related to 25168 that was preventing the property list to expand when editing panel start points to the selected item. This fix fixes that bug while retaining a proper fix for 25168. - Fixed an issue where when 2 devices exist in the list with the same IP but different ports, importing those IOs into a virtual router would only bring in the hostname from the one of them in the description. - Enhanced the loading of memory slots into the UI data table to be more performant by loading the full list at once when first loading the page rather than adding each item causing data table redraws. - 25496: Added the ability to clone virtual and SapProperty Routers. Please be aware that this feature can help spin up a new router that is similar (duplicate sources for example) to a current router but if you do not update settings so they do not overlap the original router, confusing behavior can occur. For example if you duplicate a sap property router that is tied to memory slots, clear the routes on one, but leave them in place on the other the behavior may be confusing. This option is strictly to aid during build processes. To clone a virtual or SapProperty Router, click the clone link next to the router in the routers list. ### Version 1.10.3 02/28/2026 [Version 1.10.3 (fanless engine)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.3-bank.pfc_upd) [Version 1.10.3 (R2 Platform - 1RU)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.3_r2-bank.pfc_upd) [Version 1.10.3 (X13 Platform)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.3_x13-bank.pfc_upd) [Version 1.10.3 (Virtual Machine)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.3_vm-bank.pfc_upd) - 25168: Fixed a bug where after adding an XNode mixer input in a logic flow and then re-editing the flow, it would navigate to the GPIO portion of the SapProperty tree rather than the XNode portion of the tree. - 25459: Fixed a bug in channel numbers where they were not displaying in lists for XNodes2 when the payload type is set to something other than 96. - 25455: Added an advanced option to make the skip startup state option in logic flows be enabled by default when creating new flows. This is an advanced option and should only be used if/when it makes sense to the customer’s workflow. The option is: - SET LogicFlows#0 SkipStartupStateRequestOnNewLogicFlows=False - Note: Advanced options require a restart to take effect. And they do not cluster sync so must be set on each node if the cluster if desired. - 25507: Fixed a bug where the missing NTP server warning message was appearing while a boot was in progress even thought NTP servers exist in the system. This fix only enabled that message after the boot is complete. - 25463: Added a line to the system page displaying the last time the clock has been synchronized from NTP. - 25647: Added a new property to user panels called LocalChangePage. This behaves exactly the same as the normal ChangePage except that it will only change on the local instance. Normally the ChangePage will cause all instances of the panel to switch to the new page. The LocalChangePage property never actually executes on the back end code, but instead just causes the local instance to switch to the new page. This allows multiple instances of a panel to change between page views independently. This property must be used from a panel binding (for example binding a button to the page’s LocalChangePage property). If you try to use it from a normal logic flow, it will do nothing as it is designed to only work within the inside of a user panel. ### Version 1.10.2 12/23/2025 [Version 1.10.2 (fanless engine)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.2-bank.pfc_upd) [Version 1.10.2 (R2 Platform - 1RU)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.2_r2-bank.pfc_upd) [Version 1.10.2 (X13 Platform - 1RU)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.2_x13-bank.pfc_upd) [Version 1.10.2 (Virtual Machine)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.2_vm-bank.pfc_upd) - 24977: This release adds support for the x13 platform. - 25277: Changed fresh installs to not have any NTP servers with a warning banner that the user must set them up. This will not affect upgrades but will affect factory default systems and fresh VM installs. - 25192: Fix a bug where changing name or description or the property value if an existing SapProperty router source or destination would delete the existing source or destination and hang on the UI without recreating the revised one. - 25329: Fixed a bug with current source path properties in Logic Flows introduced in recent changes where extra escaped quotes were being left in the translation of newly created flows based on current source path causing incorrect match states. ### Version 1.10.1 11/18/2025 [Version 1.10.1 (fanless engine)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.1-bank.pfc_upd) [Version 1.10.1 (R2 Platform - 1RU)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.1_r2-bank.pfc_upd) [Version 1.10.1 (Virtual Machine)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.1_vm-bank.pfc_upd) - This release fixes a compatibility issue between the most modern javascript syntax and what is compatible with Chromium v. 87. This impacts scenarios where user panels are being displayed on older devices running Chromium v. 87 such as BrightSign devices. As of the time of this release, the latest OS version by BrightSign utilizes Chromium v. 87. - This release fixes a backwards-compatibility issue related to html buttons on user panels. The scenario would be when a user panel exists with only the ‘color’ property set and when the instance is updated to the latest version of PFC the user would experience ‘—textcoloron’ or ‘—textcoloroff’ taking precedence. ### Version 1.10.0 09/23/2025 [Version 1.10.0 (fanless engine)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.0-bank.pfc_upd) [Version 1.10.0 (R2 Platform - 1RU)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.0_r2-bank.pfc_upd) [Version 1.10.0 (Virtual Machine)](https://telos-public.s3.amazonaws.com/pathfinder/pfc_os-1.10.0_vm-bank.pfc_upd) - This is the first release version of 1.10. It is the same code as 1.9.12.113 but released rather than a beta version. No additional work will be done in the 1.9.x branch after this release. - Removed the fourth octet from versioning to stay in line with other Telos product versioning.