Nuget issue after upgrading project from 5.3 to 5.5

I get NETSDK1064: Package not found error and can’t build. I tried upgrading vs 2022 to the latest. Anyone have a fix for this?

Log:
NuGet package restore failed. Please see Error List window for detailed warnings and errors.
Error occurred while restoring NuGet packages: Access to the path ‘D:\Programs\UE_5.5\Engine\Source\Programs\AutomationTool\Mutable\RunMutableCommandlet\obj\RunMutableCommandlet.Automation.csproj.nuget.g.props’ is denied.

Error List:
Package System.Data.DataSetExtensions, version 4.5.0 was not found. It might have been deleted since NuGet restore. Otherwise, NuGet restore might have only partially completed, which might have been due to maximum path length restrictions.
The “GenerateMSBuildEditorConfig” task failed unexpectedly.
System.UnauthorizedAccessException: Access to the path ‘D:\Programs\UE_5.5\Engine\Source\Programs\AutomationTool\Mutable\RunMutableCommandlet\obj\Development\RunMutableCommandlet.Automation.GeneratedMSBuildEditorConfig.editorconfig’ is denied.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream…ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.StreamWriter.CreateFile(String path, Boolean append, Boolean checkHost)
at System.IO.StreamWriter…ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize, Boolean checkHost)
at System.IO.File.InternalWriteAllText(String path, String contents, Encoding encoding, Boolean checkHost)
at Microsoft.CodeAnalysis.BuildTasks.GenerateMSBuildEditorConfig.WriteMSBuildEditorConfig()
at Microsoft.Build.BackEnd.TaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.d__26.MoveNext()
The command “D:\Programs\UE_5.5\Engine\Build\BatchFiles\Build.bat InterceptEditor Win64 DebugGame -Project=“D:\Data\UnrealProjects\Intercept55\Intercept.uproject” -WaitMutex -FromMsBuild -architecture=x64” exited with code 6.

Haven’t tried packaging yet with UE 5.5 or VS 2022 17.12 but I also experienced NuGet related issues with the latest VS version with older UE versions (by older I just mean UE 5.4.4) so I’m currently using UE 5.4.4 with 17.8 and there seems to be no issues :innocent:

1 Like

I got past this error by going to the directory ‘D:\Programs\UE_5.5\Engine\Source\Programs\AutomationTool\Mutable\RunMutableCommandlet\obj and making everything not read only.

Still other errors though…

4 Likes

Good find @MarkcusD! I’d recommend in addition also ensuring you’re running the latest VS and DotNet FM if you’re still getting errors. I hope that helps!

I have been having similar problems and took me and entire day to figure it out

so this is how i solved it

install winutil “GitHub - ChrisTitusTech/winutil: Chris Titus Tech's Windows Utility - Install Programs, Tweaks, Fixes, and Updates” and follow the steps
download revo uninstaller through winutil
uninstall visual studio 2022 and the installer through it, remove all linked registry and packages
install visual studio 2022 again through the official website
have the workloads based on your needs
basic to get started

  • .NET desktop development
  • Desktop development with C++
  • Game development with C++ (make sure unreal Engine Test Adapter is marked)

Install everything

go to your project.sln and open it, run a check on the configuration and ensure everything is good
close your vs 2022
right click your .uproject file and select Generate Visual Studio project files, wait till it finishes
open your project.sln
run the project

should be solved

1 Like

Hey, im using 5.4.4
but this issue isn’t being resolved for me even after trying out your method

I even reinstalled unreal engine 5.4.

and I had used revo uninstaller for removing VS as well as VS installer
and followed the actual Unreal Engine’s Guide on installing VS for 5.4
still keep getting the NuGet Errors saying project is vulnerable as well as like 20+ errors on build

Can you please share the individual components you changed or anything else which was changed? cuz im unable to make it run on UE 5.4.4 or older versions. getting like 20+ errors there all stating some vulnerability

Yes, there’s indeed certain things you need to adjust in order to make VS 2022 17.8 work flawlessly with UE 5.4.4. But you should only be getting a single warning and not any errors. First, verify the correct engine version from Epic Launcher and see if you can reduce the warnings to 1 and errors to 0. And to fix that last issue, you can check out this post: Microsoft.extensions.caching.memory in EpicGames.Horde still use version 6.0.1 .NET that has Denial of Service Vulnerability - #4 by ravendcode

Hey guys. Just wanted to say I followed the following steps and this worked for me.
I was upgrading from 5.4 to 5.5
Note: the build errors don’t go away but they also don’t hinder the project from being run.

  1. Download Unreal 5.5

  2. Upgrade Visual Studio via the Visual Studio Installer

  3. Avoid opening a previous project at this point

  4. Uninstall the UnrealVS plugin from Visual Studio, by opening Visual Studio without a project and uninstall the extension

  5. Reinstall the UnrealVS plugin by following this guide: Using the UnrealVS Extension for Unreal Engine C++ Projects | Unreal Engine 5.5 Documentation | Epic Developer Community

  6. Create a new C++ project with unreal. Make sure it works:

    • Try to create new C++ Project with new installed UE and make sure it work
    • Delete all auto-generated folders like Binaries, Intermediate, .sln file
    • Right click on .uproject and generate Visual Studio project.
    • Build the entire solution
    • You should get these errors (this is normal):
    The "GenerateMSBuildEditorConfig" task failed unexpectedly.
    

System.UnauthorizedAccessException: Access to the path ‘C:\Program Files\Epic Games\UE_5.5\Engine\Source\Programs\AutomationTool\Mutable\RunMutableCommandlet\obj\Development\RunMutableCommandlet.Automation.GeneratedMSBuildEditorConfig.editorconfig’ is denied.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream…ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.StreamWriter.CreateFile(String path, Boolean append, Boolean checkHost)
at System.IO.StreamWriter…ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize, Boolean checkHost)
at System.IO.File.InternalWriteAllText(String path, String contents, Encoding encoding, Boolean checkHost)
at Microsoft.CodeAnalysis.BuildTasks.GenerateMSBuildEditorConfig.WriteMSBuildEditorConfig()
at Microsoft.Build.BackEnd.TaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.d__26.MoveNext()
Package System.Data.DataSetExtensions, version 4.5.0 was not found. It might have been deleted since NuGet restore. Otherwise, NuGet restore might have only partially completed, which might have been due to maximum path length restrictions.
Could not write lines to file “obj\Development\RunMutableCommandlet.Automation.csproj.FileListAbsolute.txt”. Access to the path ‘C:\Program Files\Epic Games\UE_5.5\Engine\Source\Programs\AutomationTool\Mutable\RunMutableCommandlet\obj\Development\RunMutableCommandlet.Automation.csproj.FileListAbsolute.txt’ is denied.
```
- Ensure that the build target is set to the project name MyProject
- Debug the target to launch unreal

If everything is good at this stage, you can try to migrate your old project.
Note: the following steps were necessary.

  1. Disable VisualStudioTools plugin by opening the .uproject file in a text editor and setting Enabled to false.
  2. Attempt to open the project from the unreal launcher with unreal 5.5. It will tell you that your project is going to be upgraded. Make a copy (if you want to be safe) and proceed with the upgrade.
  3. It may or may not complain that the project needs to be built. Quit Unreal and open the project in the file explorer.
  4. Delete the .sln, Binaries and Intermediate folders.
  5. Regenerate the sln files by right clicking the .uproject and selecting “Generate Visual Studio project files”
  6. Open the solution in Visual Studio, clean the solution, build the solution (ignore the errors mentioned above)
  7. Debug the solution to launch Unreal

It worked very well for me. Thank you very much!

Had the same situation here, and making all folders and files writable in …\UE_5.5\Engine\Source\Programs\AutomationTool\Mutable\RunMutableCommandlet\obj fixed the problem. For me, this happened because I updated the NuGet packages to the next approach version (e.g., 4.0.0 to 4.0.1). VS Community 2022 was showing a warning in the Solution Manager that some packages were vulnerable.

Well, I haven’t been able to solve this issue either. After uninstalling everything related to Visual Studio Community 2022, .NET, and C++, the problem persisted. I even formatted my laptop, but the issue remains.

All of my projects are currently stuck because of this error, and I’m seriously considering rolling back to version 5.4 to see if that resolves it. I’m also strongly considering migrating all my projects to Unity 6, as I noticed this NuGet package issue doesn’t occur in Unity 6 projects.

Well, in a somewhat magical way, I managed to compile everything without issues after loading the same project in version 5.4. From my perspective, this problem seems to be related to UE 5.5 and Visual Studio Community 2022. For now, I’ll wait for version 5.6 to be released before attempting to upgrade the project again.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.