To solve your issue just do the following:
- Start Menu > Run > dcomcnfg
- Expand Component Services, Computers, and My Computer.
- Right-click My Computer and click Properties on the pop-up menu > COM Security tab.
- Under Access Permission click Edit Default.
- From the Access Permissions dialog, add the "Network Service" account with Local Access allowed.
- Close all open dialogs.
- Start Backup Service under administrator account: go to Tools > Change Service Account, enter local -- administrator account name and password, click OK. The service will be restarted automatically.
- Restart the computer.

Yes, it's perfectly safe to use Explorer to do that. You simply need to make sure the folder path mirrors the original one on the new machine and then change the prefix(under advanced settings in cloud account menu). Then simply synchronize the repository via tools > options > repository and you're good to go.

In this case the software will simply try to work according to the schedule, so full/diff/tl backups will only happen when they are supposed to happen. Since you're using 2 machines to perform backups they will run backups independently of each other, which is actually a pretty safe strategy if you using 2 backup prefixes, so you can recover the needed data from either backup destination.

File name encryption is not yet available for Linux/Mac version of the software. Added you to the list of people to be notified when this feature becomes available.

Sorry, not sure I understand the use-case and the feature request itself. On what step do you want to perform the purge of the cloud data and what do you mean by " files that are no longer part of the latest backup "?

This functions as designed, if a folder is moved it will be recognized as a new one. You can use "delete files" that have been deleted locally" option to get rid of such data.

Our licenses are distributed on a per-computer basis. You can either activate the trial version or use the restore-only version for emergency restore operations.

Sorry, but this is a conscious design decision, the data can only be decrypted by our software. If installing the software for some reason is not an option and the workaround I suggested is also not acceptable then I'm afraid I can't help with that.

If your company's security rules are strict, then you won't be able to do that, but I guess that's an extremely rare case, since the backup software should already be approved by security admin in such situations to at least back up the data within your environment.
Such permissions for installation of software are easily obtainable even in big corporations with complex security systems.

As I mentioned previously, you can restore your data on any machine and then transfer the data via external HDD or a USB stick as a workaround.

Well, the data can only be restored via our software, but you can install the application on literally any machine with internet connection and then transfer it via USB stick, for example.
You would still need internet access to log in to B2, so installing the software wouldn't pose any security threats to your network environment.

You can install the software on any Windows device you want and then restore the data without any problems if you specify the correct encryption pass during the creation of a restore plan.

The best way to do that would be to set up 2 backup plans - one to local destination, and one to Google Cloud with 2 different retention policies and then schedule them accordingly. For local backup you can simply specify to keep only 1 version of each file, and for the cloud one just set it to keep 6 versions.
In one of the future updates it'll be possible to set up different retention policies for each destination in hybrid plans.

And one additional note regarding the plan configuration: I guess it would be better if one backup plan would use regular full diff tlog backups and the other would utilize "copy only" mode and fulls only. Otherwise you may end up with differential backups to cloud that belong to local full backups and tlog backups on both that are not contiguous.

Updating integration Hyper-V integration services is the first thing that comes to my mind. Then, of course, re-registering VSS on both the host and guest VM. You might also want to try schedule the backup to the time of manual start and see if the issue persists. Maybe the service is preoccupied with something else at the time of the backup.

Checking VSS event logs might also be a good idea.

In that case rescheduling the plans should help. Most likely either another plan or something else in the system is trying to utilize VSS in your system. Another possible reason is that something is wrong with VSS itself so you might want to re-register its core components.

It seems more than one backup program installed and running. If you have more than one backup program installed on your machine, disable all of the programs except for one and try run the backup job again.

Another possible reason is that previous VSS snapshot has not completed properly and is still running. Try to restart the Volume Shadow Copy service. You can do this by going to Start > Control Panel > Administrative Tools > Services: find Volume Shadow Copy and right click and select Restart.

This error can occur if several backup plans are trying to back up the same data and/or overlap in schedule when VSS is enabled.

Most likely there was a problem with starting/running backup service. The first thing to check is the service icon in the lower-left corner of the UI. You can start/stop it there. Difficult to say what caused the issue, since there shouldn't be problems like that even on Surface devices since Windows is still Windows.
Anyway, glad that it's working now. In cases like that you can send the logs for investigation to our support team via tools > diagnostic menu.

Currently the pause button only works for the whole queue and not for individual files. I've forwarded this info to our developers, we'll try to improve that in the future versions.

If you're referring to ticket #91073 then it's already been escalated to level 2 department. Currently I can only suggest to continue communication there, since this doesn't appear to be a simple issue that we can solve via forum discussion.

Thanks for the feature request and use-case explanation. Transferred that info to our devs for consideration.

It's on our road map and we'll try to push an update with this functionality as soon as possible, but there's no concrete ETA yet. Added you to the list of people to be notified upon the release of the feature.