To those who are brave enough to get the leaked version of Windows 7 Beta 1 (Build 7000), DON’T USE your Windows Media Player 12 (built-in) to play your mp3 files!
The reason is because there’s a bug that may actually corrupt your mp3 files when you set Windows Media Player to automatically retrieve media information from the internet (or when you edit your mp3 tags). As a result, a few seconds at the beginning of your song may get corrupted/truncated because of the false meta data update.
This is a confirmed bug and will be addressed by Microsoft after the Beta has been officially released to the public. I think this should teach a lesson to us not to use a leaked version ever 
More discussions here on Neowin forum.
{ 11 comments… read them below or add one }
Thats not good! I might just wait for the full release to come out – without any bugs. What am I saying…microsoft always has bugs! haha
and I guess any other software in the world
Thank you very much for making aware of the Bug.. Btw First time at ur blog.. really enjoying here.. looking forward for interesting posts
Hey Nicholas, welcome
Just wished that I knew about the bug earlier. I think I played a few songs using WMP 12 and Windows 7 before O_o
I wonder sometimes if they leak it intentionally with a bug here or there just to see what mayhem it will create and to teach everyone a lesson.
Lucky for everyone they have you to find and post about any little problems that may arise.
Not too sure about that myself
I don’t think it’s intentional though as the public beta release would have the same bug (same build number)
Perhaps that is true, but it wouldn’t be too hard to leak a copy with the same build number but with a few intentional bugs in it just for a bit of fun. A disgruntled employee even?
Sire´s last blog post..Commenting 101 Important Rules For 2009
Thank’s God i still use winamp.
Thats really an awful bug!
Your PC Info´s last blog post..Software Review : Launchy v 2.1.2
It’s not as awful as it sounds. It does effect files on occasion but certainly shouldn’t take out your whole library.
Haha perhaps. Although I heard that the official copy (released to testers) also had this bug. So I guess it wasn’t intentional