Regarding Community Edition installation path changes

Hello,
I am a UiPath Studio Community Edition user.

Since the beginning of this year, every time the Community Edition is updated, the installation path changes, which causes the following inconveniences:

  1. UiPath Studio disappears from the Windows 10 Start Menu.
  2. Double‑clicking an existing Main.xaml no longer launches UiPath Studio.

Could you please keep the installation path fixed for a certain period of time, even for the Community Edition, which is frequently updated?

Also, in situations like this, is the correct countermeasure simply to repeatedly uninstall and reinstall the Community Edition?
If resolving the installation‑path issue is likely to take some time, would uninstalling and reinstalling the Community Edition be the correct way to get UiPath working again quickly?
This problem is affecting my work, so I would appreciate a prompt response.

Cheers

hi @gorby , I’ve raised a bug for us to investigate the behavior you are seeing regarding the start menu and not opening UiPath Studio when you click on a .xaml file. Just out of curiosity, is Studio set as the default for this filetype before you observe this behavior?

The answer is YES. However, since the beginning of this year, each version update has changed the installation location, causing Studio to be removed from the default application associated with this file type.
After uninstalling the Community Edition today and reinstalling it, the issue has been resolved.
However, I want the installation location to remain fixed to avoid annoying repeated uninstall and reinstall processes.