A factory reset always clears router configuration, so to reset a router without losing important settings, you back up and record enough verified information to rebuild the network first. Confirm that a normal reboot is not sufficient, identify the exact model, hardware revision, and firmware, save ISP and local-network details, check whether a configuration backup is compatible, then reset using the manufacturer's procedure. Restore a minimal baseline and add custom rules one group at a time. ASUS states that factory reset removes current settings, while TP-Link warns that backup files may be limited to the same model and hardware version.［1］［2］［3］

Key Takeaways

Rebooting and factory resetting are different; reset erases configuration.

Keep both a supported backup file and a human-readable recovery record.

Record ISP authentication, VLAN, phone, and IPTV details before losing access.

Do not blindly import an old, cross-model, or possibly corrupted configuration.

Restore internet and secure administration first, then verify each custom feature.

Use this decision checklist before resetting:

Question	If yes	If no
Would a documented reboot address the symptom?	Reboot first	Continue diagnosis
Can you identify exact model, hardware version, and firmware?	Record them	Stop and find the labels/support page
Do you have ISP credentials and VLAN/phone/IPTV requirements?	Verify them	Ask the ISP before resetting
Does the vendor confirm backup compatibility?	Keep the export securely	Prepare for manual rebuild
Can you connect locally by Ethernet after reset?	Prepare cable/client	Confirm supported local setup method

1. Before you reset a router without losing important settings, decide whether a reboot is enough

A reboot restarts software without intentionally deleting settings. A factory reset returns configuration to defaults and can remove internet authentication, Wi-Fi names, admin settings, reservations, DNS choices, port rules, guest networks, and service-specific configuration. Use a reboot first for a transient hang unless the exact manufacturer procedure or support case calls for a reset.

If the symptom is upstream loss while the router remains running, use the router connected but no internet guide. If it repeatedly reboots, use router restart troubleshooting before erasing settings.

2. Record hardware and firmware identity

Photograph or write down the exact model, hardware revision, serial number if support needs it, installed firmware version, region, and ISP-supplied ownership status. Obtain the manual and firmware only from the exact manufacturer's support page. Do not assume two routers with similar names accept the same configuration.

Also record how you normally reach the local administration interface and whether setup requires an official app. Never put the admin password or ISP credentials in an unencrypted shared note.

3. Preserve ISP and bundled-service requirements

Record or obtain from the ISP:

WAN type: DHCP, PPPoE, static, or another documented mode.
Username and recovery path for authentication; store secrets securely.
Required VLAN IDs and tagging for internet, voice, or IPTV.
Static IP, gateway, DNS, MTU, or MAC-registration requirements if assigned.
Telephone/VoIP and television ports or profiles.
Whether the ISP gateway must remain in router, bridge, or passthrough mode.

Do not reset an ISP-managed gateway until the provider confirms that subscriber configuration can be restored. Some voice and IPTV settings may not be available to the customer.

4. Inventory the local network

Create a readable checklist of:

Main SSID, security mode, and password recovery record.
Guest and IoT network names, isolation, and schedules.
LAN subnet, DHCP range, reservations, and fixed-device addresses.
DNS resolvers and any local host or filtering rules.
Port forwarding, inbound rules, UPnP state, and remote administration state.
Mesh nodes, access points, switches, NAS, printers, cameras, and controllers.
Parental controls, time limits, and device groups.

Record rules by purpose and owner, not just as screenshots. Remove obsolete rules during review rather than reproducing them automatically. The guest Wi-Fi guide helps preserve isolation intent.

5. Export the router configuration only when compatibility is clear

Use the router's documented backup function and store the file in a private location. TP-Link says the backup and restore process applies to the same model and hardware version; treat the exact documentation for your router as authoritative. A backup may include credentials and should not be emailed or placed in a public cloud folder without appropriate protection.

An export is not enough. Confirm that the file is nonempty, record when and from which model/hardware/firmware it was produced, and keep the readable inventory. Do not edit the backup file or import it into a different model.

6. Prepare a safe recovery path

