> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/private-cloud-director/2026.4/virtualized-clusters/troubleshooting-and-log-files/windows-vm-fails-to-boot.md).

# Windows VM Fails To Boot

## Problem

A Windows virtual machine migrated from VMware to PCD fails to boot successfully. During startup, the VM stops at the “Choose your keyboard layout” screen and does not proceed further into Windows.

## Cause

The issue occurs because Windows boot files or BCD (Boot Configuration Data) become corrupted or misaligned during the migration process.

When Windows cannot locate valid boot information, it automatically enters recovery mode and prompts for keyboard layout selection.

Possible contributing factors include:

* Missing or outdated VirtIO drivers during migration
* Incomplete or interrupted conversion process
* Boot partition corruption due to disk mapping or UUID mismatch
* File system inconsistencies on the migrated disk

## Diagnostics

{% stepper %}
{% step %}

#### Confirm boot state

Verify that the VM halts at the “Choose your keyboard layout” screen during boot.
{% endstep %}

{% step %}

#### Inspect disk from recovery media

Use WinPE or a Windows recovery ISO to access the disk and check for file system integrity issues.
{% endstep %}
{% endstepper %}

## Resolution

Running a simple filesystem check from a WinPE ISO or Windows recovery media can resolve the issue.

{% code title="Run chkdsk" %}

```powershell
chkdsk C: /f
```

{% endcode %}

Running chkdsk /f fixes most common NTFS or MBR inconsistencies that trigger WinRE.

## Additional Information

The chkdsk command runs the Check Disk utility to scan the specified drive (C: in this case) for disk or filesystem errors, and the /f flag instructs it to automatically fix any issues found. If your Windows installation uses a different drive letter, replace C: with the appropriate one for your system volume.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.platform9.com/private-cloud-director/2026.4/virtualized-clusters/troubleshooting-and-log-files/windows-vm-fails-to-boot.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.