• 0

Windows Media Player 11 Album Art Hell


Question

I'm using WMP 11 on Windows Vista and I'm having this problem with Album Art that is driving me insane... I've already searched a lot and couldn't find anything that could help me out.

I have all my album art embedded in the mp3 files, in the ID3 tags. This tag art is read just fine by WMP, Media Center and the Explorer, all of them get the album art from the file. However, every time I open up WMP, it starts creating those annoying Folder.jpg and AlbumArtSmall.jpg files inside each album folders and I really don't want that. First, cause it's resized to 200x200 and that sucks displaying in the Media Center for instance, mines are at 500x500. Second, cause I have a "Various" folder which has lots of different songs from different albums and artists, a folder with mixed content and if I have a those stupid WMP tiny art files there, then, in the WMP Library, all files that are inside that folder will have that stupid cover and not the embedded one.

How can I prevent this album art from ever being created by Windows Media Player.

I though of a solution, but I don't believe it's possible. For instance, to have Media Player, to always be executed and run with the permissions from a different user. Then, I would disallow write access to the whole Music folder. I can't use my account for that cause I need write access. WMP needed to run from a different user account, and this needed to happen from wherever I launch WMP, either shortcuts or directly through the exe. Is this even possible somehow?

I forgot to tell you one important thing... Yes, I have all those checks about "retrieve additional information from the internet" and things like that unticked... I believe there's only 2 in the Media Player options and they are both unticket. I don't understand why WMP keeps creating those art files...

Edited by Nazgulled

16 answers to this question

Recommended Posts

  • 0

ok here's what i did- same thing happened to me-

first with wmp closed go to the album folder then using folder options select 'show hidden files' and untick 'hide protected operating system files' then you will be able to see the corrupted album art, which you should remove at this point, i suggest you remove everything including the folder.jpg, then this step depends on how many files you have but i removed the write protection off the files and then the embedded album art from the .mp3's one by one, using wmp's 'advanced tag editor' can be done with any other id3tag app tho, then write protect them back. At this point you can go ahead and place your own album art in each album folder.

post-84490-1199653730.jpg

now i don't know if there's a way to stop windows from recreating those files but i'm gonna assume that there's not, because it needs it to display the album art, but also i know that wmp only does that when you retrieve the album art from the internets, not when you place your own folder.jpg on your folders. What i mean is that when wmp finds the album info but not the album art, [which only happens with obscure/foreign music] you can place you own folder.jpg and whatever size you want it, you'll be safe as long as wmp doesn't write the covers to the file, like when you drag a pic onto the album art placeholder in wmp.

Edited by takkun
  • 0

Sorry for floating an incredibly old thread... but after finding this in google I felt that I should reply to it.

It seems as though I have fixed this problem on my Vista machine by changing the permissions on my "Music" folder.

The process went as follows: right-click "music">>properties>>Security>>Edit. Highlight "SYSTEM" and on the list below, check "Deny" across from (for) "Write." Then click apply and ok for any messages that pop up.

So far this appears to work perfectly. You're welcome :)

Edit: This appears to be just stop the album art files from spawning while playing music. Manually editing the library appears to mess things up again. You might be able to stop that too by blocking yourself (and admins?) from write permission, but I don't know, I haven't tried. Good Luck.

Edited by b4andafter5
  • 0
Edit: This appears to be just stop the album art files from spawning while playing music. Manually editing the library appears to mess things up again. You might be able to stop that too by blocking yourself (and admins?) from write permission, but I don't know, I haven't tried. Good Luck.

What specifically happens when you edit the library? If I do this, can I still add music files to the music folder? If so, will they appear in the Library? Also, can I edit the ID3 tag info of my files? This problem has been bothering me for a while. I posted about this and another problem with WMP that are absolute show-stoppers for me a little while ago, but got no responses.

---

I think my biggest problem is that some real-life human being had to make a conscious decision to program WMP to behave like this. How could that person (or anyone else on the team, for that matter) not stop and think "hey, this is pretty stupid"?

My other complaint is that "Play All" is the default double-click action, rather than "Play". Once again, how could someone possibly not see how stupid that is?

Oh well, these problems still exist in WMP 12. Maybe version 13 will finally be usable.

  • 0

It look as though adding music to the folders or editing the tags does not affect it... when I did my fix, album art would respawn only when I removed files from the library. I think that items added automatically don't add the crap... I haven't thoroughly tested it, as you can see :p

  • 0

Thought I'd post this on here, as this is a very annoying issue and nobody seems to have posted a better solution.

