Update tags will save database values to the files, so yes, it's the appropriate fix.

Aha!! Thought so. So my game plan is to (1) eliminate the read only check marks to the MMW5 folders then (2) back in MMW5, Edit Tags/Update tags. Let me know IF I'm on the wrong track.

You're correct that MediaMonkey can't tag read-only files. If File Explorer shows read-only for your files, you'll need to fix this in File Explorer. You may want to do an online search to troubleshoot this.

Thanks to all for the suggestions, but I still have the subject problem. The new MMW5 Beta Version didn't help. Having 9 gigs this month, I had no choice but to give up on using the Desktop version to do the heavy work - but - that's where all 1800+ files are located, all with read-only property (can't get unchecking this to stick), so when I transfer a file from Desktop to Laptop, that property stays with the file, perhaps contributing to my inability to "Edit Tags". I still feel it's a permissions issue, but am clueless on how to proceed after all the things I've tried. Doesn't anybody else have this problem?

After making sure both paths are identical,
1. is "reassigning Path" the same as "re-assigning Drive"?
2. And on which device: Desktop or Laptop?

Thanks.

Moving between devices will always require re-assigning drive as the driveID has changed (unless you change the driveIDs to be the same).

But, if both devices use C:\User\tsoca\Music as Path, you only need to re-assign Path, which is better than Locate Moved/Missing Files as that needs to match each file, whereas re-assign just fixes the driveID, and all files work.

I'm tempted to take the easy way out (no migration) and do all the MM5 work on the Laptop. But first I have a question on the other option: both devices using the same paths. My Laptop stores all music files on C:\User\tsoca\Music and its subfolders. If I move the music files on my Desktop from its current path (C:\User\Tom\Music) to the exact Laptop path above, I can skip the "re-assign drive" step. Correct? If not, which device would need drive re-assigning -- Desktop or Laptop? Please help me understand the process. Thanks for your help.

No migration is the easiest, next easiest is where both devices use the same Paths. The worst option of the 3 is where Paths differ.

You can capture the Locate Moved/Missing Files missing the 25 files in a debug log (step 4b) and attach the log to a Support Ticket: https://www.mediamonkey.com/forum/viewtopic.php?t=86643 For debugging it may be easiest if the log captures Locate Moved/Missing Files on just those 25 files not found.

The paths on the Desktop and the Laptop are definitely not the same, leaving re-assigning drive not a viable option. I've installed the new debug Beta version on both PCs, but reading thru the Debug material has me totally confused -- I'm a musician not a technician. What I'm still very confused about when using Locate Moved/Missing...is that of 1800+ music files, only about 25 files end up with drive "name" instead of the Drive letter (C:/).

Wouldn't a much simpler solution be to abandon the Desktop-to-Laptop transfer technique, use the L/T's keyboard
or purchase an external keyboard for the Laptop, do all the new files and updates, etc. on the Laptop, with no transfer or migration needed?

The easiest is to use the exact same Paths (drive letter excluded), so you just re-assign drive.

If you can't, please capture the failure of Locate Moved/Missing Files to match those couple files in a debug log (step 4b) and attach the log to a Support Ticket: https://www.mediamonkey.com/forum/viewtopic.php?t=86643

Yes, both Desktop and Laptop have new 2024 Beta. Paths are indeed slightly different, leading me to wonder, if instead of re-assigning drive, I simply create the correct matching path on the Desktop, and move all media files to the new path. Then Locate Moved/Missing... on the Desktop.

Does laptop also have latest 2024?

Anyway, are the Paths different, if not, you should re=assign drive instead of Locate Moved/Missing Files.

More on migrating: https://www.mediamonkey.com/wiki/index. ... w_computer

Sorry Lowlander, but I gave you incorrect information. After executing the latest 2024 beta on my “working PC” (Desktop), I added a few new files and some updated files, ran Add/Rescan, and found every file in my library had the correct path (C:\User\tsoca\Music\filename.flac). So I did not run the Edit Tags tool.

I then copied the Desktop’s MM5.db to my “gig PC” Laptop plus the same aforementioned new and updated files, ran the Locate Missing Files tool, and found 19 files (out of a total of 1,860) had an incorrect path:
[0A31-490D]\Users\Tom\Music\filename.flac. (Don’t know if it makes a difference, but notice the difference in the User’s name – Tom vs tsoca on every Library file).

I checked the Properties of a “bad” file vs a “good” file using explorer and found no differences, such as read-only (not checked). Back to the Desktop, I ran the Edit Tags tool, and to my surprise, every file in the Library threw the error “Tag Update Failed; file not accessible.” If it’s a permission issue on the Laptop, why are only 1% of the files affected?

As I mentioned in a previous post, I can edit the Laptop path properties manually, but that’s getting tedious every time I add or modify a file.

Bingo! Edit tags executed flawlessly on all 1800+ files on my Desktop; or at the least, no errors were reported. I'll try it out on my Laptop next -- that's my "working gig" PC -- and will report any abnormalities. Thanks, L.

Can't hurt to try it! I'll give it a shot and report back.