{"id":13952,"date":"2026-02-16T10:39:13","date_gmt":"2026-02-16T10:39:13","guid":{"rendered":"https:\/\/howtogeek.blog\/ko\/?p=13952"},"modified":"2026-02-16T10:39:13","modified_gmt":"2026-02-16T10:39:13","slug":"how-to-resolve-the-startup-repair-couldnt-repair-your-pc-error","status":"publish","type":"post","link":"https:\/\/howtogeek.blog\/ko\/how-to-resolve-the-startup-repair-couldnt-repair-your-pc-error\/","title":{"rendered":"How To Resolve the \u201cStartup Repair Couldn\u2019t Repair Your PC\u201d Error"},"content":{"rendered":"<p>Facing a \u201cStartup Repair Couldn\u2019t Repair Your PC\u201d loop is incredibly frustrating. Sometimes Windows just doesn\u2019t want to start, and the built-in repair tools either spin their wheels or make things worse. It\u2019s kind of annoying how the system assumes it can fix everything automatically, but in reality, sometimes it\u2019s more about fixing the boot sector or some corrupted files manually. These fixes aren\u2019t always foolproof, but they\u2019ve worked on enough setups to be worth trying before wiping the drive or reinstalling from scratch. The goal here is to get your system to boot again without losing your files, which is often possible if the right steps are followed.<\/p>\n<p>Most of the time, this issue pops up because of a corrupt boot sector or a faulty bootloader. On some systems, the Windows Startup Repair tool gets stuck or misdiagnoses the problem \u2014 kind of weird, but it happens all the time. So, if you\u2019ve already tried letting Windows fix itself and it just keeps spinning or crashing, it\u2019s a good idea to do some manual repair work via command line tools or even try to recover your files first.<\/p>\n<h2>How to Fix &#8220;Startup Repair Couldn\u2019t Repair Your PC&#8221;<\/h2>\n<h3>Fix 1: Repair or Rebuild Your Boot Sector and Bootloader<\/h3>\n<p>This is usually the most direct way \u2014 if the boot sector or the bootloader is messed up, Windows won\u2019t start. But here\u2019s the thing: it\u2019s kind of hit or miss depending on whether you\u2019re running MBR or GPT partitioning, and how deep the damage runs. Nonetheless, doing these commands can sometimes make your Windows boot again without a complete reinstall. But be warned: on some setups, you might have to do this multiple times or restart a few times to see it work.<\/p>\n<ul>\n<li>Boot from your Windows installation media (USB or DVD).You can create one with <strong>Windows Media Creation Tool<\/strong> if needed, just in case.<\/li>\n<li>Pick <strong>Repair your computer<\/strong> at the initial screen, then go to <strong>Troubleshoot &gt; Advanced Options &gt; Command Prompt<\/strong>.<\/li>\n<\/ul>\n<h3>MBR Repair (for older BIOS disks)<\/h3>\n<p>If your setup still uses MBR (most older or BIOS-based systems do), these commands can help fix the boot sector. Just enter them one after the other, then restart.<\/p>\n<pre><code>bootrec \/FixMBR bootrec \/FixBoot bootrec \/ScanOs bootrec \/RebuildBcd <\/code><\/pre>\n<p>Sometimes, Windows balks at `\/FixBoot`, giving an access denied error. If so, you might need to run additional commands like `bootsect` or even assign correct permissions, but that\u2019s a rabbit hole in itself.<\/p>\n<h3>EFI Partition Repair (for GPT disks)<\/h3>\n<p>Most modern machines boot via UEFI, so fixing the EFI partition is the ticket if your system uses GPT. These steps are kind of tedious, but worth it if your EFI is corrupted or missing.<\/p>\n<ol>\n<li>Run <strong>diskpart<\/strong> (`diskpart` command in cmd) and list your disks with <strong>list disk<\/strong>.<\/li>\n<li>Figure out which disk is your boot drive \u2014 usually, it&#8217;s the one with the largest size, or you can look for an asterisk if it shows up in your environment.<\/li>\n<li>Pick the disk with <strong>sel disk X<\/strong> (replace X with the number).<\/li>\n<li>Show all volumes with <strong>list vol<\/strong>. Find the FAT32 volume, probably around 100MB, labeled as System or Boot.<\/li>\n<li>Select that volume with <strong>sel vol #<\/strong> (replace # with the volume number).<\/li>\n<li>Assign it a drive letter so you can access it, like R:\\ \u2014 just type <strong>assign letter=R<\/strong>. Now you can exit diskpart (`exit`).<\/li>\n<li>Navigate to the EFI directory \u2014 often, you&#8217;ll run something like <code>cd \/d R:\\EFI\\Microsoft\\Boot\\<\/code>. If that folder isn\u2019t there, try `<code>cd \/d R:\\Boot\\<\/code>` or `<code>cd \/d R:\\ESD\\Windows\\EFI\\Microsoft\\Boot\\<\/code>` \u2014 depends on your setup.<\/li>\n<li>Backup your current BCD (Boot Configuration Data) just in case: `<code>ren BCD BCD.bak<\/code>`.<\/li>\n<li>Create a new BCD store by copying the Windows boot files: `<code>bcdboot C:\\Windows \/s R: \/f ALL<\/code>`.Here, your Windows should be on C:\\, but double-check if it\u2019s on a different drive.<\/li>\n<li>Finally, run `<code>bootrec \/rebuildbcd<\/code>`, then restart and see if Windows boots.<\/li>\n<\/ol>\n<h3>Try Windows Recovery Environment\u2019s Other Options<\/h3>\n<p>If command line repair sounds intimidating, or if things go sideways, Windows has more tricks. If you see the recovery options menu, you can try things like restoring your registry backup, undoing recent Windows updates, system restore, or disabling automatic repair to get past the loop.<\/p>\n<h3>Restore Registry from Backup<\/h3>\n<p>This is a bit of a long shot unless you&#8217;ve previously set up registry backups. If yes, it&#8217;s one of the cleaner fixes that might bring your system back to life without wiping the drive.<\/p>\n<ul>\n<li>From <strong>Troubleshoot &gt; Advanced Options<\/strong>, pick <strong>Command Prompt<\/strong>.<\/li>\n<li>Identify your main Windows partition with <strong>diskpart<\/strong>: `list disk`, then `sel disk 0`, then `list vol`.Find your system drive (probably C:).<\/li>\n<li>Navigate to System32: `<code>cd \/d C:\\windows\\system32<\/code>`.<\/li>\n<li>Create a backup folder: `<code>mkdir rbackup<\/code>`.<\/li>\n<li>Copy your current config folder: `<code>copy config rbackup<\/code>`.<\/li>\n<li>Go into the backup folder: `<code>cd config\\regback<\/code>`.<\/li>\n<li>List files with `dir`.If files are zeroed out, no dice here; skip this fix.<\/li>\n<li>If not, restore the registry backups: `<code>copy *..\\*<\/code>` \u2014 confirm with <strong>Y<\/strong> when prompted.<\/li>\n<\/ul>\n<h3>Uninstall Bad Updates<\/h3>\n<p>If this all started after updating Windows, removing that latest update might do the trick. You can access <strong>Uninstall Updates<\/strong> in recovery options and roll back recent quality or feature updates. Sometimes updates break things, and this is the easiest fix.<\/p>\n<h3>System Restore to a Working Point<\/h3>\n<p>If you&#8217;ve got restore points set up, rolling back is worth a shot. You get back your system to a good state before the mess started.<\/p>\n<ol>\n<li>Pick <strong>System Restore<\/strong> from recovery options.<\/li>\n<li>Select a restore point from before the issue appeared and hit <strong>Next<\/strong>, then <strong>Finish<\/strong>.<\/li>\n<\/ol>\n<h3>Disable Automatic Startup Repair<\/h3>\n<p>This is kind of a last-ditch move, but turning off automatic repair can sometimes help you see errors that were hidden. It could give you more clues or even allow you to fix things manually.<\/p>\n<ol>\n<li>Open <strong>Command Prompt<\/strong> in recovery.<\/li>\n<li>Check current boot settings with `<code>bcdedit<\/code>` and identify your Windows Boot Loader entry.<\/li>\n<li>Disable automatic recovery with `<code>bcdedit \/set {default} recoveryenabled no<\/code>` (replace `{default}` with your actual identifier if needed).<\/li>\n<li>Reboot and see what error messages pop up.<\/li>\n<\/ol>\n<p>Hopefully, one of these methods gets the system back on its feet. Sometimes, fixing the boot loader or EFI isn&#8217;t super straightforward, but it beats wiping everything or doing a full reinstall blindly. Good luck!<\/p>\n<h2>Summary<\/h2>\n<ul>\n<li>Use command line tools like `bootrec` and `bcdboot` to fix boot issues.<\/li>\n<li>Repair EFI partition if Windows is UEFI-based.<\/li>\n<li>Try recovery &amp; system restore options before major reinstall.<\/li>\n<li>Backup important files before doing any major fixes.<\/li>\n<\/ul>\n<h2>Wrap-up<\/h2>\n<p>This isn\u2019t the flashiest set of fixes, but fixing boot sectors or EFI partitions manually can save a lot of hassle. Sometimes Windows just needs a little nudge to get back in shape. Fingers crossed this helps \u2014 it\u2019s worked on enough machines to be worth a shot.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Facing a \u201cStartup Repair Couldn\u2019t Repair Your PC\u201d loop is incredibly frustrating. Sometimes Windows just doesn\u2019t want to start, and the built-in repair tools either spin their wheels or make things worse. It\u2019s kind of annoying how the system assumes it can fix everything automatically, but in reality, sometimes it\u2019s more about fixing the boot [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-13952","post","type-post","status-publish","format-standard","hentry","category-how-to"],"acf":[],"_links":{"self":[{"href":"https:\/\/howtogeek.blog\/ko\/wp-json\/wp\/v2\/posts\/13952","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/howtogeek.blog\/ko\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/howtogeek.blog\/ko\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/howtogeek.blog\/ko\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/howtogeek.blog\/ko\/wp-json\/wp\/v2\/comments?post=13952"}],"version-history":[{"count":1,"href":"https:\/\/howtogeek.blog\/ko\/wp-json\/wp\/v2\/posts\/13952\/revisions"}],"predecessor-version":[{"id":13953,"href":"https:\/\/howtogeek.blog\/ko\/wp-json\/wp\/v2\/posts\/13952\/revisions\/13953"}],"wp:attachment":[{"href":"https:\/\/howtogeek.blog\/ko\/wp-json\/wp\/v2\/media?parent=13952"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/howtogeek.blog\/ko\/wp-json\/wp\/v2\/categories?post=13952"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/howtogeek.blog\/ko\/wp-json\/wp\/v2\/tags?post=13952"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}