Reset the Registry in Windows 11 and 10: Honest Guide

Start here, because it changes what you should do next: Windows has no button, command or tool that resets the registry. It has never had one. Any page promising a registry reset is describing something else.

What actually works, in order of how much damage each one does:

System Restore → reset one key's permissions → DISM then SFC → in-place repair upgrade → Reset This PC. Use the first one that solves your problem and stop.

And if you landed here because Registry Editor said "Cannot edit <name>: Error writing the value's new contents", that is a permissions problem, not a reset problem — jump straight to the fix.

The Day and a Half Jake Billed on Paper

Jake's shop PC had got slow. Not broken — slow. Four minutes to the desktop, a spinning cursor every time he opened the billing software.

A video told him the registry was "clogged". It recommended a free cleaner, and then a manual edit to a key it said would "reset the registry cache". Jake did both on a Sunday evening, because Sunday evening is when the shop is quiet.

Monday morning the machine reached a blue screen and stayed there.

He billed on paper for a day and a half. Two customers walked out during the wait, and reconstructing the weekend's invoices by hand took most of a Wednesday. Cost of the hour of tidying: roughly a day and a half of trading, plus a service charge to make the machine bootable.

"So the registry cleaner did it," he said to Ethan.

"Maybe. Maybe the edit. Maybe neither — if that drive was failing, the cleaner just made the timing look meaningful." Ethan shrugged. "But here's what annoys me. You didn't have a problem the registry could fix. Nobody does. That video sold you a repair for a condition that doesn't exist."

"Everyone says a cleaner speeds up your PC."

"Everyone said that in 2004, when a hard disk did eighty reads a second. Your registry is a few hundred megabytes on an SSD. Deleting orphaned entries from it saves nothing you could measure with a stopwatch, and Microsoft themselves publish a line saying they don't support these tools and that serious problems can happen if you use them. That's not a competitor talking. That's the vendor."

What You Are Actually About to Touch

The registry is Windows' settings database — which program opens a .pdf, which drivers load at boot, your Wi-Fi profiles, where the taskbar sits. A tree of keys (folders) holding values (settings).

It is not one file, which is why there is no reset button

Open Registry Editor and you see five top-level branches. They are not five files in a folder. They are assembled at boot from separate files called hives — HKEY_LOCAL_MACHINE from several files in C:\Windows\System32\config, HKEY_CURRENT_USER from NTUSER.DAT in your user folder — plus two branches (HKEY_CLASSES_ROOT and HKEY_CURRENT_CONFIG) that are merged views built in memory with no file of their own.

Now the point. Most of what is in there did not come from Windows. It came from every program you have ever installed. Reset the registry to "default" and you would be telling Windows that none of your software exists — not uninstalling it, just forgetting it, leaving gigabytes of orphaned program files and nothing that knows how to run them.

That is why the button does not exist. A reset to a factory registry is a reinstall. Windows just calls it something more honest.

Why TrustedInstaller owns the keys you cannot edit

Jake's question, and it is the right one: "If I'm the administrator of my own computer, why am I told I can't change something?"

Because administrator does not mean owner. Windows keeps a built-in service account called TrustedInstaller — full name NT SERVICE\TrustedInstaller — belonging to the Windows Modules Installer service, which installs and services Windows updates. It owns the core system keys deliberately, for two reasons worth understanding rather than resenting:

• Updates need a stable target. A cumulative update replaces components as TrustedInstaller. If those keys were owned by whoever last poked at them, "the update failed and rolled back" becomes a weekly event.
• It is a real speed bump against silent tampering. Malware running with your admin token still has to take an extra, noisy, auditable step to rewrite a protected key. Not a wall — a speed bump. Speed bumps still work.

So the error is not Windows malfunctioning. It is Windows saying: this key belongs to the servicing system and you have not claimed it. You are allowed to claim it. You should also give it back.

