Fix Cannot Import to Registry: All Data Not Written

If you see “Cannot import to registry: not all data was successfully written to the registry” when adding a .reg file, the fix is to run the import from an elevated Command Prompt and check for file encoding or permission issues. This error usually means Windows blocked part or all of the registry merge, often because the file is not in the correct UTF-16 LE format or you lack write access to the target keys.

What Causes This Error

Registry files (.reg) are plain text files that contain keys and values. When you double-click one, Windows merges it into the registry. The error appears when the merge fails partway through. Common causes include:

File encoding: Windows expects .reg files to be saved in UTF-16 LE (Unicode) or ANSI. If the file is UTF-8 without a BOM, the first line may be misread, and the import stops.
Permissions: You need administrative rights to write to certain registry hives like HKLM (HKEY_LOCAL_MACHINE). A standard user account will get this error.
Invalid syntax: A missing backslash, an extra comma, or an unquoted value can cause the parser to fail.
Registry key in use or protected: Some keys are protected by Windows or are in use by a service, blocking writes.
File path or name issues: Non-ASCII characters in the file name or path can confuse the import.

How Registry Import Actually Works

When you import a .reg file, Windows parses it line by line. The first line must be Windows Registry Editor Version 5.00 (for Windows 2000 and later). Each key is enclosed in square brackets, and each value follows on the next line. The import is not atomic — if it fails halfway, some keys may already be written, leaving the registry partially modified. That is why the message says “not all data was successfully written.”

The file encoding matters because the parser reads the first two bytes to detect the format. A UTF-8 BOM (bytes EF BB BF) is not recognized, so the first line becomes garbled. The import then fails immediately or after a few lines.

Step-by-Step Fixes

Run the import as administrator. Right-click the .reg file and choose “Merge,” or open Command Prompt as administrator and type reg import "C:\path\file.reg". This gives you write access to protected keys.
Check the file encoding. Open the file in Notepad, go to File > Save As, and set “Encoding” to “Unicode” (UTF-16 LE). Save with a new name, then try importing that.
Validate the syntax. Look for the version line at the top. Ensure every key line starts with [ and ends with ]. Values must be in the form "Name"=type:data. A single typo can stop the whole import.
Split the file. If the file is large, break it into smaller parts. This helps isolate the offending line. Import each part separately.
Use reg.exe instead. In an elevated Command Prompt, run reg import file.reg. The command-line tool gives more detailed error messages than the GUI merge.
Check for read-only or locked files. Make sure the .reg file itself is not marked read-only, and that it is not open in another program.

Common Mistakes and Misconceptions

One misconception is that the error means the entire import failed. In reality, partial writes can occur. Always back up the registry (export the relevant keys) before attempting a fix. Another common mistake is using a .reg file created on a different Windows version — the version line may be missing or incorrect. Also, users often forget that 64-bit Windows has a separate registry view for 32-bit applications; a key meant for a 32-bit app may need to go under Wow6432Node.

Another frequent error is copying a .reg file from a web page where the line breaks are not preserved. The file may end up as one long line. Open it in Notepad and verify that each key and value is on its own line.

When to Use the Command Line vs. GUI

The GUI merge (double-click) is fine for small, simple files. The command line (reg import) is more reliable for troubleshooting because it shows the exact line where the error occurs, like “ERROR: Invalid syntax.” It also works in scripts and can be run without a logged-in user. For system-wide changes, use an elevated command prompt. For user-specific changes, a normal prompt may suffice.

Safety and Backup Tips

Before importing any .reg file, especially one you did not create, back up the registry. In regedit, select the root key you are about to modify, go to File > Export, and save a .reg backup. You can also create a system restore point. Never import a file from an untrusted source without reviewing its contents first — a .reg file can delete keys, change security settings, or alter system behavior. If you are not sure what a key does, do not import it.

Alternatives to Manual Import

If you are trying to apply settings from a .reg file and the import keeps failing, consider using Group Policy (for domain-joined machines), PowerShell’s Set-ItemProperty to modify specific values, or a script that creates keys one by one. For simple settings, you can also use the Settings app if the option is available. These alternatives give you finer control and better error reporting.

Frequently Asked Questions

Why does the error say “not all data was successfully written”?

It means the import process encountered an error partway through. Some keys may have been written before the failure, so the registry is now partially modified. The message is generic and does not tell you which line failed.

Can I ignore this error if my program still works?

No. The program may work because the missing keys are not critical, but the import was incomplete. You should fix the file and re-import to ensure all intended changes are applied.

How do I know if my .reg file is UTF-16 LE?

Open the file in Notepad and look at the bottom right corner of the status bar. It will show “UTF-16 LE” or “ANSI.” If it says “UTF-8,” you need to re-save it as Unicode.

What does “ERROR: Invalid syntax” mean in reg import?

It means the parser found a line that does not follow the .reg format. Check for missing backslashes in key paths, unquoted strings, or extra spaces. The error message usually includes the line number.

Is it safe to import a .reg file from a forum or website?

Only if you trust the source and have reviewed the file. A .reg file can execute arbitrary registry changes, including disabling security features. Always back up first and inspect every key and value.

Can I import a .reg file on a 32-bit system that was made for 64-bit?

Yes, but the keys may be placed in different locations. The import will still run, but the intended effect may not occur because the registry structure differs. It is best to use a file designed for your system architecture.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →