# Error after Klipper firmware 0.13 update

**URL:** <https://klipper.discourse.group/t/error-after-klipper-firmware-0-13-update/24472>\
**Category:** General Discussion\
**Created:** [August 3, 2025, 1:55pm UTC](https://klipper.discourse.group/t/error-after-klipper-firmware-0-13-update/24472 "2025-08-03T13:55:55Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![nefelim4ag](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/nefelim4ag/32/2387_2.png) [@nefelim4ag](https://klipper.discourse.group/u/nefelim4ag)\
**Post date:** [August 3, 2025, 8:12pm UTC](https://klipper.discourse.group/t/error-after-klipper-firmware-0-13-update/24472/10 "2025-08-03T20:12:07Z")

</div>

> [@mistergefahrensucher](#):
>
> i think the v0.13 firmware is bad. There must something different against v0.11  
> In the past i had also the same problems with v0.12 firmware.  
> Thats why i am staying at v0.11. This pice is working with my printer.  
> thanks

It is possible that on some obscure/old/cheap/not popular MCUs, there could be issues.  
If you say that it has been broken for more than 2 years.  
It’s unfortunate.

```auto
commit 0d67d9c45d2dc39f8b4be7d1bb54b94b2698a2b6 (tag: v0.12.0)
Author: Kevin O'Connor <kevin@koconnor.net>
Date: Thu Oct 12 20:54:45 2023 -0400

    docs: Note the release of v0.12.0

```

But it also means that this whole time, no one reported it.  
It is hard to guess or debug without this particular MCU in hand.

If you will, you can go down the rabbit hole: [Klipper Versioning, Downgrading, and Bisecting](https://klipper.discourse.group/t/klipper-versioning-downgrading-and-bisecting/23359)  
To, well, isolate the change that broke your particular MCU.

---

_[View the full topic](https://klipper.discourse.group/t/error-after-klipper-firmware-0-13-update/24472)._