Query About Firmware Update 1.13.15 for Archer C64 - Any Known Issues?

Query About Firmware Update 1.13.15 for Archer C64 - Any Known Issues?

Query About Firmware Update 1.13.15 for Archer C64 - Any Known Issues?
Query About Firmware Update 1.13.15 for Archer C64 - Any Known Issues?
2 weeks ago - last edited a week ago
Tags: #Firmware Update #FirmwareUpdateC64
Model: Archer C64  
Hardware Version: V1
Firmware Version: 1.12.10 Build 230208 Rel.38878n(5553)

Hello everyone,

I recently noticed that a new firmware update (Version 1.13.15 Build 240812 Rel.53634n) is available for my TP-Link Archer C64 router. My current firmware version is 1.12.10 Build 230208 Rel.38878n.

 

The release notes mention improved device stability and several bug fixes, including issues with:

  • Client upload/download speed display on the Network Map
  • Port forwarding failure with RTSP streams
  • Device name display in AP mode when DHCP is disabled
  • Device reboot on receiving specific packets in certain environments

 

Before I proceed with the update, I'd like to ask if anyone here has already installed it and experienced any issues, particularly with range coverage, connection stability, or any other unforeseen bugs. I rely heavily on stable and extended Wi-Fi coverage, so any feedback on range changes would be especially helpful.

Thank you for your input!

 

Best regards,
Zubaer

 

 

  2      
  2      
#1
Options
2 Accepted Solutions
Re:Query About Firmware Update 1.13.15 for Archer C64 - Any Known Issues?-Solution
2 weeks ago - last edited a week ago

  @ZubaerAhmad-XI 

 

TBH, I didn't know what the signal strength was before FW update to compare it now, but I didn't notice any problems in my particular setup with the wireless coverage..

If this was helpful click on the arrow pointing upward to make it blue. If this solves your issue, click the star to make it blue and mark the post as a "Recommended Solution".
Recommended Solution
  3  
  3  
#4
Options
Re:Query About Firmware Update 1.13.15 for Archer C64 - Any Known Issues?-Solution
a week ago - last edited a week ago

  @ZubaerAhmad-XI 

 

There's a newer FW release for C64 which fixes some bugs and adds some new features regarding Easymesh in AP mode - 1.14.3 Build 241025 Rel.69770n(4555):

Improvements and Bug Fixes:
1.Introduced EasyMesh, Auto Update, and TP-Link ID functionalities in AP mode.
2.Optimized static IP and DNS settings configuration in AP mode.
3.Enhanced parental control features with added content whitelisting and resolved related issues.
4.Improved Access Control functionality, allowing manual MAC address input.
5.Upgraded client list with new filtering rules for better management.
6.Enhanced WDS functionality to support WPA3-SAE encryption.
7.Improved wireless connection stability.
8.Adapted to the latest Tether app UI design.

If this was helpful click on the arrow pointing upward to make it blue. If this solves your issue, click the star to make it blue and mark the post as a "Recommended Solution".
Recommended Solution
  1  
  1  
#10
Options
15 Reply
Re:Query About Firmware Update 1.13.15 for Archer C64 - Any Known Issues?
2 weeks ago

  @ZubaerAhmad-XI 

 

I'm using this FW version and so far haven't noticed any issues related to it.

This FW version fixed the bug that guest SSID in AP mode wasn't working - details.

If this was helpful click on the arrow pointing upward to make it blue. If this solves your issue, click the star to make it blue and mark the post as a "Recommended Solution".
  0  
  0  
#2
Options
Re:Query About Firmware Update 1.13.15 for Archer C64 - Any Known Issues?
2 weeks ago - last edited 2 weeks ago

 

Hi! @terziyski 

Thanks for the quick response and for confirming that there aren’t any known issues with the update. That’s reassuring!
 

I wanted to ask a bit more specifically about the wireless range. After applying the new firmware update, have you or anyone else noticed any change in range coverage on either the 2.4 GHz or 5 GHz bands? I’m particularly concerned about any decrease in range that might affect coverage in larger areas of my home.

 

Thanks again for the help!

Best regards,
Zubaer

  0  
  0  
