Fix it now
This one happens at launch, not at install. Microsoft publishes 14001 as ERROR_SXS_CANT_GEN_ACTCTX and its message tells you where to look: the application event log, or the sxstrace tool. The executable’s manifest asked for a shared assembly version the machine cannot supply.
sxstrace trace -logfile:%temp%\sxs.etl
sxstrace parse -logfile:%temp%\sxs.etl -outfile:%temp%\sxs.txt
notepad %temp%\sxs.txt
- Before tracing, check Event Viewer: Windows Logs, Application, entries from the SideBySide source at the time of the failure. They usually name the assembly and version outright.
- If you do trace, stop it by pressing Enter in the sxstrace window when the application has failed. Do not use Ctrl+C – it leaves the session running and can produce a log that parses to nothing. If a previous trace was interrupted, clear it with
sxstrace stoptracefirst. - Read the parsed output for the assembly name and version being requested.
- Install the matching Visual C++ redistributable in the same architecture as the application, then start it again.
Add -filter:<appname> to the parse command to cut the output down to one application. On a busy machine the unfiltered log is long enough to hide the answer.
If the application starts, you are finished. If the trace names an assembly you have already installed, the next section explains what else the loader checks.
Why it happens
Applications built with Microsoft toolchains do not simply load a DLL by name. They declare the assembly they need, with a version and a publisher identity, in a manifest embedded in the executable or placed beside it. At start-up Windows reads that manifest, resolves each dependency against the machine’s store of shared assemblies, and builds an activation context describing exactly which files the process will use.
14001 is that step failing. Microsoft publishes it as ERROR_SXS_CANT_GEN_ACTCTX, and the message text is unusually helpful for a Windows error because it names the two places to look: the application event log and sxstrace. No activation context could be built, so the process cannot start, and none of the application’s own code has run – which is why reinstalling the application rarely helps.
The neighbouring codes narrow the fault. 14002 is ERROR_SXS_INVALID_ACTCTXDATA_FORMAT, published as “The application binding data format is invalid” – a malformed or damaged manifest rather than a missing runtime. 14003 is ERROR_SXS_ASSEMBLY_NOT_FOUND, “The referenced assembly is not installed on your system”, which is the straightforward missing-prerequisite case.
The 0xC015 codes are the same conditions reported by the loader rather than by the Win32 layer. 0xC0150002 is STATUS_SXS_CANT_GEN_ACTCTX and 0xC0150004 is STATUS_SXS_ASSEMBLY_NOT_FOUND, so a dialog quoting one of those maps onto 14001 and 14003 respectively. If you have the NTSTATUS form, translate it and carry on.
The required redistributable is not installed
You have this one if The SideBySide event or the trace names an assembly and version, and no matching entry appears in the installed programs list.
- Note the assembly family and version from the event or trace.
- Install the matching Visual C++ redistributable from Microsoft.
- Install both architectures if the machine runs a mixture of 32-bit and 64-bit applications.
- Start the application again.
These redistributables are published by Microsoft at no cost. Nothing about this error is a licensing matter.
Only the wrong architecture is installed
You have this one if A 32-bit application fails while 64-bit applications using the same runtime family start normally.
- Check the installed programs list and note whether the redistributable entries are X86, X64 or both.
- Install the missing architecture from Microsoft. A 32-bit process resolves against the 32-bit assemblies whatever the operating system is.
- Restart the application; a reboot is not usually needed unless the application registers a service.
The installed runtime is damaged
You have this one if The redistributable is listed, of the right family and architecture, and the application still will not start.
- Open the entry in Settings, Apps, Installed apps and use the repair option the redistributable offers.
- If repair is unavailable or fails, remove the entry and install a fresh copy from Microsoft.
- Run
sfc /scannow, and if it reports problems,DISM /Online /Cleanup-Image /RestoreHealthbefore reinstalling.
The application’s own manifest or private assembly is wrong
You have this one if The trace reports invalid binding data, or the application ships its runtime beside the executable and that folder is incomplete.
- Reinstall the application from a clean download; a partial copy leaves a private assembly folder missing files.
- If the application was copied from another machine rather than installed, install it properly. Copied folders frequently lose the manifest folders they depend on.
- Where the fault is in the application’s own build, send the parsed trace to the vendor – only they can correct the manifest.
Full reference
The codes, in both forms
| Win32 | Name | NTSTATUS | Published meaning |
|---|---|---|---|
| 14001 | ERROR_SXS_CANT_GEN_ACTCTX | 0xC0150002 | The application has failed to start because its side-by-side configuration is incorrect. See the application event log or use sxstrace.exe for more detail |
| 14002 | ERROR_SXS_INVALID_ACTCTXDATA_FORMAT | – | The application binding data format is invalid |
| 14003 | ERROR_SXS_ASSEMBLY_NOT_FOUND | 0xC0150004 | The referenced assembly is not installed on your system |
| 14004 | ERROR_SXS_MANIFEST_FORMAT_ERROR | – | The manifest file does not begin with the required tag and format information |
| 14005 | ERROR_SXS_MANIFEST_PARSE_ERROR | – | The manifest file contains one or more syntax errors |
14004 and 14005 are worth having in view because they turn the diagnosis around completely. Both describe a manifest that is malformed rather than a machine that is missing something, which means the answer is with whoever built the application and no runtime will fix it.
Running a trace that produces a readable log
| Command | What it does |
|---|---|
sxstrace trace -logfile:<file> |
Starts recording activation context resolution and prompts you to stop |
sxstrace trace -logfile:<file> -nostop |
Records without prompting, for scripted capture |
sxstrace stoptrace |
Stops a trace that was not stopped before |
sxstrace parse -logfile:<file> -outfile:<file> |
Converts the recording into readable text |
sxstrace parse ... -filter:<appname> |
Restricts the output to one application |
Stop the trace by answering its prompt, or with the stoptrace verb. Killing sxstrace with Ctrl+C does not close the trace session cleanly, and the usual result is a log that parses to nothing while a session is still running in the background.
Reading the parsed output
The parsed file reads as a sequence of resolution attempts. Look for the line that begins a dependency resolution, the identity it is looking for – name, version, processor architecture and public key token – and the line that reports the outcome. The version and architecture on the failing identity are the two values that decide what you install. Everything else in the file is context.
Version and architecture both have to match
Microsoft’s C and C++ runtimes have shipped as a series of redistributables, and an application binds to a specific family. Microsoft’s current guidance is that Visual Studio 2017 and later share the same redistributable files, and that the Redistributable installed must be the same version as, or later than, the build tools used to build the application. That covers modern applications; an application built against an earlier family still needs that family present.
- Architecture is strict. A 32-bit process resolves against 32-bit assemblies whatever the operating system is, so it needs the X86 package.
- Microsoft notes that the X64 Redistributable package contains both ARM64 and X64 binaries, which is what you want on an ARM64 device.
- Installing the newest package does not retire the need for an older family, only for older versions within the same family.
- A private assembly shipped in the application’s own folder bypasses the store entirely, and an incomplete copy of that folder produces the same error.
- If the machine has been imaged, check that the image actually included the runtimes rather than assuming it did.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
14001 |
ERROR_SXS_CANT_GEN_ACTCTX: the activation context could not be generated, so the side-by-side configuration is incorrect | Microsoft Learn |
14002 |
ERROR_SXS_INVALID_ACTCTXDATA_FORMAT: the application binding data format is invalid | Microsoft Learn |
14003 |
ERROR_SXS_ASSEMBLY_NOT_FOUND: the referenced assembly is not installed on the system | Microsoft Learn |
0xC0150002 |
STATUS_SXS_CANT_GEN_ACTCTX: the loader’s form of the same failure as 14001 | Microsoft Learn |
0xC0150004 |
STATUS_SXS_ASSEMBLY_NOT_FOUND: the loader’s form of the same failure as 14003 | Microsoft Learn |
Confirm the fix worked
- Start the application and confirm it opens without the side-by-side error.
- Check the Application event log and confirm no new SideBySide entries appear after the launch.
- Confirm the redistributable now appears in the installed programs list in the architecture you needed.
- Reboot and launch the application once more, so you know the fix survives a restart.
- Run a fresh trace and confirm the dependency that previously failed now resolves.
Questions people ask about this
Do I need to buy anything?
No. Every Visual C++ redistributable is a free download from Microsoft, and installing one does not affect your Windows licence or activation. If a website offers to sell you a fix for this error, it is selling you a free file.
How do I stop an sxstrace capture?
Press Enter in the sxstrace window when prompted, or run sxstrace stoptrace if the trace was interrupted. Do not use Ctrl+C: it ends the process without closing the trace session cleanly, and the log often parses to nothing.
Should I download the missing DLL from a file site?
No. Individual DLLs from third-party sites are a well-known malware vector, and even a clean one will not resolve correctly because the loader resolves the assembly through the store rather than by file name. Install the proper redistributable.
Will installing the newest redistributable cover the older ones?
Within a family, yes – Microsoft’s rule is that the installed Redistributable must be the same version or later than the build tools used. Across families, no: an application built against an earlier family still needs that family installed. The trace tells you which.
Why did this start after an update?
Usually because something removed or replaced a runtime the application quietly depended on, or the application was upgraded to a build needing a newer runtime than the machine has. The trace shows which version is now being asked for.