Back Up Properly First — and Why the Usual Advice Is Half a Backup

Every registry guide tells you to export the key first. That advice is fine and incomplete, and the gap in it is where people get hurt.

Layer 1 — export the key you are about to edit (.reg file)

Right-click the key in Registry Editor → Export → confirm Selected branch shows the right path → save it, named for the date and the key rather than backup.reg, because you will make three of these before the afternoon is out.

To put it back: double-click the .reg file and confirm, or File → Import in Registry Editor. Same thing. Our registry backup walkthrough has it with screenshots.

Layer 2 — a System Restore point (this is the real one)

A restore point captures the registry hives as a set. It is the only readily available thing that genuinely reverts the registry to a prior state, including removing what you added.

1. Press Windows + R, type sysdm.cpl, press Enter. (The Run box launches things by name. A .cpl file is a Control Panel applet — this one is System Properties.)
2. Open the System Protection tab.
3. If Protection says Off for C:, select the drive → Configure → Turn on system protection, and allow it around 5–10% of the disk.
4. Create, name it before registry edit, wait.

System Protection is off by default on many clean installs and OEM machines, so a great many people discover at the worst possible moment that they have no restore points at all. Check now, not later — our guides to turning on System Protection and creating a restore point cover it, and there is a shortcut you can pin if you do this often.

Layer 3 — your actual files, on something that is not this computer

Restore points are not a data backup. If the plan you are reading might end at "Reset This PC", your documents need to exist somewhere else first — not on the same drive, not on another partition of it.

Two no-cost routes built into Windows: File History for a rolling copy, and a straight copy to an external drive, which takes ten minutes and is what Jake now does on the first of every month. For a shop machine holding billing data, that drive costs less than the two customers who walked out.

The Fix for "Error Writing the Value's New Contents"

The full message reads something like "Cannot edit Start: Error writing the value's new contents", and its close relatives are "Cannot create value: Error writing to the registry" and "Cannot delete key: Error while deleting key". Same cause, same fix.

You do not have write permission on that key. Take ownership, grant yourself Full Control, make the change, hand ownership back.

These steps are identical on Windows 11 and Windows 10. The Registry Editor permissions dialogs have not changed since Windows 7. The only thing that differs is how you open Registry Editor in the first place, which is covered in the Windows 10 note further down.

Windows 11 — the full walkthrough

1. Press Windows + R, type regedit, press Enter, and approve the User Account Control prompt. If you are not prompted at all, you are not running it elevated — close it and start again from the Start menu with Run as administrator.
2. Navigate to the key. Faster: paste the full path into Registry Editor's address bar and press Enter.
3. Right-click the key itself in the left-hand tree — the folder, not the value on the right — and choose Permissions.
4. Click Advanced, bottom right.
5. At the top, Owner: will read TrustedInstaller. Click Change next to it.
6. In Enter the object name to select, type your Windows username, click Check Names — it should underline and expand to MACHINENAME\YourName — then OK.
   Not sure of your username? Type whoami at a Command Prompt. Typing Administrators instead works too, and is arguably tidier.
7. Back on the Advanced screen, tick "Replace owner on subcontainers and objects". This is the checkbox people miss, and missing it is why the error returns the moment you touch a subkey.
8. Apply. Errors may scroll past for subkeys nobody is allowed to own — normal, dismiss them. Then OK.
9. On the Permissions window, select your username (or Administrators) and tick Allow next to Full Control.
10. Apply, OK. Make your edit. It will now save.

If the Permissions window will not open, or Change is greyed out, you are not running Registry Editor as administrator. That is the single most common reason this sequence fails at step 4.

Windows 10 — what differs

The permissions dialogs are pixel-identical, and every step above applies unchanged. The only difference is getting to Registry Editor: on Windows 10 you can right-click Start and use the menu directly, whereas on Windows 11 the older context menus are hidden behind Show more options — the trap that catches nearly everyone who upgrades.

