# Mp3tag Not Able to Access Track

**URL:** https://community.mp3tag.de/t/mp3tag-not-able-to-access-track/49583
**Category:** Support
**Created:** [July 11, 2020, 3:53am UTC](https://community.mp3tag.de/t/mp3tag-not-able-to-access-track/49583 "2020-07-11T03:53:48Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### 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: [July 11, 2020, 6:50am UTC](https://community.mp3tag.de/t/mp3tag-not-able-to-access-track/49583/3 "2020-07-11T06:50:23Z")

</div>

> [@YinzerRuss](#):
>
> I've tried fiddling around with a couple things

Which were? If you had told us what you did, we would not recommend the same thing again.

The warning is usually issued by the OS that the file is blocked - which is usually caused by another program. You would have to investigate which one that could be and avoid it.

Another cause could be esp. with downloaded files, that the file is corrupt. Check it with the linked utilities:

> [@How to check files for errors?](https://community.mp3tag.de/t/how-to-check-files-for-errors/44633):
>
> It’s required and often helps to reduce support cycles to check files for errors before filing a bug report. Symptoms of erroneous files are often missing or wrong bitrate or length audible blips or skips tags seem to be sticky and cannot be removed There are some really good tools to check the files for errors, namely MP3 Diags — identifies many different issues in MP3 files Website: [http://mp3diags.sourceforge.net](http://mp3diags.sourceforge.net) Download: [MP3 Diags - Getting MP3 Diags](http://mp3diags.sourceforge.net/010_getting_the_program.html#binWindows) If the font size in MP3 Diags is …

---

_[View the full topic](https://community.mp3tag.de/t/mp3tag-not-able-to-access-track/49583)._
