Nuget vulnerability on UE 5.6.1 on fresh installation
Engine Version 5.6.1. VS 2022 version latest 17.14.34, same with VS 2026
The problem suddenly appeared with updating some plugin via FAB, that required a c++ compilation (deleting intermediate/saved/binaries/.vs folder in project). I spare you
the iterations and details about that and made a clean c++ test project to exclude any local - project bound configuration details, where i still cant compile successfull:
fresh installation of Engine and VS, a fresh c++ blank project
in VS warning for NuGet vulnerability packages, that lead to failed compilation
see excerpt log on picture… and output log: AutomationUtils.Automation.csproj has an error NU1902 as Magick.Net-Q16-HDRI-AnyCPU Version 14.7.0 )
and for Microsoft.build 17.11.4
Note: considering the problems 5.6.1 version had a year ago: now that is the version which was suggested in all fixes here in the forum and does not work.
Now, updating Magick.Net-Q16-HDRI-AnyCPU to 14.13.1 and Microsoft.build to 17.11.48 : is failing in one point:
26>Expecting to find a type to be declared in a module rules named ‘VisualStudioTools’ in ‘UE5Rules, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null’. This type must derive from the ‘ModuleRules’ type defined by UnrealBuildTool.
26>
26>Result: Failed (RulesError)
26>Total execution time: 0.99 seconds
26>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.MakeFile.Targets(44,5): error MSB3073: The command ““C:\Program Files\Epic Games\UE_5.6\Engine\Build\BatchFiles\Build.bat” testCppEditor Win64 Development -Project=“D:\TESTProject\testCpp\testCpp.uproject” -WaitMutex -FromMsBuild -architecture=x64” exited with code 8.
26>Done building project “testCpp.vcxproj” – FAILED.
I am aware that manually updating these packages can break the build tool - and i really dont feel comfortable doing this. If you have any suggestions <3 - i need help
i did not try to downgrade it to the 14.9.1 - but might have found a compatible version in 14.14.0 for the magick.Net package. Note the earlier mentioned 14.13.1 is as well vulnerable since this week.
which compiled fine until i deleted intermediate … / … and regenerated the vs project files: → then it had the following problem:
Meanwhile VS needed an update too - so not sure to which update this problem is related.
i did not try to downgrade it to the 14.9.1 - but might have found a compatible version in 14.14.0 for the magick.Net package. Note the earlier mentioned 14.13.1 is as well vulnerable since this week.
which compiled fine until i deleted intermediate … / … and regenerated the vs project files: → then it had the following problem:
Meanwhile VS needed an update too - so not sure to which update this problem is related.
For those who might run into the similar trouble - i am one step further and i will check if it causes further troubles - if not will soon close this ticket.
The problem maybe even at its beginning seems to be linked to the “Unreal IntegrationTool” which seems to be outdated and not needed. This would explain, why the problem i experienced was somehow linked to the project environment at some point and looked in some lines of the output log like a fallback for some missing other part.
The last mentioned error ( “SetENV” task VS )that after reinstallation and updating this magick.Net and microsoft.build NuGet packages appeared can be repaired by following: solution and seems to be bound to VS 2026 and the local app data of Unreal Engine.
After this a new error appeared - which was linked to the IntegrationTool:
Expecting to find a type to be declared in a module rules named ‘VisualStudioTools’ in ‘UE5Rules, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null’. This type must derive from the ‘ModuleRules’ type defined by UnrealBuildTool.
this can be fixed by deinstalling the IntegrationTool plugin + regenerating project files etc…
The NuGet versions which worked so far for me are :
Magick.NET-Q16-HDRI-AnyCPU 14.14.0 only installed on the demanded check point
Microsoft.build 17.11.48
… they might have again a short expiration time (LOL)
Maybe worth mentioning:
the reposted suggestion of fixing “SetENV” VS error using 2026 and setting the pathlength to a particular number did not fix the problem (and this only can be done in VS 2026)
It was a BAD BAD BAD IDEA of repairing the VS-2022 installation: VS installer failed with an error that some UnrealEngine.msi could not be repaired and broke VS installation
!