One honest note for Windows 10 users, since it affects everything on this page: Windows 10 reached end of support on 14 October 2025. Every instruction here still works on it. But it will not receive fixes for anything discussed here, and a registry workaround on an unpatched system is one you will be maintaining forever.

Give ownership back when you are done

This is the step our own 2016 version of this article never mentioned, and we were wrong to leave it out. A future cumulative update that needs to service that key can fail, because the servicing stack expects TrustedInstaller in charge — you get an update that installs to 90% and rolls back, with an error code that says nothing about a permission you changed months earlier. And you have permanently removed a protection that exists for a reason.

1. Right-click the key → Permissions → Advanced → Change next to Owner.
2. Type exactly NT SERVICE\TrustedInstaller and click Check Names. It resolves to TrustedInstaller.
3. OK, then Apply. If you ticked "replace owner on subcontainers" on the way in, tick it again on the way out.
4. Optionally remove the Full Control entry you granted yourself.

Full walkthrough: restoring TrustedInstaller as the default owner. The two halves belong together.

When you own the key and it still refuses

This is where most articles stop and most readers are still stuck. Five causes, likeliest first:

1. Tamper Protection. If the key sits under HKLM\SOFTWARE\Microsoft\Windows Defender or its policy branches, Windows Security blocks the write regardless of who owns it — ownership is simply not the mechanism in play. This is now one of the commonest causes of this exact error and almost no guide mentions it. Open Windows Security → Virus & threat protection → Manage settings, turn Tamper Protection off, make the change, turn it back on. If you are turning it off because a guide told you to disable Defender permanently, stop and reconsider.

2. Group Policy or MDM is rewriting it. On a work laptop or an Intune-enrolled machine, policy reapplies on a schedule. Your edit saves fine and is silently overwritten within the hour. No registry trick beats this; the setting is managed on purpose.

3. The key is in use. Some keys are locked while a service holds them open. Safe Mode loads a minimal set of drivers and frees most of them; a clean boot is the gentler version.

4. You are editing the wrong view. On 64-bit Windows, 32-bit programs read from a parallel branch under WOW6432Node. Editing HKLM\SOFTWARE\Vendor\App when the program reads HKLM\SOFTWARE\WOW6432Node\Vendor\App means your change saves perfectly and does nothing.

5. It genuinely cannot be edited. Parts of HKLM\SECURITY and certain virtualisation-based-security and Secure Boot keys are protected by the kernel, not by permissions. No amount of ownership changes that. Naming the limit honestly: if the kernel is refusing, you are not getting in, and you should not want to.

"Reset the Registry" — the Options, Ranked by Damage

Here is the whole honest picture on one screen. Work down it and stop at the first row that fixes your problem — every row below costs you more than the one above.

Option 3 in Detail: System Restore, the Real Undo Button

System Restore is frequently dismissed as a relic. It is not. It is specifically and deliberately a registry-and-system-files time machine, and it is the closest Windows will ever come to the button people are searching for.

What a restore point contains: the registry hives, system files, installed drivers, and program installation state.

What it does not contain: your documents, photos, videos, downloads, email or browser data. Those are left completely alone, in both directions — restoring will not bring back a deleted file, and it will not delete a file you made yesterday.

Running it from inside Windows

Same on Windows 11 and Windows 10:

1. Press Windows + R, type rstrui, press Enter.
2. Click Next. You will see a list of restore points with dates and a description of what created each one.
3. Tick "Show more restore points" at the bottom left if the list looks short — older points are hidden by default and this catches people out.
4. Select a point dated before the change that caused the problem.
5. Click Scan for affected programs. This is the step almost everyone skips, and it is the most useful button on the screen: it tells you exactly which applications will be removed or restored. No surprises afterwards.
6. Next, then Finish. The machine restarts and works for 10–30 minutes. Do not interrupt it.

Running it when Windows will not start

