UiPath 2023.10 support has run out and 2024.10 is next. What we'd upgrade first

UiPath's 2023.10 release is out of support for OrchestratordefinitionThink of it as the robots' dispatcher. It holds the schedules, queues and credentials, and tells each robot what to run next., Studio and robots, and Automation SuitedefinitionThe version of UiPath you host yourself on Kubernetes or Linux, with Orchestrator and the other services inside it. It has its own support dates, which trail standalone Orchestrator by days or weeks. 2023.10 follows on November 3, 2026. Standalone 2024.10 left mainstream support in October and now gets only critical security fixes. Automation Suite 2024.10 follows on November 11. If anything you run still says 2023.10, move it to 2025.10 now. If it says 2024.10, book that upgrade for the first half of 2027 so you aren't doing it in a panic next October.

Robots usually sit in the middle of money and customer work. When one stops, invoices pile up and someone in finance keys them by hand until it's fixed. On an unsupported version, UiPath's support team won't help with that outage, and it won't send a fix if the bug is theirs.

2024.10 is in a quieter kind of trouble. UiPath's support terms say extended supportdefinitionThe third and last year of normal support. UiPath still fixes bugs and critical security holes. Anything rated lower stays open. still covers incidents, bug fixes and critical security fixes, but leaves out non-critical security fixes. So for the next year, medium-rated flaws in the version you run won't get patched. Most auditors will ask about that, and some cyber insurers too.

There's a fourth year for some customers. UiPath says Gold and Platinum support customers on 2024.10 can get Extended Support Plus, which covers incidents and workarounds but no security updates at all. Treat it as a safety net for a late project, since it won't keep you patched.

Orchestrator on Automation Suite runs about 11 days to three weeks behind standalone Orchestrator, because UiPath tracks it as its own product. Check both if you run both. Small pieces can differ too: Action Center, Insights and Test Manager have their own dates on the lifecycle page, so look each one up rather than assuming it follows Orchestrator.

If you're on 2023.10, go straight to 2025.10. UiPath only publishes LTSdefinitionLong-term support. Each October UiPath puts out one of these for self-hosted customers, and keeps it supported for about three years. versions for self-hosted products now, so there's no point stopping on 2024.10 for a year and doing it all again.

The next LTS, 2026.10, is the other option, and it's a bigger change. Studio, Robot and Assistant move to a new installer there, and the Auto Update policies many teams use to push robot versions stop applying. There's also no standalone Test Manager 2026.10. Teams that want a quiet upgrade usually take 2025.10 now and look at 2026.10 once it has a few patches behind it.

The installer is the easy part. For standalone Orchestrator, UiPath's update guide says to back up your packages, the web.config and UiPath.Orchestrator.dll.config files, and the database. If you run Insights, back up its database too, before Orchestrator. Then check the hardware and software pages for 2025.10, because they may have changed.

Robots are more forgiving than people expect. UiPath's compatibility matrix lists Robot 2023.10, 2024.10 and 2025.10 as working with Orchestrator 2025.10, so you can upgrade Orchestrator first and move the robot machines in waves after.

Studio is where teams get caught. UiPath doesn't support forward compatibility, and its matrix marks Studio 2025.10 as not compatible with Robot 2024.10. So if a developer upgrades Studio and publishes, that package may fail on robots still on 2024.10. Upgrade the robots that run a process before the developers who maintain it move to the new Studio.

# Check the .NET runtimes first. If 10.0.x isn't listed, install the hosting bundle before you run anything else
PS> dotnet --list-runtimes
# Look for config files that still point at the old Azure DevOps feed. Each hit needs pkgs.uipath.com instead
PS> sls .\*.config 'pkgs.dev.azure.com'
# Copy the two Orchestrator config files somewhere safe, as UiPath's update guide says
PS> Copy-Item web.config, UiPath.Orchestrator.dll.config D:\backup\

We upgrade UiPath estates to 2025.10: Orchestrator, Insights, Automation Suite and the robot fleet, with Windows - LegacydefinitionAn older Studio project type. Studio LTS still opens and edits these projects, and Studio has a built-in tool that converts them to the newer Windows type. conversion where it pays off. We start with an inventory of exact builds and processes, rehearse on a copy of your database, and move robots in waves. Read more on our UiPath page, or book an assessment if you'd like the version check done for you.