studio
2025.10
false
Studio release notes
2025.10.17
2025.10.17 release notes for Studio.
Release date: September 2, 2026
Improvements
Manage Packages now supports the new official UiPath package feed at https://pkgs.uipath.com/official/index.json. Your installation still points to the current feed, but the new feed is already available and you can manually add it. We plan to deprecate the old feed by April 2027. A future patch will force the update to the new address.
Inline code editor for Invoke Code
The Invoke Code activity now embeds an ActiPro-powered code editor directly on the activity card, replacing the previous plain-text preview. The editor provides syntax highlighting and IntelliSense for C# and VB.NET, so you can write and edit code inline without opening a separate editor window.
Requires System activities package 26.6.1 or later.
Bug fixes
- Converting a Windows - Legacy project to Windows could silently downgrade a dependency below the version another selected package required. The project then restored with an NU1605 warning and failed at runtime with a
MissingMethodException. The conversion now raises the pinned versions to satisfy the requirements declared by the selected packages, and a dependency that still resolves below a requirement is marked in the Project panel with a warning icon and a tooltip naming the package that requires the higher version. - Studio could hang on Adding dependencies... when opening medium to large projects, because the code editor re-registered a service on a syntax language that was already in use.
- Starting a debug session for a coded workflow could stop with the error
Job stopped with unexpected exit code: 0xC0000354when the .NET debugger took longer than expected to attach. Studio now waits for a late attach instead of tearing the session down, and reports that it is still waiting. - A coded workflow debug session could hang indefinitely when attaching to the debugger failed.
- Remote debugging could fail with a The operation has timed out. error when the robot agent on the target machine took longer than the fixed 40-second wait to report that it was ready, which slow interactive logins can cause. The wait is now configurable through the
UIPATH_STUDIO_AGENT_READY_TIMEOUT_SECONDSenvironment variable, expressed in seconds and accepting values from 10 to 1800. Values outside that range are clamped to it, and a value that is not a positive whole number is ignored in favor of the default. The variable is read once when Studio starts, so restart Studio after changing it. - In a project mixing VB workflows with
.cscoded files, spurious C# parse errors such asCS1525,CS1002, andCS1022could appear on the VB workflows, because non-C# files were being added to the C# workspace. - All Switch case values were silently cleared after a debug error and a rerun, because widgets could save their empty initial state over the model before their real value finished loading.
- Adding a new case to a Switch activity with a
System.Charexpression type threw an error, and a typed character was never saved, so new cases collided on the default key. - Ctrl + D and Ctrl + E moved the selection to a different activity instead of disabling or enabling the currently selected one.
- Local package feeds could stay stuck loading in Manage Packages, and the Project Dependencies Mass Update Tool did not discover feeds correctly.
- The cloud catalog offered an activity that was already installed as Available, and selecting it silently upgraded the installed package.
- Importing a library did not correctly resolve the types of local and global variables.
- Running a Windows - Legacy project with Run in PiP silently ran it in the main session instead of the picture-in-picture session.
- The ST-USG-026 Activity Restrictions Workflow Analyzer rule could fail with an
InvalidOperationExceptionwhen several analyzer jobs ran at the same time. UiPath.Studio.Project.execould crash on startup in Windows - Legacy projects because of duplicate theme resource keys, with nothing written to the Studio logs.- In Windows projects, an error indicator could remain in front of the text in the Expression Editor while typing, hiding the expression being edited. Dismissing it by clicking elsewhere worked only until typing resumed.
- The bundled .NET 8 runtime has been updated from 8.0.28 to 8.0.30 to address known security vulnerabilities, including CVE-2026-50650.
Corrections, October 21, 2026
The following changes were included in this release but were not listed in the release notes at the time.
Structured PowerShell results in Autopilot
When Autopilot runs a PowerShell command, it now receives the exit code, the standard output, and the error output separately. Previously, any output on the error stream or a non-zero exit code was reported only as a failure, without the command's output, and every command was stopped after two minutes. Autopilot now sets the timeout for each command.
Bug fixes
- When Autopilot read a project file through PowerShell, characters outside the ASCII range, such as German umlauts, were garbled in UTF-8 files without a byte order mark, which includes the workflow files Studio saves. A workflow that Autopilot then rewrote kept the garbled text, and no error was reported. PowerShell commands that Autopilot runs now read files as UTF-8 by default.
- Starting with Studio 2025.10.16, in projects under source control, Autopilot project listings and file searches included every file in the
.gitfolder, which could hide the actual project files from Autopilot. Listings and searches now skip the.git,.svn,.hg,.vs,node_modules,bin, andobjfolders. The.localfolder remains visible. - When Autopilot edited a file that did not exist, Studio created a new file containing the text that was meant to be replaced, and reported the edit as successful. The edit now fails with an error.
- Asking Autopilot to create a file at a path that included folders discarded the folders and wrote the file to the project root, while reporting the path that had been requested. A path inside the project is now honored, missing parent folders are created, and a path outside the project is refused instead of being redirected.
- The Autopilot file editing tool described itself with the parameters of a read operation, so a request meant to re-read part of a file could modify it instead.
- Reading part of a file through Autopilot ignored the requested start line and line count and always returned the whole file from the beginning, so an inspection of a specific region actually saw the start of the file. A partial read now returns the requested window, states which lines it covers out of the file's total, and reports the line to continue from.
- Searching across a project could silently omit whole files while reporting the search as complete, because results were cut at a fixed length in the middle of the output. Results are now limited per file and in total, and a limited result states how many matches and files it covers.
- A skill added to a project's skills folder was never listed as available to Autopilot, and restarting Studio made no difference, because nothing read that folder. The folder is now read, so a skill you add there is discovered.
Activity package versions
The following activity packages and versions are included in the UiPathStudio.msi installer and can be found in the local feed.
| Activity package | Version |
|---|---|
| UiPath.UIAutomation.Activities | v25.10.39 |
| UiPath.System.Activities | v26.2.7 |
| UiPath.Excel.Activities | v3.4.1 |
| UiPath.Mail.Activities | v2.7.12 |
| UiPath.Word.Activities | v2.4.1 |
| UiPath.ComplexScenarios.Activities | v1.5.1 |
| UiPath.Presentations.Activities | v2.4.1 |
| UiPath.Testing.Activities | v25.10.1 |
| UiPath.WebAPI.Activities | v2.4.0 |
| UiPath.Form.Activities | v25.10.2 |
| UiPath.Callout.Activities | v25.10.2 |
| UiPath.DataService.Activities | v25.2.0 |
| UiPath.DocumentUnderstanding.Activities | v2.17.5 |