Restore points live outside the running system, so you can use them from the Recovery Environment. Full detail is in the recovery section below, but the short version: interrupt the boot three times, then Troubleshoot → Advanced options → System Restore.

When System Restore itself fails

• "No restore points have been created" — System Protection was off. There is nothing to recover from and no way to create one retroactively. This is the moment people learn the lesson; there is no gentle version of it.
• Error 0x80070091 — usually a folder that will not clear during the roll back, and it has a specific fix documented in our guide to System Restore failing with 0x80070091.
• It completes but says it failed — try again from Safe Mode, where antivirus and third-party services are not running to interfere. This works surprisingly often.
• Your restore points vanished — a feature upgrade, a disk cleanup, or the allocated shadow-copy space filling up will silently discard old points. They are insurance, not archives.

Option 4: DISM and SFC — What They Repair, and What They Do Not

Let us kill the biggest myth on this topic first, because it is repeated on nearly every page that claims to reset the registry.

Neither of these tools repairs the registry. Not partially, not indirectly. sfc /scannow will not undo a value you changed, will not restore a key you deleted, and will not report a single thing about the registry. If a page tells you that running SFC resets the registry to default, that page is wrong and you should weigh everything else on it accordingly.

They are still worth running, for two honest reasons: registry symptoms and file damage often share a cause, and if your component store is broken you want to know that before you attempt anything bigger.

What each one is

• SFC (System File Checker) compares Windows' protected system files against known-good copies and replaces any that differ. Its source of known-good copies is a local folder called the component store, at C:\Windows\WinSxS.
• DISM (Deployment Image Servicing and Management) repairs the component store itself, pulling clean components from Windows Update when needed.

The order, and why most guides get it backwards

SFC repairs files by copying replacements out of the component store. If the component store is damaged, SFC has nothing clean to copy from, and it finishes with "Windows Resource Protection found corrupt files but was unable to fix some of them" — the message that sends thousands of people to forums every week.

So: repair the source first, then run the tool that depends on it. DISM, then SFC.

Open Command Prompt as administrator — it will not work otherwise — and run these in order, letting each finish completely:

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

What each line does:

• /CheckHealth — reads a flag that says whether damage was already detected. Instant. Does not scan anything.
• /ScanHealth — actually scans the component store. Several minutes. Reports, repairs nothing.
• /RestoreHealth — the one that repairs. Downloads replacement components from Windows Update as needed, so you need a working internet connection. Takes 10–30 minutes and often sits at 20% or 62.3% for a long time. It is not frozen. Leave it.
• sfc /scannow — now that its source is clean, this repairs the system files. Around 10–20 minutes.

Run sfc /scannow a second time afterwards. It is normal for a first pass to fix something that lets a second pass fix something else, and a clean second run is your confirmation.

When RestoreHealth cannot find a source

If DISM reports "The source files could not be found", error 0x800f081f, it could not reach Windows Update or the update path itself is broken. Point it at a mounted Windows ISO instead:

DISM /Online /Cleanup-Image /RestoreHealth /Source:esd:E:\sources\install.esd:1 /LimitAccess

Replace E: with the drive letter the mounted ISO got, and use install.wim in place of install.esd if that is what the ISO contains. The ISO must match your installed version — a Windows 11 ISO will not repair Windows 10.

And if DISM completes but the same corruption reappears on the next scan, that is a different problem with its own causes, covered in our guide to DISM reporting corruption after a successful repair.

Two Popular Fixes That Stopped Working Years Ago

If you have been searching for a while you will have hit both of these. Both are still confidently recommended by pages that were written once and never checked again. We published one of them ourselves, and this is where we correct it.

The RegBack folder is empty, and that is deliberate

The advice goes: copy the files from C:\Windows\System32\config\RegBack over the live hives in C:\Windows\System32\config, and you have restored the registry.

