GitHub Copilot Agent Host fails to start on Windows 10 x64 — runtime.node DLL initialization error

Does this issue occur when all extensions are disabled?: Yes/No

- VS Code Version: 1.135.0
- OS Version: Windows 10x64

Home, Version 22H2 (OS Build 19045.6466)

Steps to Reproduce:

1. Open the workspace in VS Code.
2. Make sure GitHub Copilot is authenticated.
3. Start a Copilot Agent session.
4. Observe the Agent Host startup failure.

## Environment

- GitHub Copilot Chat: 0.63.0
- Copilot account: Free Limited Copilot
- Workspace: D:\IVD_SOURCE_LIBRARY

## Summary

GitHub Copilot Chat works normally: authentication succeeds and the Chat interface is available.

However, when I start a Copilot Agent session, Agent Host fails during startup before it can execute any user task.

## Expected behavior

The Copilot Agent should start and be able to perform a simple read-only task in the workspace.

## Actual behavior

Agent Host fails to load the native Copilot SDK runtime.

The VS Code log reports:

[CopilotCLISession] Failed to load @GitHub/copilot/sdk:
Error: Native addon "runtime" not found for win32-x64.

The first attempted native binary reports:

"A dynamic link library (DLL) initialization routine failed."

The loader then reports that runtime.win32-x64-msvc.node cannot be found.

The relevant path is:

extensions/copilot/node_modules/@GitHub/copilot/sdk/prebuilds/win32-x64/runtime.node

Authentication and normal Copilot Chat functionality work correctly.

## Important diagnostic detail

The failure appears to occur specifically during Agent Host startup. The normal Copilot Chat functionality is not affected.

The generic VS Code bug-report instructions recommend reproducing issues with extensions disabled. This particular failure cannot be reproduced without Copilot because the failing Agent Host is part of the Copilot functionality itself.

## Questions

1. Is this a known Windows compatibility or native-runtime issue in Copilot Agent Host?
2. How can I identify the exact DLL or Windows dependency preventing runtime.node from initializing?
3. Is there a known dependency on a specific Windows build, MSVC runtime, CPU instruction set, or Windows API?
4. What diagnostic procedure should be performed before reinstalling VS Code and Copilot?

I can provide the complete VS Code logs and perform additional diagnostic tests if required.