Hi @Nitya1, thanks for your message. There are no Robot logs at the folder path you mentioned. But as previously mentioned, there is an error related to the missing package: “Could not load file or assembly ‘UiPath.System.Activities, Version=23.4.2.0, Culture=neutral, PublicKeyToken=null’. The system cannot find the file specified.”
The package is not installed. So how do I go about getting the latest System.Activities package?
Hey @Anil_G, I deleted the whole .nuget packages folder and it was re-downloaded by UiPath but the issue still persists 
Yep, they are both the same version, 23.4.0. I think maybe because I am using the newest version that for some reason UiPath Orchestrator doesn’t have the latest version of the system.activities package? It’s weird.
As per compatibility matrix they should be
Can you open orchestrator and check the packages once
Also just a blind shot…turn off firewall and see if its able to download
If its present in orchestrator you can change extension to .zip and it should be unpacked which you can copy to the .nuget/packages folder
cheers
Thanks again for your continued assistance! I disabled the firewall, deleted the package from my nuget folder to get a new version of the package, and re-installed it via Assistant and it still doesn’t work.
The compatibility is fine.
Where do I go in Orchestrator to see the System.Activities package? I don’t see it anywhere.
Okay. I did that but I do not see the UiPath.System.Activities in there. I only see my published processes / packages. Thank you btw.
Thats an issue…as your orchestrator should be having them…
Okay so can you find nuget.config file from your robot system…
Its generally in C:\Users\<Username>\appdata\Roaming\nuget
If installation folder is different then open there or search in cdrive
Openit in notepad and check the nuget source in it…
And try adding this
https://pkgs.dev.azure.com/uipath/Public.Feeds/_packaging/UiPath-Official/nuget/v3/index.json
Cheers
Hi @oscar
Try to upload the package to orchestrator as oppose to have on the local, we have seen similar issues for our robots
following are some of the things which we have tried and it resolved it
Ensure that u are running the bot in the same machine in which u have opened it via studio.
Thanks guys for the responses.
I made a discovery which you might find interesting!
I deleted the latest version of Studio (23.4.0) and installed 22.10.7.
I made no changes to the project and published it again to Orchestrator.
Now the package works just fine, and it runs perfectly on my development PC as well as my Robot PC.
The only thing that changed was my version of UiPath Studio. 23.4.0 does not work when publishing the package. But 22.10.7 does work.
So there is definitely something wrong in Studio 23.4.0.
I think we just have to wait for UiPath Devs to update and fix Studio 23.4.0, but in the meantime I would suggest using the old and stable version of Studio, 22.10.7.
Thanks.
Hi @oscar ,
can you please replicate your setup again and provide us the Diagnostic Tool report?
Thank you,
Andrei
I’m having the exact same issue, and it started happening after updating both robot and development machine to version 23.4.0. I think I have found the culprit. I compared the .nuspec file for the published nupkg, and in version 23.4.0 I can find the following dependencies listed:
<dependency id="UiPath.System.Runtime.Windows" version="23.4.2" />
<dependency id="UiPath.UIAutomation.Activities.Runtime" version="23.4.5" />
And in version 22.10.7:
<dependency id="UiPath.System.Activities" version="[23.4.2]" />
<dependency id="UiPath.UIAutomation.Activities" version="[23.4.5]" />
So basically it looks like the proper dependencies were missing from the nupkg published by new version of Studio? I just added the lines from old version of the .nuspec -file to the new version (I didn’t delete the runtime dependencies, idk if those are actually required?) and re-zipped the packaged and renamed back to .nupkg and boom it works. Hopefully a fix is on the way. 
Wow nice find, @antti.saaristo!! I will forward this off to my UiPath rep so he can share it with the dev team.
Awesome, thanks!!
Hi @antti.saaristo ,
While this solves your problem, unfortunately this is not the correct solution.
In 23.4, we split the packages in design time and runtime and the problem you and @oscar are facing is because of this split that is conflicting with other packages that you have in the process.
Your solution brings the whole design time package at runtime and that’s how other packages don’t have conflicts.
Stay tuned, a fix should be coming in the following week.
Hello @erghe ,
I see, well the most important thing is you have located the root issue and a fix is on the way! Thanks a lot!
Good news. We launched a fix for the issue reported, you can find the release notes here: Studio - 2023.4.1 (uipath.com)
Thank you very much for reporting this and for the patience along the way.
Hi @radutzp and @antti.saaristo and @erghe and @Anil_G,
Just saying that the new version of Studio Enterprise 23.4.1 fixes the issue!
I upgraded to the new version of Studio and published the same process and it finally works on my dev machine and on my Robot machine.
So good work UiPath devs for fixing this. And good work to me for reporting it and going through the debugging process 
Anil_G
Parvathy
Yoichi
Nguyen_Van_Luong1
yu.li
usertest114
sruthi_I
i.kamianetskaya
ppr
Pranav_Kashyap