Network-Share: Access denied

[admin]

That didn't help. I also deinstalled hasleo, deleted remaining folders & files in program dir and restarted. Then fresh install - still the same. It also keeps my standard backup-folder after re-install. Seems I need to edit the registry to get rid of old/wrong stuff.

Can you create a new backup task to see if the issue still persists?

That's what I did. No change.

Edit:
I deinstalled now, deleted halseo in program-folder and deleted everything from registry containing "hasleo". After a new install it asked me again for the standard folder, my username and password, what it didn't do before. But next backup task ended like before with "access denied". I think I'll stay with my "old" Macrium Reflect.

This is weird, if the remote folder allows writes and the account has write access to this remote folder then this problem shouldn't happen, so please double-check them. And please add Hasleo Backup Suite (BackupMainUI.exe, BackupService.exe, BackupWorker.exe  and other .exe files) to the list of allowed applications (may be called Trusted Applications/Whitelisted applications) of your anti-virus software to see if the issue still persists?

If it still fails, please click "" > "Save log file" to open the save log file dialog, save the log file and then send it to us via email at [email protected].

Thanks.

My anti-virus software is the windows defender firewall. On the "hasleo"-machine I allowed all *.exe files living in bin folder, on the remote machine I disabled the firewall completely. No change - access denied.

What I didn't notice before: when hasleo asks me for the target, I can open the remote folder in question but it doesn't show me the present content. It shows the state before I did the test with macrium - an empty folder with only 2 hidden sytem folders ($RECYCLE.BIN and System Volume Information) in it.

I sent the log files.

You say “I can open the remote folder in question but it doesn't show me the present content.”, since the standard Open Windows File dialog is used here, this usually means that haven't set the access rights to the shared folder correctly. Please make sure that you have set the access rights correctly when setting up the shared folder, as shown in the screenshot below: