[BMPCC 6K FF] Angelbird CFexpress SE 1TB with OS 9.5

Hi everyone,

I’m using a BMPCC 6K FF (L-Mount), and after updating to Camera OS 9.5, both of my Angelbird AV PRO CFexpress SE Type B 1TB cards stopped working. The camera doesn’t recognize them — they don’t mount or show up in the media list.

However, external SSDs still work perfectly fine, so the issue seems limited to CFexpress media.

To verify, I downgraded back to Camera OS 8.3.2, and both CFexpress cards are working again without any problems.

Has anyone else experienced this issue with the 9.5 update? Hopefully Blackmagic can restore compatibility in a future update.

Thanks!

Have you updated the card to the latest firmware version?
I have the same card and mine works fine.

Have you updated the card to the latest firmware version?
I have the same card and mine works fine.

May I kindly ask when you updated the firmware on your card?
I have four cards purchased between January and February, and I’m experiencing the issue with all of them. Unless they came from an older stock, they should already have the latest firmware.

That said, I’ve just ordered the official Angelbird card reader, so I’ll soon be able to check the firmware version and apply any available updates.

I bought the 1TB card in November and had to do an update. The firmware is dated to September '23. I don't know, although the card is new, the installed firmware was not. Maybe they don't update at the factory? In addition I did format the card as ExFat.

Just did some more intense tests:
format internally - works
writing to 30min - works
deleting selected files - works

One more thing: I bought the CFexpress™ 2.0 version with 1785 MB/s, not the newer version with 3700 MB/s.

I bought the 1TB card in November and had to do an update. The firmware is dated to September '23. I don't know, although the card is new, the installed firmware was not. Maybe they don't update at the factory? In addition I did format the card as ExFat.

Just did some more intense tests:
format internally - works
writing to 30min - works
deleting selected files - works

One more thing: I bought the CFexpress™ 2.0 version with 1785 MB/s, not the newer version with 3700 MB/s.

Thanks so much for your help!
I also bought the x4 CFexpress™ 2.0 version with 1785 MB/s 1TB, so it’s interesting to hear that yours needed a firmware update despite being new.
I guess the only thing left for me to do is to check for updates as soon as the Angelbird CFexpress reader arrives.

You might want to compare when you get your reader:

Anglebird firmware version

Bildschirmfoto 2025-04-06 um 13.35.10.jpg (36.12 KiB) Viewed 11595 times

You might want to compare when you get your reader:

Bildschirmfoto 2025-04-06 um 13.35.10.jpg

You’ve been really kind, thank you so much!
I’ll definitely compare everything once I get the reader.

This bug/glitch (assuming its a bug or glitch) has be present since in the last two beta firmwares for the 6K FF.

If you want to check which version your card has you can use CrystalDiskInfo software (its free) that will tell your current version.

I have the AV PRO CFexpress B SE 512GB firmware version AVX2.15 and I have to use beta 8.6 for the card reader to recongise my card.

This issue has been reported multiple times to BM and nothing has been said or done yet.

Hi everyone,
I have 6 cards Angelbird AV PRO CFexpress SE Type B 512GB 1785mb/s. I bought 4 of them 15 months ago and bought 2 half a year ago. All cards work in the camera. I haven't updated the firmware.

In my opinion this seems to be a little too random. It would have been nice to see the production dates of the cards working/not working. Maybe Anglebird should be contacted for further information.

In my opinion this seems to be a little too random. It would have been nice to see the production dates of the cards working/not working. Maybe Anglebird should be contacted for further information.

That would be good, but I don't think its an Angelbird issue, if you downgrade the firmware to a previous version (in my case Beta 8.6) the cards are read fine with no issues. Its the BM updates that seem to break things.

I also can confirm that the CC 6K wont recognize my CFexpress Cards after the 9.5 Update.
I tried it with Angelbird, Lexar and a DIY one (M2 2230 SSD to CF), all of them have 2TB of storage each. none of them were recognized.
Only by inserting the cards into a CFexpress to USB C reader and plugging it into the cam makes them visible.

No problems before the update and after downgrading to Camera OS 8.6, all work fine again.
So there is some problem with the new OS unfortunately.

Update:
I’ve done further testing and can now confirm that the issue is not related to the CFexpress cards themselves, since all four of my Angelbird AV PRO CFexpress Type B 1TB cards are updated to the latest firmware (AVX2.15) and work perfectly on one of my two Blackmagic Cinema Camera 6K Full Frame units running firmware 9.5.

However, on the other camera, with the exact same firmware version (9.5), none of the CFexpress cards are recognized — regardless of how they’re formatted (exFAT or Mac OS Extended).
If I downgrade that camera back to firmware 8.3.1, the cards are detected and function normally again.

I also tried a full factory reset on the affected unit, but the problem remains.

So at this point, it seems clear that the issue is firmware-related, but somehow affects only certain hardware revisions of the camera.

Update:
I’ve done further testing and can now confirm that the issue is not related to the CFexpress cards themselves… So at this point, it seems clear that the issue is firmware-related, but somehow affects only certain hardware revisions of the camera.

Given the serial numbers on the cameras are now random, that makes it difficult to know if the camera that works is older or younger than the camera that doesn’t work. I’d call BMD Support to see if they have access to the date of manufacture for both cameras when you tell them the serial numbers. There may be a hardware ID that also can be used to infer older and younger manufacturing dates.

Update:
I’ve done further testing and can now confirm that the issue is not related to the CFexpress cards themselves… So at this point, it seems clear that the issue is firmware-related, but somehow affects only certain hardware revisions of the camera.

Given the serial numbers on the cameras are now random, that makes it difficult to know if the camera that works is older or younger than the camera that doesn’t work. I’d call BMD Support to see if they have access to the date of manufacture for both cameras when you tell them the serial numbers. There may be a hardware ID that also can be used to infer older and younger manufacturing dates.

Thank you for the advice.
I’ve already contacted BMD Support and provided both the serial number and the hardware ID of my cameras.
At this point, I really hope the issue will be resolved quickly and that I won’t be required to provide too many “proofs” like videos, screenshots, and so on….as that would just take valuable time away from my work.

My cf express card is not reading after the 9.5 update. I have an Angelbird AV Pro SE CF Express B 1TB. The card has been updated with the Angelbird card reader and was working before the update with my BMCC 6k.

So I don't think updating the card is going to to do it.

Hi,

Does anyone have any news about this issue ? I have the same problem and had to downgrade my BMCC 6k FF to 8.3.1 to get my Angelbird CF express to work.
Is this issue only with the Angelbird cards, or other CFexpress cards also ? Does anyone know ?

Thanks for the help,

Michael

I'm having the same problem, only firmware version 8.6 detects my AngelBird AV PRO SE 1TB card. I'm stuck with that firmware version.

I’ve already contacted BMD Support and provided both the serial number and the hardware ID of my cameras.

Do you have some answer?

I'm having the same problem, only firmware version 8.6 detects my AngelBird AV PRO SE 1TB card. I'm stuck with that firmware version.

I’ve already contacted BMD Support and provided both the serial number and the hardware ID of my cameras.

Do you have some answer?

Thanks for checking in — I’ve sent the camera to Blackmagic support following their RMA procedure.

I’ve documented two issues:
1. Some CFexpress Type B cards (Angelbird and Lexar, both supported) are not recognized in the internal slot,
2. Occasional system freezes during normal operation.

Blackmagic has confirmed that CFexpress compatibility is still under investigation, but hasn’t offered a fix or timeline.

I’ve requested a written statement about the current situation (in case the unit is returned unrepaired), which I would use to assert my warranty rights with the reseller.

I’ll keep this thread updated as soon as I hear back. If others are seeing similar behavior, it might help to share your experience too.

I just want to add my voice to this that I'm experiencing this on 9.5 with a Angelbird 1750mb/s SE 512gb card. Rolling back to 8.3.2 fixes this.

[Kristian Lam]

Hey guys, we are looking into this issue. Non of the cards in our labs (we pretty much have every) exhibit this issue so it's taking a bit longer to track down. It's looking more like a software issue than anything else.

Hey guys, we are looking into this issue. Non of the cards in our labs (we pretty much have every) exhibit this issue so it's taking a bit longer to track down. It's looking more like a software issue than anything else.

Thanks for the update!

Just to add — like I mentioned earlier, I have two BMCC6K FF cameras, both on firmware 9.5.

What’s weird is that only one of them has this issue with CFexpress cards (Angelbird and Lexar), while the other reads them just fine.

Also, on the affected camera, if I connect the same cards using an external CFexpress reader via the USB-C port, they’re detected correctly — which makes it even more puzzling.

So yeah, feels like some combination of firmware behavior and hardware tolerances, not just a card or software thing.

Hope this helps!

[Kristian Lam]

