How to Fix Enshrouded Crashes, Launch Errors, and Black Screens on PC

If Enshrouded crashes, refuses to start, or shows a black screen, begin with two checks that can be confirmed rather than guessed: compare your PC with the published requirements and verify the Steam installation. If those do not resolve the problem, identify the exact error, separate launch failures from network failures, and send Enshrouded support the logs and hardware report it requests. The steps below follow that order and distinguish documented historical fixes from causes that still need diagnosis.

1. Identify which failure you are actually seeing

“Crashing,” “does not start up,” and “black screen” describe different points in the launch process. Record what happens and when:

#	Preview	Product	Price
1		Games Workshop - Warhammer 40,000 - Craftworlds Spiritseer	$29.75	Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

• Crash: the game opens and then closes, freezes, or returns to the desktop.
• Launch failure: Steam reports the game as running briefly, but no game window appears, or the process closes immediately.
• Black screen: a window appears but displays no usable image. Note whether you can hear audio, move a cursor, or open the game menu.
• Graphics initialization error: write down the complete message if you see “Failed to initialize the graphics system.” That exact wording has a specific historical reference and should not be treated as a label for every black screen.
• Multiplayer problem: the game reaches its menus, but a server list does not populate or a session disconnects. That is a network symptom, not automatically a graphics or installation failure.

Save the exact wording, a screenshot if possible, and whether the problem began after an update, hardware change, or Windows change. Those details make later support reports much more useful.

2. Check your PC against the published requirements

Before changing settings or buying hardware, record your Windows edition and version, processor, installed system memory, graphics-card model and VRAM, and free storage. Compare those values with the requirements published by Keen Games / Enshrouded Support. The support page displays a January 24, 2024 publication date, so use the current page and Steam listing for any later changes.

#1 Best Overall

Games Workshop - Warhammer 40,000 - Craftworlds Spiritseer

• Games Workshop - Warhammer 40,000 - Craftworlds Spiritseer
• Plastic multipart miniatures - assembly required - tools, paints and glue not included
• Games Workshop

$29.75

Buy on Amazon

These are examples from the official system-requirements page, not a guarantee that every configuration with an equivalent label behaves identically. The Steam technical listing also shows Intel Arc A380 as a minimum example and Arc A770 as a recommended example, and recommends an SSD. The two sources do not present identical GPU lists, so check the current Steam listing for the hardware details applicable to your edition and date.

Being below one listed example does not prove that it caused your particular crash, and meeting the minimum does not prove that a black screen has a single identifiable cause. The comparison tells you whether the PC is within the publisher’s stated baseline; it is not a diagnosis.

What to record in Windows

• Press Windows key + R, enter dxdiag, and note the operating-system, processor, memory, and display-device information. You can save the report for support later.
• In Windows Settings, open System > About to confirm the Windows version and installed RAM.
• Check free space on the drive containing the Steam library. The published requirement is 60 GB available, not merely 60 GB total capacity.
• Use the graphics vendor’s control panel or Windows Device Manager to identify the exact GPU model and its VRAM. Do not substitute a family name for the model when reporting the problem.

The requirements pages do not establish that buying more RAM, a different graphics card, or an SSD is a general cure for these symptoms. The SSD note is a recommendation about storage; it is not evidence that an SSD fixes crashes or launch failures.

3. Verify the Enshrouded installation in Steam

For a crash, a game that will not start, or a black screen, the first repair action with direct official support is Steam’s file verification. Square Enix’s PC support instructions say to validate the installation to confirm that files were properly installed. Steam has changed its labels over time, so follow the current wording for the verification command rather than looking for one exact legacy phrase.

1. Open the Steam Library and select Enshrouded.
2. Open the game’s Properties from its library entry.
3. Find the installed-files or local-files section. Older instructions call this Local Files.
4. Choose the current option that verifies or checks the integrity of the installed files. The older Square Enix page calls it Verify integrity of game cache.
5. Wait for Steam to finish. If it reacquires files, allow the download to complete before starting the game.
6. Launch Enshrouded again and note whether the symptom changed. A result that says no files needed replacement does not prove that your drivers, hardware, or save data are healthy; it only reports the installation check.

The original support path is documented in Square Enix’s PC troubleshooting article. Current Steam clients may place the command under a slightly different heading, but the action is the same: check the local installation and repair files Steam identifies as missing or damaged.

If verification does not help

Do not repeatedly verify as a substitute for collecting evidence. Record the verification result, the time it completed, and any files Steam downloaded. Then continue with the exact error and diagnostics below. If the game was installed on a drive with very little free space, make room before retrying so Steam can complete repairs; the requirement is 60 GB available storage.

4. Match “Failed to initialize the graphics system” to its documented history

Keen Games’ Hotfix #3, released January 25, 2024 as version 487224, says it fixed an issue that prevented the game from starting and displayed “Failed to initialize the graphics system” on older AMD graphics cards. The same hotfix notes that several crashes were fixed.

This is historical patch evidence. It establishes that the message existed and that Keen Games listed a fix in that 2024 build; it does not establish that the same bug remains common in the current release, nor that a particular driver update is a current universal remedy. If you still receive the exact message, include the wording, GPU model, driver version, game build, and whether Steam verification changed anything in your report.

AMD’s release notes for Adrenalin 23.40.02.03 for Enshrouded separately list an intermittent crash when first launching Enshrouded on Radeon 7000-series products. That is a dated driver-release note, not proof that every Radeon 7000 owner is affected or that this driver remains the right download for a current system. Treat it as useful historical context when describing your configuration, not as a blanket prescription.

What this error does—and does not—tell you

• It points to graphics-system initialization, not automatically to a damaged save, network connection, or insufficient RAM.
• It does not identify the exact cause on your PC without the GPU, driver, log, and game-build details.
• It does not make every black screen the same problem. A silent black window, a crash after the logo, and a multiplayer disconnect require different evidence.

5. Keep multiplayer connection symptoms separate

If Enshrouded reaches the menu but servers do not appear or multiplayer sessions drop, use the game’s network guidance instead of treating the problem as a black-screen fix. The official Network Troubleshooting page states that multiplayer currently uses IPv4, gives default query port 15637, and discusses clearing Steam’s download cache and flushing DNS for connection problems.

Those actions are scoped to connection symptoms. They are not confirmed repairs for a game that never creates a visible window, fails during graphics initialization, or closes at startup. First decide whether you can reach the main menu; only then follow network-specific steps.

When to use the network checklist

• Use it when the game launches normally but the server browser is empty.
• Use it when you can join a world but lose the session or cannot connect to a host.
• Do not use a DNS flush or Steam download-cache reset as evidence that a graphics driver or installation problem has been fixed.

6. Gather the files Enshrouded support needs

If the requirements check and Steam verification do not resolve the failure, report it with reproducible details rather than a one-line “it crashes” description. Enshrouded’s Reporting Bugs instructions ask for a detailed description, reproduction steps when possible, a DxDiag report, and a zip containing the client log and backup folder.

1. Write a concise timeline. State when the problem began, whether it occurs every launch, and whether it followed a game, Windows, driver, or hardware change.
2. Describe the trigger. For example, say “Steam shows Running for about ten seconds, then returns to Play” or “the window opens to a black image but audio continues.” Include the complete error text, including capitalization.
3. List your configuration. Include Windows version, CPU, total RAM, exact GPU and VRAM, free storage, and the Enshrouded version shown by Steam. If you tested more than one display or resolution, say so.
4. Create DxDiag. Press Windows key + R, enter dxdiag, allow the tool to finish collecting information, and select Save All Information to produce the report file.
5. Open the local game files. In Steam, use Enshrouded’s library entry and its Browse local files command. Locate enshrouded.log and the backup folder.
6. Make one zip archive. Include the log and backup folder as requested, and keep the DxDiag report available to attach separately if the form provides separate fields.
7. Submit through the available reporting route. If the game starts, use its in-game report option when appropriate. If it will not start and that option is unavailable, use the external report form described on the support page.

Do not edit the log before sending it, and do not omit the error text because the game closes too quickly to reproduce it reliably. Tell support exactly which steps you completed and what changed after each one.

A compact report template

Symptom: [exact visible behavior or error text]
Started: [date or event that preceded it]
Reproduction: [numbered steps, or “every launch”]
Windows: [version]
CPU / RAM: [model] / [amount]
GPU / VRAM: [model] / [amount]
Free storage: [amount]
Steam verification: [result]
Enshrouded version: [version shown by Steam]
Attachments: DxDiag, enshrouded.log, backup folder zip

7. Avoid unsupported “fixes” that can obscure the diagnosis

The available official material does not provide a universal graphics-setting tweak, driver version, registry edit, or hardware purchase that resolves every Enshrouded crash or black screen. Avoid presenting generic PC maintenance as a confirmed game fix.

• Do not buy RAM, a graphics card, or an SSD solely because the game crashes. Compare the published baseline first and diagnose the individual failure.
• Do not call a driver update a guaranteed solution. The AMD note is tied to a dated release and a specific intermittent launch-crash description.
• Do not infer that a successful Steam verification proves the GPU, display path, or Windows installation is healthy.
• Do not treat a multiplayer disconnect as proof of a black-screen or graphics-initialization problem.
• Do not claim that a historical hotfix proves the same issue is present in the current build. Current known-issue status requires current official patch or support information.

8. Use a symptom-based decision path

This table is a triage order, not a ranking of causes or a promise that one step has a particular success rate. The cause of an individual failure cannot be established from the symptom alone.

What can be concluded—and what remains unknown

The published requirements establish a baseline, Steam verification checks whether local files are complete, and the historical hotfix documents one graphics-initialization problem on older AMD cards. Network guidance applies once the game is running far enough to exhibit multiplayer symptoms. None of those sources supplies a current prevalence rate, a universal black-screen fix, or a ranked success rate for the troubleshooting steps.

If Enshrouded still fails after the checks above, the most useful next action is a complete report containing the exact behavior, reproduction path, hardware details, DxDiag, enshrouded.log, and backup folder. That gives support the information needed to distinguish an installation problem from a graphics initialization failure, an environment-specific crash, or a separate issue in the current build.

Quick Recap

Bestseller No. 1

Games Workshop - Warhammer 40,000 - Craftworlds Spiritseer

Games Workshop - Warhammer 40,000 - Craftworlds Spiritseer; Plastic multipart miniatures - assembly required - tools, paints and glue not included

$29.75

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

black screen fixesEnshroudedgame crashesPC gamingSteam troubleshooting