This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 19%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERR%3C/text%3E%3C/svg%3E)
Hello Team, I am currently working on a vulnerability fix for Visual Studio. I have enabled the administrative update registry key to allow patching via SCCM. I have Visual Studio 2022 product version 17.8.1 installed on my device. However, it is marked as not required for the security update (Visual Studio 2022 version 17.8.20 update), while it is marked as required for the update (Visual Studio 2022 version 17.13.6 update). I have concerns about the minor version. According to the Microsoft blog, the minor version will be released as a feature update. If I install version 17.13.6 on top of 17.8.1, what is the impact, and is it recommended?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 32%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMT%3C/text%3E%3C/svg%3E)
I'm not clear on what your actual question is. Are you asking if it is OK to update from VS 17.8.1 to 17.13.6? If so then yes it is fine. It is a minor version update. VS increments the minor version whenever there are significant new features to warrant it. In fact you should generally be on the latest minor update for all your VS installs (currently 17.13). Unless you have a specific scenario that breaks with the newer update (in which case you should report it to MS) then you should be keeping VS updated to the latest minor version.
Thanks for your response, my problem is,i have VS professional 2022 product version 17.8.1 , vulnerability detected and recommended to go 17.8.19 or later to fix it.So I am planning to deploy the latest security update 17.8.20 from sccm and the update 17.8.20 is marked as not required, I have already enabled the administratorupdateenabled =1 reg key based on the visual studio architecture. Is there any way to fix this issue and deploy 17.8.20 instead of going 17.13.x version since our developers not interested to go for 17.13.x for now.
I know nothing about SCCM so I cannot answer that question. AFAIK auto updates will go to the latest version. Not sure why you wouldn't do that since there are security updates in later minor versions as well.
The only thing I can see mentioned related to this is here where it mentions you can download the bootstrapper for the version you want and then run it. Perhaps with SCCM you can tell it to use the specific bootstrapper for the version you want. I've never tried that.