You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
EPERM, Permission denied when creating a backup #107
Since some update in May, backups won't work for my setup anymore. I already changed the backup folder from the user folder, but this didn't help. I get the following error:
A folder C:\my files\JoplinBackup\default\joplin_active_backup_job gets created an filled. There's also a notes.7z inside but no date folders containing the daily backup.
Please set the Log Level to Verbose and then upload the log, maybe I can see something in it.
The log should be stored in .config\joplin-desktop\cache\io.github.jackgruber.backup
Unfortunatly the log does not tell anymore than the initial error message, it just ends with it.
I'm a bit irritated by the "?" at the beginning of the path.
I mean the \\?\, was fine. It comes from the Node.js path...
Can you create on the in the command window the folder C:\my files\JoplinBackup\default\joplin_active_backup_job ?
Most of the time, this has to do with access issues because another process still has the folder locked, such as an antivirus program, Dropbox, ...
yes, I have no issues manually doing anything in the folders. Here's what the structure looks like after creating some test-folders:
In a somewhat desperate move I even gave write access to every user for every folder in the tree.
However, I found something odd: The folder "JoplinBackup" and all subfolders seem to be created with write protection for some reason. When I remove the flag I get "Fehler beim Ordner erstellen: ENOTEMPTY, Directory not empty" on the same directory, the flag gets set again and I get the same issue as before.
The read only box on the folder is ok. The folder doesn't know the attributes of all files and folders, so it displays this message.
This is indicated by the minus sign and the box that is not fully highlighted.
Please try creating a backup directly to c:\testbackup or something like that—it shouldn't contain any spaces or anything like that. Is the same thing happening here, too?
Is the C:\my files or some of the path a NTFS Hard Link/Junction?
What version of Windows do you have?
I'm seeing this issue as well, it seems related to the backup folder being shared with onedrive (even when always keep offline is enabled). I had it setup this way for a long time and it suddenly stopped working
It actually seems to create the folder and the files fine during the backup process (if I look in the folder while backup is happening, the active backup folder is created, the jex file is created, the plugins are copied), but fails to delete the active backup folder after which causes the error
Changing it to use a folder not shared by onedrive works
Activity
JackGruber commentedon Jun 23, 2026
Please set the Log Level to Verbose and then upload the log, maybe I can see something in it.
The log should be stored in .config\joplin-desktop\cache\io.github.jackgruber.backup
derhappy commentedon Jun 23, 2026
Unfortunatly the log does not tell anymore than the initial error message, it just ends with it.
I'm a bit irritated by the "?" at the beginning of the path.
Backup Log
JackGruber commentedon Jun 24, 2026
I mean the
\\?\, was fine. It comes from the Node.js path...Can you create on the in the command window the folder
C:\my files\JoplinBackup\default\joplin_active_backup_job?Most of the time, this has to do with access issues because another process still has the folder locked, such as an antivirus program, Dropbox, ...
derhappy commentedon Jun 24, 2026
yes, I have no issues manually doing anything in the folders. Here's what the structure looks like after creating some test-folders:
In a somewhat desperate move I even gave write access to every user for every folder in the tree.
However, I found something odd: The folder "JoplinBackup" and all subfolders seem to be created with write protection for some reason. When I remove the flag I get "Fehler beim Ordner erstellen: ENOTEMPTY, Directory not empty" on the same directory, the flag gets set again and I get the same issue as before.
JackGruber commentedon Jun 27, 2026
The read only box on the folder is ok. The folder doesn't know the attributes of all files and folders, so it displays this message.
This is indicated by the minus sign and the box that is not fully highlighted.
Please try creating a backup directly to c:\testbackup or something like that—it shouldn't contain any spaces or anything like that. Is the same thing happening here, too?
Is the
C:\my filesor some of the path a NTFS Hard Link/Junction?What version of Windows do you have?
bwat47 commentedon Aug 9, 2026
I'm seeing this issue as well, it seems related to the backup folder being shared with onedrive (even when always keep offline is enabled). I had it setup this way for a long time and it suddenly stopped working
It actually seems to create the folder and the files fine during the backup process (if I look in the folder while backup is happening, the active backup folder is created, the jex file is created, the plugins are copied), but fails to delete the active backup folder after which causes the error
Changing it to use a folder not shared by onedrive works