Wie repariere ich nach der Installation von Windows 10 Enterprise LTSC 2019 den Fehler „Invalid partition table“, wenn der Start nach dem Neustart abbricht und die automatische Reparatur fehlschlägt?

**The most likely cause is a boot-mode/partition-style mismatch or missing boot files: Windows 10 LTSC 2019 was installed, but the PC is trying to boot it the wrong way, so “Automatic Repair” usually cannot fix it.** ([learn.microsoft.com](https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-installing-using-the-mbr-or-gpt-partition-style?view=windows-11)) ## What usually caused this On an older Windows 7 Pro PC, the disk is often still **MBR** and the firmware is often set to **Legacy BIOS/CSM**. Windows 10 can boot that way, but only if the boot files were written correctly to the active system partition. If setup was started in **UEFI mode** on an **MBR** disk, or in **Legacy mode** on a **GPT** disk, boot can stop immediately with partition-table or boot-manager errors. Microsoft explicitly distinguishes BIOS/MBR from UEFI/GPT installs. ([learn.microsoft.com](https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-installing-using-the-mbr-or-gpt-partition-style?view=windows-11)) The practical consequence: before repairing, you must identify whether your installed Windows is on an **MBR/BIOS** or **GPT/UEFI** layout. Otherwise the usual `bootrec` commands may do nothing useful. ([learn.microsoft.com](https://learn.microsoft.com/en-gb/windows-hardware/manufacture/desktop/bcdboot-command-line-options-techref-di?view=windows-11)) ## First: identify the disk layout in Command Prompt Boot from the Windows 10 installer USB/DVD, choose **Repair your computer** → **Troubleshoot** → **Command Prompt**, then run: ```cmd diskpart list disk select disk 0 list vol exit ``` What matters: - If disk 0 shows a `*` in the **GPT** column, the disk is **GPT / UEFI**. - If there is **no** `*`, it is usually **MBR / Legacy BIOS**. - Look for a small **FAT32** partition: that is usually the **EFI System Partition** on UEFI systems. - Look for a small **System Reserved** NTFS partition marked active: that is typical for BIOS/MBR systems. ([learn.microsoft.com](https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-installing-using-the-mbr-or-gpt-partition-style?view=windows-11)) Also find the Windows partition letter, because in WinRE it is often **not C:**. Check with: ```cmd dir C:\Windows dir D:\Windows dir E:\Windows ``` Use the letter that actually contains `Windows`. Microsoft notes that drive letters can change in Windows PE/Recovery. ([learn.microsoft.com](https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/configure-biosmbr-based-hard-drive-partitions?view=windows-10)) ## Repair if the disk is MBR / Legacy BIOS If the disk is **MBR** and the machine should boot in **Legacy/CSM** mode, run: ```cmd bootrec /fixmbr bootrec /fixboot bootrec /scanos bootrec /rebuildbcd ``` If your Windows folder is on `D:`, then also rebuild boot files explicitly: ```cmd bcdboot D:\Windows /l en-us /f BIOS ``` If there is a separate System Reserved partition, assign it a letter first: ```cmd diskpart list vol select vol X assign letter=S exit bcdboot D:\Windows /s S: /f BIOS ``` `bootrec /fixmbr` rewrites the MBR without overwriting the partition table, and `bcdboot` recreates the boot files from the installed Windows image. That is often the decisive step when Automatic Repair fails. ([support.microsoft.com](https://support.microsoft.com/en-us/help/927392)) Important on BIOS/MBR: the correct system partition must be **Active**. If needed: ```cmd diskpart select disk 0 list partition select partition X active exit ``` ## Repair if the disk is GPT / UEFI If disk 0 is **GPT**, repair it as **UEFI**, not with BIOS assumptions. First assign a letter to the EFI partition: ```cmd diskpart list vol select vol X assign letter=S exit ``` The EFI partition is usually small and **FAT32**. Then rebuild boot files: ```cmd bcdboot D:\Windows /s S: /f UEFI ``` If you want Windows to create files for both firmware types, Microsoft documents: ```cmd bcdboot D:\Windows /s S: /f ALL ``` That is often more reliable than relying on `bootrec /fixboot`, especially on newer Windows 10 recovery environments. ([learn.microsoft.com](https://learn.microsoft.com/en-gb/windows-hardware/manufacture/desktop/bcdboot-command-line-options-techref-di?view=windows-11)) ## The mistake many guides miss “Invalid partition table” is often treated like a damaged disk, but after a fresh install it is more often a **firmware boot mismatch**: - **GPT disk + BIOS/Legacy boot** = won’t boot correctly - **MBR disk + pure UEFI boot** = won’t boot correctly ([learn.microsoft.com](https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-installing-using-the-mbr-or-gpt-partition-style?view=windows-11)) So after running the repair commands, check firmware setup immediately: - If disk is **MBR** → enable **Legacy/CSM** - If disk is **GPT** → enable **UEFI**, disable Legacy if necessary That setting must match the installed layout, or the repair will appear to “fail” even when the boot files are correct. ([learn.microsoft.com](https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-installing-using-the-mbr-or-gpt-partition-style?view=windows-11)) ## Best practical sequence Use this order: 1. Identify whether the disk is **MBR or GPT** 2. Find the real Windows drive letter 3. Rebuild boot files with **`bcdboot`** 4. Make firmware mode match the disk layout 5. Only if still broken, restart installation and wipe old partitions so setup creates the correct layout automatically If you want the shortest working command set, the highest-yield repair is usually one of these: ```cmd bcdboot D:\Windows /f BIOS ``` or ```cmd bcdboot D:\Windows /s S: /f UEFI ``` That is usually more effective than repeating Automatic Repair. ([learn.microsoft.com](https://learn.microsoft.com/en-gb/windows-hardware/manufacture/desktop/bcdboot-command-line-options-techref-di?view=windows-11))