Opened this issue 9 months ago · 1 comments
Workaround: run the launcher as administrator.
Perhaps restart the launcher as administrator when this error is caught (Windows-only)?