Fix HRESULT 0X000036FD: Side-by-side assembly error

What is HRESULT 0X000036FD and why you're seeing it

This error pops up when you try to open a program — often a game or business app — and Windows throws back "An error occurred. HRESULT error code: 0X000036FD." The full message says something like "could not be translated to a corresponding Win32 error code." That's Windows being unhelpful.

In plain language: the program needs a side-by-side assembly (a bunch of DLL and manifest files) that's either missing, corrupt, or the wrong version. This happens most often after a Windows update overwrites a key DLL, or when you install a new Visual C++ redistributable that conflicts with an older one.

The real fix is almost always repairing or reinstalling the Visual C++ runtimes and .NET Framework. I've seen this error dozens of times. Let's start with the most common cause.

Cause #1: Corrupt or missing Visual C++ Redistributable

About 70% of the time, this error is a bad Visual C++ install. You might have updated from 2015 to 2022, but the old 2015 files are still there and conflicted. Or a Windows update broke them.

Fix: Uninstall and reinstall all Visual C++ redistributables

1. Press Windows Key + R, type appwiz.cpl, hit Enter. The Programs and Features window opens.
2. Look for any entry that says "Microsoft Visual C++ 20XX Redistributable." You'll see versions from 2005 to 2022. Leave the 2022 one alone for now — we'll reinstall it last.
3. Right-click each older version (2015, 2017, 2019) and select Uninstall. Confirm any prompts. After each uninstall you should see the entry disappear from the list.
4. After uninstalling all older ones, right-click the 2022 version and choose Change. Then select Repair. Wait for it to finish — you'll see a green checkmark when done.
5. If you don't have the 2022 version, download it from Microsoft's official site. Run the installer and choose Repair, not Install.
6. Restart your computer. After reboot, try launching the program that gave the error.

If that didn't fix it, move to the second cause.

Cause #2: .NET Framework corruption

Another common trigger: a .NET update that didn't install right. The error shows up silently in Event Viewer under .NET runtime errors. You might not see it unless you check.

Fix: Run the .NET Framework Repair Tool

1. Download the Microsoft .NET Framework Repair Tool. It's a small exe file.
2. Right-click the downloaded file and select Run as administrator. A wizard starts.
3. Click Next. The tool scans your system. It takes 2-5 minutes. You'll see a progress bar.
4. If it finds issues, it offers to fix them. Click Apply this fix. After it finishes, you'll see a green checkmark and a "Restart now" button.
5. Restart. After reboot, test your program again.

If the error persists, do a manual .NET cleanup. Open Command Prompt as admin and run:

dism /online /cleanup-image /restorehealth
sfc /scannow

Let both finish. SFC takes about 15 minutes. If it finds corrupt files, it replaces them. Restart after SFC completes. Then test the program.

Cause #3: System file corruption from a recent update

Windows updates sometimes mess up the assembly cache. This is rarer — maybe 10% of cases — but when it happens, the error won't go away with just reinstall tools.

Fix: Repair the Windows side-by-side store manually

1. Open Command Prompt as administrator. Press Windows Key + X, choose Terminal (Admin) or Command Prompt (Admin).
2. Type this command and press Enter:

dism /online /cleanup-image /checkhealth

You'll see a message like "No component store corruption detected" or "The component store is repairable."

3. If repairable, run:

dism /online /cleanup-image /restorehealth

This downloads fresh files from Windows Update. It takes 10-20 minutes. Don't interrupt it. When it finishes, you'll see "The restoration completed successfully."

4. Now run SFC again:

sfc /scannow

5. After SFC finishes, restart. If the program still fails, try a clean boot to rule out third-party conflicts:

• Press Windows Key + R, type msconfig, hit Enter.
• Go to the Services tab. Check Hide all Microsoft services. Then click Disable all.
• Go to the Startup tab, click Open Task Manager. Disable all startup items.
• Click OK, restart. Test the program. If it works, enable services one by one to find the culprit.

Quick-reference table

Try them in this order. I bet the first one fixes it. If not, the .NET tool almost certainly will. The system file scan is your last resort — but it's saved my bacon more than once.