clr-activation-debugging
Diagnoses .NET Framework CLR activation issues using CLR activation logs (CLRLoad logs) produced by mscoree.dll
Install / Use
npx skills add dotnet/skills --skill clr-activation-debuggingInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
MarketingSupported Platforms
Tags
Our assessment of clr-activation-debugging
clr-activation-debugging scores 93/100 on our quality scale, 130th of 642 Marketing skills we index (top 21%).
Its SKILL.md is 20 KB long, well organised into 30 sections with 5 code examples: a thorough specification that gives an agent plenty to work with.
With 5,471 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so clr-activation-debugging is actively maintained.
- Our last check on 2026-10-26 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-27. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
clr-activation-debugging compared with similar skills
All 4 of these similar skills score higher than clr-activation-debugging; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| clr-activation-debugging (this skill)by dotnet | 93 | 5.5k | 53d ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 149.0k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install clr-activation-debugging?
- Run
npx skills add dotnet/skills --skill clr-activation-debugging. The install tabs above show the steps for each supported agent. - Which AI agents does clr-activation-debugging work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is clr-activation-debugging safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is clr-activation-debugging still maintained?
- The repository was last updated about 2 months ago, so clr-activation-debugging is actively maintained.
Skill content
View source on GitHubname: clr-activation-debugging description: >- Diagnoses .NET Framework CLR activation issues using CLR activation logs (CLRLoad logs) produced by mscoree.dll. Use when: the shim picks the wrong runtime, fails to load any runtime, shows unexpected .NET 3.5 Feature-on-Demand (FOD) dialogs, unexpectedly does NOT show FOD dialogs, loads both v2 and v4 into the same process causing failures, or any time someone is wondering "what is happening with .NET Framework activation?" license: MIT
CLR Activation Debugging
Diagnose .NET Framework runtime activation issues by analyzing CLR activation logs (CLRLoad logs) produced by the shim (mscoree.dll). These logs record every decision the shim makes when selecting and loading a CLR version.
When to Use
- A process fails to load the CLR at all ("Unable to find a version of the runtime to use")
- The shim picks the wrong CLR version (e.g., v2.0 instead of v4.0)
- Unexpected .NET 3.5 Feature-on-Demand (FOD) install dialogs appear
- FOD dialogs are expected but do NOT appear
- Both CLR v2 and CLR v4 load into the same process, causing failures
- A COM object fails to activate because the shim can't resolve the runtime
- Legacy hosting APIs (CorBindToRuntime) bind to an unexpected version
When Not to Use
- Modern .NET (CoreCLR / .NET 5+) — this skill covers .NET Framework only (the mscoree.dll shim)
- Assembly binding failures — use Fusion logs (fuslogvw.exe), not CLR activation logs
- Runtime crashes after the CLR has loaded — activation succeeded; the problem is elsewhere
Background
The Shim Architecture
The .NET Framework shim has two layers:
- mscoree.dll (the "shell shim") — the public-facing DLL that is the registered
InprocServer32for CLR-hosted COM objects and the entry point for_CorExeMain, legacy APIs, etc. - mscoreei.dll — the actual shim implementation where the runtime selection logic, logging, and activation decisions live. mscoree.dll forwards into mscoreei.dll.
When reading logs, the caller-name:mscoreei.dll in FOD command lines reflects this — it's mscoreei.dll doing the work.
.NET 3.5 / v2.0.50727 Version Mapping
.NET 2.0, 3.0, and 3.5 all share the same CLR runtime version: v2.0.50727. The "3.0" and "3.5" releases were library additions on top of CLR v2.0. For activation purposes, they are all "v2.0.50727." When the shim resolves to v2.0.50727 or FOD offers to install "NetFx3", it's installing the CLR v2.0 runtime (plus the 3.0/3.5 libraries). Similarly, CLR v4.0 (v4.0.30319) covers all .NET Framework versions from 4.0 through 4.8.x.
.NET 3.5 Availability on Recent Windows
On recent Windows versions (Windows 11 Insider Preview Build 27965 and future platform releases), .NET Framework 3.5 is no longer available as a Windows optional component (Feature-on-Demand). It must be installed from a standalone MSI. This means the FOD dialog (fondue.exe /enable-feature:NetFx3) will not succeed on these systems even if it fires. On Windows 10 and Windows 11 through 25H2, FOD remains available. .NET Framework 3.5 reaches end of support on January 9, 2029.
Shim HRESULT Codes
When the shim fails, it returns specific HRESULTs in the 0x8013xxxx range. These are the errors you'll see from callers (not in the activation logs themselves, which log human-readable messages):
| HRESULT | Symbol | Meaning |
|---------|--------|---------|
| 0x80131700 | CLR_E_SHIM_RUNTIMELOAD | Cannot find or load a suitable runtime version. This is the most common shim error — it's what callers see when capped legacy activation fails on a v4-only machine. |
| 0x80131701 | CLR_E_SHIM_RUNTIMEEXPORT | Found a runtime but failed to get a required export or interface from it. |
| 0x80131702 | CLR_E_SHIM_INSTALLROOT | The .NET Framework install root is missing or invalid in the registry. |
| 0x80131703 | CLR_E_SHIM_INSTALLCOMP | A required component of the installation is missing. |
| 0x80131704 | CLR_E_SHIM_LEGACYRUNTIMEALREADYBOUND | A different runtime is already bound as the legacy runtime. A legacy API tried to bind to a version that conflicts with the one already chosen. |
| 0x80131705 | CLR_E_SHIM_SHUTDOWNINPROGRESS | The shim is shutting down and cannot service the request. |
If a user reports one of these HRESULTs (especially 0x80131700), CLR activation logs are the right diagnostic tool.
Prerequisites
CLR activation logging must be enabled to produce log files. If the user doesn't have logs yet, instruct them to enable logging:
Via environment variable (recommended — scoped to current session):
set COMPLUS_CLRLoadLogDir=C:\CLRLoadLogs
Via registry (machine-wide — affects all .NET Framework processes):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework
CLRLoadLogDir = "C:\CLRLoadLogs" (REG_SZ)
On 64-bit systems, also set under Wow6432Node if 32-bit processes are involved.
⚠️ The log directory must already exist. The shim will not create it. If it doesn't exist, no logs will be written and there will be no error or indication of failure.
Logs are written as {ProcessName}.CLRLoad{NN}.log (NN = 00–99, one per process instance). Logs cannot be read until the process exits — the file is held open.
After capturing, remove the env var or registry key to stop logging.
Inputs
| Input | Required | Description |
|-------|----------|-------------|
| CLR activation log files | Yes | One or more .CLRLoad*.log files |
| Symptom description | Recommended | What the user observed (FOD dialog, wrong runtime, failure, etc.) |
| Expected behavior | Recommended | What the user expected to happen |
Workflow
Step 1: Load Reference Material
Resolve bundled paths from the directory that contains this SKILL.md, not from the user's workspace. Load the reference files in this order — they contain the detailed log format, decision flow, and CLSID registry documentation:
references/log-format.md— Log line format, fields, and all known log message typesreferences/activation-flow.md— The shim's decision tree for runtime selectionreferences/com-activation.md— COM (DllGetClassObject) activation specifics, CLSID registry layout
If a direct read fails, list this skill's references/ directory once and retry only when the listing shows the expected file. Do not use workspace file or text search to locate the skill installation.
If one or more expected reference files remain unavailable, use the loaded references where possible and the inline knowledge below for the missing coverage. Include Reference coverage: reduced; unavailable: <paths>; used inline guidance for missing references. in the final diagnosis, with <paths> replaced by the missing relative paths.
Step 2: Survey the Log Files
Get the big picture before diving into any single log:
- List all log files and group by process name — this shows which executables triggered CLR activation
- For each process, scan for outcome lines:
Decided on runtime: vX.Y.Z— successful resolutionERROR:— failed resolutionLaunching feature-on-demand— FOD dialog was shownCould have launched feature-on-demand— FOD would have fired but was suppressedV2.0 Capping is preventing consideration— v4+ was skipped due to capping
grep -l "ERROR:\|Launching feature-on-demand\|Could have launched" *.log
grep -c "Launching feature-on-demand" *.log
- Build a summary table:
| Process | Log Files | Outcome | Runtime Selected | FOD? | |---------|-----------|---------|-----------------|------| | ... | ... | ... | ... | ... |
Step 3: Analyze Problematic Logs
For each log file with an unexpected outcome, trace the full activation flow. Read the log top-to-bottom and identify:
⚠️ Nested log entries: The shim's own internal calls can trigger additional log entries within an activation sequence that is already being logged. For example, a
DllGetClassObjectcall may internally callComputeVersionString, which callsFindLatestVersion, each generating log lines. When the FOD check runs ("Checking if feature-on-demand installation would help"), it re-runs the entire version computation — producing a secondComputeVersionStringblock within the same activation. Don't mistake these nested/re-entrant entries for separate activation attempts.
3a. Entry Point
The first FunctionCall: or MethodCall: line tells you how activation was triggered:
| Entry Point | Meaning |
|-------------|---------|
| _CorExeMain | Managed EXE launch — the binary IS a .NET assembly |
| DllGetClassObject. Clsid: {guid} | COM activation — something CoCreated a COM class routed through mscoree.dll |
| ClrCreateInstance | Modern (v4+) hosting API |
| CorBindToRuntimeEx | Legacy (v1/v2) hosting API — binds the process to one runtime |
| ICLRMetaHostPolicy::GetRequestedRuntime | Policy-based hosting API (often called internally after other entry points) |
| LoadLibraryShim | Legacy API to load a framework DLL by name |
3b. Input Parameters
Immediately after the entry point, the log dumps the version computation inputs:
IsLegacyBind: Is this a legacy (pre-v4) activation path? If 1, the shim uses the single-runtime "legacy" view of the world. Legacy APIs (CorBindToRuntimeEx,DllGetClassObjectfor legacy COM,LoadLibraryShim, etc.) set this.IsCapped: If 1, the shim's roll-forward semantics are capped at Whidbey (v2.0.50727) — it will NOT consider v4.0+ when enumerating installed runtimes. This is the mechanism that makes v4 installation non-impactful: legacy codepaths continue to behave as if v4 doesn't exist. On a v4-only machine with no .NET 3.5, a capped enumeration sees no runtimes at all. Capping does NOT prevent loading v4+ if a specific v4 version string is explicitly provided (e.g., viaCorBindToRuntimeEx("v4.0.30319", ...)or via config withuseLegacyV2RuntimeActivationPolicy).SkuCheckFlags: Controls SKU (edition) compatibility checking.ShouldEmulateExeLaunch: Whether to pretend this is an EXE launch for policy purposes.LegacyBindRequired: Whether a legacy bind is strictly required.
3c. Config File Processing
Look for config file parsing results:
Parsing config file: {path}— the shim is looking for a.configfileConfig File (Open). Result:00000000— config file found and opened successfullyConfig File (Open). Result:80070002— config file not found (HRESULT for ERROR_FILE_NOT_FOUND)Found config file: {path}— config was successfully readUseLegacyV2RuntimeActivationPolicy is set to {0|1}— whether<startup useLegacyV2RuntimeActivationPolicy="true">is present. When 1, all runtimes are treated as candidates for legacy codepaths — meaning legacy shim APIs can enumerate and choose v4+. This can be used with multiple<supportedRuntime>entries, with other config options, or even with no<supportedRuntime>entries at all (in which case legacy APIs can simply enumerate v4). Side effect: turns off in-proc SxS with pre-v4 runtimes — locks them out of the process.Config file includes SupportedRuntime entry. Version: vX.Y.Z, SKU: {sku}— each<supportedRuntime>found in config
Key insight: If a process has no config file AND is doing a capped legacy bind, the shim has nothing to direct it to v4.0. It will enumerate installed runtimes (capped to ≤v2.0), find nothing if 3.5 isn't installed, and fail. This is by design — v4 is intentionally invisible to these codepaths to keep v4 installation non-impactful.
3d. Version Resolution
Installed Runtime: vX.Y.Z. VERSION_ARCHITECTURE: N— what's installed on the machine{exe} was built with version: vX.Y.Z— version from the binary's PE header (managed assemblies only; native EXEs won't have this)Using supportedRuntime: vX.Y.Z— the shim picked a version from the config's `<supportedRu
Truncated for display — read the full file on GitHub.
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
149.0kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
