What does Windows error code 150 (ERROR_SYSTEM_TRACE) mean?

ERROR_SYSTEM_TRACE

What ERROR_SYSTEM_TRACE means

ERROR_SYSTEM_TRACE is Win32 system error code associated with the documented message: “System trace information was not specified in your CONFIG.SYS file, or tracing is disallowed.” The significant condition is that a legacy tracing facility was requested without the configuration or privilege state expected by that subsystem.

The message describes a historical boot and compatibility contract. Modern Windows tracing is configured through different facilities, so applying contemporary ETW advice directly would be misleading.

Likely causes

• a DOS or OS/2-era utility expects CONFIG.SYS trace directives that are absent
• the program runs under a compatibility environment that does not expose the tracing service
• policy or emulator settings deliberately disable low-level system tracing

Troubleshooting steps

1. Identify the executable format and the compatibility layer that launched it
2. Inspect the program documentation for required CONFIG.SYS or emulator directives
3. Repeat the operation in a supported environment rather than modifying modern Windows boot configuration blindly

Code-specific investigation notes

The reference to CONFIG.SYS is a strong age indicator. Native 64-bit Windows applications do not enable ETW or WPP tracing through CONFIG.SYS, so an ETW session list is not a direct diagnostic for this condition.

Preserve the original utility and its documentation before attempting compatibility changes. Some historical trace programs required a specific DOS extender or virtual device, not merely a configuration line.

If the software is business-critical, an isolated virtual machine matching the supported OS is safer and more reproducible than weakening the host configuration.

Example

A diagnostic utility written for a historical DOS configuration is started under a current compatibility environment. Its required trace facility is absent and it reports it.

Difference from related errors

It is tied to historical execution environments; it should not be confused with modern Event Tracing for Windows failures, which use different APIs and status codes.

References

• Microsoft: System error codes 0–499