Do you mind listing down the serial numbers of both cameras? Even for the one that work. Every bit of data point will help speed this up.

Do you mind listing down the serial numbers of both cameras? Even for the one that work. Every bit of data point will help speed this up.

Sure, here are the serial numbers:
• Camera 1 (not working with CFexpress): S/N: 12483299
• Camera 2 (working fine with the same CFexpress cards): S/N: 12290429

Both running firmware 9.5.

I’m using the exact same CFexpress cards (Angelbird and Lexar) in both units, so we can definitely rule out a media-related hardware issue.

Let me know if I can share anything else!

Hi, I'm also having the same issue with these same cards after updating to 9.5. Serial number 12099647, just came back from repair for a faulty HDMI port and tried to import my LUTs using the 1TB Angelbird CFE card (which showed up fine on my laptop including all clips recorded prior to the update still on the card) but the card wasn't recognized by the camera. Please advise, we love the autofocus promise but this is a bummer, I'd hate to have to go back to external recording even if autofocus might be worth it!

Do you mind listing down the serial numbers of both cameras? Even for the one that work. Every bit of data point will help speed this up.

It gives me hope to know that Blackmagic is working on a fix.

I'm also sharing the SN of my camera with the same problem: 12090192

I'll keep an eye on this thread. Thanks

I contacted Blackmagic support through email. They got back to me for the serial number. The lady told me she will pass on the information to the product management team. She didn't mention any timeline or priority though.
So I'm curious...

Will keep an eye on this thread also

Hi all,

same problem with my 1TB cards. Blackmagic Support replied to me as well, requesting the serial number and a video of the behavior. I share both with them. I'll wait a bit to see if anything comes back.

@Kristian Lam: Would it be help if I'd send one of my cards that shows the behavior to you since you mentioned none of those in your lab show the issue? I'm willing to do that since I have two identical cards and can do without one of them for a reasonable time. If so, could you get back to me via a message to work out the details?

[Kristian Lam]

@Kristian Lam: Would it be help if I'd send one of my cards that shows the behavior to you since you mentioned none of those in your lab show the issue? I'm willing to do that since I have two identical cards and can do without one of them for a reasonable time. If so, could you get back to me via a message to work out the details?

Thanks for the offer. It may not be necessary at the moment but I'll keep that in mind.

[Kristian Lam]

Ok. I think we have a fix but we need to verify this as some of you guys have multiple cameras with some having issues and some not.

If you're keen to give us a hand in checking if the fix will allow the problematic card to be recognised on your camera, please send me a PM and I'll send you a link. This is strictly a test build only and not recommended for production.

Ok. I think we have a fix but we need to verify this as some of you guys have multiple cameras with some having issues and some not.

If you're keen to give us a hand in checking if the fix will allow the problematic card to be recognised on your camera, please send me a PM and I'll send you a link. This is strictly a test build only and not recommended for production.

Unfortunately, one of my two cameras (the one with the CFexpress issue) is currently at Blackmagic support, not only for the CF problem but also because of random freezes.
Therefore, I’m unable to test the firmware myself at the moment.

I have never been able to get my CFExpress cards to work on Beta firmware. On the last beta, 8.6 or 8.7 they would show up maybe 30% of the time. I'd have to toggle the camera on and off until the card was finally read. This became so unreliable I had to downgrade.

Ok. I think we have a fix but we need to verify this as some of you guys have multiple cameras with some having issues and some not.

If you're keen to give us a hand in checking if the fix will allow the problematic card to be recognised on your camera, please send me a PM and I'll send you a link. This is strictly a test build only and not recommended for production.