If you have the correct album art in place, all saved as proper 500x500 images or whatever, and WMP keeps replacing these with those terrible 200x200 or 200x179 images, you can do the following:

1. ensure WMP is closed fully

2. add your folder.jpg files in the appropriate directories

3. run the following command at the root of your music directory

E:\Music> forfiles /S /M folder.jpg /C "cmd /c echo @file && attrib +r +s +h @file"

That will basically run through the whole music directory and hide and write-protect the folder images. Basically, when WMP loads that directory and tries to add its nasty low-res images to your music folder, it finds the folder.jpg is read-only, fails, and then doesn't bother creating the albumart*.jpg files either.

On a related note, the correct place for these images is in the ID3 tags embedded in the music itself; the excellent mp3tag is a great way to manage this.

  • 0

Thought I'd post this on here, as this is a very annoying issue and nobody seems to have posted a better solution.

If you have the correct album art in place, all saved as proper 500x500 images or whatever, and WMP keeps replacing these with those terrible 200x200 or 200x179 images, you can do the following:

1. ensure WMP is closed fully

2. add your folder.jpg files in the appropriate directories

3. run the following command at the root of your music directory

E:\Music> forfiles /S /M folder.jpg /C "cmd /c echo @file && attrib +r +s +h @file"

That will basically run through the whole music directory and hide and write-protect the folder images. Basically, when WMP loads that directory and tries to add its nasty low-res images to your music folder, it finds the folder.jpg is read-only, fails, and then doesn't bother creating the albumart*.jpg files either.

On a related note, the correct place for these images is in the ID3 tags embedded in the music itself; the excellent mp3tag is a great way to manage this.

Old thread is old, but good post is good! Reppy up! +

  • 0

3. run the following command at the root of your music directory

E:\Music> forfiles /S /M folder.jpg /C "cmd /c echo @file && attrib +r +s +h @file"

That will basically run through the whole music directory and hide and write-protect the folder images. Basically, when WMP loads that directory and tries to add its nasty low-res images to your music folder, it finds the folder.jpg is read-only, fails, and then doesn't bother creating the albumart*.jpg files either.

Not sure how to run a command at the root. Help a layman out.

  • 0

Not sure how to run a command at the root. Help a layman out.

The instructions are kinda broken. Folder.jpg and AlbumArtSmall.jpg are completely reserved filenames for WMP. You cannot safely nor sanely use those filenames for your own purposes. They will be overwritten. By default WMP creates those files system hidden, which was the initial clue long ago to not touch those files. Don't touch them: those are reserved filenames.

This:

* https://www.neowin.net/forum/topic/767036-wmp12-win7-7100-stop-wmp12-from-touching-folderjpg-files/page__st__60__p__591704002#entry591704002

is probably way way more interesting to you.

Again, those two filenames in particular are absolutely reserved filenames by WMP that there is no method whatsoever of overwriting WMP's perceived "ownership" of those two files. Those files get created when anything using the album art system asks for album art for the files in question. If both folder.jpg and albumartsmall.jpg already exist, they *usually* won't be recreated. But if they're not around and the album art system is asked for those images, they'll be recreated if possible. =\

  • 0

Funny thing, I was about to post a request about this very topic, but it appears I have been beat to the punch. On several places on the internet I have found a response to this question, but it requires modifying the registry. I am slightly retarded when it comes to messing with the registry. Is it possible that someone can interpret the following modification and turn it into an executable registry script so that making the change is fool proof? It is supposed to prevent WMP from creating any folder.jpg or albumart.jpg files.

[HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\Preferences]

"LargeAlbumArtSize"=dword:ffffffff

"SmallAlbumArtSize"=dword:ffffffff

Again, when it comes to the registry, I am slightly retarded, so your help is much appreciated.

  • 0

Funny thing, I was about to post a request about this very topic, but it appears I have been beat to the punch. On several places on the internet I have found a response to this question, but it requires modifying the registry. I am slightly retarded when it comes to messing with the registry. Is it possible that someone can interpret the following modification and turn it into an executable registry script so that making the change is fool proof? It is supposed to prevent WMP from creating any folder.jpg or albumart.jpg files.

[HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\Preferences]

"LargeAlbumArtSize"=dword:ffffffff

"SmallAlbumArtSize"=dword:ffffffff

Again, when it comes to the registry, I am slightly retarded, so your help is much appreciated.

No, that only affects the maximum dimensions of the files.

