Ошибка при запуске Unity

Как решить эту проблему При запуске Unity появляеться ошибка.
Пишет что нету UnityPackageManager.exe в папке Server. Антивируса у меня нет, по этому это не из-за антивируса. CCleaner[-ом] чистил давно поэтому это тоже не может бить из-за CCLeaner. Та даже если, пробовал переустановливать Unity, а так же пробовал установить другую версию, тоже эта проблема. Не знаете как решить? Второй день мучаюсь . Если у вас не прогрузиться скрин ошибки то вот моя проблема (И кстати устанавливал через Unity Hub):

Could not find Unity Package Manager local server aplication at
[E:/Unity/2020.2.1f1/Editor/Data/Resources/PackageManager/Server/UnityPackageManager.exe].
Missing files could be the result of an antivirus action or corrupt Unity installation.

Click on Retry to relaunch Unity and reopen you project.

Click Diagnose to launch the Unity Package Manager Diagnostic Tool.

Ошибка при запуске unity
В чем дело? Как исправить эту ошибку?

Ошибка при запуске скрипта в Unity (C#)
using System.Collections; using System.Collections.Generic; using UnityEngine; public class.

Есть ли здесь ошибка? Писал скрипт в Unity для игры, но почему-то при запуске все зависает и нечего не работает
Я скинул пару примеров с циклами может ошибка в них. 1) int Amaunt = 0; foreach (int.

Unity крашится при запуске
Вечер добрый! Помогите Unity запускается и при загрузке пустой сцены выходит окно с.

Security update KB2533623 no longer available #20459

Comments

florenzen commented Sep 4, 2020 •

The security update KB2533623 is no longer available for download from Microsoft. Does that mean a .NET Core Installation on Windows 7 is not possible anymore?

I know, Windows 7 is out of support but there is also Windows Embedded Standard which is based in that version and which still has support in industrial applications.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 1eeab451-820f-de42-983e-4d0d5764f6ab
• Version Independent ID: d11d0d14-8a03-50e4-5c00-9a4417ad4d0a
• Content: Install .NET Core on Windows
• Content Source: docs/core/install/windows.md
• Product: dotnet-core
• GitHub Login: @adegeo
• Microsoft Alias: adegeo

The text was updated successfully, but these errors were encountered:

adegeo commented Sep 4, 2020

adegeo commented Sep 4, 2020

@florenzen The download is restored. Thank you for reporting it!

adegeo commented Sep 7, 2020

Download is gone again.. Or I was mistaken when I thought it was restored. Reopening.

adegeo commented Sep 9, 2020

Seems to be there again. hrm

florenzen commented Sep 9, 2020

The thread claims that KB2533623 is superseded by KB3063858 or KB4457144. As a test, I installed KB4457144 from https://www.catalog.update.microsoft.com/Search.aspx?q=KB4457144 and .NET 5 Preview 8 worked for me on Windows 7. (I did not check KB3063858.)

I had the link for the update from https://docs.microsoft.com/en-us/dotnet/core/install/windows?tabs=netcore31 since I did not find an equivalent page for .NET 5 Preview 8. Perhaps, the documentation could be updated to point to KB4457144.

adegeo commented Sep 9, 2020 •

Ahhh the link inside of the link! Thank you for the clarification.

To note for .NET 5, I doubt it will be officially supported on Win 7, and wouldn’t be documented as such here. Core 3.1 was released while Win 7 was in extended support, but that ended in January. Considering .NET 5 is yet to be released, I don’t think they would guarantee that it works on Win 7.
EDIT: The release notes for supported OS on .NET 5 indicates it’s supported.

florenzen commented Sep 9, 2020

Thanks for the clarification wrt. the Windows 7 support period. There are still Windows Embedded Standard 7 Systems running in e. g. industrial systems that still receive (paid) support, which is the kind of system we are working with. Is there any chance to get a statement from the .NET development wrt. to that kind of Installation? Anyone I could ask?

adegeo commented Sep 9, 2020

You could try filing an issue at the source repo for .NET: https://github.com/dotnet/core/issues they would hopefully be able to get you some sort of information. If that doesn’t work after some time, hit me up again and I’ll see if I can find someone.

OraDotNetDev commented Sep 30, 2020 •

I was wondering you might be able to get any further information, there’s not been any conclusion to the issue @florenzen raised for this on the .Net Core repo?

adegeo commented Sep 30, 2020

Thanks for the ping. I’ll send out another email internally.

adegeo commented Sep 30, 2020

Has anyone tested installing KB4457144 as a replacement for KB2533623 on Win7?

jberezanski commented Oct 5, 2020

I have tested KB3063858, which is a tiny update (as opposed to KB4457144 — a full monthly rollup), and it does make .NET Core 3.1 work correctly. Once KB3063858 and updated KB2533623 Chocolatey packages pass moderation, .NET Core will again be installable (runtime, sdk, windowshosting) with Chocolatey on Windows 7/2008 R2.

doghappy commented Nov 11, 2020

KB3063858 fixed the problem for me!

bairog commented Nov 24, 2020 •

Same here! KB2533623 liks are broken, but still mentioned as a .NET Core 3.1/.NET 5 necessary dependency.
I will test KB3063858 (links are ok) tomorrow — but it is NOT mentioned as .NET Core 3.1/.NET 5 dependency
P. S. @adegeo — you’ve closed my issue #21706 as duplicate. What steps are going to be performed to fix existing problem — fixing KB2533623 broken links or correcting description at .NET Core 3.1/.NET 5 dependencies page? What is estimated timeframe?
Thank you.

bairog commented Dec 2, 2020 •

The team is researching this. Does anyone have the errors they receive when they run or install .NET 5/Core without these patches?

We have two testing environments with clean Windows 7 SP1 x86 (without any updates installed) and clean Windows 10 1607 x64.
On Windows 7 SP1 x86 .NET Desktop Runtime 5.0.0 (windowsdesktop-runtime-5.0.0-win-x86.exe) installs without any problems, but when we run our .NET 5.0 test applications (console/WinForms x86) — we get an error:

The library hostfxr.dll was found, but loading it from C:\Program Files\dotnet\host\fxr\5.0.0\hostfxr.dll failed
Installing .NET Core prerequisites might help resolve this problem. https://go.microsoft.com/fwlink/?linkid=798306

Installing KB2533623 (from Web Archive) solves the problem, didn’t test KB3063858 yet, mybe later..

P. S. Some of our customers have PCs isolated from Internet/WSUS — so we are to include KB patches in our software installer.

bairog commented Dec 22, 2020

@adegeo
Today we again performed a test on our clean Windows 7 SP1 x86 (without any updates installed):


Latest .NET Desktop Runtime 5.0.1 (windowsdesktop-runtime-5.0.1-win-x86.exe) installs without any problems.
But when we run our .NET 5.0 test applications (console/WinForms x86) — we get an error:

The program can’t start because api-ms-win-crt-runtime-l1-1-0.dll is missing from your computer. Try reinstalling the program to fix this problem.

The main difference is that neither KB2533623 (from Web Archive) nor KB3063858 solves the problem this time.
The only working solution was installing KB2999226 (very strange because it is a prerequisite for .NET Framework 4.8 offline installer) and after that installing KB2533623 or KB3063858 (no matter which one).
Investigate this problem ASAP please.

P. S. Some of our customers have PCs isolated from Internet/WSUS — so we are to include KB patches in our software installer.

adegeo commented Dec 22, 2020

@bairog Thank you very much for this information, I’ll pass it on to the team!

Avispa commented Jan 3, 2021

I can confirm that the security update is still not available.

@bairog Thank you very much for this information, I’ll pass it on to the team!

@adegeo Don’t pass it anywhere, just re-upload the file or fix the link.

In case you lost it, you can download it from web.archive.org. Maybe consider to make a big donation to the Internet Archive since they manage to to keep your security patches available and by that de facto handle Microsoft’s customer service too. So I think they deserve some appreciation.

Side note: your dots below the blue helicopter don’t scale consistently in different resolutions as seen in the screen shot. Upon interpretation the helicopter appears to pick up the wrong dot or straight lost it. Kinda ironic.

adegeo commented Jan 5, 2021 •

I got some clarifications on what has happened. The old patches were removed because they are all signed with SHA-1 certificates, which are no longer secure due to shatter attacks. Microsoft as a whole has moved on to at least SHA-256 security and thus there was a company-wide effort to remove SHA-1 stuff.

However, there are newer patches which have been reported as including the fixes required to install .NET on Windows 7: https://www.catalog.update.microsoft.com/Search.aspx?q=kb4534310

@bairog would you be able to confirm this fixes your problem (if you have an easy test environment) I’m going to work on creating a test environment but it would be good to hear from you.

bairog commented Jan 6, 2021 •

@bairog would you be able to confirm this fixes your problem (if you have an easy test environment) I’m going to work on creating a test environment but it would be good to hear from you.

I’ve performed a test on our clean Windows 7 SP1 x86 (without any updates installed). Installing KB4534310 update results in error:

UPDATE I had same error message before (when installing .NET Framework 4.8 on clean Windows7 SP1 x86).
Than time I’ve solved the problem by installing MicrosoftRootCertificateAuthority2011.cer (more info at StackOveflow).
But even installing that certificate is not enough for KB4534310 update. So the problem is still here.

P.S. Even if you find a way to install KB4534310 update and this update makes our our .NET 5.0 test applications (console/WinForms x86) work correctly — that is hardly suitable for us. KB4534310 update is a full monthly rollup (size for Windows 7 SP1 x86 is 204Mb). Including an update that is more than 2 times bigger than our software installer itself (it is less than 100Mb) — is a nonsence.
But we are to include KB patches in our software installer because some of our customers have PCs isolated from Internet/WSUS.
Hope you will a smaller separate update (1-5Mb) that will make .NET 5 work on clean Windows 7 SP1 x86.
Good luck.

adegeo commented Jan 7, 2021 •

@bairog Thank you for testing and giving me some results. I was able to spin up a test machine today too, a clean Win 7 x64 SP1 from the Visual Studio downloads. I also had that same error on some files but I fixed it by unblocking it in the file properties, was that not the source of the problem?

Your requirement of having a small footprint for distribution is noted. I’m passing that info and this post on to the team. I was able to boil down and confirm that these steps worked for me. I don’t know though if windows update installed something behind me that may have contributed to its success:

I’m going to do another test networkless and make sure it works.
I validated on a connectionless VM that installing those two downloads worked, even with a .NET 5 WinForms project. I only tested with .NET 5. I think they said they improved things for .NET 5 so I’ll have to test with 3.1 to see if that works too.

bairog commented Jan 7, 2021 •

@adegeo
I can confirm that installing the following:

makes our .NET 5.0 test applications (console/WinForms x86) work correctly.

I can also confirm that Microsoft Visual C++ 2015-2019 Redistributable 32-bit / 64-bit can be used instead of Microsoft Visual C++ 2015 Redistributable Update 3.
It is already included in our software installer (part of our modules are C++) — so we need only include KB3063858 update (905Kb).
Great job!

[Unity] Не работает Package Manager

Не отображаются ВСЕ пакеты, бесконечно отображается «Loading packages».

Версия юнити 2018.3.8f1.

Нет пинга к packages.unity.com (в консоле почему-то bintray.com) — в браузере просто белый лист (заходит на сайт https://bintray.com/).
Asset Store — работает. Unity с правами админа запускал. Пустой проект пробовал.

Неужели с таким никто не сталкивался?

2018.3.8f1 список пакетов отображается без проблем.

> Нет пинга к packages.unity.com (в консоле почему-то bintray.com) — в браузере просто белый лист
Тоже белый лист и не пингуется. Возможно, и не должен. Microsoft.com, например, никогда не пинговался.

Не белый лист:

список пакетов отображается без проблем.

Версия 2019.1.0f проблема сохраняется. Нашел способ как обойти — в файле manifest.json дописываем необходимый пакет (например «com.unity.probuilder»: «4.0.4») в «dependencies», перезапускаем юнити и пакет устанавливается автоматом.
Откуда взять название и версию? — отключаем интернет, заходим в «Package Manager» появляется весь список, запоминаем название (по крайней мере с probuilder прокатило) и версию.

Названия, версии да и сами пакеты можно получить тут: https://download.packages.unity.com/

alexzzzz
> Названия, версии да и сами пакеты можно получить тут:
> https://download.packages.unity.com/
спасибо за ссылку.

Вот сетевая статистика с момента открывания менеджера пакетов в 2019.1 до пропадания надписи «Loading packages».

Первые два адреса в списке — это туда по протоколу HTTPS обращается UnityPackageManager.exe. Остальное ― это UnityPackageManager.exe и Unity.exe общаются между собой.

Вместо 75.126.118.184 могут быть 108.168.194.93 или 75.126.208.206 ― это всё одно и то же. Ни один не пингуется.

Трассировка packages.unity.com (bintray.com, 75.126.118.184)

Трассировка маршрута к bintray.com [75.126.118.184]
с максимальным числом прыжков 30:

1 1 ms 1 ms 1 ms 192.168.1.1
2 8 ms 8 ms 8 ms 178.34.128.49
3 8 ms 8 ms 8 ms 178.34.129.235
4 60 ms 68 ms 60 ms 188.254.15.87
5 * * * Превышен интервал ожидания для запроса.
6 86 ms 88 ms 86 ms ae5.cbs02.tg01.lon01.networklayer.com [169.45.18.16]
7 80 ms 80 ms 83 ms ae8.cbs02.eq01.lon03.networklayer.com [169.45.19.44]
8 80 ms * 79 ms ae2.cbs02.eq01.ams02.networklayer.com [50.97.19.184]
9 78 ms 78 ms * ae7.cbs01.eq01.ams02.networklayer.com [50.97.17.248]
10 158 ms 159 ms * ae3.cbs02.eq01.wdc02.networklayer.com [50.97.17.242]
11 158 ms 156 ms * ae7.cbs01.eq01.wdc02.networklayer.com [50.97.17.142]
12 * * * Превышен интервал ожидания для запроса.
13 * 185 ms * ae0.cbs02.eq01.dal03.networklayer.com [50.97.17.162]
14 184 ms 202 ms 184 ms ae34.bbr02.eq01.dal03.networklayer.com [50.97.17.59]
15 183 ms 183 ms 183 ms ae5.dar02.dal05.networklayer.com [173.192.18.217]
16 186 ms 187 ms 186 ms po2.fcr04.sr03.dal05.networklayer.com [173.192.118.151]
17 * * * Превышен интервал ожидания для запроса.
18 * * * Превышен интервал ожидания для запроса.
19 * * * Превышен интервал ожидания для запроса.
20 * * * Превышен интервал ожидания для запроса.
21 * * * Превышен интервал ожидания для запроса.
22 * * * Превышен интервал ожидания для запроса.
23 * * * Превышен интервал ожидания для запроса.
24 * * * Превышен интервал ожидания для запроса.
25 * * * Превышен интервал ожидания для запроса.
26 * * * Превышен интервал ожидания для запроса.
27 * * * Превышен интервал ожидания для запроса.
28 * * * Превышен интервал ожидания для запроса.
29 * * * Превышен интервал ожидания для запроса.
30 * * * Превышен интервал ожидания для запроса.

18.184.45.40 — не засветился, через браузер выдает туже ошибку:

Касперский показывает для «Node.js: Server-side JavaScript» разное количество соединений
— сначала было 44, а при открытии окна «Package Manager» прыгало до 64 и резко назад до 44.
[лез к ip: часть 75.126.118.184, часть 75.126.208.206]
Вырубил процесс UnityPackageManager.exe
— все соединения исчезли
Снова открыл «Package Manager»
— 25 соединений [все 108.168.194.93]
Переоткрыл «Package Manager»
— 60 соединений и резко упало до 25 [все 108.168.194.93]
Последующие переоткрытия завесили 60 соединений, которые перестали уменьшаться, а при очередном переоткрытии перестал отображаться список того, что у меня установлено.

Непонятно зачем ему куча соединений.

Жаль что никакие ошибки не сыпятся, только при удалении процесса UnityPackageManager.exe.

> — сначала было 44, а при открытии окна «Package Manager» прыгало до 64 и резко назад до 44.
Я смотрел через tcpview.

В простое UnityPackageManager.exe только слушает какой-нибудь порт на локальном адресе, ждёт команд от Unity.exe. Когда открываешь менеджер пакетов, UnityPackageManager.exe открывает полтора экрана https-соединений с кем-нибудь из 75.126.118.184, 108.168.194.93, 75.126.208.206. Потом их все закрывает, когда закончит.

Мне кажется, у тебя какой-то косяк с HTTPS. Или Касперский вмешивается, или Ростелеком.

В логе есть что-нибудь интересное? ― C:\Users\ \AppData\Local\Unity\Editor\upm.log

Трейсы у меня выглядят похоже:

alexzzzz
> Я смотрел через tcpview.
хм.. «Network Summary» я не нашел, а tcpview вот что показал:

Unity Hub.exe 15356 TCP DESKTOP-MJ2UEBD 39000 DESKTOP-MJ2UEBD 0 LISTENING
Unity Hub.exe 15356 TCPV6 desktop-mj2uebd 39000 desktop-mj2uebd 0 LISTENING
Unity.exe 13520 TCP DESKTOP-MJ2UEBD 1217 DESKTOP-MJ2UEBD 0 LISTENING
Unity.exe 13520 TCP DESKTOP-MJ2UEBD 34999 DESKTOP-MJ2UEBD 0 LISTENING
Unity.exe 13520 TCP DESKTOP-MJ2UEBD 38000 DESKTOP-MJ2UEBD 0 LISTENING
Unity.exe 13520 TCP DESKTOP-MJ2UEBD 38443 DESKTOP-MJ2UEBD 0 LISTENING
Unity.exe 13520 UDP DESKTOP-MJ2UEBD 34997 * *
Unity.exe 13520 UDP DESKTOP-MJ2UEBD 54997 * *
Unity.exe 13520 UDP DESKTOP-MJ2UEBD 56974 * *
Unity.exe 13520 UDP DESKTOP-MJ2UEBD 56975 * *
Unity.exe 13520 TCP desktop-mj2uebd.home 1220 ec2-52-17-201-152.eu-west-1.compute.amazonaws.com https ESTABLISHED
Unity.exe 13520 TCP DESKTOP-MJ2UEBD 56520 DESKTOP-MJ2UEBD 0 LISTENING
Unity.exe 13520 TCP DESKTOP-MJ2UEBD 1217 localhost 1223 ESTABLISHED
Unity.exe 13520 UDP DESKTOP-MJ2UEBD 56522 * *
Unity.exe 13520 TCP DESKTOP-MJ2UEBD 1226 localhost 1227 ESTABLISHED
Unity.exe 13520 TCP DESKTOP-MJ2UEBD 1227 localhost 1226 ESTABLISHED
Unity.exe 13520 TCP desktop-mj2uebd.home 1230 138.21.238.35.bc.googleusercontent.com http CLOSE_WAIT
Unity.exe 13520 TCP DESKTOP-MJ2UEBD 1234 localhost 56973 CLOSE_WAIT
Unity.exe 13520 TCP DESKTOP-MJ2UEBD 1235 localhost 56973 CLOSE_WAIT
Unity.exe 13520 TCP DESKTOP-MJ2UEBD 1236 localhost 56973 ESTABLISHED

UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14744 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14757 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14758 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14768 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14769 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14774 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14775 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14776 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14780 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14782 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14786 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14788 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14790 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14792 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14793 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14796 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14805 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14807 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14810 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14812 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14813 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14817 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14818 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14819 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14823 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14824 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14825 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14826 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14827 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14828 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14829 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14830 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14831 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14833 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14834 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14835 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14836 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14837 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14838 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP desktop-mj2uebd.home 14839 ce.d0.7e4b.ip4.static.sl-reverse.com https ESTABLISHED
UnityPackageManager.exe 23004 TCP DESKTOP-MJ2UEBD 56412 DESKTOP-MJ2UEBD 0 LISTENING
UnityPackageManager.exe 23004 TCP DESKTOP-MJ2UEBD 56412 localhost 14722 ESTABLISHED

alexzzzz
> В логе есть что-нибудь интересное?

alexzzzz
> Или Касперский вмешивается
Отключал самозащиту, выходил из него.

alexzzzz
> или Ростелеком
Раньше же не вмешивался, да и у многих бы был тогда такой косяк.

alexzzzz
> Мне кажется, у тебя какой-то косяк с HTTPS
я хз.. но пакеты-то устанавливаются.

Файл hosts на всякий сбросил на значения по дефолту — не помогло. Самое косячное, что он ошибку не выдает, а тупо бесконечно пытается подключиться.