Home / Software / Downloads /

RB951 recovery with Netinstall

For RB951Ui-2HnD and RB951G-2HnD. Use this guide when the router cannot boot or you want to return from FreeISP OS to RouterOS. You do not need to log in to enter physical recovery mode.

Restoration erases the router’s settings and files. Netinstall reinstalls RouterOS and removes FreeISP OS. It retains the RouterOS licence and RouterBOOT settings. Recovery requires a working bootloader and hardware; repeated beeps alone do not identify the fault.
1. Get files2. Prepare Ethernet3. Find the router4. RestoreMAC not appearing?

1. Prepare the recovery files

  1. Let any firmware write finish. If FreeISP Install is still writing, keep power connected. Once it has stopped or finished checking first boot, save its latest local report and close the app before starting Netinstall. Do not clear an unknown-write record or repeatedly start another FreeISP installation.
  2. Download Netinstall for Windows, the RouterOS MIPSBE system package and the matching wireless MIPSBE package from MikroTik Downloads. Choose a Stable or Long-term release and use the same release version for all three. Both RB951 models use MIPSBE.
  3. Extract the Netinstall ZIP and put the two .npk files in a folder on the PC connected to the router. For example, a 7.23.8 set contains netinstall64.exe, routeros-7.23.8-mipsbe.npk and wireless-7.23.8-mipsbe.npk. The version is an example, not a requirement to use that older release.

Recovery files are separate from the FreeISP installation files. Get them when recovery is needed; a FreeISP image cannot be selected as a RouterOS package in Netinstall.

2. Prepare the PC and ether1

Using UltraViewer or another remote-support tool? Disabling Wi-Fi may disconnect your remote session. Download everything first and arrange for a person at the PC to complete the Ethernet-only steps. Do not disable the connection carrying remote support until they are ready.
  1. Connect the PC directly to the router’s ether1 port. Disconnect other router network cables. Keep the router’s normal power supply available.
  2. Record the PC’s original Ethernet settings so you can restore them afterward. Press Windows + R, type ncpa.cpl, then open the connected Ethernet → Properties → Internet Protocol Version 4 (TCP/IPv4) → Properties.
  3. Set the Ethernet address below. If previous attempts left extra IPv4 addresses, review Advanced → IP addresses and use only this address on the dedicated recovery adapter. Do not change unrelated adapters.
SettingValue
PC Ethernet IPv4 address192.168.89.254
Subnet mask255.255.255.0
Gateway and DNSLeave blank on this Ethernet connection
Netinstall client IP (the router)192.168.89.2

MikroTik recommends leaving only the installation Ethernet interface enabled for Netinstall. With someone at the PC, temporarily disable Wi-Fi, VPN and other network adapters. Re-enable them after recovery.

3. Start Netinstall and enter recovery mode

  1. Right-click netinstall64.exe and choose Run as administrator. Allow Netinstall through Windows Firewall if prompted.
  2. Open Net booting, tick Boot Server enabled, enter 192.168.89.2 as the Client IP address, then click OK. This differs from the PC’s address.
  3. With Netinstall already open and the cable in ether1, disconnect the router’s power. Press and hold the physical RESET button, reconnect power, and keep holding.
  4. Watch the user/activity indicator: flashing → steady → off. Release RESET when it turns off—approximately 15 seconds on RB951. Follow the indicator, not just the clock. Releasing at the earlier flashing or steady stage selects a different function.
  5. Wait for the router to appear in Netinstall’s Routers/Drives list. Its MAC appears after recovery discovery; ordinary browser access or RouterOS login is not required. If nothing appears, use the troubleshooting section below.

4. Select the packages and restore RouterOS

  1. Select the router entry and confirm its model and known ether1 MAC address. Never select a PC disk or a different router.
  2. Click Browse and choose the folder containing your .npk files. Tick both the routeros and wireless packages for MIPSBE, with matching versions.
  3. For a clean return to RouterOS, leave Keep old configuration unchecked and enable Apply default config. Click Install when you are ready to erase the router’s settings and files.
  4. Keep power connected until Netinstall reports completion. Use Reboot if it does not restart automatically.
  5. Move the PC’s cable to ether2. Restore the PC’s original network settings—normally automatic IP and DNS—and re-enable the adapters you disabled. Open 192.168.88.1 or use WinBox Neighbors to confirm RouterOS is running. Use the device’s applicable default/label credentials and set a new password.

If recovery followed a failed FreeISP boot, keep the installation report and image version for support before trying FreeISP again.

If Netinstall does not show the MAC address

  1. Check ether1 and the link. Use ether1 for recovery, not ether2. Check that the PC Ethernet adapter shows connected, and try a known-good cable.
  2. Repeat the button sequence with Netinstall already open. Hold through flashing and steady light; release when the indicator turns off. Check Boot Server is enabled before powering the router.
  3. Check the two addresses. PC: 192.168.89.254/24; client: 192.168.89.2. They must be different and on the same subnet. Leave gateway and DNS blank on the dedicated Ethernet adapter.
  4. Check which PC connection Netinstall uses. Temporarily use only the dedicated Ethernet adapter, with an onsite person if remote support depends on Wi-Fi. Close FreeISP Install and other network-boot utilities.
  5. Check permissions. Run Netinstall as administrator and allow the application through Windows Firewall. Do not leave the firewall disabled as a workaround.
  6. Try a simple Ethernet switch. Some PC or USB adapters briefly drop the link during startup and miss recovery packets. Put a simple switch between the PC and router’s ether1; connect no unrelated network or DHCP server to it.
  7. Try another PC or adapter. If it still does not appear, test another Ethernet adapter or Windows PC. Protected RouterBOOT settings, power or hardware faults may need model-specific support. Failure to appear alone does not prove the router is permanently damaged.

Official references