I've never ran into this, but Server 2012 R2 x64 is obviously new in our environment.
I have the latest beta installed (and also tried 7.1.4, but no older than that) on my system and this MAY be due to some of the strict security standards we have, but I ran into a permissions issue with the 'VC-Settings.zip' file being automatically saved via the daily backup task.
Backup File / Default Path: C:\Program Files (x86)\VisualCron\backup\VC-Settings.zip'
As far as I can tell, the VisualCron Service, running as the 'LOCAL SYSTEM' account, temporarily writes the backup/export data to C:\Windows\TEMP\VisualCron\
C:\Windows\TEMP\ is not where i have my TMP and TEMP environment variables set on the system, so it must be hardcoded to use the %windir%\Temp\VisualCron path.
The problem is, My Id (even though i'm domain admin/local admin) for whatever reason didn't have permission to C:\Windows\TEMP\VisualCron\ so when the temporary backup/export data is written there, and presumably moved into the Default Path of C:\Program Files (x86)\VisualCron\backup, The VC-Settings.zip file inherited the permissions of the C:\Windows\TEMP\VisualCron\ folder, which meant I could no use the zip file to restore data. I easily overcame this by taking ownership of the file. And ultimately gave myself permissions to c:\Windows\TEMP\ and all subfolders.
I was curious if anyone else had ran into this. I only have the one system that is running 2012 R2 that I can test on that is not 'in production' and those are running the VC service as a domain service account, not Local System... so it's not a valid test (i don't have the problem on those).
I guess what i'm wondering is, would it not be better to write that sort of 'temp' data into a temp folder that VisualCron owns (such as in the Program Files\VisualCron\ directory, or is there a reason for the C:\Windows\Temp\ ?
I'm probably one of the only people that'll run into this, but it struck me as odd as it's the first time i've ran into it, and is something with our security in 2012 and nothing to do with VC itself, other than it writing using the local system (has permission) and then moving the file to a folder i 'should' have access to only now the file is locked down.
Brian