It looks like an old bug I had with cloud files (it was mostly OneDrive, once again...) and their permissions that was fixed on July 2018:
https://www.technibble.com/forums/t...-a-must-have-tool-for-techs.78308/post-647553
Those exports and reports are not processed the same way as user files so it looks like this issue still exists for them.
I'm installing a W10 Home machine with folders (Desktop, Documents and Pictures) redirected to OneDrive (gosh, I hate this !) to reproduce the issue and fix the problem. An update release will follow.
Edit: The issue I was talking about was with files belonging to user profile synced with OneDrive. In your current case, there's nothing I can do since these are items stored on "public" desktop in a first place. This explains why they have quite different permission settings and why OneDrive rejects them. Windows does not change permissions when moving them from a public folder to another one that belongs to user's desktop (or any One drive synced folder). A simple work around for this would to save logs and reports somewhere else so desktop remains "clean" from Fab's stuff. This can be defined in the autobackup.ini file.
Here's something that can be used :
Code:
[CONFIG]
LogStoragePath=%AutoBackupDrive%\LOGS
ReportsStorage=C:\Fabs_ExportsAndReports
LogStoragePath defines where logs will be stored for every job.
About ReportsStorage variable, make sure the path you set is always writable. If folder does not exists, Fab's will try to create it. If it fails, default paths will be used instead. Here, it could be something like C:\LOGS. Avoid any drive root like C:\ as Windows does not like this at all.
No Fab's update is needed as all of this is already handled.