Meridian docs · revised 2026-10-13 · Windows installer

Windows 10 / 11 · x64

MeridianPS5 emulator Download

PHow-to · revised 2026-10-13

Boot system software

Reach menu idle with firmware installed. The log names the failing stage on any stop.

Section
Protocol
Host
Windows 10 / 11, x64
Revised
2026-10-13
White PlayStation 5 DualSense controller lying face-up on a dark wooden desk.
Fig. P1How-to: Boot system softwareProtocol

01At a glance

Precondition
Firmware installed; version in About
Pass
System menu reaches idle, no error dialog
Evidence
Boot log names the failing stage
Next
Index your library

02Procedure

Precondition: firmware installed per Install firmware.

  1. Launch Meridian and choose Boot → System Software. Wait — first boot builds caches and is slower than later boots.
  2. Confirm the system menu reaches idle with no error dialog. That is the pass condition; anything else is a diagnosed stop, not a flake.
  3. If it stops, read the last 30 lines of the log before changing anything. The log names firmware, Vulkan, or runtime as the stage — each maps to one fix page.

03Failure map

  • Firmware stage: About shows no version. Repeat Install firmware with a fresh official PUP.
  • Vulkan stage: update GPU drivers and re-run Vulkan check.
  • Runtime stage: install Microsoft's official Visual C++ 2015–2022 x64 runtime per Missing runtime.

Report only after one clean retry per fix. Include build number, firmware version, and GPU driver — see Compatibility methodology.

04After first boot

Continue to Index your library with one owned Stable title. New install? Begin at Download Meridian and work forward.

05Questions

Q.01First boot is slow — is that normal?

Yes. First boot builds caches. Measure from the second boot onward.

Q.02Black screen after boot — what failed?

Read the log tail. Firmware, Vulkan, and runtime failures each name their stage; fix only the named one.

Q.03Should I change settings before first boot?

No. Boot at defaults so the log reflects a known configuration.