EDIT SOLVED!:

The last problem seemed to be with permission, the thinbackup was not given admin privilege to run, running as administrator seems to have solved the issue. Thinbackup is now running a backup.

---------------

Thanks i tried this but it doesn't seem to work still.. I get the same error. I have uninstalled the ol 6.0 then installed the 5.1.4. Then done the rest you said with putting the folder in there, then have the thinbackup differ from the folder.

I also read the documentation on the SSL error but making that .reg file to fix it does not seem to work either.


Verifying virtual machine exists on server... Virtual machine located successfully.

Virtual Machine Guest OS: Microsoft Windows 10 (64-bit)

GuestOS property for W10 updated.

Validating license... License validated.

License:
- Type: Perpetual
- Status: Active
- Edition in Use: Standard

Checking for licensing issues... No licensing issues found.

Checking for feature usage issues... No feature usage issues found.

E-mail notification is not supported with Standard Edition licenses, e-mail notification disabled.

Backup Folder: C:\Backup\W10

Backup: 160801_182803

Log File: C:\Backup\W10\vBackup.log

Executing backup job...

Checking for existing temporary snapshot(s)... No temporary snapshots found.

Creating folder for backup data... Done.

Retrieving virtual machine ID... Virtual Machine ID: 2

Creating temporary snapshot... Done.

Obtaining reference to temporary snapshot... Done.

Temporary Snapshot: vBackup-TMP-160801_182803

Copying virtual machine configuration file... Done.

Checking for duplicate virtual disk file names... None found.

Copying virtual machine virtual disk file(s)...

VMware Virtual Disk Manager: VMware Virtual Disk Manager - build 2454786

Hard disk 1: [datastore1] W10_1/W10_1-000001.vmdk
Creating disk 'C:\Backup\W10\160801_182803\W10_1-000001.vmdk'

VMware Virtual Disk Manager response for Hard disk 1: [datastore1] W10_1/W10_1-000001.vmdk:
VixDiskLib: Invalid configuration file parameter. Failed to read configuration file.
SSL_IsVerifyEnabled: failed to open the product registry key. Falling back to default behavior: verification on. LastError = 0
SSL: Unknown SSL Error
SSL: connect failed
[NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: The remote host certificate has these problems:
* The host certificate chain is incomplete.
* Host name does not match the subject name(s) in certificate.
* unable to get local issuer certificate
Failed to convert disk: Cannot connect to the host (0x4650).

Tips:
- The 'VerifySSLCertificates' registry key is missing resulting in a default setting of 'SSL certificate verification enabled'. To resolve this, add the missing registry key (name: VerifySSLCertificates, type: REG_DWORD, value: disabled = 0|enabled = 1). For VMware Virtual Disk Development 5.1.x and earlier this key should be located in 'HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware Virtual Disk Development Kit'. For VMware Virtual Disk Development 5.5.x and later this key should be located in 'HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.\VMware Virtual Disk Development Kit'.
- SSL certificate verification is enabled and one or more errors were encountered while trying to verify the host server's certificate. To resolve this, add the missing registry key (setting it's value to 0) as indicated in the tip above or correct the certificate verification error(s) by installing a valid CA-signed certificate on your host server and installing a valid CA-signed root certificate on your vBackup server.

CRITICAL: Unable to verify successful transfer of virtual machine virtual disk file C:\Backup\W10\160801_182803\W10_1-000001.vmdk.

CRITICAL: Unable to complete backup.

Retrieving temporary snapshot ID... Snapshot ID: 13

Removing temporary snapshot... Done.

Cleaning up temporary files... Temporary files successfully removed.

Cleaning up after job failure... Done.