Support
NVR Has No Monitor Display or Will Not Boot
Recorder Startup
Summary
Follow the four stages below to diagnose an NVR has no local picture or does not complete startup without losing evidence, configuration or device ownership.
Applies to
- CCTV NVRs and DVRs with HDMI or VGA output
- Recorders that are blank, boot-looping or apparently dead
Difficulty and time
Difficulty: Moderate
Estimated time: 15 to 40 minutes
What you will need
- The exact model and current firmware or app version
- Administrator access where authorised
- A photo or screenshot of the current status
- One controlled test case and its exact time
What this guide covers
- Preserve and reproduce the fault
- Open the correct diagnostic screen
- Correct the proven cause
- Verify and document the result
Use this page when an NVR has no local picture or does not complete startup. It includes the menu or screen to look for, the status that matters and a repeatable proof test.
Exact labels can differ between recorder, controller, app and firmware versions. If the named screen is not present, do not guess at destructive options; note the model and current version for support.
Before you start
Protect the current system and record a baseline before changing anything.
- Write down the exact symptom: the monitor says No Signal, the recorder loops at its logo, or no front-panel activity appears.
- Photograph the current status, error text, wiring or timeline as applicable.
- Record the last known working time and anything changed immediately before the fault.
- Do not open the recorder or swap power supplies unless qualified; photograph every front and rear status indication first.
A matching plug does not prove a power supply is compatible
Wrong voltage, polarity or inadequate current can damage the NVR. Use the original supply or an explicitly approved replacement.
If the required option is missing or the result does not match this guide, stop and identify the exact model before continuing.
What usually causes this
- Monitor is on the wrong input
- HDMI/VGA cable or display handshake failed
- Output resolution is unsupported
- Power supply or recorder hardware is failing
Step 1: Preserve the current state and reproduce the fault
Begin with a repeatable baseline so you know whether a later change genuinely helped.
- Reproduce the problem once and record: the monitor says No Signal, the recorder loops at its logo, or no front-panel activity appears.
- Note whether every device or user is affected, or only one.
- Compare one working path with the failing path if a comparison exists.
- Do not open the recorder or swap power supplies unless qualified; photograph every front and rear status indication first.
Step 2: Open the correct screen and inspect the evidence
The primary diagnostic location is Monitor Input/Source menu, then NVR local Display or System settings when a picture is available. Do not change anything until the displayed state is recorded.
- Open Monitor Input/Source menu, then NVR local Display or System settings when a picture is available. Menu wording can vary by model and firmware; use the nearest equivalent label.
- Confirm the monitor is on the exact HDMI or VGA input being used.
- Observe NVR power, network and HDD LEDs and listen for a normal boot sequence.
- Test one known-good short video cable and, if available, a second monitor.
Step 3: Correct only the cause you proved
Use the matching correction below. Make one change, save it, then repeat the same test.
- Disconnect nonessential USB devices and cameras, then retry with only power and one monitor attached.
- Use the supplied or model-correct power supply; do not substitute on voltage alone.
- If a resolution mismatch is suspected, try the alternative supported video output or a monitor supporting the previous resolution.
- If the unit loops or remains dead, stop repeated power cycling and arrange hardware assessment.
Step 4: Verify, monitor and document the handover
A saved setting is not proof. Test the real outcome locally first, then test any app, cloud or client path separately.
- Confirm the login screen appears and remains stable for ten minutes.
- Reconnect cameras and USB devices one group at a time.
- Check system time, disk state and event logs after the boot.
- Restart once through the shutdown menu and confirm normal return.
Controlled support test
Situation: The reported symptom was: the monitor says No Signal, the recorder loops at its logo, or no front-panel activity appears.
Solution used: The current state was recorded in Monitor Input/Source menu, then NVR local Display or System settings when a picture is available, one matching correction was made, and the same test was repeated.
Why this was chosen: This separated the proven cause from unrelated settings.
Installation notes: The final screenshot and test time were saved with the handover record.
Official reference used for this guide
Menu names differ between releases. Confirm model-specific behaviour in Uniview official FAQ library before firmware, reset, storage or security-sensitive work.
Common mistakes
- Changing several settings before repeating the original test.
- Using a factory reset, initialise or format option as an early troubleshooting step.
- Treating an app symptom as proof that the local hardware or recording has failed.
- Failing to record the model, version, exact error and test time before escalation.
- Assuming similar-looking models use identical menus or features.
Troubleshooting table
| Symptom | What to check | What to do next |
|---|---|---|
| the monitor says No Signal, the recorder loops at its logo, or no front-panel activity appears | wrong monitor input, failed cable, unsupported output resolution, weak power supply, USB fault or recorder hardware failure | Open the named diagnostic screen, record the displayed state and use the matching correction above. |
| The named menu is not visible | Different firmware, permissions or model capability | Do not substitute a destructive menu. Capture the model and version and use its official manual. |
| The change saves but the fault remains | The selected cause was not the root cause | Undo the change if appropriate, return to the baseline and compare the failing path with a working one. |
| Local test works but app or client test fails | Account, permission, cloud or remote-network path | Keep the proven local configuration and diagnose the remote path separately. |
| Problem returns later | Intermittent power, cable, storage, network or schedule condition | Record the new failure time and status; correlate it with logs, events and the last known working interval. |
When to contact support
Contact SecurityWholesalers support when a known-good display and cable still show no output, the NVR boot-loops, or the approved power supply is unstable.
Send the order number if available, exact model, firmware or app version, screenshot of Monitor Input/Source menu, then NVR local Display or System settings when a picture is available, the failure time, and the result of the local proof test.
Related support guides
- CCTV Networking Support - Browse every guide in this support area.
- All Technical Support Guides - Return to the complete support library.
Related buying guides
- CCTV Buying Guide - General CCTV planning guide.
Relevant product categories
- CCTV Products - General CCTV products.
Still stuck?
Need help choosing or setting up a system? Contact SecurityWholesalers support with your order number, product model and a clear description of the issue.
Frequently asked questions
-
Where should I click first for NVR no display?
Start at Monitor Input/Source menu, then NVR local Display or System settings when a picture is available. Record the existing state before changing it because labels and available options can vary by model and firmware.
-
What should I look for on that screen?
Look for a stable boot screen, front-panel LEDs, fan activity, network link and whether the monitor reports No Signal versus a black image.
-
What must I avoid changing during the first check?
Wrong voltage, polarity or inadequate current can damage the NVR. Use the original supply or an explicitly approved replacement.
-
How do I prove the correction worked?
Reach the login screen, leave the recorder stable, reconnect peripherals gradually and complete one menu-driven restart.
-
Why might my menu names look different?
Recorder, controller, camera, app and firmware releases can use different labels. Use the closest equivalent only when its function is clear; otherwise record the model and version for support.
-
Should I factory-reset the device?
Not as an early step. A reset may erase users, network settings, recording configuration, licences or cloud ownership. Back up the configuration and confirm the recovery plan first.
-
What should I send technical support?
Send the exact model and version, screenshot of Monitor Input/Source menu, then NVR local Display or System settings when a picture is available, exact error text, failure time, what changed before the fault and the result of the controlled local test.
-
Can configuration changes recover data or events that were never recorded?
No. A correction can restore future operation, but it cannot recreate footage, alarm events or access transactions that were never stored.