I ran into a small problem while upgrading Visual Studio 2022 to 17.14.0, so <a href="https://developercommunity.visualstudio.com/t/PackageId:MicrosoftVisualStudioCommuni/10906984#T-ND10907459" source="Visual Studio Developer Community">I reported it</a> with the following text, <bq>The Microsoft.VisualStudio.Community.MSI component could not be installed. At one point, the installer told me that another installer was running, but there wasn’t any installer running. An installer had run before the Visual Studio upgrade: JetBrains Rider. It’s possible that this interfered? I am unsure how this problem will affect my work. I don’t really use the MSI tools in Visual Studio (that I’m aware).</bq> I received a response relatively quickly, as follows. I have highlighted what I consider to be problematic passages that I addressed in my <bq>After reviewing the error you reported regarding the error with a VS Installer package. <b>Please make sure you have disabled any antivirus, group policies or firewall</b> that you may have on your machine as they sometimes avoid the installations. If they are disables and the error persists, please try the following: Step 1: Please go to this path: <c>C:\ProgramData\Microsoft\VisualStudio\Packages</c> Step 2: In the above path there should be a folder with the name <c>Microsoft.VisualStudio.Community.Msi;PackageAction</c>. Inside this folder there should be either a .msi or an .exe file, if there is and run it, if there is no .msi or .exe, please delete the folder. Step 3: Then go to the VS installer and if there is a <b>“More > Repair” option, select that. If it only shows the option “retry” please select that.</b> <img attachment="it_crowd_-_have_you_tried_turning_it_off_and_on_again.webp" align="right" caption="IT Crowd - Have you tried turning it off and on again?">Step 4: If that workaround was not successful then, <b>try to uninstall Visual Studio using the install cleanup tool</b> See: <a href="https://learn.microsoft.com/en-us/visualstudio/install/uninstall-visual-studio?view=vs-2022#remove-all-with-installcleanupexe">Remove all with InstallCleanup.exe</a>. (After you run the command form CMD, please delete the “Installer” folder from the following path and retry the installation: <c>C:\Program Files (x86)\Microsoft Visual Studio</c>) Please let me know if the solution worked for you! If not, we will continue investigating your issue. Let us know if there’s anything else I can help you with.</bq> I replied as follows: Thanks for you help. I've found the folder you described and run the installer. I also found the <c>More</c> => <c>Repair</c> option but elected not to execute it because it warns me that, <bq>Repairing will reset the environment. Local customizations like per-user extensions and your user settings will be removed. Your synchronized settings will be restored.</bq> I'm not so interested in getting rid of that ⚠️ icon in the VS installer that I'm going to take the time to re-install all of my extensions. I'll just wait for the next VS update to (hopefully) clean things up for me. For the same reason, I'm not going to reinstall VS unless something I actually use has stopped working. On a final note, I was somewhat surprised to see this advice: <bq>Please make sure you have <b>disabled any antivirus, group policies or firewall</b> that you may have on your machine as they sometimes avoid the installations.</bq> While I understand that Windows Defender can issue false positives, I'm not a fan of the advice "don't worry bro, our installer will work just fine once you disable all of the security on your machine." I mean, that sounds like something an actual scammer would say. No offense. On top of that, there are a lot of users (myself included) who work on machines configured by other organizations who do not have control over antivirus or firewall on our machines. I don't know what you mean by "disable group policies" because they are <i>legion</i> and cannot "all" be disabled. Thanks again for the detailed instructions. They worked as advertised. If I run into more problems, then I'll have to try the "Repair" option.