FAQ (WMP Tag Plus)
Is WMP Tag Plus compatible with my system?
WMP Tag Plus supports Windows Media Player 12 on Windows 7, Windows 8/8.1, and Windows 10.
The plug-in should also still work fine with Windows Media Player 11 on Windows Vista, but that combination isn't officially supported anymore.
Microsoft has added native FLAC support in Windows 10. This means that, in a default Windows 10 installation, WMP Tag Plus isn't used anymore by Windows Media Player for FLAC tags.
Unfortunately, Microsoft's native FLAC support has been proven to still contain some issues. For example, it doesn't recognize certain tags that are recognized by WMP Tag Plus and most other FLAC implementations. The first thing you should do when you come across such an issue, is report it via the Windows 10 feedback tool. That's the best way to urge Microsoft to fix their FLAC support.
Because of the issues with the native FLAC support, you can optionally force the use of WMP Tag Plus for FLAC on Windows 10, thereby giving you the same FLAC support as in earlier Windows versions. For this, you will need to disable the native FLAC support. See the next question for instructions on how to do this.
How do I disable Microsoft's native FLAC tag support in Windows 10?
First of all, make sure that you have the latest available version of WMP Tag Plus. Only versions 2.6 and newer support Windows 10.
Removing existing FLAC songs from the library
Warning: if you skip this step, there's a high risk that you will lose some of the tags in your FLAC files!
- In Windows Media Player's library, select
Musicon the left, and type
type:flacin the Search field.
- Select a single song, then press
Ctrl+Ato select all songs.
- Right-click the selection and select
Delete from library only, then click
- Close Windows Media Player.
Disabling the native FLAC tag support
This will not only disable the native FLAC tag support in Windows Media Player, but also in Windows Explorer. It's not possible to disable the support for Windows Media Player and leave it enabled for Explorer at the same time. However, if you're experiencing issues with FLAC tags in Windows Media Player, then you will very likely see the same issues in Explorer, so there's not much point in leaving it enabled in the latter anyway.
- Create a system restore point, just in case things get messed up.
- Launch the Registry Editor: press
regedit, and press
- Navigate to the registry key
- Select the
Del, and click
- 64-bit Windows only: repeat the previous step for the registry key
- Navigate to the registry key
- Right-click the
SystemPropertyHandlerskey in the tree, select
Permissions, and click
- Click the
Changelink next to
Administratorsas the object name, and click
- In the existing Permission entries, select the
- Tick the
Full Controlbox, then click
OKthree times so that you're back in the main Registry Editor window.
- Select the
Del, and click
- 64-bit Windows only: repeat steps 7-11 for the registry key
- Close the Registry Editor, and restart Windows for the changes to take effect.
Adding FLAC songs back to the library
- Launch Windows Media Player and make sure that WMP Tag Plus is ticked in the
Plug-insmenu, meaning that the plug-in is active (press
Ctrl+Mif you don't see the
- Make sure that the native FLAC tag support was successfully disabled. To do this, go to WMP Tag Plus settings (
WMP Tag Plus–
Properties). In the list of supported file extensions, the
Native supportcolumn should show
Nofor FLAC. Finally, close the WMP Tag Plus settings dialog again.
- To re-add the FLAC songs that were previously removed, go to
Restore deleted library items, and click
Undoing your changes
If you want to enable the native FLAC tag support again, you can undo these changes by downloading and opening one of the following .zip files. Then unzip and open the included .reg file to import it into the registry:
After the .reg file has been successfully imported, remember to restart Windows for the changes to take effect.
Why aren't the tag changes that I make in Windows Media Player being written to file?
In more recent versions of Windows 10 (more specifically, since the April 2018 Update), there's a new setting in Windows Media Player called
Write media information changes to files. By default, this setting is turned off, which means that any tag changes made in Windows Media Player won't be written back to file. This applies to files in a format natively supported by Windows Media Player, as well as to files in a format supported through the WMP Tag Plus plug-in.
Because of this, it's highly recommended to manually turn this setting on before making any tag changes, otherwise you run the risk that the tags in Windows Media Player get out-of-sync with the tags embedded in the files. To do so, go to
Ctrl+M if you don't see the
Tools menu), tick the
Write media information changes to files box, and press
If you're running Windows 10, please check the section above first. For other versions of Windows, or in case the information above doesn't help, here's a list of more general items to check/try:
- Make sure that WMP Tag Plus is loaded in Windows Media Player: the plug-in should be listed in the
Plug-insmenu and should have a check-mark next to its name.
- Check if the file is in a format supported by WMP Tag Plus and if the tag support for that format is still enabled. To do so, go to WMP Tag Plus settings:
WMP Tag Plus–
Properties. On the
Extensionstab, make sure that the file's extension is present in the list of supported extensions. On the
Formatstab, find back the format in the list and make sure that it is ticked, meaning the format's tag support is enabled.
- Make sure that the file is present in the media library and that the
Lengthcolumn for the file isn't empty and shows the correct duration. WMP Tag Plus refuses to write any tag changes to a file whose duration isn't known in the library, because that usually means that the file has been added to the library while WMP Tag Plus wasn't active. In most cases, running
Refresh song tags(on the
Toolstab in WMP Tag Plus settings) will resolve these missing song durations.
- Instead of writing tag changes to file immediately, Windows Media Player usually does this at a later time in the background. You can force it to write any pending tag changes immediately by using the
Apply media information changescommand in the
- Make sure that the file isn't being held open by Windows Media Player or any other running application. While a file is being held open, no other programs can write changes to it, and WMP Tag Plus is no exception to this rule. The same applies when the file is marked as read-only. If you have the Windows Media Player Plus! plug-in installed, you can quickly check whether this is the case by using its Tag Editor Plus feature – the
Commentstab of this tag editor show a warning message if the file is being held open or marked as read-only.
- As a last measure, you can try editing the file's tags outside of Windows Media Player, in an external application. A good example of such an application is Mp3tag, which includes support for all formats that WMP Tag Plus supports.
What's the meaning of the setting “Prevent Windows Media Player from leaking memory while it reads album art from music files”?
In WMP Tag Plus version 2.7 and newer, if you go to the
Advanced tab of the plug-in's settings, there's a check box called
Prevent Windows Media Player from leaking memory while it reads album art from music files. This setting is there to control a fix in WMP Tag Plus for a bug in Windows Media Player 12.
A while back, the author of WMP Tag Plus discovered a rather serious issue in Windows Media Player 12. Whenever a music file containing album art is added to the library, Windows Media Player allocates a block of memory to read the album art into. That wouldn't be an issue if Windows Media Player would eventually free this memory block again, but it seems that this never happens. The result is a memory leak: a memory block that is wasted and not available for anything useful until Windows Media Player is closed again.
This issue can be reproduced pretty easily by embedding a large JPEG image as album art into an MP3 file (using for example Mp3tag), and repeatedly adding this same MP3 file to the media library and removing it again. You should see
wmplayer.exe's memory usage increase each time the file is added, without seeing the usage ever decrease again later. This can eventually lead to Windows Media Player exhausting all of its available memory space, especially when an empty library is initially filled with music files and many of the files have large album art embedded. When this exhaustion has occurred and Windows Media Player still tries to allocate some more memory, the program crashes with the dreaded
Windows Media Player has stopped working message.
Microsoft has already been notified of this bug a few years ago, but up until now, hasn't released any patch that fixes it. Even more striking, the same bug is still present in Windows Media Player 12 on Windows 10. Because of this, the author of WMP Tag Plus decided to take matters into his own hands and added some code to the plug-in that forces Windows Media Player to free the leaked memory block again after it has read album art.
The check box on the
Advanced tab can be used to enable or disable that piece of code in WMP Tag Plus. Usually you should leave it enabled, but a way to disable it was still provided just in case it causes any unforeseen issues (even though the fix has already been tested extensively). It's not necessary to disable the setting once Microsoft has fixed the bug in Windows Media Player. In that case the aforementioned piece of code in WMP Tag Plus just won't run and the setting won't have anymore effect.
There's no particular file type that's affected by this bug: all file types that Windows Media Player adds to its library and for which it reads album art are affected. The fix in WMP Tag Plus is independent of the file type as well. So the bug and its fix apply to file types natively supported by Windows Media Player (such as
.wma), as well as file types for which support is added by WMP Tag Plus (such as