#3
Options
Re:Query About Firmware Update 1.13.15 for Archer C64 - Any Known Issues?-Solution
2 weeks ago - last edited a week ago

  @ZubaerAhmad-XI 

 

TBH, I didn't know what the signal strength was before FW update to compare it now, but I didn't notice any problems in my particular setup with the wireless coverage..

If this was helpful click on the arrow pointing upward to make it blue. If this solves your issue, click the star to make it blue and mark the post as a "Recommended Solution".
Recommended Solution
  3  
  3  
#4
Options
Re:Query About Firmware Update 1.13.15 for Archer C64 - Any Known Issues?
a week ago - last edited a week ago

A have Smartconnect problem. On 1.13.15 and on beta 1.14.3:

 

once android\phone device connected to 5Ghz, then move to low signal zone, connect switched to 2.4Ghz and keep slow 2.4ghz link all the time, even standing straight ahead the router it WONT switch back to 5Ghz. 

 

  1  
  1  
#5
Options
Re:Query About Firmware Update 1.13.15 for Archer C64 - Any Known Issues?
a week ago

 Hello @YuriyB,  
Does this issue occur only when the Archer C64 is used as a repeater? After the update, I haven't encountered any problems so far.

  0  
  0  
#6
Options
Re:Query About Firmware Update 1.13.15 for Archer C64 - Any Known Issues?
a week ago - last edited a week ago

  @ZubaerAhmad-XI 

in any mode. sdandalone, repeater, easymesh

 

Did you enabled smartconnect?

pleasy try move to weak signal zone so your device will switch from 5 to 2.4ghz.

and then go back to check whether it will switch back to 5ghz or will keep slow 2.4ghz

  1  
  1  
#7
Options
Re:Query About Firmware Update 1.13.15 for Archer C64 - Any Known Issues?
a week ago - last edited a week ago

  @YuriyB Yes, I enabled the SmartConnect feature and encountered the same problem in Router mode. The devices did not switch from the 2.4 GHz to the 5 GHz band consistently. However, it does not seem to happen all the time. Additionally, the update notes mentioned that the speed displayed on the client page for devices is either inaccurate or shows a very low value. After installing the update, I conducted a multi-connection test on Speedtest.net, which reported speeds of over 800 Mbps. However, during the test, the router displayed values ranging from 0 Kbps to 300 Kbps. This indicates that the bug has not been resolved yet.

  1  
  1  
#8
Options
Re:Query About Firmware Update 1.13.15 for Archer C64 - Any Known Issues?
a week ago

  @ZubaerAhmad-XI  here's my problem with smartconnect, pls confirm there https://community.tp-link.com/en/home/forum/topic/707852

  1  
  1  
#9
Options
Re:Query About Firmware Update 1.13.15 for Archer C64 - Any Known Issues?-Solution
a week ago - last edited a week ago

  @ZubaerAhmad-XI 

 

There's a newer FW release for C64 which fixes some bugs and adds some new features regarding Easymesh in AP mode - 1.14.3 Build 241025 Rel.69770n(4555):

Improvements and Bug Fixes:
1.Introduced EasyMesh, Auto Update, and TP-Link ID functionalities in AP mode.
2.Optimized static IP and DNS settings configuration in AP mode.
3.Enhanced parental control features with added content whitelisting and resolved related issues.
4.Improved Access Control functionality, allowing manual MAC address input.
5.Upgraded client list with new filtering rules for better management.
6.Enhanced WDS functionality to support WPA3-SAE encryption.
7.Improved wireless connection stability.
8.Adapted to the latest Tether app UI design.

If this was helpful click on the arrow pointing upward to make it blue. If this solves your issue, click the star to make it blue and mark the post as a "Recommended Solution".
Recommended Solution
  1  
  1  
#10
Options
Re:Query About Firmware Update 1.13.15 for Archer C64 - Any Known Issues?
a week ago

  @terziyski It's great to know that! However, I'm from Bangladesh, and on local websites, the firmware update function is unavailable. Would manually updating the firmware void the warranty, or should I wait for the OTA update instead?

  0  
  0  
#11
Options