The problem seems to me to be that where Windows Update sees that a matching Visual Studio SKU is installed on the local machine, it attempts to apply the update. If you've installed it once, you shouldn't need to install it again to have it disappear from the list of patches to Radford - Following up via email.Īgain, please don't hesitate to contact me or Microsoft Support if you have problems with this patch (for more information regarding our support policies for security updates, please see the bulletin itself: ). I asked around a bit to determine the best set of steps to get into the stable and secure state, and a final installation of the patch is not required. To answer your question about applying this to multiple machines, the expectation is that the workaround steps are only required if, after a few days, the updated patch isn't automatically downloaded and applied. Hopefully it wasn't too painful restoring them? Hello again, - great to hear that our changes solved your nemo - I'm sorry to hear that the workaround erased some of your preferences - to be honest, I wasn't aware that this was a side effect of the steps I provided.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |