Archer C64 Freezes and Goes Offline After Updating to Firmware 1.14.3
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
A while ago backup file format was possible to read as a simple text file but they've changed this due to a security reasons (administrator password has appeared there).
As a last resort till everything settles you could try the beta FW offered here by YuriyB.
I am pretty sure that @Kevin_Z or @Sunshine would see this thread and do the necessary, so you can resolve this issue.
- Copy Link
- Report Inappropriate Content
I tried downgrading after resetting to factory settings, but the same error persists. It says there’s an issue with the configuration.
So now I’m stuck with a router that freezes and no way to downgrade.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@YuriyB I installed the beta firmware on the main router, and it has stopped freezing.
The satellites are running the latest official firmware and are working fine.
So, it can be concluded that the latest official firmware doesn’t function properly on the main router.
- Copy Link
- Report Inappropriate Content
It seems I celebrated too soon. The main router is still freezing, although not as frequently as it did with the latest official firmware.
- Copy Link
- Report Inappropriate Content
@tapac3 so it is your local problem, I have two c64's in mesh working 24/7 for two months with 11 clients on this beta firmware with ZERO problems.
- Copy Link
- Report Inappropriate Content
Yes, this is a localized issue, which is why I was asking for help with downgrading.
I don’t know exactly what was updated in the new firmware or why it doesn’t work with my setup.
I have three Archer C64 routers, two of which act as satellites.
On firmware 1.13.3 Build 240223 Rel.60864n(4555), everything was working perfectly.
However, when the update was released, I encountered a pop-up in the web interface that I couldn’t close.
It gave me two options: Update Now or Auto Update Later.
In other words, I was forced to update the firmware, and now I have a device that doesn’t work properly.
@YuriyB
I’m glad everything works for you, but that doesn’t mean the problem doesn’t exist.
I have a custom DHCP setup and a different routing table, which could be factors.
Also, I have no idea how you’re managing to work with the beta firmware.
At the very least, the background image in it is incredibly annoying.
- Copy Link
- Report Inappropriate Content
tapac3 wrote
...
However, when the update was released, I encountered a pop-up in the web interface that I couldn’t close.
It gave me two options: Update Now or Auto Update Later.In other words, I was forced to update the firmware, and now I have a device that doesn’t work properly.
....
That's strange because the Auto Update feature was introduced in this new FW release v1.14.3:
- Copy Link
- Report Inappropriate Content
For obvious reasons, I can’t show how this window looked on the previous firmware version.
However, it appeared immediately upon logging into the router.
The background was dimmed, making all content behind the window inaccessible (no links, no text selection, etc.).
The window couldn’t be closed and displayed a message that a new firmware version was available, with only two options: Update Now or Auto Update Later.
But if you want to see how this window looked without the dimming effect and background blocking, you can type the following into the browser console (on the router's index page):
$('#update-fail-msg').show();
But that’s not the main issue. The main problem is that I can’t even install the previous firmware version, even if I’m willing to lose all my settings.
- Copy Link
- Report Inappropriate Content
For safety reasons I keep the Auto Update feature off and starting the FW update process manually.
If you're willing to tell us more about your customized setup, it would be beneficial for the troubleshooting and pinpoint the culprit.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 19
Views: 415
Replies: 20