Why do activities differ in UiPath Studio?

[Matias_Clemente.Arg (Matias Clemente)]

I cannot comprehend why the activities exhibit distinct properties when I open them in different instances of UiPath Studio. The following image pertains to my setup at home, running on Windows 11.

And the image below is from my work computer, running on Windows Server; observe that the ‘applies to’ options do not appear.

Both UiPath Studios are updated to the latest version. Now, it becomes challenging for me because I cannot select the correct value in UiPath as I am unsure how to set it.

[ashokkarale]

@Matias_Clemente.Arg

The properties or appearance of the activity also depends on the package version.

In your case make sure your UiPath.System.Activities package is installed with same version in both studios.

[Gokul001 (Gokul Balaji)]

Hi @Matias_Clemente.Arg

Install the UiPath.system.activities from manage package

Unable to open process.xaml

Hi @Valdez_Daniela Welcome to UiPath community Could install the uipath.system.activities from manage package. it will resolve your issue. You have install only runtime package Regards Gokul

Regards
Gokul

[MohammedShabbir]

The properties or appearance of the activity depends on the package version.

Make sure your UiPath.System.Activities package is updated using manage activities.

[Harshini_Here (Harshini Priya. R)]

Hi @Matias_Clemente.Arg,

Nothing to do with Windows Server, nothing to do with “published activity”, nothing to do with NuGet executable mode.

The Kill Process activity always has the AppliesTo property with options
All / OnlyCurrentUser / OnlyCurrentSession / OnlyCurrentDesktop.
This is confirmed by UiPath documentation. [docs.uipath.com]

When UiPath Studio loads an older activity package, or the project is in Windows‑Legacy, the designer cannot render the enum dropdown, so it shows a plain expression field instead.

This is exactly what you’re seeing.

Fix it with the below steps:

1. On the work machine, open the project → Manage Packages

Update these packages to match your home machine:

UiPath.System.Activities

UiPath.UIAutomation.Activities (if installed)

Use the latest stable version available.

2. Ensure the project compatibility is the same

Go to: Project Settings → General → Compatibility

Make sure BOTH machines use:

• Windows (recommended)
  NOT Windows‑Legacy.

3. Restart Studio and reopen the workflow

After aligning package versions + compatibility, the AppliesTo dropdown WILL appear, exactly like your home screenshot.

[sarvesh.b (Sarvesh)]

Hi @Matias_Clemente.Arg

Please check the manage package in which you can view the activities version. Make sure to keep the package version of all the activities same

Thanks

[SorenB]

Hello @Matias_Clemente.Arg

Is your machine at home connected to the same Orchestrator?
It could be that the packages are being resolved from different package sources.

Update the mentioned package above to the newest version on both and compare the version numbers.

Regards
Soren

[postwick (Paul Ostwick)]

Windows vs Windows Legacy are not machine-level settings. They’re project settings.

[Matias_Clemente.Arg (Matias Clemente)]

Thank you all for your responses, however.
Both have the same version of packages; the one below is on Windows Server.

The one below on my machine running Windows 11.

@Gokul001 @ashokkarale @SorenB @MohammedShabbir @sarvesh.b

[Matias_Clemente.Arg (Matias Clemente)]

Well, I noticed a discrepancy between the “Preview” version; I installed the latest version on both, and the options then appeared.
Thank you all for your responses; I regret not being able to mark all of them as the solution.
Best regards.