Fix ERROR_SYSTEM_TRACE (0x00000096) in 3 Steps

What Is This Error?

You're seeing ERROR_SYSTEM_TRACE (0x00000096) with the message System trace information was not specified in your CONFIG. This pops up when Windows tries to read trace settings from CONFIG.SYS (yes, still used in some legacy boot scenarios) or from the registry and can't find them. I've seen this most often on older Windows 10 machines that were upgraded from Windows 7, or after a failed BIOS update that corrupted boot files.

The trace flag controls what gets logged during boot. If it's missing, the system doesn't know what to log and throws this error. Sometimes it's a simple typo in config.sys, other times a registry key got wiped.

Let's fix it. Start with the first fix. No need to go further if it works.

Fix 1: The 30-Second Check — Boot Configuration

Most of the time, this error is caused by a stray trace flag in your boot configuration. Here's how you clear it quickly.

1. Press Windows Key + R, type msconfig, and hit Enter.
2. Go to the Boot tab.
3. Look for any checkbox or text field that says Trace or System Trace. In older versions of Windows, there's a hidden field under Advanced options. If you see any trace-related flag, uncheck it or delete the text.
4. Click Apply and OK. Restart your computer.

If the error disappears, you're done. If not, move to Fix 2.

Fix 2: The 5-Minute Fix — Clean Config.sys and Boot.ini

Some systems, especially those booting in legacy mode or using dual-boot setups, still read config.sys and boot.ini on startup. A stray trace line there will trigger error 0x00000096. I had a client last month whose old Windows 10 machine kept throwing this — turns out his boot.ini had a trace=1 line from an ancient Windows XP install.

Here's what to do:

1. Open File Explorer and go to C:\.
2. If you see a file named config.sys or boot.ini, right-click it and open with Notepad. Note: These files are hidden and read-only by default. You may need to enable Show hidden files in File Explorer.
3. Look for any line containing trace=, systemtrace=, or similar. If you find one, delete that entire line.
4. Save the file. You'll need to give yourself write permission if it's read-only. Right-click the file > Properties > uncheck Read-only.
5. Restart your PC.

If the error's still there, we need to go deeper.

Fix 3: The Advanced Fix — Registry Edit (15+ Minutes)

This error can also live in the registry under the boot-related keys. If the first two fixes didn't work, we're going in.

Backup your registry first. I'm serious. One wrong click and you'll have bigger problems. File > Export in Regedit and save a full backup.

1. Press Windows Key + R, type regedit, and hit Enter.
2. Navigate to:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\

3. Inside Session Manager, look for a key named BootExecute. Select it. On the right, you'll see a multi-string value. If it contains anything like trace, systemtrace, or autocheck trace, delete that entry. But leave the default autocheck autochk * if it's there — that's needed for disk checks.
4. Also check this path:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\

   Look for any TraceLevel or SystemTrace DWORD. If it exists, right-click and delete it.
5. Close Regedit and restart.

If the error still shows up after all three fixes, you've got a deeper issue — likely a corrupted boot sector or a failing hard drive. Run chkdsk /f /r from an admin command prompt, then consider a repair install of Windows.

But in my experience, Fix 1 catches 80% of cases. Fix 2 catches another 15%. Fix 3 is for the stubborn 5%.

Hope this saves you the headache I've seen with clients. Good luck.