Visual Studio 2022 Preview 1 now available!

We’re excited to announce that the first preview release of Visual Studio 2022 is ready to install! This is the first release of a 64-bit Visual Studio and we’d love for you to download it, try it out, and join us in shaping the next major release of Visual Studio with your feedback.

Our key goal with this preview is to test and tune the scalability of the new 64-bit platform! With the new 64-bit platform Visual Studio is now capable of scaling to make use of all the system resources you have to improve the reliability of Visual Studio especially when working with complex solutions or using Visual Studio over long periods of time. The 64-bit conversion effort affects every part of Visual Studio, so the scope is much bigger than our usual previews.

We know that you expect quality, stability, and scalability from Visual Studio. And to be totally transparent, the quickest way for us to get there is when real developers like you tell us where we can improve. We really do pay attention to every bug report, suggestion, and upvote! Which you can submit from inside Visual Studio via report a problem.

Report a problem with visual studio
Help us improve the quality and stability by reporting a problem within Visual Studio

The Visual Studio 2022 previews can be installed side-by-side with earlier versions of Visual Studio, are available in all three editions (Community, Pro, and Enterprise), and are free to use.

We need your feedback

We encourage you to try out the preview and use it just like Visual Studio 2019. We appreciate your time in providing feedback and completing in-product surveys, which are invaluable in making Visual Studio 2022 the best developer environment for you.

We would particularly love to hear about your experiences working with very large and complex solutions in Visual Studio 2022. Before the 64-bit upgrade, customers with this kind of solution would sometimes experience issues with Visual Studio as it ran out of memory to use in the main 32-bit process. During early testing of Visual Studio 2022, the same customers were able to run the IDE for days, even with solutions containing 700 (or more!) projects.

What’s coming

Because most of the Preview 1 upgrades have to do with 64-bit support, we’ll be releasing an exciting slate of new features and performance improvements starting in Preview 2. You can read all about those upcoming features on the Visual Studio roadmap. One new feature you can try right away is the update to IntelliCode – you can automatically complete code, up to a whole line at a time.

There’s still some work left in moving Visual Studio to 64-bit, and a small number of the features in Visual Studio 2019 are not included in Visual Studio 2022 Preview 1. You can find a list of those upcoming features in the release notes.

During the Visual Studio 2022 preview, our partners who build the extensions that you use and love will be working to update their extensions. While they do that, their extensions won’t be available in Visual Studio 2022 right away.

The first preview of Visual Studio 2022 for Mac will be coming soon, giving you a first look at the new modern macOS UI for Visual Studio. We still have some work to do before we feel it’s ready for developer feedback and we’ll keep you updated on its progress here on the Visual Studio blog.

Calling all extension authors

If you make extensions, we want to help you get your extensions into Visual Studio 2022. To get you started, check out our guide to migrating your extensions to Preview 1.

Also! This Friday, June 18, you can watch Mads Kristensen, a senior PM on the Visual Studio team, demonstrate how to update extensions for Visual Studio 2022. The livestream starts here at 3 p.m. Pacific time: https://youtu.be/-PKIPTW6km0

We’ll continue to share details with our extension authors and maintainers as we get closer to the official product release for Visual Studio 2022. If you have any thoughts about how we can make this process better, you can share your thoughts on this short survey.

Help shape Visual Studio 2022

Take part in shaping Visual Studio 2022 by installing it, using it, taking part in surveys, and sharing your thoughts on Developer Community.

70 comments

Comments are closed. Login to edit/delete your existing comments

  • Piotr Karczmarz

    This was quick! The first announcement about public VS 2022 Preview mentioned the summer but I wasn’t expecting anything earlier than July/August. Impressive! Downloading starts now … !


    Piotr Karczmarz, CTO at ContextKeeper.io, building VS plugin allowing to instant jump to deep work via “mental snapshots”.

    • Justin JohnsonMicrosoft employee

      The team has been working hard on the conversion process! Thanks for your comment and I hope you enjoy the first preview of VS 2022.

      • Piotr Karczmarz

        I must say I’m really impressed by the quality of the VS 2022 Preview build and how smooth VSIX porting experience was. It simply worked out of the box despite the fact that ContextKeeper uses a lot of internal VS APIs to do its magic and I was prepared for long days and hours to port it to VS 2022. Wow!


        Piotr Karczmarz, CTO at ContextKeeper.io, building VS plugin allowing to instant jump to deep work via “mental snapshots”.

  • Praveen Potturu

    Nice to see this ready to try but bad that I don’t have hard drive space to install it.

  • Federico Berasategui

    Please Microsoft, Please, get rid of the horrendous XML abomination required to define new buttons/commands in Visual Studio’s Menu. Or keep it abstracted underneath if really needed, but please don’t shove it down our (extension authors’) throats. Give us a sane, easy to use, understandable, discoverable, statically typed, intellisense-enabled C# API instead.

    Also: Why am I still paying for MyGet? might seem like no big deal from your perspective, but for small software companies in third world countries, it’s an additional burdensome cost. Please allow me to host my own private VSIX feed on Azure Devops Artifacts, just like I’m using it for Nuget packages.

    • Piotr Karczmarz

      100% I share similar feelings. Adding a context menu or something as simple as command button to a tool windows is such a pain. Thousands of groups, parents, guids, symbols etc. to make simple button or command entry. And there is no way to debug it, you could only run it and pray that will work. Definilty huge pain point for VSIX developers.


      Piotr Karczmarz, CTO at ContextKeeper.io, building VS plugin allowing to instant jump to deep work via “mental snapshots”.

      • Leslie RichardsonMicrosoft employee

        Thanks for your feedback! We are currently working on improving the command definition experience via our new, upcoming extensibility model and Mads Kristensen’s upcoming VS SDK Community Toolkit. We will share additional info about both projects in the near future.

  • Daniel Smith

    Wow, I’m really impressed! I’ve been testing various project types, and loading all my existing solutions, and everything just works.

    Honestly, I was expecting some older project types to be missing, legacy designers to be broken etc. but I’ve not hit a single issue so far.

    Congrats to the team for all the hard work porting to 64-bit, and delivering a super high quality 1st preview release. It looks like you’ve got a really solid foundation, and I’m looking forward to see how things progress before RTM.

    • Ahmed Hemdan

      I did the same and it was impressive. Have you tried creating a new project using VS 2022, it wasn’t able to do that also it broke all other VS 2019 versions I have.

      • Daniel Smith

        I’ve created numerous new projects in VS2022 and they’ve all worked perfectly so far e.g. WinForms (both Framework 4.8 and .NET 6), console apps, ASP.NET Core Web apps, Blazor Server, etc. What type of project were you having trouble with?

        My VS2019 instance wasn’t affected at all by the VS2022 installation. Sounds like you’ve maybe got a corrupt installation. Maybe worth uninstalling both products, and then try a fresh install?

  • Jeremy Morton

    As a former Builder in DevDiv, I didn’t know if I would ever see the day where a 64-bit devenv.exe would be released; the amount of work, both on the product itself, and then getting the ecosystem to support it, was always daunting.

    I like to think that, somewhere, Dave Cutler is smiling.

  • Huo Yaoyuan

    Please, don’t always change the icon at major version. Only change it when the design is updated.
    The minor change that make it distinguishable with previous version often make the good design worse. Distinguishing versions by icon shouldn’t be a good request, as different SKUs of the same version can already be installed side by side.