That was excellent advice until 2018. Since Windows 10 version 1803, Windows no longer writes those automatic backups. Microsoft made the change to reduce disk footprint. Go and look at the folder now — the filenames are there, and every one is 0 bytes. Copying them over your working hives replaces a functioning registry with nothing at all, which is a uniquely bad outcome from a step described as a backup.

Our own 2016 article on resetting the registry recommended exactly this. It was true when it was written and it has been false for eight years. That is the honest reason this page exists in the form it does.

You can switch the behaviour back on if you want it, at the cost of some disk space. Create a DWORD value named EnablePeriodicBackup, set to 1, under:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Configuration Manager

Reboot, and Windows resumes writing hive backups to RegBack on its maintenance schedule. Useful on a machine you tinker with. Not a substitute for restore points, because it runs on Windows' schedule rather than yours.

Last Known Good Configuration is gone from the boot menu

The old F8 option that booted using the last set of settings that produced a successful logon — genuinely useful in the Windows XP and 7 era — was removed from the startup menu in Windows 8 and has not come back in Windows 10 or Windows 11.

The mechanism still exists internally; the registry keeps a LastKnownGood control set. But there is no supported way to select it at boot on a normal modern PC, and pressing F8 on a fast-booting UEFI machine will usually just take you into firmware settings.

System Restore is its replacement, and is strictly better: it is dated, it is browsable, and it tells you what it will change before it changes it.

Registry Cleaners: Do Not

Half the internet is telling you to install one. Here is why the answer is still no.

1. Microsoft does not support it

This is not a matter of opinion between blogs. Microsoft's own published position is that it does not support the use of registry cleaning utilities, and warns that serious problems may occur that require reinstalling the operating system. When the vendor of the database says do not run third-party tools against the database, that settles it.

2. There is no performance to recover

The premise is that orphaned entries left behind by uninstalled programs slow Windows down. Registry lookups are indexed, held largely in memory, and measured in microseconds. Removing ten thousand dead entries from a database of several hundred thousand changes nothing you can perceive, and nobody publishing a cleaner has ever produced a credible benchmark showing otherwise.

If your PC is slow, the causes are almost always startup programs, a failing or nearly full drive, a mechanical hard disk that should be an SSD, or too little RAM. Every one of those is measurable, and every one has a real fix. None of them is the registry. Open Task Manager, look at the Startup tab and the disk column, and you will find the real culprit in about ninety seconds.

3. The category is a distribution channel

"Free registry cleaner" is one of the oldest and most reliably poisoned search terms there is. The pattern is consistent: a free scan that always finds hundreds of "critical errors", a payment demanded to fix them, a bundled toolbar or three, and in a meaningful share of cases outright malware. Some are legitimate tools with an unnecessary feature. Distinguishing them from a search result page is genuinely hard, and the upside if you get it right is zero.

When the Registry Is Genuinely Damaged

Sometimes it really is broken. The signals are specific rather than vague: applications that fail to launch with class-not-registered errors, Windows Update refusing to run at all, Settings pages that open blank, or a blue screen naming a registry error such as REGISTRY_ERROR or BAD_SYSTEM_CONFIG_INFO.

"Slow" and "cluttered" are not on that list.

The in-place repair upgrade — the step nobody mentions

This is the most underrated repair in Windows, and it sits exactly where people need it: a full Windows reinstall that keeps your files and your installed programs. It rebuilds the system portions of the registry while preserving the parts your software depends on.

1. Download the official Media Creation Tool or the ISO from Microsoft's own download page. Type the address; do not use a search result.
2. Get the ISO for the same version you are running — Windows 11 for Windows 11.
3. Double-click the ISO to mount it, then run setup.exe from inside Windows. Do not boot from it — booting from the media gives you a clean install, which is a different and far more destructive thing.
4. When asked what to keep, choose Keep personal files and apps. If that option is greyed out, your ISO version or edition or language does not match what is installed.
5. Let it run. 45–90 minutes, several restarts.

