Using VSCodium, when I edit a file I created then attempt to save it, I get an error saying Error: insufficient permissions, as in the following.
VSCodium is a version of Microsoft Visual Studio Code, a developer's editor. Whenever there is an update for VSCodium Norton blocks the update because not enough people use VSCodium. I managed to get it to update by trusting the install but there was a complication, I had to also delete a folder that is normally removed by the update. VSCodium however got updated but then when I tried to edit a file, I get the error. I have previously updated the file using VSCodium without a problem in the past. I am able to use Visual Studio Code to do the same update; it is only VSCodium that has the problem and it obviously is caused by Norton.
In the past I have uninstalled VSCodium and reinstalled it to get updates. Is there a way to fix the insufficient permissions problem following the update without having to uninstall and reinstall?
fwiw ~ often posted for developers => Exclude Xs 2
Sorry, I've no notion if "Items to Exclude" Xs 2 => Configure...will help your scenario.
Note: Data Protector exclusions are per process [info here].
As a developer, you need to create a master folder for all your projects. Then exclude that folder and all sub folders from Both items in the image below.
Note:
Disable Auto-Protect does not turn off Data Protector.
Disable Smart Firewall does not turn off Data Protector.
fwiw ~
I've needed to disable Data Protector to get known safe programs installed/updated.
Data Protector (may) objects to (unsigned) temp files created by installs/updates.
I posted an image. I do not understand what part of those instructions are relevant to me, since I obviously already know how to post images. Something that would help would be instructions for how to look in my Norton history. I assume I can figure that out but that is what would be more helpful than instructions on something I obviously already know how to do.
Hello. The screenshot you posted doesn't appear to be by Norton. Have a look in your Norton history for entries where Norton is blocking this. Please post those screenshots here for us to review. Here is how: