Bug Check 0x00000085: SETUP_FAILURE – Windows Setup Fatal Error

Quick Answer

Windows Bug Check 0x00000085 (SETUP_FAILURE) indicates that a fatal error occurred during Windows setup. Microsoft documents several possible failure categories, including invalid OEM HAL font files, video initialization failures, insufficient memory, keyboard initialization failures, unresolved ARC device paths, and partitioning sanity-check failures.

The first bug-check parameter identifies the failure category. Parameters 2 and 3 provide additional information for certain failures, while Parameter 4 is unused. The correct troubleshooting procedure depends on these values and the installation environment. This is a legacy Windows bug-check definition rather than a typical modern Windows installation error.

What Is SETUP_FAILURE 0x00000085?

SETUP_FAILURE is a Windows bug check with the hexadecimal value 0x00000085 (decimal 133). It represents a fatal error encountered during the Windows setup process.

Microsoft's documentation describes this error in the context of older Windows setup environments. Several conditions that previously caused setup to stop with a bug check are handled through more descriptive error messages in later setup technologies. Therefore, this code should not automatically be treated as a common Windows 10 or Windows 11 installation problem.

The error can relate to the initialization of essential setup components, including display hardware, keyboard devices, memory, boot-device paths, and storage drivers.

SETUP_FAILURE Bug Check Parameters

The bug check uses four parameters. Parameter 1 identifies the type of failure, and the interpretation of Parameters 2 and 3 depends on its value.

Parameter 4 is not used. The documented parameter combinations should be interpreted according to Microsoft's bug-check reference.

Parameter 1 = 0x0: Invalid OEM HAL Font

This condition occurs when the OEM Hardware Abstraction Layer (HAL) font is not a valid .fon format file. Windows Setup cannot display text using the invalid font file.

Microsoft identifies a damaged Vgaxxx.fon file on the boot floppy disk or CD as a possible cause. This is associated with legacy installation environments.

Parameter 1 = 0x1: Video Initialization Failure

This condition indicates that Windows Setup could not initialize the video subsystem.

Parameter 2 identifies the operation that failed:

Parameter 3 contains the NT API status code when applicable.

Microsoft identifies possible causes such as a damaged disk containing Vga.sys or another appropriate video driver, or video hardware that Windows cannot communicate with.

Parameter 1 = 0x2: Out of Memory

This parameter identifies an out-of-memory condition during setup.

It does not independently establish that a physical RAM module is defective. The available memory, installation environment and hardware configuration should be investigated before replacing components.

Parameter 1 = 0x3: Keyboard Initialization Failure

This condition indicates that Windows Setup could not initialize the keyboard subsystem.

Parameter 2 identifies the failure:

• 0: NtCreateFile could not open \device\KeyboardClass0. Setup did not find a connected keyboard.
• 1: The keyboard layout DLL could not be loaded. Microsoft gives Kbdus.dll as an example for the US release.

Microsoft also identifies possible problems involving the keyboard drivers I8042prt.sys and Kbdclass.sys, keyboard hardware communication, or missing keyboard layout files.

Parameter 1 = 0x4: ARC Device Path Resolution Failure

This condition occurs when Windows Setup cannot resolve the ARC (Advanced RISC Computing) device path of the device from which setup was started.

Microsoft classifies this as an internal setup error. It should not automatically be interpreted as evidence of a physically damaged storage device.

Parameter 1 = 0x5: Partitioning Sanity-Check Failure

This parameter indicates that a partitioning sanity check failed. Microsoft identifies this condition as a bug in a disk driver.

Investigate the storage-controller driver and installation environment. Do not immediately delete partitions, format the disk or replace the storage device.

Possible Causes of SETUP_FAILURE

The actual cause depends on the first bug-check parameter. The following are the documented failure categories and their corresponding investigation areas.

These are not interchangeable causes. Identifying the parameter values is essential before selecting a troubleshooting method.

How to Troubleshoot Windows Bug Check 0x00000085

1. Record the Complete Error Parameters

Before attempting repairs, record the complete bug-check information:

• Bug check code: 0x00000085.
• Bug check name: SETUP_FAILURE.
• Parameter 1.
• Parameter 2.
• Parameter 3.
• Windows version and installation media details.
• The stage at which setup stopped.

Parameter 1 is the most useful starting point because it identifies the documented failure category.

2. Check the Installation Media

If the error occurs while starting Windows Setup from USB or optical media, check the installation source.

1. Inspect the USB drive or optical disc for physical damage.
2. Reconnect the USB drive and try another working USB port.
3. Where possible, recreate the installation media using Microsoft's official installation resources.
4. Check that the installation image matches the intended Windows edition and system architecture.
5. Test with another known-good USB drive if the problem continues.

These checks can help eliminate damaged or incomplete installation media. They are particularly relevant when setup cannot load required legacy files.

Official resources:

• Download Windows 11
• Download Windows 10

3. Troubleshoot Video Initialization

If Parameter 1 is 0x1, investigate the display subsystem.

1. Check the monitor, display cable and graphics connections.
2. Reconnect the display cable and test another supported display output if available.
3. Check whether a dedicated graphics card is properly installed.
4. Where supported, test the computer's integrated graphics configuration.
5. Remove unnecessary display adapters or conversion devices during the installation test.
6. Check the computer manufacturer's documentation for supported graphics configurations.

If Parameter 2 identifies a particular failed video operation, use it to narrow the investigation. For example, a failure to set a display mode is different from a failure to open the video device.

Do not randomly install or remove graphics drivers without evidence identifying a driver compatibility problem.

4. Investigate Memory Problems

If Parameter 1 is 0x2, investigate memory availability and the hardware configuration.

1. Check the installed RAM capacity against the computer manufacturer's specifications.
2. Check whether recently installed memory is compatible with the motherboard.
3. Run the manufacturer's memory diagnostic utility, if available.
4. Check for memory-related errors in available diagnostic records.
5. If physical memory testing reports errors, follow the manufacturer's service instructions.

An out-of-memory parameter does not automatically mean that RAM must be replaced. Additional diagnostic evidence is required.

5. Troubleshoot Keyboard Initialization

If Parameter 1 is 0x3, check the keyboard connection and initialization environment.

1. Disconnect and reconnect the keyboard.
2. Try another USB port.
3. Test using a known-working wired USB keyboard.
4. Check whether the selected keyboard layout is appropriate for the installation media.
5. If a layout DLL is missing or damaged, recreate the installation media from an official source.

For legacy systems, consult the computer manufacturer's documentation before changing keyboard-controller or firmware settings.

6. Check the Boot Device Configuration

If Parameter 1 is 0x4, investigate the device and environment used to start Windows Setup.

• Confirm that the intended installation device is selected in the boot menu.
• Check whether the installation media is detected consistently.
• Review recent boot configuration or storage-controller changes.
• Check the installation environment for device-path or boot-device errors.

Since Microsoft identifies this as an internal setup error, collect the relevant logs and complete bug-check parameters before making boot configuration changes.

7. Investigate Storage and Partitioning

If Parameter 1 is 0x5, investigate the storage subsystem.

1. Check whether BIOS/UEFI detects the intended SSD or hard drive.
2. Check the storage-controller configuration against the manufacturer's documentation.
3. Review recent storage driver or firmware changes.
4. Obtain compatible storage-controller drivers from the computer or motherboard manufacturer's official support website when necessary.
5. Review Windows Setup logs for storage and driver initialization errors.

Locate Windows Setup Log Files

Windows Setup maintains diagnostic logs that can help identify the operation that failed. The available locations depend on the setup stage and Windows environment.

The X: drive commonly represents the temporary RAM drive used by Windows PE. It is not necessarily the drive containing the installed Windows operating system.

Important Setup Logs

• setupact.log: Records Windows Setup activities.
• setuperr.log: Records setup errors.
• setupapi.dev.log: Records device and driver installation activity in applicable environments.

Look for the last relevant operations before the failure. An error in a log does not automatically establish the root cause. Compare its timestamp and operation with the bug-check parameters.

For further information, consult Microsoft's Windows Setup Log Files and Event Logs documentation.

Analyze a Crash Dump Using WinDbg

IT support technicians and system administrators can use Windows Debugger (WinDbg) to examine an available crash dump.

Requirements

• A suitable Windows crash dump file.
• WinDbg installed on a diagnostic computer.
• Access to appropriate debugging symbols.
• Basic familiarity with Windows debugging.

Analysis procedure

1. Install and open WinDbg on a diagnostic computer.
2. Open the crash dump using the File and Open Crash Dump options.
3. Allow the debugger to load the necessary symbols.
4. Enter the following command in the debugger command window.

!analyze -v

This command requests a detailed analysis of the bug check and available crash information.

To display the bug-check code and parameters, use:

.bugcheck

Review the bug-check parameters, stack information and available diagnostic evidence together. A module name appearing in a crash report does not independently prove that the module caused the failure.

Microsoft documentation:

• Analyze a Kernel-Mode Dump File Using WinDbg
• !analyze command reference

Use SetupDiag for Windows Upgrade Problems

For Windows feature-upgrade failures, Microsoft's SetupDiag utility can analyze setup logs and identify patterns associated with known installation problems.

SetupDiag is intended for supported Windows Setup diagnostic scenarios. It should not be considered a guaranteed solution or a replacement for analyzing the legacy 0x00000085 bug-check parameters.

For example, after downloading SetupDiag and collecting the relevant logs into C:\Temp\WindowsSetupLogs, an administrator can run:

SetupDiag.exe /LogsPath "C:\Temp\WindowsSetupLogs" /Output "C:\Temp\SetupDiag-Results.txt"

Ensure the executable and log directory exist and that the paths correspond to the diagnostic computer. The command analyzes logs and writes a report; it does not repair Windows or modify the installation.

Refer to Microsoft's Deployment Troubleshooting and Log Files documentation.

How to Verify the Problem Is Resolved

After applying a corrective action based on the identified failure, verify the installation result.

• Restart the setup process using the corrected installation environment.
• Confirm that the previously failing initialization stage completes.
• Check that Windows proceeds to the next installation stage.
• Review setup logs if the failure occurs again.
• Record the complete parameters if another bug check appears.

If the same failure continues, compare the new diagnostic information with the original logs instead of repeating unrelated troubleshooting steps.

When to Contact a Technician

Professional assistance may be appropriate when:

• Memory diagnostics report hardware errors.
• The storage device is intermittently detected or reports hardware faults.
• The video subsystem cannot initialize with a supported configuration.
• The computer repeatedly crashes during setup despite verified installation media.
• Storage-controller, firmware or partitioning changes require specialist attention.
• Important data must be recovered or preserved before installation.

Provide the complete bug-check parameters, Windows version, installation stage and relevant setup logs. Remove passwords, recovery keys and other confidential information before sharing diagnostic files.

Frequently Asked Questions

What does Windows error 0x00000085 mean?

It identifies the SETUP_FAILURE bug check, which indicates a fatal error during Windows setup.

Is SETUP_FAILURE always caused by faulty hardware?

No. Microsoft's documented failure categories also include damaged setup files, video or keyboard initialization failures, insufficient memory, internal setup errors and disk-driver problems.

What is the most important parameter in bug check 0x85?

Parameter 1 is the starting point because it identifies the failure category. Parameters 2 and 3 provide additional information for certain categories.

Does SETUP_FAILURE mean my SSD or hard drive is damaged?

No. Parameter 1 value 0x5 identifies a partitioning sanity-check failure associated with a disk-driver bug. It does not establish that the physical storage device is defective.

Can faulty RAM cause SETUP_FAILURE?

Microsoft documents Parameter 1 value 0x2 as an out-of-memory condition. This does not independently prove that a physical RAM module is faulty. Memory diagnostics and additional evidence are necessary.

Can reinstalling Windows fix error 0x00000085?

Reinstallation is not a universal solution. Investigate the actual setup, driver, memory, video, keyboard or storage problem first. Reinstallation and partition changes can also result in data loss.

Where are Windows Setup error logs stored?

Common locations include X:\Windows\Panther\ and %WINDIR%\Panther\. The correct location depends on the installation stage and environment.

Is SETUP_FAILURE 0x85 common in Windows 10 and Windows 11?

It is a legacy bug-check definition. Modern Windows Setup generally uses more descriptive installation errors and diagnostic logs. The documented code should not be assumed to represent a typical modern Windows installation failure.

Sources

• Microsoft Learn – Bug Check 0x85: SETUP_FAILURE
• Microsoft Learn – Windows Setup Log Files and Event Logs
• Microsoft Learn – Analyzing a Kernel-Mode Dump File with WinDbg
• Microsoft Learn – !analyze Command Reference
• Microsoft Learn – Deployment Troubleshooting and Log Files
• Microsoft – Windows 11 Download