This appears to be a known bug in the Archer VR1600 v2. Is that correct?
I'm currently running the latest Firmware Version – 0.1.0.0.9.1 v5006.0 Build 200810 Rel.53181n Hardware Version – Archer VR1600 v2 00000000.
Can somebody confirm this please?
Thanks for raising this with us.
This has been raised to our Network Engineers to further check this issue with the Auto Reboot.
Any updates will be posted as soon as it becomes available.