# Cannot be opened for writing - Yet again

**URL:** https://community.mp3tag.de/t/cannot-be-opened-for-writing-yet-again/56154
**Category:** Support
**Created:** [February 1, 2022, 2:21am UTC](https://community.mp3tag.de/t/cannot-be-opened-for-writing-yet-again/56154 "2022-02-01T02:21:35Z")
**Posts on this page:** 1
**Showing post:** 20

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [February 2, 2022, 8:47am UTC](https://community.mp3tag.de/t/cannot-be-opened-for-writing-yet-again/56154/20 "2022-02-02T08:47:56Z")

</div>

I've analyzed the file and noticed that some of the RIFF chunks don't report valid sizes. This means that the file is malformed. I've also checked the file with [foobar2000's integrity checker](https://community.mp3tag.de/t/how-to-check-files-for-errors/44633) which reports

> Warning: Malformed or truncated chunk found at 1046548524 bytes, claimed length 12544 bytes, truncated to 2554 bytes

And to answer my question from above:

> [@Florian](#):
>
> Are common properties like length, bitrate, ... of these files displayed in Mp3tag's file list?

No, those are not displayed — which is an early indication of a problem with the file.

---

_[View the full topic](https://community.mp3tag.de/t/cannot-be-opened-for-writing-yet-again/56154)._