Tested after update to v 7.0.220 and confirmed fixed.
Cheers!

In case anyone else has similar issues, with support's assistance we've found the cause.. The problem is the periods in the bucket name - for some reason B4all v7 doesn't like them. Switching to dashes fixed it.
The reason for periods not working is being investigated further.

I've sent the log from the test job that I setup as it's significantly smaller (attempting to backup a couple of files as opposed to hundreds/thousands of files). Per email sent, I can provide the log for the actual backup - but the error and circumstances are exactly the same.

Loving v7 - but since upgrading all of my backups to Amazon S3 have stopped working. All were working fine in Backup4all v6.. Every run now ends with a failure per the below (bucket below isn't the actual one used) [14/10/2017 4:48:44 PM] Testing content of zip C:\Users\123\AppData\Local\Temp\Softla...

Never got around to trying any fixes out (once everything was setup, the huge delay only annoyed me when I had to manually go into the program to check/fix something - so out of sight out of mind - and the thought of potentially messing up my backups was too much to bear).. But my reason for posting...

@mattj7 - Thanks for the suggestions.. At least now I'm sure that the huge delay isn't normal. Do you mind posting roughly how long the program takes to launch for you? Not that I'm expecting mine to match yours exactly, but a ballpark figure would be handy. Unfortunately, Latest version - it is; SS...

First up, this is going to seem like a complaint. It's not - Backup4all Pro filled my requirements for a new backup solution, and I recently purchased it so I obviously like the software. This is more along the lines of "some observations from a new user". So far, my main issue with the app is start...