QuickBooks Error 1402

Let’s Dive in to see…

How to Fix QuickBooks Error=1402

QuickBooks Payroll Error PS060

QuickBooks Installation Error · Registry Access

How to Fix QuickBooks Error 1402

QuickBooks installer displays: "Error 1402: Could not open key: UNKNOWN\Components\..." or "Error 1402: Could not open key: HKEY_LOCAL_MACHINE\..."

Error 1402 is a Windows Registry key permission failure — the three words "Could not open key" in the error tell you exactly what layer failed. At QuickFix Bookkeeping, the fastest specific fix is the reboot.bat file — it re-registers all QB registry entries in one step without manual regedit editing.

The QuickFix Bookkeeping Distinction — The reboot.bat Fast Fix

Error 1402 specifically means the QB installer lacks permission to read or write a Windows Registry key it needs during installation. There are two levels of fix — the fast one and the manual one.

Fast fix — reboot.bat (try this first)

Navigate to C:\ProgramData\Common Files\Intuit\QuickBooks\ → find reboot.bat → double-click to run. This script re-registers all QB components in the Windows Registry in one step. Takes 30 seconds. Resolves 1402 in most cases without any manual registry editing.

Manual fix — regedit permissions (if reboot.bat fails)

regedit → HKEY_LOCAL_MACHINE\SOFTWARE\Classes → Edit → Permissions → Advanced → Add → type Everyone → Full Control → OK. This grants the QB installer read/write access to the entire Classes branch where it needs to register its components.

Error 1402 is not exclusive to QuickBooks — it is a Windows Installer error code that appears identically in Microsoft Office, Adobe Acrobat, and other enterprise software. The cause is always the same: Windows registry permissions are preventing the installer from accessing keys it needs. This is why the fix involves Windows registry permissions rather than anything QB-specific. If you see 1402 on other software installs too, the underlying Windows registry configuration needs repair.

What Causes QuickBooks Error 1402?

Registry Key Permissions Locked or Restricted

Primary cause — specific registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Classes have permissions that prevent non-system processes from reading or writing them. The QB installer needs to write its registration data into these keys and is denied access. This happens after a group policy change, a security software lockdown, or a Windows update that tightened registry security.

Leftover Registry Entries from Previous QB Install

A previous QB installation that was removed incompletely left registry entries in a locked or broken state. When a new QB installer tries to write to these entries, it encounters a conflict — the key exists but cannot be overwritten because of the orphaned permissions from the old installation. The reboot.bat file clears and re-registers these correctly.

Damaged .NET Framework, MSXML, or C++ Components

These components use the Windows Registry for their own registration. If they are corrupted, their registry entries may have incorrect permissions or be in a locked state — causing 1402 when the QB installer attempts to interact with those entries. The Install Diagnostic Tool repairs both the components and their registry entries simultaneously.

Antivirus or Firewall Protecting Registry Keys

Some security software specifically monitors and protects registry keys from being written to by external processes. When QB's installer attempts to register its components, the security software denies the write and QB reports 1402. Temporarily disabling the security software during installation removes this protection.

Insufficient User Account Permissions

The Windows user account running the QB installer does not have administrator rights, or is a restricted account on a corporate machine. The Windows Registry requires administrator-level access to write to HKEY_LOCAL_MACHINE keys. Running the installer with "Run as administrator" resolves this variant.

Temp Folder Permission Issue

If the Windows Temp folder (%temp%) has incorrect permissions, the QB installer cannot extract its files before registering them — producing 1402 indirectly. Granting Full Control to the current Windows user on the Temp folder resolves this variant.

How to Fix QuickBooks Error 1402

Start with Method 1 — run reboot.bat. This resolves most Error 1402 cases in 30 seconds without any manual registry editing.

METHOD 1 Run the reboot.bat File 30 seconds — resolves most 1402 cases
1

Open File Explorer → navigate to C:\ProgramData\Common Files\Intuit\QuickBooks\. Note: ProgramData is a hidden folder — if you can't see it, in File Explorer go to View → check "Hidden items."

2

Find the file named reboot.bat. Right-click → Run as administrator. A command prompt window opens briefly and closes. The script re-registers all QB components in the Windows Registry. After it completes, update QB Desktop (Help → Update QuickBooks Desktop) and retry installation. If 1402 clears — it's resolved.

METHOD 2 Run QuickBooks Install Diagnostic Tool Damaged .NET / MSXML / C++ components
1

Tool Hub → Installation IssuesQuickBooks Install Diagnostic Tool. Close all other programs. Let it run (up to 20 min). It repairs .NET Framework, MSXML, and C++ Redistributable — including their registry entries. Restart after completion → retry QB installation.

METHOD 3 Fix Registry Permissions Manually via Regedit reboot.bat didn't resolve — registry key access denied

Registry warning: Always export a backup before editing. File → Export → save to Desktop. An incorrect registry change can damage Windows. If unsure, use the Install Diagnostic Tool instead.

1

Press Windows + R → type regedit → Enter. File → Export → name it "RegistryBackup" → save to Desktop.

2

In the left panel navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Classes. Click Edit → Permissions → Advanced → click Add → type Everyone → Check Names → OK. Check Full Control. Click OK → Apply → OK. Close Registry Editor. Retry QB installation. This grants the installer access to all registry keys in the Classes branch where it registers its components.

METHOD 4 Fix Temp Folder Permissions + Disable Antivirus Temp folder access denied or antivirus blocking
1

Temp folder permissions: Windows + R → %temp% → Enter → right-click the temp folder address bar → Properties → Security tab → Edit → select your Windows username → check Full Control → Apply → OK.

2

Disable antivirus: right-click tray icon → disable real-time protection. Retry the QB installation immediately. After successful install, re-enable antivirus and add the QB folder to exclusions.

METHOD 5 Install in Selective Startup + Clean Install All above tried
1

Selective Startup: msconfig → Selective startup → Load system services → uncheck Load startup items → Services: Hide all Microsoft → Disable all → check Windows Installer → OK → Restart → retry install → then Normal startup. Clean Install (last resort, backup data first): Tool Hub → Installation Issues → Clean Install Tool. A clean install removes all previous QB installation remnants including leftover registry entries that could be causing persistent 1402 permission conflicts.

Quick Reference

Your situation Likely cause Start with
Any 1402 — first attempt Registry key permission Method 1 — run reboot.bat
reboot.bat didn't help — 1402 still on same key Damaged components with locked registry entries Method 2 — Install Diagnostic Tool
1402 error message shows specific key path Direct registry permission lockout Method 3 — regedit + Everyone Full Control
1402 on multiple software (not just QB) System-wide registry permission problem Method 3 → consider Windows repair

Frequently Asked Questions

Is Error 1402 exclusive to QuickBooks?
No — Error 1402 is a Windows Installer error code that appears identically across many applications including Microsoft Office, Adobe Acrobat, AutoCAD, and various other enterprise software. The cause is always a Windows Registry key permission problem, not anything specific to QuickBooks. If you see 1402 on other software installs as well as QB, the underlying Windows registry permissions need a broader repair — this is a Windows configuration issue, not a QB-specific bug. The regedit fix (granting Everyone Full Control on HKEY_LOCAL_MACHINE\SOFTWARE\Classes) addresses it at the system level for all applications.
What does reboot.bat actually do?
The reboot.bat script in the QB Common Files folder runs a series of Windows commands that re-register all QuickBooks-related components in the Windows Registry. It uses regsvr32 and msiexec commands to re-register DLL files, COM objects, and installer packages associated with QB. This clears any stale or incorrectly-permissioned registry entries from previous QB installations and sets them up fresh with the correct permissions. It is faster and safer than manual regedit editing because it only touches QB-specific registry entries rather than broad system keys.
Is it safe to grant Everyone Full Control on HKEY_LOCAL_MACHINE\SOFTWARE\Classes?
This is a common and widely-documented fix for registry permission errors affecting QB and other software. HKEY_LOCAL_MACHINE\SOFTWARE\Classes is the registry branch where COM objects and file type associations are registered — it is not a sensitive security-critical key. Granting Everyone read/write access here allows any application's installer to register its components properly. On a home or small business PC, this is a standard troubleshooting step. On a domain-joined corporate PC, consult your IT administrator before modifying Group Policy-managed registry keys, as the permission change may be reverted by policy.

Related QuickBooks Installation Errors

Error 1402 Persisting After reboot.bat and regedit Fix?

Let QuickFix Bookkeeping Get QuickBooks Installed.

Certified Intuit ProAdvisors — Installation Specialists

Persistent Error 1402 after reboot.bat and registry permission fix typically indicates a Group Policy restriction on a domain-joined machine, or deeper Windows registry corruption that requires specialist-level repair tools.

Book a Free 30-Minute Consultation

No obligation. Same-day response. QuickBooks installed fast.