temp.zip seems to be a file created by mylar then claimed it doesn't have permissions to - i am not sure what it is trying to do with it.

It's trying to create the temp.zip file in order to extract the metadata from the cbz file (it copies the .cbz file into the mylar cache and names it temp.zip).

So basically, either the user running Mylar doesn't have the full permissions to it's own cache directory, or the user running Mylar doesn't have the proper permissions to be able to copy the file from it's original location.

temp.zip seems to be a file created by mylar then claimed it doesn't have permissions to - i am not sure what it is trying to do with it.

It's trying to create the temp.zip file in order to extract the metadata from the cbz file (it copies the .cbz file into the mylar cache and names it temp.zip).

So basically, either the user running Mylar doesn't have the full permissions to it's own cache directory, or the user running Mylar doesn't have the proper permissions to be able to copy the file from it's original location.

Thanks for the response. That seems to match my interpretation as well, but how could that happen? More importantly how can I resolve?

How are you running Mylar and what user is logged in / actually running Mylar?

It's a straight-up permissions problem that's localized to your Windows installation - there's not much I can do on this side to fix things unfortunately.

What you need to do is make sure that the user that's running Mylar has proper permissions to the entire directory structure of Mylar. So if you installed Mylar as Administrator, but you're signed on using a non-administrator account - you're pretty much screwed in running things as is. You'd need to either wipe the install and install it as a non-administrator, or change the permissions for the entire mylar directory structure to allow the user to run things.

evilhero wrote:How are you running Mylar and what user is logged in / actually running Mylar?

It's a straight-up permissions problem that's localized to your Windows installation - there's not much I can do on this side to fix things unfortunately.

What you need to do is make sure that the user that's running Mylar has proper permissions to the entire directory structure of Mylar. So if you installed Mylar as Administrator, but you're signed on using a non-administrator account - you're pretty much screwed in running things as is. You'd need to either wipe the install and install it as a non-administrator, or change the permissions for the entire mylar directory structure to allow the user to run things.

I appreciate the detailed explanation. I am running Mylar as an administrator in Windows 10, and this is a new issue. In fact it worked less than a week ago and abruptly stopped working and started throwing this error. I will see if messing around with permissions could make a difference but again, logically - the user running Mylar would be the one creating the file, so that would also be the user trying to access the file. neither users, both as a function of the process.