run2's Posts

Hi @julatoski  Do you have a direct link for the download, the link on the trial page doesn't seem to work? The version number on the webpage doesn't seem to be displayed correctly so maybe this is ... See more...
Hi @julatoski  Do you have a direct link for the download, the link on the trial page doesn't seem to work? The version number on the webpage doesn't seem to be displayed correctly so maybe this is the issue (see attached screenshot). Thanks again,
Hi @julatoski ,   As mentioned before, these were clean machines that never had the Agent installed only the Tools.   To close this thread out and for anyone who is having the same issue, our pac... See more...
Hi @julatoski ,   As mentioned before, these were clean machines that never had the Agent installed only the Tools.   To close this thread out and for anyone who is having the same issue, our packaging team investigated this issue and found that the driver in the Tools MSI is not correct.  It is different to the driver in the Agent package that does work, therefore the fix for us was to copy the driver from the Agent package into C:\Windows\System32 on the machine that has the Tools installed and then it works. Thanks,
Hi Jeff, Thanks for the reply, I can confirm that all of the machines used for testing are new machines which have never had App Volumes installed on them before.   You are correct, the svdriver i... See more...
Hi Jeff, Thanks for the reply, I can confirm that all of the machines used for testing are new machines which have never had App Volumes installed on them before.   You are correct, the svdriver is running on the working Win7 box and it is not running on any of the win10 boxes.   What is the process to get this working? I tried loading the driver manually from an administrative command prompt using the command 'fltmc load svdriver' but get an error message that "Windows cannot verify the digital signature for this file..." When I check the svdriver.sys file it does appear to be correctly signed until September 2021.   Thanks,
Hi All, We're just trying out AppVolumes but AppCapture doesn't seem to work on Windows 10 for me, running it from an elevated command prompt, logged on as administrator, UAC disabled. Have tried it... See more...
Hi All, We're just trying out AppVolumes but AppCapture doesn't seem to work on Windows 10 for me, running it from an elevated command prompt, logged on as administrator, UAC disabled. Have tried it on an ESXi hosted VM, Hyper-V VM, physical machine and it won't work on any of them!  The command I am using is appcapture.exe /new test, this works just fine on an ESXi hosted Win7 VM. Win10 version is 20H2 19042.928 AppVolumes version is 4.4.0 Appcapture version is 4.4.0.73 The VHD seems to be cloned and mounted successfully, I can see it in the filesystem and in the disk management MMC.  It gets as far as "INFO: waiting to become capture-ready:" but then times out after 300 seconds, with the following output: "ERROR: disk-identify event not signaled after 300 secs" "ERROR: program failed in install mode CmdNew (Error: 0x0)   Any advice would be great! Thanks,