Unattended Robot Fails to Download .NET UCV Bundle / UIAutomation Runtime After Publishing

Hello everyone,

I am facing a strange issue with a UiPath unattended process and I would like to understand if anyone has already experienced something similar.

Context:
• UiPath version: 25.10.11
• Same server/environment for Studio and Robot
• The robot is running unattended through Orchestrator
• The process initially worked correctly

What happened:
I downloaded an existing working package/process and reused the same workflows and activities in a new process. The process mainly uses UI Automation activities such as:
• Use Application/Browser
• Click
• Check App State

I noticed that after publishing, additional runtime dependencies seem to appear automatically, especially related to:
• UiPath.UIAutomation.Activities.Runtime
• OCR / Vision runtime
• .NET UCV Bundle

Even though I am not explicitly using OCR activities.

Symptoms:
• Publishing succeeds but with warnings
• Sometimes random ClippingRegion properties appear automatically in activities
• The unattended robot fails when trying to download the package/runtime dependencies
• Sometimes the process starts only when using an older cached version
• In some executions, the package version appears empty in the logs
• As soon as I modify and republish the package, the unattended execution fails again

I already tried:
• creating a completely new process
• clearing package/cache folders
• removing unused dependencies
• republishing packages
• removing ClippingRegion entries
• disabling Computer Vision/Fuzzy selectors where possible

But the issue still occurs.

My main question now is: how can I fix this issue?

I have been trying to solve it for quite some time and already tested many solutions, but nothing is working consistently.

If anyone has experienced this before or has any idea/tip on how to properly fix it, I would really appreciate your help.

Try publishing the project again but with Separate Runtime Dependencies disabled from the Project Settings.

This will help the published nupkg package to not have the main UiPath packages set as *.Runtime.

If the project works in Studio but doesn’t work in the unattended robot as he cannot download and install the packages, either there is a network issue on the robot VM or the robot is not using the same package feeds as the Studio machine.

Thanks for you answer Marian,
I have tried this but it is still not working

Provide the UiPath Diagnostic Tool logs from the impacted robot VM to see the errors.
Let me know the time and date when the issue occurred.

Hi ,
Bellow is the error, it accours when the bot tries to install the package on the server to run it.

UiPath.Ipc.RemoteException: Failed to install package
‘***’

—> UiPath.Ipc.RemoteException: Failed to download package
’ from 'https:///nuget/v3//packages//***.nupkg’.

Could not find file
‘C:\Windows\SystemTemp\NuGetScratch\4fe515a8-f3ba-4d2e-a542-e584cad967fd\b0xndllv.sah’.

The feed ‘LT1 Processes Folder Feed [https:///nuget/v3//index.json]’
lists package ‘***’ but multiple attempts to download the nupkg have failed.
The feed is either invalid or required packages were removed while the current
operation was in progress. Verify the package exists on the feed and try again.

— End of inner exception stack trace —

Hi @teyssir1,

Try uninstalling the UiPath.UIAutomation.Activities.Runtime package and then install the UiPath.UIAutomation.Activities package. This may resolve the issue if the Runtime package was installed instead of the Activities package.

Thanks

Hi,
Thanks for you answer,
I have tried that and I’ve installed different version of Uiautomation.activities but it didn’t work

I need the UiPath Diagnostic Tool logs

From the provided error, I can spot at least that one URL (LT1 Processes Folder Feed) cannot be accessed on your machine.

Hi @teyssir1,

Could you please check whether your robot has access to the LT1 folder?

Since you have published the package at the folder level, that could be the reason for the issue.

Alternatively, try publishing the package at the tenant level and check if that resolves the problem.

Thanks