I sent you a message, even though I only have one camera (and that one's affected).

Ok. I think we have a fix but we need to verify this as some of you guys have multiple cameras with some having issues and some not.

If you're keen to give us a hand in checking if the fix will allow the problematic card to be recognised on your camera, please send me a PM and I'll send you a link. This is strictly a test build only and not recommended for production.

I sent you a message, even though I only have one camera (and that one's affected).

Same here.

Ok. I think we have a fix but we need to verify this as some of you guys have multiple cameras with some having issues and some not.

If you're keen to give us a hand in checking if the fix will allow the problematic card to be recognised on your camera, please send me a PM and I'll send you a link. This is strictly a test build only and not recommended for production.

Unfortunately, one of my two cameras (the one with the CFexpress issue) is currently at Blackmagic support, not only for the CF problem but also because of random freezes.
Therefore, I’m unable to test the firmware myself at the moment.

Same here!

Clearly caused by the 9.5 firmware beta. I regret updating. Ruined an entire shoot tonight because it was a live multicam, and now there's no master shot (it had started recording, then kept stopping by itself).

Auto-focus performed poorly anyway; should've waited; am rummaging now (for the first time ever for me) to figure out how to safely downgrade to the prior version.

Clearly caused by the 9.5 firmware beta. I regret updating. Ruined an entire shoot tonight because it was a live multicam, and now there's no master shot (it had started recording, then kept stopping by itself).

Auto-focus performed poorly anyway; should've waited; am rummaging now (for the first time ever for me) to figure out how to safely downgrade to the prior version.

Never use beta software during working session.
I know is late to tell you, but…
It Is a golden rule


Inviato dal mio iPhone utilizzando Tapatalk

I’m quite sure that the problem of cam cards support relay in the different way they use power of camera and sustain cards in the internal reader.

From first beta of new usb/support way there were troubles with internal and external supports, the same support that work fine with previous firmware, and that work with support that require less power to work (ssd data versus nvme).


Inviato dal mio iPhone utilizzando Tapatalk

Quick update: Blackmagic confirmed that they were able to replicate the CFexpress issue on my camera and resolved it by installing a beta firmware that is not yet publicly released.

While I appreciate the effort and communication, I'm not entirely comfortable with the idea of having a non-official firmware on a production camera — especially since the freeze issue is still being investigated.

I'll wait for the final assessment, but for now, the solution feels more like a workaround than a stable fix. I really hope BMD can offer an official firmware update soon that addresses both problems properly.

Quick update: Blackmagic confirmed that they were able to replicate the CFexpress issue on my camera and resolved it by installing a beta firmware that is not yet publicly released.

While I appreciate the effort and communication, I'm not entirely comfortable with the idea of having a non-official firmware on a production camera — especially since the freeze issue is still being investigated.

I'll wait for the final assessment, but for now, the solution feels more like a workaround than a stable fix. I really hope BMD can offer an official firmware update soon that addresses both problems properly.

Is 9.5 is half a beta, you have a problem downgrading to production firmware problem disappear.
If a newer beta solve it, it’s the right way of beta working : finding troubles and solve it.
Good if they found problems and solve it


Inviato dal mio iPhone utilizzando Tapatalk

Quick update: Blackmagic confirmed that they were able to replicate the CFexpress issue on my camera and resolved it by installing a beta firmware that is not yet publicly released.

While I appreciate the effort and communication, I'm not entirely comfortable with the idea of having a non-official firmware on a production camera — especially since the freeze issue is still being investigated.

I'll wait for the final assessment, but for now, the solution feels more like a workaround than a stable fix. I really hope BMD can offer an official firmware update soon that addresses both problems properly.

Is 9.5 is half a beta, you have a problem downgrading to production firmware problem disappear.
If a newer beta solve it, it’s the right way of beta working : finding troubles and solve it.
Good if they found problems and solve it


Inviato dal mio iPhone utilizzando Tapatalk

Just to clarify — version 9.5 is not a beta firmware.

It's an official, production release distributed by Blackmagic on April 6, 2025. Some of the new features — like PDAF, continuous autofocus, and object/facial tracking — are specifically labeled as "beta support", but the firmware as a whole is not in beta.

That’s very different from what Blackmagic installed on my camera to fix the CFexpress issue, which is a true internal beta firmware, not yet publicly available.

Quick update: Blackmagic confirmed that they were able to replicate the CFexpress issue on my camera and resolved it by installing a beta firmware that is not yet publicly released.

While I appreciate the effort and communication, I'm not entirely comfortable with the idea of having a non-official firmware on a production camera — especially since the freeze issue is still being investigated.

I'll wait for the final assessment, but for now, the solution feels more like a workaround than a stable fix. I really hope BMD can offer an official firmware update soon that addresses both problems properly.

Is 9.5 is half a beta, you have a problem downgrading to production firmware problem disappear.
If a newer beta solve it, it’s the right way of beta working : finding troubles and solve it.
Good if they found problems and solve it


Inviato dal mio iPhone utilizzando Tapatalk

Just to clarify — version 9.5 is not a beta firmware.

It's an official, production release distributed by Blackmagic on April 6, 2025. Some of the new features — like PDAF, continuous autofocus, and object/facial tracking — are specifically labeled as "beta support", but the firmware as a whole is not in beta.

That’s very different from what Blackmagic installed on my camera to fix the CFexpress issue, which is a true internal beta firmware, not yet publicly available.

Great point; something Blackmagic might want to message better next time; official firmware release with beta features implies that only the beta features incur risk, compared to a beta firmware release that can develop larger/encompassing problems like this one.

I mentioned the beta firmware for exactly this reason. If you check the specs, they clearly state that it includes features from the 8.6 and 8.7 beta rounds—like the GM update—which introduced support optimizations. These have caused a lot of issues for all Pocket users, including myself, even when using approved external and internal supports.

If you don’t want to use the beta, you can simply roll back to the previous stable firmware and everything will work fine.

One of the great things about Blackmagic Design is precisely this: they let us move freely between firmware versions. Unlike other brands—I’m not naming names—I once had a photo camera without autofocus for 8 months due to a firmware issue. Downgrading required paying, sending it outside of Italy, just to do something I could have done myself, like a simple firmware update.

So let’s appreciate the fact that Blackmagic gives us this flexibility.
If I seemed to say something different, forgive me—English isn’t my first language, and sometimes I might not express myself perfectly.


Inviato dal mio iPhone utilizzando Tapatalk

I mentioned the beta firmware for exactly this reason. If you check the specs, they clearly state that it includes features from the 8.6 and 8.7 beta rounds—like the GM update—which introduced support optimizations. These have caused a lot of issues for all Pocket users, including myself, even when using approved external and internal supports.

If you don’t want to use the beta, you can simply roll back to the previous stable firmware and everything will work fine.

One of the great things about Blackmagic Design is precisely this: they let us move freely between firmware versions. Unlike other brands—I’m not naming names—I once had a photo camera without autofocus for 8 months due to a firmware issue. Downgrading required paying, sending it outside of Italy, just to do something I could have done myself, like a simple firmware update.

So let’s appreciate the fact that Blackmagic gives us this flexibility.
If I seemed to say something different, forgive me—English isn’t my first language, and sometimes I might not express myself perfectly.


Inviato dal mio iPhone utilizzando Tapatalk

You have been declaring self-obvious and redundant principles that we have known for many years, universally. Future firmware releases with beta features and meltdown risks like 9.5 need to be labeled in the future as betas in the firmware title/announcement/marquee heading.

It can also be true in hindsight, apart from broad sentiments, that 9.5 simply should not have been released because of the CFexpress problem.

Personally, I’ve never installed beta firmware on any of my devices — stability is essential in production work, and undocumented fixes simply don’t belong in that context. I’ll keep everyone updated as the situation evolves.

I mentioned the beta firmware for exactly this reason. If you check the specs, they clearly state that it includes features from the 8.6 and 8.7 beta rounds—like the GM update—which introduced support optimizations. These have caused a lot of issues for all Pocket users, including myself, even when using approved external and internal supports.

If you don’t want to use the beta, you can simply roll back to the previous stable firmware and everything will work fine.

One of the great things about Blackmagic Design is precisely this: they let us move freely between firmware versions. Unlike other brands—I’m not naming names—I once had a photo camera without autofocus for 8 months due to a firmware issue. Downgrading required paying, sending it outside of Italy, just to do something I could have done myself, like a simple firmware update.

So let’s appreciate the fact that Blackmagic gives us this flexibility.
If I seemed to say something different, forgive me—English isn’t my first language, and sometimes I might not express myself perfectly.


Inviato dal mio iPhone utilizzando Tapatalk

You have been declaring self-obvious and redundant principles that we have known for many years, universally. Future firmware releases with beta features and meltdown risks like 9.5 need to be labeled in the future as betas in the firmware title/announcement/marquee heading.

It can also be true in hindsight, apart from broad sentiments, that 9.5 simply should not have been released because of the CFexpress problem.

I’m totally agree with you.


Inviato dal mio iPhone utilizzando Tapatalk

[Kristian Lam]

This issue is now fixed with v9.5.2. Thanks.

This issue is now fixed with v9.5.2. Thanks.

Thank you, will test cautiously and optimistically.

Huzzah 9.5.2! That did it. It now recognizes my CF Express cards. Thank you to the Blackmagic team for getting this fixed.

After a full month, Blackmagic confirms they fixed the CF issue — by installing the new firmware (which was already about to be released publicly).
No fix for the freezes: “not replicated.”

And guess what?
As of today, I still haven’t received the camera back. No tracking. No confirmation.

One month without a working camera, no clear answers, and no assurance the real problem is gone.
Honestly? Worst support experience I’ve had with any camera brand. Ever.