What if the DVR / NVR system is stuck in a boot loop?

It sounds like the DVR / NVR system is experiencing a firmware crash. Manually applying a firmware update should help it to function normally.

On the bottom of the DVR / NVR there's a sticker with the DVR / NVR's model information. Could you please send an image to us?

If you could please respond with these details, we should be able to provide you with a link to the firmware update and some directions on how to proceed.

If you have found the correct upgrade file to upgrade the DVR / NVR system, but you're not seeing an "updating..." message on the screen for at least three minutes, the DVR / NVR isn't detecting the update file. There are a few reasons this could be: 

1) If the DVR / NVR has alternative places to look for the update, it won't run. The ethernet cable needs to be disconnected, as well as any other USB devices including the mouse. The power should be disconnected for at least 10 seconds before connecting the USB drive and reconnecting the power.

2) If the USB is 3.0, the DVR / NVR will not be able to read it. USB 3.0 was developed after the DVR / NVR motherboards. Likewise, the DVR / NVR is not in FAT32 format, it won't be read. The easy way to tell if a USB drive is 3.0 is the color of the board chip inside the USB connection. 2.0 always uses a black board, while 3.0 generally has a colored board, often red or blue. 

3) The file name must remain exactly as listed in the article for the DVR / NVR to recognize it as an update. If the file was downloaded twice, a PC will add (1) to the end of the name, which will create an issue. If the file was downloaded using the Microsoft Edge browser, this will cause the file to be converted to a text file, which can't be read by the DVR / NVR. 

4) The DVR / NVR cannot navigate through folders in the USB to find the update. The file must be placed in the USB root directory. 

If the DVR / NVR system still isn't updating after confirming these things, please let us know. 


Related Articles