dakanji

Why would Refind be trying to write to anything on boot? It doesn't (apart from logging but this is not related to that). I took a closer look at things and it looks more like there might be an issue with your setup. rEFInd tries to open misc dirs with the DirIterOpen function while scanning for loaders. This is done with the EFI_FILE_MODE_READ attribute but for some reason, this appears to be denied on your setup and an EFI_WRITE_PROTECTED error returned. It's not like it is trying EFI_FILE_MODE_WRITE...

You could try setting the log_level config option in rEFInd to 0to disable logging. However, it could be that in the backend and unseen by users, the logging is actually always started (some items need logging before the config file is read) and that such logging is subsequently discarded if the log_level is found to be 0 when the config file is processed. If that is the case and the issue is related to logging, you might still get the issue. You could try the REL version of RefindPlus as it does...

You could try setting the log_level config option in rEFInd to 0to disable logging. However, it could be that in the backend and unseen by users, the logging is actually always started (some items need logging before the config file is read) and that such logging is subsequently discarded if the log_level is found to be 0 when the config file is processed. If that is the case and the issue is related to logging, you might still get the issue. You could try the REL version of RefindPlus as it does...

You could try setting the log_level config option in rEFInd to 0to disable logging. However, I it could be that in the backend and unseen by users, the logging is actually always started (some items need logging before the config file is read) and that such logging is subsequently discarded if the log_level is found to be 0 when the config file is processed. If that is the case and the issue is related to logging, you might still get the issue. You could try the REL version of RefindPlus as it does...

You could try setting the log_level config option in rEFInd to 0to disable logging. However, I think that in the backend and unseen by users, the logging is actually always started (some items need logging before the config file is read) and such logging is discarded if log_level is found to be 0 after the config file is processed. If that is the case and the issue is related to logging, you might still get the issue. You could try the REL version of RefindPlus as it does not create a log file at...

You could try setting the log_level config option in rEFInd to 0to disable logging. However, I think that in the backend and unseen by users, the logging is actually always started (some items need logging before the config files is read) and discarded if log_level is found to be 0 after the config file is processed. If that is the case and the issue is related to logging, you might still get the issue. You could try the REL version of RefindPlus as it does not create a log file at all.

My request was to replace the rEFInd efi with one from RefindPlus in whatever setup you used with the rEFInd efi to see whether you get the same result. Do you mean to say you since have found the issue you reported is actually because you tried to run without an ISO that that such an ISO is required or is it that the rEFInd setup is packaged in an ISO and you cannot change the efi without creating a new ISO?

My request was to replace the rEFInd efi with one from RefindPlus in whatever setup you used with the rEFInd efi to see whether you get the same result. Do you mean to say you since have found the issue you reported is actually because you tried to run without an ISO that that such an ISO is required?