You come out the other side with a fresh Windows installation, your programs still installed, your files untouched, and the system registry rebuilt. Nine times out of ten this is what somebody actually needed when they searched for a registry reset.

Reset This PC on Windows 11

1. Settings → System → Recovery.
2. Next to Reset this PC, click Reset PC.
3. Choose Keep my files or Remove everything.
4. Choose Cloud download (fetches a fresh copy, needs several GB of data) or Local reinstall (rebuilds from files on the machine). If the damage might extend to those local files, pick Cloud download.

Reset This PC on Windows 10

1. Settings → Update & Security → Recovery — a different location from Windows 11, which catches people who follow a Windows 11 guide.
2. Under Reset this PC, click Get started.
3. The same two choices follow, with the same meanings.

"Keep my files" still removes every desktop application you have installed. Office, your billing software, your printer drivers, browser extensions, saved app logins. It keeps documents, photos, downloads and desktop contents. People routinely misread this and are surprised, so read it twice.

Allow real time. A reset can appear stuck for a long stretch — our note on a reset sitting at 99% exists because it is common, usually harmless, and interrupting it is how a recoverable machine becomes an unbootable one. On a laptop, keep it plugged in.

When It Goes Wrong: Windows Will Not Boot

This is Jake's Monday morning. Work through it in order and do not skip ahead — each step is less destructive than the next.

Step 1 — if you can reach the sign-in screen, try Safe Mode

On the sign-in screen, hold Shift, click the power icon, and choose Restart. You land in the recovery menu. Then Troubleshoot → Advanced options → Startup Settings → Restart, and press 4 for Safe Mode.

Safe Mode loads a minimal set of drivers and services. If your edit broke something loaded by a driver or a startup service, Safe Mode will often boot cleanly — and from there you can undo the edit, or run System Restore, normally. Our two-step guide to Safe Mode covers the variants, and there is a separate note on getting back out of Safe Mode, which is less obvious than it should be.

Step 2 — force the Recovery Environment

If you cannot reach sign-in at all, you have to make Windows give up on booting:

1. Power on. The moment you see the manufacturer logo or the spinning dots, hold the power button until the machine switches off.
2. Do that three times.
3. On the fourth start, Windows displays Preparing Automatic Repair and takes you into the Windows Recovery Environment.

It feels wrong to force-power-off a computer repeatedly. It is the documented, intended way to trigger recovery on a machine that will not boot — there is no gentler alternative once the startup menu is unreachable. Our guide to reaching Advanced Startup lists every other route in, for when the machine still boots and you just want the menu.

Step 3 — System Restore from recovery

Troubleshoot → Advanced options → System Restore. Pick a point from before the edit. This resolves the large majority of registry-caused boot failures, and it is why the forty seconds spent creating a restore point matters so much.

Step 4 — Startup Repair

Troubleshoot → Advanced options → Startup Repair. It is automated, harmless to try, and fixes boot configuration problems rather than registry content. Worth ten minutes before anything heavier. On very recent Windows 11 builds this is being extended by Quick Machine Recovery, which can pull a targeted fix from Microsoft while the machine is still in the recovery environment.

Step 5 — replacing a hive by hand from Command Prompt

Last resort before a reset, and only if you know which hive you damaged. From Troubleshoot → Advanced options → Command Prompt — the same command prompt at boot covered in its own guide.

The critical detail: the drive letter in recovery is often not C:. Run diskpart, then list volume, then exit, and identify the volume holding Windows by its size and label before you type anything destructive.

Then, first, make a copy of the damaged hives — because if this goes wrong you want the option of putting things back exactly as they were:

cd D:\Windows\System32\config
md backup_broken
copy *.* backup_broken

Now the source of a good copy. RegBack is empty on any modern build, so the realistic source is a restore point's snapshot, which lives under D:\System Volume Information in a folder beginning _restore or a long GUID. Locating the right one from a command prompt is fiddly, and honestly: if System Restore from step 3 did not work, this is the point at which a repair upgrade or a reset is the faster, safer, more honest answer. We are naming the limit rather than pretending there is a neat command.

Editing the Registry Without Ending Up Here Again

Habits that cost nothing and prevent most of what is on this page.

• Ask what the edit does before you make it. If a guide gives you a path and a value with no explanation of what the value means, that guide does not know either. Search the value name on its own first.
• Restore point first. Every time. Forty seconds.
• Use Favorites. Registry Editor has a Favorites menu almost nobody uses. Add the key before you work on it and you can return to it in one click instead of retyping a path and mistyping it.
• Write down what you changed. Path, value name, old data, new data, date. Three lines in a text file. When something breaks in a fortnight, this is the difference between a two-minute fix and a reinstall.
• Change one thing at a time and restart. Six edits in one sitting means you cannot tell which one caused the problem.
• Prefer Settings or Group Policy where they exist. On Pro editions, gpedit.msc writes the same registry values with names, descriptions and validation, and a supported way to set them back to Not Configured. On Home, where there is no Group Policy Editor, the registry is your only route — which is exactly why Home users end up doing this more often, not less.

A worked example worth copying

Our guide to re-enabling Task Manager when it has been disabled by an administrator is a good model of what a sane registry fix looks like: a named value with a stated meaning, one setting changed, an explanation of what disabled it in the first place, and a way back. If the guide you are following does not read like that, find a different guide.

Questions People Actually Ask

Is there a way to reset the Windows registry to default?

Not as a single command or button, and this is the honest headline of the whole page. Windows has never shipped a reset-the-registry function, because the registry is not one file and most of what is in it was put there by your installed software rather than by Windows. The four things that genuinely undo registry damage are System Restore, resetting the permissions on one specific key, an in-place repair upgrade, and Reset This PC — ranked here from least to most destructive.

How do I reset the registry in Windows 11 without reinstalling?

Use System Restore. Press Windows + R, type rstrui, press Enter, and pick a restore point dated before the problem started. Restore points snapshot the registry hives specifically, so this is the closest thing Windows has to an undo button. Your documents, photos and email are not touched.

Why do I get Error writing the value's new contents?

Your account does not have write permission on that key. Most system keys are owned by TrustedInstaller rather than by you or by Administrators, so even an administrator account is refused. Take ownership, grant Full Control, edit, then hand ownership back. Tamper Protection and Group Policy can produce the identical message for entirely different reasons.

How do I take ownership of a registry key?

Right-click the key → Permissions → Advanced. Next to Owner click Change, type your username, click Check Names and OK. Tick Replace owner on subcontainers and objects, then Apply. Back on Permissions, select your username and tick Full Control under Allow.

Should I leave my account with Full Control of a system key?

No. Put ownership back to TrustedInstaller once the edit is done. Windows Update services those keys as TrustedInstaller, and a key you permanently own can make a future update fail and roll back with an error code that tells you nothing. Open the same Advanced dialog and set the owner to NT SERVICE\TrustedInstaller.

Does sfc scannow repair the registry?

No, and it is the most repeated wrong answer on this topic. System File Checker verifies protected Windows system files against known-good copies and replaces damaged ones. It does not inspect registry values, will not undo a value you changed, and will not restore a key you deleted. Still worth running, because file damage and registry symptoms often share a cause.

Should I run DISM or SFC first?

DISM first, then SFC. SFC repairs damaged files by copying replacements out of the local component store, so if that store is itself damaged, SFC has nothing good to copy from and reports that it could not fix everything. DISM /Online /Cleanup-Image /RestoreHealth repairs the store. Fix the source, then run the tool that depends on it.

Is the RegBack folder empty and can I still use it?

