failed to start unity package manager operation timed out

Nyper · January 18, 2018, 6:34pm

I need help.
When I try to load or create any project i got this error. (https://image.prntscr.com/image/4Bz7K6pzT-6p_eyA5BHX9w.png)

I tried seting localhost on UNITY_NOPROXY as I read in some pages, but it doesnt work. I also reinstall unty in different versions without results. I need it for job, ¿do you know how to fix it?

Thanks.

My Editor.log:

LICENSE SYSTEM [2018118 17:43:11] Next license update check is after 2018-01-17T20:39:18


LICENSE SYSTEM [2018118 17:43:11] 00331-10000-00001-AA393 != 00331-10000-00001-AA934

Built from '2017.3/staging' branch; Version is '2017.3.0f3 (a9f86dcd79df) revision 11139181'; Using compiler version '160040219'
OS: 'Windows 10  (10.0.0) 64bit' Language: 'es' Physical Memory: 16271 MB
BatchMode: 0, IsHumanControllingUs: 1, StartBugReporterOnCrash: 1, Is64bit: 1, IsPro: 0
[Package Manager] Server::Start -- Port 62602 was selected
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1

 COMMAND LINE ARGUMENTS:
E:\Unity\Editor\Unity.exe
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
[Package Manager] Server::EnsureServerProcessIsRunning -- ReadyRequest exceeded maximum alloted time, ran for [10] seconds
[Package Manager] Server::Kill -- Server was shutdown
[Package Manager] PackageManager Server::Start -- Process restart attempt #2

[Package Manager] Server::Start -- Port 53555 was selected
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
[Package Manager] Server::EnsureServerProcessIsRunning -- ReadyRequest exceeded maximum alloted time, ran for [10] seconds
[Package Manager] Server::Kill -- Server was shutdown
[Package Manager] PackageManager Server::Start -- Process restart attempt #3

[Package Manager] Server::Start -- Port 57360 was selected
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
[Package Manager] Server::EnsureServerProcessIsRunning -- ReadyRequest exceeded maximum alloted time, ran for [10] seconds
[Package Manager] Server::Kill -- Server was shutdown
[Package Manager] PackageManager Server::Start -- Process restart attempt #4

[Package Manager] Server::Start -- Port 57361 was selected
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
[Package Manager] Server::EnsureServerProcessIsRunning -- ReadyRequest exceeded maximum alloted time, ran for [10] seconds
[Package Manager] Server::Kill -- Server was shutdown
[Package Manager] PackageManager Server::Start -- Process restart attempt #5

[Package Manager] Server::Start -- Port 54855 was selected
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
[Package Manager] Server::EnsureServerProcessIsRunning -- ReadyRequest exceeded maximum alloted time, ran for [10] seconds
[Package Manager] Server::Kill -- Server was shutdown
[Package Manager] PackageManager Server::Start -- Process restart attempt #6

[Package Manager] Server::Start -- Port 62725 was selected
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
[Package Manager] Server::EnsureServerProcessIsRunning -- ReadyRequest exceeded maximum alloted time, ran for [10] seconds
[Package Manager] Server::Kill -- Server was shutdown
[Package Manager] PackageManager Server::Start -- Process restart attempt #7

[Package Manager] Server::Start -- Port 56123 was selected
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
[Package Manager] Server::EnsureServerProcessIsRunning -- ReadyRequest exceeded maximum alloted time, ran for [10] seconds
[Package Manager] Server::Kill -- Server was shutdown
[Package Manager] PackageManager Server::Start -- Process restart attempt #8

[Package Manager] Server::Start -- Port 63761 was selected
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
[Package Manager] Server::EnsureServerProcessIsRunning -- ReadyRequest exceeded maximum alloted time, ran for [10] seconds
[Package Manager] Server::Kill -- Server was shutdown
[Package Manager] PackageManager Server::Start -- Process restart attempt #9

[Package Manager] Server::Start -- Port 63763 was selected
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
[Package Manager] Server::EnsureServerProcessIsRunning -- ReadyRequest exceeded maximum alloted time, ran for [10] seconds
[Package Manager] Server::Kill -- Server was shutdown
[Package Manager] PackageManager Server::Start -- Process restart attempt #10

[Package Manager] Server::Start -- Port 58183 was selected
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
[Package Manager] Server::EnsureServerProcessIsRunning -- ReadyRequest exceeded maximum alloted time, ran for [10] seconds
[Package Manager] Server::Kill -- Server was shutdown
[Package Manager] PackageManager Server::Start -- Process restart attempt #11

[Package Manager] Server::Start -- Port 55844 was selected
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
D:/Proyectos Unity/pleaseeeeee
Loading GUID <-> Path mappings...0.000065 seconds
Loading Asset Database...0.000616 seconds
Audio: FMOD Profiler initialized on port 54900
AssetDatabase consistency checks...0.032908 seconds
Refreshing native plugins compatible for Editor in 0.01 ms, found 0 plugins.
Preloading 0 native plugins for Editor in 0.00 ms.
[Package Manager] Server::EnsureServerProcessIsRunning -- ReadyRequest exceeded maximum alloted time, ran for [10] seconds
[Package Manager] Server::Kill -- Server was shutdown
[Package Manager] PackageManager Server::Start -- Process restart attempt #12

[Package Manager] Server::Start -- Port 54979 was selected
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
[Package Manager] Server::EnsureServerProcessIsRunning -- ReadyRequest exceeded maximum alloted time, ran for [10] seconds
[Package Manager] Server::Kill -- Server was shutdown
[Package Manager] PackageManager Server::Start -- Process restart attempt #13

[Package Manager] Server::Start -- Port 63566 was selected
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
[Package Manager] Server::EnsureServerProcessIsRunning -- ReadyRequest exceeded maximum alloted time, ran for [11] seconds
[Package Manager] Server::Kill -- Server was shutdown
[Package Manager] PackageManager Server::Start -- Process restart attempt #14

[Package Manager] Server::Start -- Port 63568 was selected
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
Setting up noproxy from UNITY_NOPROXY environment variable. Setting to: localhost,127.0.0.1
[Package Manager] Failed to start Unity Package Manager: operation timed out.

okcompute_unity · March 3, 2018, 10:13pm

Hi,

First recommendation to fix this issue is to install the latest patch release for the major release you are using. We have fixed all known issues related to startup problems where the Package Manager is involved. You can download latest patch releases here: https://unity3d.com/unity/qa/patch-releases

If the issue persist after updating to the latest version. Please follow these guidelines:

1) The Unity Package Manager process (upm-win.exe on Windows or upm-macos on macOS) is signed and marked as legit. Anti-virus software should not block the process for most part. But, we still sometime get reports from users of this happening. Try to whitelist the process in your anti-virus software configuration (refer to your anti-virus software documentation to learn how to do it).

2) By default Unity http request to the package manager process do not goes through the proxy if you have one configured. But you can break this by accident if you have not overridden the `UNITY_NOPROXY` environment variable properly. If you did override this env var, make sure to include `127.0.0.1` in the list of addresses that should not go through your proxy (ex: `UNITY_NOPROXY=127,0.0.1,....`

3) There is a bug in March 2018 beta release of Windows Defender. This bug affects many softwares and Unity is one of those.

Until Microsoft fix the issue, the workaround they posted is to revert the antimalware platform to the version before the Beta. From an elevated command line prompt:

`"%programfiles%\Windows Defender\MpCmdRun.exe" -resetplatform `

If this solution still does not work for you. Try this solution instead (thank you @RobertRy!):

1. Open the Windows Defender Security Center (you can find it by typing Windows Defender in the Windows 10 search box)

2. Open the item called "Virus & threat protection" - it is the one with the shield icon

3. Click on the "Virus & threat protection settings"

4. Scroll down to "Exclusions"

5. Click on "Add or remove an exclusion"

6. Click on the plus sign "+ Add an exclusion"

7. Select the last exclusion type with the name "Process"

8. Type the name "upm-win.exe" into the box and click on "Add"

9. Close the Windows Defender Security Center 10.

That's it!

If after trying these workarounds you are still enable to start Unity, please report a bug so we can investigate further and resolve the problem for you and others: https://unity3d.com/unity/qa/bug-reporting

Regards,

Pascal

BrayanKrad03 · July 14, 2018, 11:51pm

For those who have this problem in unity 2018.1.8, i found a temporany fix, just disconnect from internet, then start unity and it will run normaly, its the only way that let me use Unity.

SLICKCODER · September 2, 2018, 8:32pm

