whenever there is an update in visual studio this error occurs and after updating the visual studio it is fine, is there any permanent fix?
