If you could try one thing for me, it might help us get a better handle on this problem: Could you completely delete the. openshot_qt folder that's owned by Administrator, which will definitely prevent it from writing to that folder as a regular user.
The fact that running it as an admin succeeds would seem to confirm that, but it also may be making the problem worse: when run like that, OpenShot will create an. The only way that would fail is if your user account doesn't have permission to create folders in your own home dir. openshot_qt folder in your home directory should fix it, because OpenShot will automatically re-create that folder on startup.
Some of the other developers may have better testing resources, but since I don't have access to a Windows 10 system, I rely on affected users to provide information that might help us solve it.įrom #1319 (comment) The problem is that it's a permission problem on your local computer, which is not something we can easily fix.
Clearly that's not sufficient in some cases.) We believed that removing the settings directory should fix it, which is why that previous bug was closed. (It's not something that most Windows users experience at all, which is why we still haven't ascertained the exact cause of the issue. Which means that a bug in OpenShot could cause you to lose important data, or even prevent Windows from working at all.įor the security of your own system, please uncheck that box.Īnd if you're willing to work with us to find the problem, we can hopefully fix this properly. When started like that, OpenShot has access to modify every file on the system, even protected system files. It's also a configuration we can't support, as OpenShot was not meant to be run with admin privileges. but first, on the issue of running OpenShot as an administrator: That may succeed in getting OpenShot to run, but it is a dangerous workaround that I would urge anyone to avoid trying. I'll copy my comment from #1319 here, since that is a closed issue.
0 kommentar(er)
