Summary
Optimize Windows startup path by reducing registry probe overhead for VC++ runtime detection.
Why
Module import currently performs registry checks that add cold-start latency. Successful native initialization can often be used as the practical runtime proof.
Proposed change
- Evaluate replacing or minimizing registry probing in
Assert-VisualCRedistributableInstalled path.
- Favor fast-fail based on native load/init outcome where appropriate.
- Preserve actionable warning/error guidance when runtime dependencies are truly missing.
Acceptance criteria
- Windows cold-start improves or remains neutral.
- Missing-runtime scenarios still produce actionable diagnostics.
- Existing tests pass.
- No false-positive success when runtime is unavailable.
Summary
Optimize Windows startup path by reducing registry probe overhead for VC++ runtime detection.
Why
Module import currently performs registry checks that add cold-start latency. Successful native initialization can often be used as the practical runtime proof.
Proposed change
Assert-VisualCRedistributableInstalledpath.Acceptance criteria