UiPath 26.0.179 October Community Release

[loginerror (Maciej Kuźmicz)]

Latest Update — November 5

We’ve temporarily paused the UiPath Platform rollout (initially targeted at 1% of Community users) after detecting errors in our telemetry.

Here’s what you need to know:

• No action needed for most users.
  Our telemetry shows that the rollback mechanism worked correctly in all reported cases.
  • If your migration succeeded, you’re now running version 26.0.179 (Studio, Assistant, Robot).
  • If it failed, the system automatically rolled back to version 25.0.176 using the classic MSI installation.
• Manual reinstall is only needed as a last resort.
  If, for any reason, your installation is broken and you can’t open Studio or Assistant, you can repair it manually using:
  UiPath Platform Installer (Community)

Next steps

• We’ll soon distribute version 26.0.179 to all Community users via the classic MSI channel — again, no action required.
• We’ll analyze the cause of the migration errors, apply fixes, and retry the UiPath Platform rollout at a later time.

UiPath Platform remains our lightweight, modern, and fast distribution mechanism for UiPath desktop clients (Studio, Assistant, Robot, and Extensions).

Thanks for your patience and for helping us ensure a smooth transition for everyone.

---

UiPath 26.0.179 October Community Release

UiPath Platform - Automatic Rollout for Community Users

Hey everyone

Starting this week, we’re introducing a new automatic update system for UiPath Community users.
It’s called UiPath Platform, and it keeps Studio, Assistant, Robot, and Browser Extensions always up to date — faster, and lighter than before.

What’s changing

You don’t need to take any action.
Your current UiPath installation will be migrated automatically to UiPath Platform during the next few weeks.
All your settings, projects, and connections will stay exactly the same.

What you get as a user

Once migrated, you’ll notice updates feel effortless:

• Much smaller downloads – only file changes are downloaded (no more full installers).
• Faster updates – most complete in just a few seconds.
• No interruptions – everything happens quietly in the background.
• Built-in safety net – if something ever fails, UiPath Platform automatically rolls back to the last working version.

In short: your UiPath apps stay current, stable, and ready to use, without you needing to lift a finger.

Gradual rollout

We’re releasing it gradually to make sure everything works smoothly:

• Around 1% of Community users will receive it first.
• We’ll monitor telemetry and feedback closely.
• The rollout will expand in waves until it reaches everyone.

So if you don’t have it yet — no worries, it’s coming soon!

What you might notice

After migration, you might see UiPath Platform listed in Control Panel → Programs and Features.
That means your installation is now managed by the new system.

We preserve your original installation type — per-machine or per-user — so nothing changes in how you use UiPath.
For new installs, UiPath Platform prefers per-machine (recommended) and falls back to per-user if you don’t have admin rights.

(If you open “Modify” from Control Panel, you’ll see a screen like this)

If something goes wrong

If the update or migration fails:

1. Download the diagnostics tool: UiPath.Connected.InstallDiagnostics.exe
2. Run it on the affected machine — please DM the generated .zip to @Alexandru_Bizon so we can investigate.

What stays the same

• The classic MSI installers remain available for Enterprise and offline (LTS) environments.
• The new UiPath Platform rollout applies only to Community users

Thank you

This is a big step toward faster, safer, and zero-effort updates for everyone.
We’ll keep an eye on telemetry and feedback as the rollout continues — your input really helps.

If you notice anything unusual or want to share your experience, please reply below.

Happy automating!

Studio

Build a Project

We added a new option under to Build a project. This reports validation errors across all workflows that are not caught otherwise.
This is useful when a workflow file was deleted or renamed — the compiler will flag every Invoke Workflow activity that references a missing file. It’s an efficient way to identify and fix broken references after refactoring or cleanup.

Update Arguments in Invoked Workflows

When renaming arguments in a workflow, Studio will now update all Invoke Workflow references automatically. Existing default values are preserved, so you don’t lose configurations already defined in those invocations.

Healing Agent Integration with Autopilot for Developers

With the upgrade of Autopilot for Developers to a new conversational experience, the Healing Agent has also been integrated accordingly.

This integration brings several key advantages.

Analyze Healing Agent Execution Data

You can now instantly access information about jobs from the tenant connected to Studio, specifically for the project currently open. If the data includes fix recommendations, they will be automatically displayed—no need to manually import a file.

Interactive Recommendations via Autopilot

You can continue the conversation with Autopilot to get more details about each recommendation or healed activity, enabling a deeper understanding and faster resolution.

Manual Debug File Import Still Available

The option to manually load healing data remains accessible via the Load Healing Data from File feature.

Please tell us what you think

Which features excite you the most and are you going to try right away? We want to hear what you think! Please use the button below

[Jon_Smith]

Love this update, in particular the Build option, as thats been needed for ages since the validation things don’t always catch things (they sometimes give false positives too so would love to fully disable it and just build instead) and the arguments changing in invoked workflows is an awesome change i didnt know I needed or wanted. Would it be a step to far to ask if its possible to extend it so that argument direction also gets changed? So if an in argument becomes an Out, or becomes an In/Out that changes too?!

[Jon_Smith]

Removed other posts for clarity since the ones I was replying to seem to have been removed.

[ashokkarale]

This is great! My favourite and much awaited - Update Arguments in Invoked Workflows

[johannes.schulte]

Hi there,

I’m not able to install the latest community version to my windows machine.
What information do you need to help me.

