GeezerVison is showing github.com — “Could not write to temporary directory” in the Contribution Manager when BitDefender is installed · Issue #4757 · processing/processing
“Could not write to temporary directory” in the Contribution Manager when BitDefender is installed #4757DescriptionHi.
Downloaded Processing 3.2.3 copied the files to:
C:\Program Files\Processing\processing-3.2.3
The Documents folder is located at:
D:\Users\<user-name>\Documents\Processing
When I try to download a module or library I get the following error: Could Not Write To Temporary Directory

Restarting processing makes no difference, neither does a system restart. ActivityForge-Media commented on Nov 8, 2017 benfry commented on Nov 9, 2017 Open a command prompt and type ECHO %TEMP%. That'll print out a location on your machine. Go find that directory and make sure that you have permissions to write to it. Sometimes weird things happen on Windows where you get locked out of your own folders. Forge-Media commented on Nov 21, 2017 Bitdefender...
Safe Files & Application Access Module, causing this problem. benfry commented on Nov 26, 2017 Very odd… why would it be complaining about a folder created by Processing, though? (We do all the temporary files inside the sketchbook folder to avoid this kind of problem.) AyakaKouyama commented on Jul 9, 2018 Wow Bitdefender =_= Had same issue thanks :D dandylow commented on Jun 7, 2020 changed the title [-]Could Not Write To Temporary Directory [Win 10] [3.2.3][/-] [+]“Could not write to temporary directory” in the Contribution Manager when BitDefender is installed[/+] on Sep 23, 2020benfry commented on Sep 23, 2020 What's Bitdefender doing, though? We're writing a temporary file to the sketchbook folder there, it's not like it's a Windows system directory. hydra981 commented on May 13, 2022 might be really late now but I hope this helps
file > pref > sketchbook location > I removed OneDrive and works perfectly
C:\Users*\OneDrive\Documents\Processing
C:\Users*\Documents\Processing github-actions commented on Jul 15, 2026 This issue has been automatically closed and locked.
Processing 3.x is no longer actively developed. Since January 2020, development moved to the Processing 4 repository.
If this issue is still relevant to Processing 4, we'd love to hear from you. Please open a new issue at:
https://github.com/processing/processing4/issues/new/choose
Thank you for helping improve Processing. locked as resolved and limited conversation to collaborators on Jul 15, 2026
MetadataMetadataDevelopmentNo branches or pull requestsIssue actions
|