0X000036BA

SXS Thread Queries Disabled (0x000036BA) – Fix in Minutes

This error means Windows side-by-side (SxS) assembly queries are blocked, usually by a corrupt .dll or a tweak tool. Quick fix: clear the SxS store or disable a rogue startup tool.

1. Corrupt SxS Assembly Store (Most Common)

This is the culprit 90% of the time. Windows caches side-by-side assemblies in the C:\Windows\WinSxS folder. If a system file or a hotfix install leaves a broken manifest or a missing .dll, the SxS query thread gets disabled. You'll see the error when launching apps like Office, Adobe, or even Windows Explorer.

Don't bother manually deleting files — you'll break Windows. Use the built-in system tools:

  1. Open Command Prompt as admin (right-click Start → Command Prompt (Admin) or PowerShell (Admin)).
  2. Run DISM /Online /Cleanup-Image /RestoreHealth. Wait — it can take 10-15 minutes.
  3. After DISM finishes, run sfc /scannow. This checks and replaces corrupt system files.
  4. Reboot. If the error persists, run sfc /scannow again — sometimes it needs a second pass.

Real-world trigger: This happens a lot after a failed Windows Update or a manual registry tweak that goes wrong. I've seen it after someone used a 'debloater' script on Windows 10 22H2.

2. Startup Manager or Tweak Tool Blocking the Thread

Sometimes a third-party tool disables the SxS thread to 'optimize' performance. CCleaner, Razer Cortex, or any 'game booster' can do this. They often mess with the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide and set DisableThread to 1.

Check it manually:

  1. Press Win + R, type regedit, hit Enter.
  2. Go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide.
  3. Look for a DWORD named DisableThread. If it exists and is set to 1, double-click it and change to 0.
  4. If you don't see that key, create a new DWORD (32-bit) named DisableThread and set it to 0.
  5. Reboot.

Also: Open Task Manager, go to the Startup tab, and disable anything that looks like a 'cleaner' or 'optimizer'. Restart and test. Most people skip this step — don't. I've fixed this in 30 seconds by disabling Razer Cortex's startup entry.

3. Missing or Corrupt Microsoft Visual C++ Redistributables

If the first two fixes don't work, the SxS thread might be failing because a runtime .dll (like msvcp140.dll or vcruntime140.dll) is missing or corrupt. This is less common but easy to check.

Here's how to repair them:

  1. Go to Control Panel → Programs and Features.
  2. Look for 'Microsoft Visual C++' entries. You'll see about a dozen from 2005 to 2022.
  3. Right-click each one and select Change → Repair. Do this for all of them.
  4. If repair doesn't help, uninstall all of them and reinstall the latest all-in-one package from Microsoft's website. Search for 'Visual C++ Redistributable latest supported downloads'.
  5. Reboot.

Quick tip: Use the x64 and x86 installers — grab both. Even on a 64-bit system, some apps need the 32-bit runtime.

Quick-Reference Summary Table

CauseFixTime
Corrupt SxS storeRun DISM + SFC20 min
Startup tool blocking threadCheck registry DisableThread key, disable startup tools5 min
Missing VC++ runtimesRepair or reinstall all Visual C++ Redistributables15 min

Final word: If none of this works, you might be dealing with a corrupted user profile. Create a new local admin account and test. That's a last resort, but I've seen it twice in 14 years.

Related Errors in Windows Errors
0XC01A0014 Fix 0xC01A0014: Log Policy Already Installed 0X0000215A Active Directory 0X0000215A: Source Object Must Be Group or User 0X000002AE Fix ERROR_DLL_MIGHT_BE_INSECURE (0X000002AE) on Windows 0X0000045B Fix ERROR_SHUTDOWN_IN_PROGRESS (0X0000045B) on Windows

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.