This is the end of the log file:
Property(C): GPTSupport = 1
Property(C): OLEAdvtSupport = 1
Property(C): ShellAdvtSupport = 1
Property(C): MsiAMD64 = 23
Property(C): Msix64 = 23
Property(C): Intel = 23
Property(C): PhysicalMemory = 8171
Property(C): VirtualMemory = 5603
Property(C): LogonUser = johannes.schulte
Property(C): UserSID = S-1-5-21-1993341775-2222561642-884886105-1287
Property(C): UserLanguageID = 1031
Property(C): ComputerName = VM03
Property(C): SystemLanguageID = 1031
Property(C): ScreenX = 1920
Property(C): ScreenY = 1080
Property(C): CaptionHeight = 23
Property(C): BorderTop = 1
Property(C): BorderSide = 1
Property(C): TextHeight = 16
Property(C): TextInternalLeading = 3
Property(C): ColorBits = 32
Property(C): TTCSupport = 1
Property(C): Time = 15:47:59
Property(C): Date = 10.11.2025
Property(C): MsiNetAssemblySupport = 4.8.9032.0
Property(C): MsiWin32AssemblySupport = 6.3.26100.1
Property(C): RedirectedDllSupport = 2
Property(C): AdminUser = 1
Property(C): Privileged = 1
Property(C): USERNAME = install
Property(C): DATABASE = C:\Users\johannes.schulte\Downloads\UiPathPlatform(1).msi
Property(C): OriginalDatabase = C:\Users\johannes.schulte\Downloads\UiPathPlatform(1).msi
Property(C): SOURCEDIR = C:\Users\johannes.schulte\Downloads
Property(C): VersionHandler = 5.00
Property(C): TELEMETRY_ENABLED = 1
Property(C): INSTALLATION_ID = bad44a96-5d90-4363-8693-0df5ab3b3de3
Property(C): INSTALLER_LANGUAGE = 7
Property(C): EXECUTEACTION = INSTALL
Property(C): ACTION = INSTALL
Property(C): UILevel = 5
Property(C): TRACE_ID = 52dd3211670e006afba929297d4da710
Property(C): SPAN_ID = d726bc7a4d89ae4d
Property(C): PLATFORM_CONFIGURATION_FILE = C:\Users\johannes.schulte\AppData\Local\Temp\UiPathConnected\platformConfiguration_letdom5o.wtq.json
Property(C): ROOTDRIVE = C:
Property(C): CostingComplete = 0
Property(C): OutOfDiskSpace = 0
Property(C): OutOfNoRbDiskSpace = 0
Property(C): PrimaryVolumeSpaceAvailable = 0
Property(C): PrimaryVolumeSpaceRequired = 0
Property(C): PrimaryVolumeSpaceRemaining = 0
=== Logging stopped: 10.11.2025 15:47:59 ===
MSI (c) (F0:C0) [15:47:59:410]: Note: 1: 1708
MSI (c) (F0:C0) [15:47:59:410]: Note: 1: 2205 2: 3: Error
MSI (c) (F0:C0) [15:47:59:413]: Note: 1: 2228 2: 3: Error 4: SELECT Message FROM Error WHERE Error = 1708
MSI (c) (F0:C0) [15:47:59:413]: Note: 1: 2205 2: 3: Error
MSI (c) (F0:C0) [15:47:59:413]: Note: 1: 2228 2: 3: Error 4: SELECT Message FROM Error WHERE Error = 1709
MSI (c) (F0:C0) [15:47:59:413]: Product: UiPath Platform – Installation failed.

MSI (c) (F0:C0) [15:47:59:415]: Windows Installer installed the product. Product Name: UiPath Platform. Product Version: 25.0.180. Product Language: 1033. Manufacturer: UiPath. Installation success or error status: 1603.

MSI (c) (F0:C0) [15:47:59:417]: Grabbed execution mutex.
MSI (c) (F0:C0) [15:47:59:417]: Cleaning up uninstalled install packages, if any exist
MSI (c) (F0:C0) [15:47:59:430]: MainEngineThread is returning 1603
=== Verbose logging stopped: 10.11.2025 15:47:59 ===

[Bonnie]

Dear UiPath Support Team,

I am writing to request assistance with an issue preventing UiPath Studio from launching on my computer.

After the latest update, UiPath Studio shows a message prompting me to install the .NET Desktop Runtime, even though it is already installed. My current environment includes the following:

UiPath Studio version: 26.0.179.0
.NET Desktop Runtime version: 8.0.11 (x64)
Operating System: Windows 10 (64-bit)

Despite confirming that the runtime is properly installed and visible when running dotnet --list-runtimes, UiPath Studio still fails to recognize it and does not start.

Interestingly, one of my colleagues is using an older runtime version and can still open and run the latest UiPath update without issues. This suggests that the problem might be related to the specific runtime detection logic or compatibility in version 26.0.179.0.

Could you please advise how to resolve this problem or which .NET Desktop Runtime version is officially compatible with UiPath 26.0.179.0?

Thank you very much for your support.

I am happy to provide additional information, logs, or screenshots if needed.

[marian.platonov]

Try these approaches:

Approach #1

Open Environment Variables → System → Edit Path → look for C:\Program Files\dotnet\ and move it in upper levels to take the precedence and save the changes.

Retry

Approach #2

Uninstall the .NET Desktop Runtime version: 8.0.11 (x64), install Download .NET 8.0 Desktop Runtime (v8.0.22) - Windows x64 Installer or Download .NET 8.0 Desktop Runtime (v8.0.15) - Windows x64 Installer
Retry