# Is there any workaround for the Visual Studio 2017 15.9+ requirement for UE4.21?

**URL:** <https://forums.unrealengine.com/t/is-there-any-workaround-for-the-visual-studio-2017-15-9-requirement-for-ue4-21/442425>\
**Category:** Pipeline & Plugins\
**Tags:** visual-c-platform-to, workaround, unreal-engine, Visual-Studio, CPP, question\
**Created:** [January 30, 2019, 10:53pm UTC](https://forums.unrealengine.com/t/is-there-any-workaround-for-the-visual-studio-2017-15-9-requirement-for-ue4-21/442425 "2019-01-30T22:53:28Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![anonymous\_user\_4965f77a](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_4965f77a](https://forums.unrealengine.com/u/anonymous_user_4965f77a)\
**Post date:** [January 30, 2019, 10:53pm UTC](https://forums.unrealengine.com/t/is-there-any-workaround-for-the-visual-studio-2017-15-9-requirement-for-ue4-21/442425/1 "2019-01-30T22:53:28Z")

</div>

In `WindowsPlatformCompilerSetup.h`, there is a static\_assert that checks:

`static_assert(_MSC_VER != 1914 && _MSC_VER != 1915, "Visual Studio 2017 versions 15.7 and 15.8 are known to have code generation bugs that affect UE4. Please update to version 15.9.");`

I’m in a situation where I may not be able to upgrade the compiler version just yet. Does anyone know exactly what triggers these code generation bugs? Perhaps I can avoid them by selecting a particular optimization level?

I will eventually be able to upgrade to 15.9 (I’ve long since done so on my personal dev machine), but I could really use a workaround for the present. I’d rather not try to hack around this and just cross my fingers, hoping that my users will never happen upon a crash.

Update: I believe I found the root cause here: [Developer Community](https://developercommunity.visualstudio.com/content/problem/345511/bad-code-generation-in-vs-2017-v1585.html)