# Update NuGet Magick.NET Packages

**URL:** <https://forums.unrealengine.com/t/update-nuget-magick-net-packages/2655207>\
**Category:** Feedback & Requests\
**Tags:** unreal-engine\
**Created:** [September 9, 2025, 10:28pm UTC](https://forums.unrealengine.com/t/update-nuget-magick-net-packages/2655207 "2025-09-09T22:28:56Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Smokey019](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Smokey019](https://forums.unrealengine.com/u/Smokey019)\
**Post date:** [September 9, 2025, 10:28pm UTC](https://forums.unrealengine.com/t/update-nuget-magick-net-packages/2655207/1 "2025-09-09T22:28:56Z")

</div>

It’s probably a good idea to let people know to update the NuGet packages while building from source.

I’ve been debugging for an entire day not realizing that msbuild just won’t accept Unreal Engine 5.6.1’s default Magick .NET library because of security vulnerabilities.

If you’re having issues with Automation errors or warnings, this is what is causing it. Use Visual Studio Code to Manage NuGet packages and update the Magick .NET libraries for all Automations.

---

<div class="post-metadata">

**Author:** ![nande](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/nande/32/1057698_2.png) [@nande](https://forums.unrealengine.com/u/nande)\
**Post date:** [September 23, 2025, 9:18pm UTC](https://forums.unrealengine.com/t/update-nuget-magick-net-packages/2655207/2 "2025-09-23T21:18:38Z")

</div>

> [@Knowledge Base: Tech Note: Errors when compiling the Unreal Automation Tool in 5.6](https://forums.unrealengine.com/t/knowledge-base-tech-note-errors-when-compiling-the-unreal-automation-tool-in-5-6/2651216):
>
> We have identified errors when compiling the UAT and have found a solution. [https://dev.epicgames.com/community/learning/knowledge-base/DBLR/unreal-engine-tech-note-errors-when-compiling-the-unreal-automation-tool-in-5-6](https://dev.epicgames.com/community/learning/knowledge-base/DBLR/unreal-engine-tech-note-errors-when-compiling-the-unreal-automation-tool-in-5-6)

---

<div class="post-metadata">

**Author:** ![MangyGoblinGam](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@MangyGoblinGam](https://forums.unrealengine.com/u/MangyGoblinGam)\
**Post date:** [November 18, 2025, 1:34am UTC](https://forums.unrealengine.com/t/update-nuget-magick-net-packages/2655207/3 "2025-11-18T01:34:14Z")

</div>

If anyone ends up on this page because of this error all you have to do is open the automation project via visual studio at Engine\Source\Programs\AutomationTool\Gauntlet\Gauntlet.Automation.csproj and then use the NuGet package system to update it. You don’t need to build it to do this or generate/save the sln file. This is for the Error: appError called: Assertion failed: (!FPlatformProcess::SupportsMultithreading()) || (!bIsRunning error or the [Magick.net](http://Magick.net) warningaserror issue.

---

<div class="post-metadata">

**Author:** ![DaWhirlpool](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/dawhirlpool/32/561471_2.png) [@DaWhirlpool](https://forums.unrealengine.com/u/DaWhirlpool)\
**Post date:** [February 19, 2026, 4:53pm UTC](https://forums.unrealengine.com/t/update-nuget-magick-net-packages/2655207/4 "2026-02-19T16:53:28Z")

</div>

It’s been a number of months since this but I’m in a situation where I have been working on a number of things including significant changes to UE5.6’s render pipeline. I’m very proud of the results and as an indie game dev, this represents a significant part of my game dev. I have had nothing but issues with NuGet vulnerabilities and [Magick.NET](http://Magick.NET) updates all the way through.

The “Turnkey” is blocked because warnings are treated as errors. As a result, I have spent multiple days trying to package my prototype with no success. I tried using the changelist mentioned above (while updating the logic to the recent versions). No dice. It’s hard to imagine that the “turnkey” is where I’m blocked. Epic’s architectural choice to treat the NuGet ecosystem warnings as terminal errors without actually verifying that the engine’s sub-plugins (like Mutable or LowLevelTests) have also been updated to match the new rules is seemingly the issue.

Does anyone have any ideas how I can consolidate the clash? Or am I looking at migrating to a newer engine?