A very common problem is when a QVD file is accessed by multiple applications where one application is storing data into the QVD file while another application is attempting to write to it or read from it.
1. For concurrent reloads: Implement a retry script. This is a common and a safe solution to approach locked files to make sure that the process is finished by the system.
It will not unlock the file but will automate the detection process.
See article: During STORE command the File Save occasionally fails
2. If due to external process see article: Process Monitoring - How to find locked files and the processes locking them
3. Another point to check is the location of the QVD files, are they stored and accessed via a UNC path over the network ? Would this be causing delay in communication and therefore delay in writing the QVD files, as a result the files stay locked for longer.
4. There are powershell scripts that force the files to get unlocked such as: Get-SmbOpenFile / Close-SmbOpenFile but this is NOT supported and will be entirely the users responsibility to use as it may corrupt the QVD file while getting written.