"File in Use" When it Isn't

[phred]

Using 3.4.37755 P

I'm trying to edit (individually) two files using the Tag Editor. One I'm trying to edit lyrics. The other I'm changing the album artwork.
Upon saving I'm getting this error message

Code

1 - I'll Remember April.mp3  --  Z:\Oliver Jones\Festival International de Jazz de Montreal\
     The process cannot access the file because it is being used by another process. This file cannot be updated as another application has this file open at the same time.

After seeing this a couple of times, and knowing that no other process could be using the file, I rebooted Windows. And the error is still showing. It seems pretty unlikely another process is using the file when MB is the first thing I launched after the reboot.

MP3val doesn't indicate either file is corrupt and both files play fine in MB.

Does anyone have a clue as to what's going on here?

[hiccup]

, and knowing that no other process could be using the file,

You know-know, or you 'know'?
Have you verified with something like this?:
https://alternativeto.net/software/lockhunter/about/

[phred]

You know-know, or you 'know'?
Have you verified with something like this?:

Yes, I -know- know.
By using that exact tool.
So -there-   :-)

[phred]

Well ... I was able to re-rip the two files in question and then move them to where I wanted them. Initially I used Move to Organized Folder and allowed it to overwrite, but it wouldn't as the original was still "in use." Then I moved them and MB put a "_1" after the file name, so at that point they were in the correct directory. Unfortunately it was a real pain in the butt the delete the original files, but I did it. I had to reboot Windows in Safe Mode to delete them. And then back to MB to rename the file removing the "_1".

But I'd still like to know why this happened. [rhetorical]

[hiccup]

But I'd still like to know why this happened. [rhetorical]

Are these files on your local pc?
Or perhaps on a network drive?
Maybe something such as user file permissions playing a role?

[phred]

The problem files were on a NAS, with a mapped drive letter, which is where MB goes for all music files that have been moved to the library. Inbox files are on a local drive.

Permissions were/are fine on the NAS. Properties showed the files to be read/write.

I dunno ... I'm hoping I can forget about this so it doesn't keep me awake all night.

[hiccup]

The problem files were on a NAS, with a mapped drive letter,

A NAS has it's own OS and file system.
It could be that (due to e.g. changed configurations in the network somewhere) it has restricted write actions on files.
But if it only happens to one file between others in the same folder, copied there at the same time, that would be strange.
But if it happens, Windows resource manager (and lockhunter) probably won't be able to identify the cause/process because the file is not being blocked by any Windows related process.

[phred]

It could be that (due to e.g. changed configurations in the network somewhere) it has restricted write actions on files.

Both 'problem' files were part of an album that were added to the library many years ago. The other tracks of each album did not present a problem when updating the lyrics or artwork. The entire directory in which the music files live on the NAS is read/write.

For the record, I did sleep well last night and didn't think about this at all until you brought it up again.   
I do appreciate your trying to help me figure out why this happened, but there's no need to invest any more of either of our brain cells on this. There are always other issues (not MB related) I can work on.

[hiccup]

…but there's no need to invest any more of either of our brain cells on this.

At first glance I read 'either of your brain cells' ;-)
Phew.

I thought the information might be handy both as a possible explanation, and if you run into this again in the future.
Or when other users have the same issue and do a forum search for it.

[phred]

At first glance I read 'either of your brain cells' ;-)
Phew.

I suppose that could be the case for either of us.

I thought the information might be handy both as a possible explanation, and if you run into this again in the future.
Or when other users have the same issue and do a forum search for it.

Understood. But I'm fairly certain this is one of those uniquely phred issues. There have been so many of them lately.

[hiccup]

At first glance I read 'either of your brain cells' ;-)
Phew.

I suppose that could be the case for either of us.

And finally I know how it is to 'feel offended'.
Thanks for that.

[phred]

And finally I know how it is to 'feel offended'.
Thanks for that.

Happy to provide a needed service.