Our team is currently using UiPath Studio version 23.4.8, and we cannot upgrade because many of our production processes are running on this version.
I installed UiPath Studio 23.4.8 on a new machine, and the Studio version matches the version installed on our other two working machines. However, when I open an existing project on the new machine, Studio displays a “Packages Not Installed” message.
I have tried the following steps:
Manually installing the missing packages.
Downgrading and upgrading the project packages.
Restoring dependencies.
Unfortunately, the issue still persists, and the project does not load correctly.
Has anyone experienced a similar issue? Are there any additional checks I should perform, such as package source configuration, compatibility settings, or project dependencies?
it should not matter if your existing packages are on lower version and you are moving to a higher version..
all packages would still be backward compatible…
if the studio says package not installed, that means you have to install that particular package as it is not a standard project configuration.
Might be this issue occurs when required project dependencies are not found in configured package feeds, so Studio shows error.
you must ensure all original package sources (Official, Orchestrator, Local, or custom feeds) are correctly configured and accessible, because dependencies are restored only from those feeds and listed in project.json.
If helpful, mark as solution. Happy automation with UiPath
In addition to checking the package feeds, also verify that the required package versions are available in those feeds. Sometimes the project references a specific package version that is missing on the new machine.
You can also try:
Open project.json and check the dependency versions.
Verify Official, Orchestrator, Local, and any custom feeds are configured correctly.
Clear the local package cache and restore dependencies again.
Check if any custom libraries used by the project are missing.
UiPath package management documentation:
This usually happens because Studio cannot find one or more required dependencies from the configured package sources.
First thing check if there are any network or ip restrcitions on new machine…that might cause the download of package to fail…checking event viewer logs when opening the project might give you some insights
as a work around you can follow as @SorenB mentioned
also you should consider upgrading as old versions would be out of support sooner or later
I checked in Project.josn and also try to upgrate and downgrade microsoft 265 package but its showing following warning and when I run this process give me error
At least the UiPath.MicrosoftOffice365.Activities.2.6.24 dependency is not compatible with Studio 23.4.8.
“This version of the activity package can be used with UiPath Studio versions 2023.10 and newer. If used with older Studio Desktop versions, some functionalities might be missing or unexpected behaviors may occur.”
As we have more than 100 automations running, if I update the Studio, we also have to update Assistant in Production. The current version is 23.4.8, and I cannot take the risk of updating Assistant on all our production and development environments. Moreover, on the two other development machines, we have the same version, 23.4.8, and the same package is working on them.
could you check the .NET framework version that is installed on your target machine…
it think it could be still 4.x version that is installed.
if yes, then upgrade it it to 6.X
