# Updated comments are not actually updated in Explorer **URL:** \ **Category:** Support\ **Created:** [October 14, 2026, 6:28pm UTC](https://community.mp3tag.de/t/updated-comments-are-not-actually-updated-in-explorer/71963 "2026-10-14T18:28:58Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)\ **Post date:** [October 14, 2026, 7:54pm UTC](https://community.mp3tag.de/t/updated-comments-are-not-actually-updated-in-explorer/71963/6 "2026-10-14T19:54:38Z")
The comment field is somewhat special as it has a language token plus another specifier that allows further differentiation, e.g. there are fields like `COMMENT ITUNNORM` or `COMMENT ITUNPGAP` and so there could also be a field `COMMENT ID3V1 COMMENT`. MP3tag keeps these differentiated fields, see here: > [@\[X\] Blank comment should also delete ID3V1 COMMENT field](https://community.mp3tag.de/t/x-blank-comment-should-also-delete-id3v1-comment-field/8679): > > Hi, I just realized that the "\< blank \>" action in the "Comment" field does not remove "COMMENT ID3V1 COMMENT" fields as visible in the "Extended Tags" dialog for my MP3s. Due to its strange name, I'm not sure if this field is standard, but I would expect "Blank Comment" to blank any comment there is. So depending on that you may consider this a feature request instead of a bug report. Thanks. So any other application that can deal with multi-value fields should be satisfied to find several COMMENT fields. Explorer cannot. --- _[View the full topic](https://community.mp3tag.de/t/updated-comments-are-not-actually-updated-in-explorer/71963)._