Archer C64 Freezes and Goes Offline After Updating to Firmware 1.14.3
Hello,
After updating to the latest firmware, my Archer C64 started freezing, and I can no longer connect to it either online or within the local network.
The only solution that works is a physical reboot. The issue occurs every 1-2 hours.
I have a main router and two secondary ones set up with EasyMesh. Before the update, everything was working perfectly.
Unfortunately, I cannot seem to downgrade to the previous firmware version (e.g., Archer C64(EU)_V1_1.13.15 Build 240812) from:
https://www.tp-link.com/en/support/download/archer-c64/#Firmware
In the logs, I see the following entries:
158 INFO 0days, 00:11:21, [upgrade]start upgrade
159 ERROR 0days, 00:11:21, [upgrade]SID not match, 0x5545:0x5355
160 ERROR 0days, 00:11:21, [upgrade]CID not match, 0x4444:0x4544
161 ERROR 0days, 00:11:21, [upgrade]SID not match, 0x5545:0x504a
162 ERROR 0days, 00:11:21, [upgrade]SID not match, 0x5545:0x5552
163 ERROR 0days, 00:11:21, [upgrade]SID not match, 0x5545:0x5754
164 ERROR 0days, 00:11:21, [upgrade]SID not match, 0x5545:0x5242
165 ERROR 0days, 00:11:21, [upgrade]SID not match, 0x5545:0x4143
166 ERROR 0days, 00:11:21, [upgrade]SID not match, 0x5545:0x5355
167 ERROR 0days, 00:11:21, [upgrade]CID not match, 0x4444:0x4144
168 ERROR 0days, 00:11:21, [upgrade]SID not match, 0x5545:0x5552
169 ERROR 0days, 00:11:21, [upgrade]SID not match, 0x5545:0x5355
170 ERROR 0days, 00:11:21, [upgrade]main version 0x10d00 is smaller than 0x10e00!
Considering that resolving this issue might take time, I kindly ask you to provide instructions on how to downgrade to the previous firmware version.
These problems have rendered my device almost unusable, and I urgently need a solution.
Thank you!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@terziyski Let’s not speculate about what might be wrong. I’ve contacted support directly and will provide them with all the necessary information. Since the bug manifests after a certain amount of time, I can only assume it might be related to a memory leak.
The best solution for me would be the ability to simply install an older version of the firmware (1.13.3 Build 240223 Rel.60864n(4555)).
To be honest, I’m already tired of manually rebooting the device.
- Copy Link
- Report Inappropriate Content
@tapac3 i wrote tens of emails to tplink support with my problems, they fixed them in betas and forgot to include in public release.
as for me firmwares with annoying background images are the only right solution:)). this beta that you have is the only one firmware for c64 that dont have port forwarding problem in mesh, accesing chromecast, rdp, smb etc devices wireleslly connected to different routers.
- Copy Link
- Report Inappropriate Content
I saw your email and have escalated it to the support engineers for further investigation.
You mentioned that you have a custom DHCP setup and a different routing table. Could you please provide more details about these settings on the main C64? You can share this information directly with the support engineers via email.
@terziyski @YuriyB Thank you both very much for joining this discussion and providing valuable suggestions. I will update the community once this issue is confirmed or resolved.
- Copy Link
- Report Inappropriate Content
@Kevin_Z To be honest, I don’t have any complex settings that might seem to cause an issue at first glance.
I’m attaching a list of my settings, with the exception of the reserved DHCP client list, which I’m not including here.
- Copy Link
- Report Inappropriate Content
Thank you very much for the update.
Our support engineers will follow up via email. Please check the email you've created.
- Copy Link
- Report Inappropriate Content
@Kevin_Z To speed up the troubleshooting process, I’m attaching a portion of the logs from the UART interface captured at the moment when the device freezes.
When the log shows "[mt7626]kick out msg fail"
, the device is already unresponsive.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 20
Views: 613
Replies: 26