@BrayanKrad03 Tried EVERYTHING…still can’t get Unity to work…TERRIBLE…what’s up with software?? any new ways to fix this problem?

okaybenji · December 13, 2019, 5:56pm

I was able to fix this issue by uninstalling and reinstalling the version of Unity that was causing it (2019.2.15f1). I have a fair degree of confidence it was caused by one of two things:

Uninstalling a different version of
Unity in Unity Hub while installing
this one (which has caused me
problems in the past, for instance
Hub uninstalling the wrong version),
or
Downloading/installing this
version of Unity in Unity Hub while
low on disk space (just a few gigs
free); I did free up some disk space
before trying again

Further details: I am on macOS Catalina. I was seeing this error when trying to open an existing project I downloaded from a GitHub repo. Also, if I tried to create a new Unity project with this version, Unity would start but nothing would happen. Trying to open the new project from Unity Hub gave the error “Invalid project path”.

Nyper · January 18, 2018, 6:53pm

Maybe this is the problem, but I dont know how to fix it.
https://image.prntscr.com/image/7j_xbF4qSi2afIcICGmXXg.png

botri · March 13, 2018, 8:45am

@okcompute_unity I’m also getting the package manager timing out when attempting to open (or create new) projects.
Here’s my Editor.log, showing no reason whatsoever for the package manager to time out:

LICENSE SYSTEM [2018312 17:21:15] Next license update check is after 2018-03-14T00:11:46

Built from '2017.3/staging' branch; Version is '2017.3.0f3 (a9f86dcd79df) revision 11139181'; Using compiler version '160040219'
OS: 'Windows 10  (10.0.0) 64bit' Language: 'en' Physical Memory: 32684 MB
BatchMode: 0, IsHumanControllingUs: 1, StartBugReporterOnCrash: 1, Is64bit: 1, IsPro: 1
[Package Manager] Server::Start -- Port 49515 was selected

 COMMAND LINE ARGUMENTS:
D:\msvso_externals\Xbox_XES_UnityHolographic\2017.3.0f3\Editor\Unity.exe
E:/App_MRMW.Milwaukee/src/MilwaukeeMR
Loading GUID <-> Path mappings...0.000095 seconds
Loading Asset Database...0.000562 seconds
Audio: FMOD Profiler initialized on port 54900
AssetDatabase consistency checks...0.038213 seconds
Refreshing native plugins compatible for Editor in 0.01 ms, found 0 plugins.
Preloading 0 native plugins for Editor in 0.00 ms.
[Package Manager] Server::EnsureServerProcessIsRunning -- ReadyRequest exceeded maximum alloted time, ran for [10] seconds
[Package Manager] Server::Kill -- Server was shutdown
[Package Manager] PackageManager Server::Start -- Process restart attempt #2

[Package Manager] Server::Start -- Port 49768 was selected
[Package Manager] Server::EnsureServerProcessIsRunning -- ReadyRequest exceeded maximum alloted time, ran for [11] seconds
[Package Manager] Server::Kill -- Server was shutdown
[Package Manager] PackageManager Server::Start -- Process restart attempt #3

[Package Manager] Server::Start -- Port 57138 was selected
[Package Manager] Server::EnsureServerProcessIsRunning -- ReadyRequest exceeded maximum alloted time, ran for [10] seconds
[Package Manager] Server::Kill -- Server was shutdown
[Package Manager] PackageManager Server::Start -- Process restart attempt #4

[Package Manager] Server::Start -- Port 53165 was selected
[Package Manager] Failed to start Unity Package Manager: operation timed out.

bkrabach · March 20, 2018, 2:28am

Hmm. Tried the exclusion in Windows Defender (sounded promising), but still didn’t work on this pc. I did try installing on another system running Windows Insider preview build 17115 and that worked fine. There is a newer build (17120) that I’m scheduled to upgrade to tonight, so I’ll see if it still works after that or not.

Shiromeow · October 23, 2018, 5:43pm

For those finding answer from this question, I find a solution for you which is work for me.
Unity seems sometime won’t automatic start server service which cause this problem.
Go to your service and find “Server” service and start it will solve your problem.

arktos888 · June 28, 2021, 4:52am

Hello!
This seems stupid enough but if you log out of the Unity Hub, it opens the editor!