You cannot prevent WMP from creating any folder.jpg or albumartsmall.jpg files unless you hack your folder permissions or other such nonsense. If you don't like WMP's album art behavior, I would suggest not using it nor Media Center (which uses the same logic in part).

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Zed 1.7.2 has landed with updated OpenCode models, bug fixes and other improvements by David Uzondu Zed 1.7.2 recently landed on the stable release channel, bringing a host of AI-related features including automatic context compaction and settings-based skill management, along with other things like better Markdown preview rendering and custom git commands in the graph view. Starting with the AI stuff, the developers introduced "/compact", a command that basically summarizes your conversation history on demand. This tool prevents your active chat window from hitting token limits by compressing older parts of the dialogue into a brief overview. In addition to that, the team relocated skill management to the settings UI, improving how the application communicates errors regarding those skills, and updated the OpenCode model roster to support DeepSeek V4 Flash, MiniMax M3, Qwen 3.7 Plus, and Nemotron 3 Ultra Free. External agent users can also monitor context window cost metrics and delete individual sessions directly from their history. Right-clicking ref labels in the git graph now opens a context menu that runs different actions against selected targets, kind of how VS Code does it. Here are some of the bug fixes this new release brings: The active agent fails to auto-select when creating a new git worktree. A scrollbar unexpectedly appears on wrapped code blocks in the agent chat. Collapse indicators for project headers appear when performing sidebar searches. Bracketed ellipsis title prefixes fail to show the ellipsis icon properly. Project icons render incorrectly in the recent projects picker. Diff hunk controls appear inside non-editable commit view multibuffers. The software update button hangs indefinitely on the downloading stage. Restoring an agent terminal in a remote project triggers a sudden crash. Splitting a pane that contains an active commit view causes a crash. Linux Wayland freezes when trying to read the clipboard from laggy external apps. Zed is a "newish" code editor trying to break the massive stronghold VS Code has on the developer community. Funny enough, the editor was created by former GitHub employees who worked on the Atom text editor (which Microsoft killed in 2022, several years after it bought GitHub). The project officially hit version 1.0 back in April, introducing platform parity for Windows and Linux alongside deep support for DeepSeek-V4-Pro.
    • 26H2 absolutely will support ARM Windows just not on devices that came with 26H1. This is evident by the fact I am running 26H2, which on my MacBook Neo and Surface Pro 12 (inch), within a VM.
    • Mp3tag 3.35 by Razvan Serea Mp3tag is a powerful and yet easy-to-use tool to edit metadata (ID3, Vorbis Comments and APE) of common audio formats. It can rename files based on the tag information, replace characters or words from tags and filenames, import/export tag information, create playlists and more. The program supports online freedb database lookups for selected files, allowing you to automatically gather proper tag information for select files or CDs. Mp3tag supports the following audio formats: Advanced Audio Coding (aac) Free Lossless Audio Codec (flac) Monkeys Audio (ape) Mpeg Layer 3 (mp3) MPEG-4 (mp4 / m4a / m4b / iTunes compatible) Musepack (mpc) Ogg Vorbis (ogg) OptimFROG (ofr) OptimFROG DualStream (ofs) Speex (spx) Toms Audio Kompressor (tak) True Audio (tta) Windows Media Audio (wma) WavPack (wv) Mp3tag 3.35 changelog: This version introduces a new Files options page, enhanced toolbar customization, support for RF64 WAV files, improved Discogs and MusicBrainz tag sources, and many other improvements and fixes. See the Release Notes for more details. Download: Mp3tag 64-bit | 5.7 MB (Freeware) Download: Mp3tag 32-bit | 5.2 MB Link: Mp3tag Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • The FIFA World Cup is not US centric.
    • It’s amusing how Microsoft is pushing IT admins as if this was a major, game-changing update. In reality, it’s just an enablement package that bumps the build number, which is disappointing compared to the more substantial 22H2 and 24H2 releases. Technically, 25H2, 26H1, and the upcoming 26H2 are essentially the same, differing only in support schedules. They could have included the Windows K2 improvements here, but chose not to. The era of Windows being in the backburner continues, and this 26H2 release feels like an afterthought. Shame, Nadella, shame.
  • Recent Achievements

    • Week One Done
      AMV earned a badge
      Week One Done
    • One Month Later
      AMV earned a badge
      One Month Later
    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      523
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      78
    4. 4
      Steven P.
      72
    5. 5
      Michael Scrip
      71
  • Tell a friend

    Love Neowin? Tell a friend!