# Locked out of using UE5 because Visual Studio 2022 Community is not available anymore

**URL:** <https://forums.unrealengine.com/t/locked-out-of-using-ue5-because-visual-studio-2022-community-is-not-available-anymore/2675624>\
**Category:** Feedback & Requests\
**Tags:** unreal-engine\
**Created:** [November 16, 2025, 4:49pm UTC](https://forums.unrealengine.com/t/locked-out-of-using-ue5-because-visual-studio-2022-community-is-not-available-anymore/2675624 "2025-11-16T16:49:45Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Slipbit](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Slipbit](https://forums.unrealengine.com/u/Slipbit)\
**Post date:** [January 1, 2026, 4:30pm UTC](https://forums.unrealengine.com/t/locked-out-of-using-ue5-because-visual-studio-2022-community-is-not-available-anymore/2675624/8 "2026-01-01T16:30:46Z")

</div>

I got the Visual Studio 2022 tool-chain to work in Visual Studio 2026 “Insiders” edition:

> [@UE5.6.1 with Visual Studio 2026 bug and hack.](https://forums.unrealengine.com/t/ue5-6-1-with-visual-studio-2026-bug-and-hack/2688792):
>
> Just upgraded to Win11 and was presented with no options for VS-2022 (would have waited if I had known.) So this is what I did to get my UE5.6.1 project to compile successfully using VS-2026. Major breaking errors encountered: Tough one, burnt quite a bit of time - it’s a BUG \>\>\> UE5.vcxproj : warning : The build tools for Visual Studio 2022 (v143) cannot be found. Install Visual Studio 2022 (v143) to build using the Visual Studio 2022 (v143) build tools: a) REQUIRED Insiders version: Inst…

Have to agree with [@Rawalanche](https://dev.epicgames.com/community/api/user_profiles/tab-redirect/about?discourse_username=Rawalanche), Microsoft has us dancing on ice all the time; Does the VS2026 Insiders edition break (they randomly do) before they publish the bug fix for the general release version? Forcing a, obviously, poorly tested IDE that doesn’t recognize it’s own installed build-chains (the supposed bug) onto their user base shows where the quality is heading… They could have actually waited until mid-2026 and done more QA (or at least unit tests using their own build tools which would have exposed the failures) and/or made 2022 easily available in the MS Store for those not able to use the lone “Happy Path” tool-chain available in v2026.

Hunting for alternatives when the ice breaks is an unacceptable waste of time. Wasted time installing/uninstalling v2026 and it’s components, before wasting more time researching, only to find it had a bug and would never work. Wasted more time looking for a valid v2022. Repeated the wasted time installing/uninstalling v2026 “Insider” edition components until I realized it was broken, as well; I found a simple hack for it, though. Burned over a day…

---

_[View the full topic](https://forums.unrealengine.com/t/locked-out-of-using-ue5-because-visual-studio-2022-community-is-not-available-anymore/2675624)._
