Hi,
I’m on Windows 11, running n8n locally (no Docker). Since upgrading to n8n v2.6.4, I can no longer write files using the Read/Write Files from Disk node.
I’m trying to write to simple local paths like:
C:\n8n-files\test.js
C:\temp\n8n\test.js
The file may get created, but n8n fails when writing.
I already reinstalled n8n multiple times and the issue persists.
The output of read/write
The file “…txt” is not writable
The file was created but its identity does not match and cannot be written
What I tried
Created folders manually (e.g. C:\n8n-files, C:\temp\n8n)
Confirmed I can write manually in PowerShell to the same folder
Tried configuring file access restrictions via env vars
HI , thanks for your help !I actually already tested this configuration multiple times.
I tried setting:
and also tested writing specifically to:
Desktop
a specific folder on Desktop
even with / and without
In all cases the behavior is the same: the file may be created, but n8n returns: The file has changed and cannot be written.
I also verified that the environment variable is correctly loaded in n8n, so it seems not to be an env-loading issue.
I have already checked multiple community discussions, Reddit threads, and tried different suggestions (including Claude and GPT recommendations), but none of them fixed the issue on my local Windows setup (no Docker).
If this is a known Windows-specific limitation or a bug introduced in v2.x, I would really appreciate confirmation or any recommended workaround.
Also tested direct environment variable injection via PowerShell
Verified variables were correctly loaded (e.g., Execute Command node works when N8N_ALLOW_EXECUTE_COMMAND=true, confirming env variables are being read)
Result: variables are correctly read, but filesystem write still fails.
Permissions
Verified Windows folder permissions manually
Modified permissions using icacls to grant full control
Tested writing in:
user directories
root disk folders
temporary directories
Disabled Windows Defender temporarily
Confirmed files can be written manually via PowerShell in the same folders
Result: permissions appear correct and do not solve the issue.
Installation tests
Reinstalled n8n
Tested multiple environment setups
Confirmed npm environment variables are correctly configured
Verified that environment variables are accessible from inside n8n
Result: issue persists across reinstalls and configurations.
Current understanding
At this stage, it does not appear to be:
a Windows filesystem permission issue
a Windows Defender issue
an environment variable loading issue
a path configuration issue
Since:
environment variables are correctly read (confirmed via node behavior)
permissions were explicitly granted and tested
multiple folders were tested
reinstallations did not change behavior
This suggests the possibility of a Windows-specific filesystem handling issue or a bug related to N8N_RESTRICT_FILE_ACCESS_TO behavior on Windows local npm installations.
, to save yourself the headache, just go with Docker installation..