Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.30f1
Issue ID
UUM-53122
Regression
No
"An assembly specified in the application dependencies manifest (Microsoft.NETCore.App.deps.json) was not found" error is thrown when creating a new project
How to reproduce:
1. Create and open a new project
2. Observe the Console
Expected result: No errors are seen
Actual result: Error is seen
Reproducible with: 2021.3.30f1
Reproducible on: Windows 10
Not reproducible on: No other environment tested
Notes:
- Error: An assembly specified in the application dependencies manifest (Microsoft.NETCore.App.deps.json) was not found:
package: 'runtime.win-x64.Microsoft.NETCore.App', version: '5.0.3-servicing.21072.12'
path: 'runtimes/win-x64/native/ucrtbase.dll'
- Not reproduced by CQA
Comments (1)
-
Tematl
Mar 09, 2025 11:01
Исправил данную ошибку переустановив 2021.3.X с дополнительными пакетами поддержки виндоус
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
If you still encounter this bug please replace the SDK with the Dotnet SDK instead, this seems to fix the issue