I attached the two attachments from running the diagnostics tool. Any idea what I should do in my situation?
I am kind of lost. It began to happen after I just upgraded my PC and did a clean installation of every program on my C drive (my project is located on a Seagate Expansion Drive F)
6871559–801977–diagnostic_report.txt.txt (1.53 KB)
6871559–801998–upm-diag.txt (1.34 KB)
Hello,
Sorry to see you are having this issue. As per the report, it seems that something is preventing the package manger to start. We need more information in order to find the source of your problem.
Could you please provide the Editor.log and upm.log? You can find instructions on how to find them and upload them here: How to expedite support/help request in this forum?
Keep in mind that the logs are written every time there is a successful launch. If you run the diagnostic tool, the Package Manager will be ran, and upm.log will be written again, so please, don’t run run the Diagnostic tool before coping the log files.
Also, you can check out the pinned thread **READ ME FIRST** Troubleshooting connection/loading project issues with Package Manager for more information on how to resolve this.
Cheers,
Supi
I think you are hitting a know issue posted already in **READ ME FIRST** Troubleshooting connection/loading project issues with Package Manager
Unity Installation Path Suggestions
There is a known issue where Unity installation paths containing special characters can prevent UPM from starting. This will manifest in an error saying that Unity could not connect to Package Manager. We are working on fixing these issues but in the meantime, if Unity is installed in a path containing the following characters, please move the installation folder or remove these characters from the path:
-
(number sign)
- ’ (apostrophe)
In Unity 2019, the problem is fixed in 2019.4.13f1 version and above
thank you for the reply. Just odd that before my pc upgrade. I could open it without any issues. But I am going to change the name right away.
EDIT: Installing version “2020.2.6f1” hopefully it will fix it