Download only the exact manual and, if needed, supported firmware before the reset. Have a known-good Ethernet cable, a local computer, the router's default local address, and the default setup credentials or documented first-run method. Ensure you can recover the ISP account without relying solely on the network you are about to erase.

Schedule downtime and tell household users. Disconnect optional USB storage and document cable positions. Do not press reset during a firmware update or when power is unstable.

7. Perform the manufacturer-documented reset

Follow the exact method for the model: the administration control or physical reset button may require a specific powered-on state and hold time. ASUS and TP-Link both state that factory defaults erase personalized configuration. Do not guess the hold time, use a pin on an unidentified opening, or repeatedly interrupt power.

Wait for the full startup sequence. Connect locally using the supported method. Set a unique administrator credential, install supported firmware if required by the official sequence, and disable remote administration unless there is a documented need.

8. Restore the minimum baseline, then verify in layers

First restore only WAN/ISP access, secure administration, LAN subnet, and one protected main Wi-Fi network. Verify local administration, DHCP, DNS resolution, multiple destinations, and a second device. Then add guest/IoT isolation, reservations, phone/IPTV, mesh nodes, and necessary custom rules one group at a time, testing after each group.

Import a backup only if the manufacturer confirms compatibility and the previous configuration is not suspected of causing the fault. If importing brings the problem back, reset again and rebuild manually from the readable record instead of repeatedly importing the same state. Finish with the new router setup checklist and document the verified result.

After you reset the router without losing settings, close the recovery record

Keep a simple before-and-after table. For each restored group, record what was added, who needs it, the test performed, the result, and how to remove it. Start with local administration and one wired client, then WAN access, one protected Wi-Fi network, DNS, and a second device. Add guest or IoT isolation, reservations, phone/IPTV, mesh, and necessary inbound rules only after the previous layer remains stable.

Restored layer	Minimum evidence before continuing
Administration	Unique credential works locally; remote access is off unless required
WAN and DNS	More than one destination works and the ISP-required profile is present
Main Wi-Fi	A second trusted device joins with the intended security mode
Guest or IoT	Isolation and intended local access are tested separately
Custom rules	Owner, purpose, target, test, and rollback are recorded

Compare the final record carefully with the pre-reset inventory. Missing obsolete rules may be intentional; unexplained differences are not. Store the compatible export and readable record privately, label them with model, hardware revision, firmware, and date, and remove temporary copies from shared locations. Never include passwords in a support screenshot.

If the original fault returns immediately after one group, stop there. Remove that group or return to the last verified baseline instead of importing everything again. This staged evidence is what makes recovery reliable: the reset itself erases settings, while the record lets you rebuild only the configuration that is still needed and known to work.

FAQ

Can a factory reset keep my settings?

No. It restores defaults. You preserve important information by recording and backing it up before the reset.

Is rebooting the same as resetting?

No. A reboot restarts the router; a factory reset erases configuration.

What ISP details should I save?

WAN mode, authentication recovery, VLANs, static addressing, MTU/MAC requirements, and voice/IPTV profiles.

Can I restore a backup to a different router?

Do not unless the manufacturer explicitly supports that exact model and hardware combination.

Does a router backup contain passwords?

It may contain sensitive settings or recoverable secrets. Store it privately and follow vendor guidance.

Should I import the backup immediately?

Restore a minimum baseline first. Import only if compatible and the old configuration is not suspected.

What if the ISP owns the router?

Contact the ISP before resetting; managed voice, IPTV, and authentication settings may require provider recovery.

How do I know the reset worked?

The router returns to documented defaults and starts first-run setup. Then verify each restored layer independently. AethoVPN cannot back up or restore a router's configuration; verify WAN credentials, Wi‑Fi, DNS, guest access, and port rules after any reset.

Sources

ASUS Support - How to reset the router to factory default settings — https://www.asus.com/support/faq/1000925/
TP-Link Support - How to back up and restore router configuration — https://www.tp-link.com/us/support/faq/2015/
TP-Link Support - How to restore a router to factory defaults — https://www.tp-link.com/uk/support/faq/497/?app=aginet

Sources checked 28 August 2026.

How to Reset a Router Without Losing Important Settings