It is empty on purpose. Since Windows 10 version 1803 Microsoft stopped writing automatic registry backups there to save disk space, so the files exist but are zero bytes. Any guide telling you to copy them over your live hives is describing behaviour that ended in 2018. You can switch it back on with a DWORD called EnablePeriodicBackup.

Does Last Known Good Configuration still exist in Windows 11?

Not as the boot menu option people remember. Microsoft removed it from the startup menu in Windows 8 and it has not returned in Windows 10 or Windows 11. The underlying control set still exists in the registry, but there is no supported way to select it during boot on a normal modern PC. System Restore replaced it, and is better.

Will importing a .reg file undo all my registry changes?

No, and this catches nearly everyone. Importing writes back every value the file contains, but it cannot remove values or keys you created after the export — they are not mentioned in the file, so nothing instructs Windows to delete them. A .reg export is insurance against editing a value wrongly. It is not a snapshot of the key.

Are registry cleaners safe to use?

They are unnecessary and carry real risk. Microsoft does not support registry cleaning utilities and warns that serious issues can occur. Orphaned entries cost no measurable performance on modern hardware, and the category has been a distribution channel for bundled adware and worse for two decades. There is nothing to gain.

Will resetting the registry delete my files?

System Restore does not touch personal files at all. An in-place repair upgrade keeps files and installed programs. Reset This PC with "Keep my files" keeps documents but removes every installed desktop application. "Remove everything" erases the drive. Back up regardless — a repair attempted on an already-unstable machine can fail partway.

What do I do if Windows will not boot after a registry edit?

Interrupt the boot three times with the power button to force the Recovery Environment, then Troubleshoot → Advanced options → System Restore and pick a point from before the edit. If that is unavailable, try Startup Repair, then Command Prompt from the same menu. If the machine still reaches the sign-in screen, try Safe Mode first.

Can I edit the registry on Windows 11 Home?

Yes. Registry Editor is on every edition. Home is where registry editing matters most, because Home has no Local Group Policy Editor, so settings a Pro user changes in a policy console can only be reached through the registry on Home. Permissions and ownership behave identically across editions.

Why does my registry edit keep reverting?

Something is rewriting it. Usually Group Policy or an MDM profile reapplying a managed setting on a schedule, Tamper Protection restoring Defender's own keys, an application that writes its settings on exit, or the wrong registry view — on 64-bit Windows a 32-bit program reads from the WOW6432Node branch instead.

Is System Restore enough to undo a bad registry change?

Usually yes, provided System Protection was on before the change. Restore points explicitly include the registry hives, so rolling back reverts the registry with them. The catch is that System Protection is off by default on many clean installs, so people discover they have no restore points at exactly the wrong moment. Check it now, while nothing is broken.

What Jake Does Now

The shop PC did come back — System Restore, from the Recovery Environment, to a point Windows had created automatically before a driver update the previous week. Not a point Jake made. Pure luck, and he knows it.

Three things changed after that week. System Protection is on, with 10% of the disk allocated. There is an external drive that gets a copy of the billing folder on the first of the month. And the registry cleaner is gone, along with the belief that the four-minute boot had anything to do with the registry.

It did not. It was a mechanical hard disk in a machine doing point-of-sale work. An SSD fixed in twenty minutes what an hour of registry tidying made permanently worse — which is the callback Ethan has been waiting all article to make, and he made it insufferably.

If your PC is slow rather than broken, start with speeding up Windows 11 and 10. It is a much better use of an hour than anything on this page.

Related Guides

Originally published November 2016 as a fix for one permissions error. We had Rewritten and re-tested in 2026 on Windows 11 24H2 and 25H2 and Windows 10 22H2. Two things we previously got wrong are corrected here: we never told you to hand ownership back to TrustedInstaller, and our companion article recommended the RegBack folder, which has been empty by design since Windows 10 version 1803. Tamper Protection, the in-place repair upgrade route, and the removal of Last Known Good Configuration are new to this version.