However, the previous app appears to have exited with a clean success code. Google tells me that 1618 means that another instance of msiexec is already running/another install is in progress. We traced back through the logs, and found that, in the AppEnforce.log, it was always failing on a specific app, giving the 0x80070652 error and informing us that the app was exiting with code 1618. For the record, nothing has changed on the SCCM servers, the OSD Task Sequence, or any of the software which it is deploying. However, over the last 2 days, around 50% of machines have begun failing to complete the OSD Task Sequence. Our deployment department images/re-images around 130 machines in any given day. I don't think this is what you are looking for, but here is another link, just in case.Got a really strange one here. Also, the user was asking for a 30fps video but it should work for 25fps. I'm pretty sure that the sentence I took the liberty of making bold, is the answer.

To make a 30fps project, go back to the projects-browser (by clicking the arrow icon in the lower right corner), and fill in the details at the top. So if you're in a 25fps project, the available playback rates will be 25 & 50. Once you enter that project/room you can then change the output rate in that project using the setting you describe on the project-card. This governs the frame-rate that all your edits are created at in that project. You choose the project-rate when you first create your project from the projects browser (the window that you see when you first run up the app). I haven't used LightWorks recently or extensively, and I am not sure how the whole EyeFrame converter works, but if you want to change your output frame-rate, I think this link will help.

Lightworks error code 1618