Fix it now
0x84B10001 is a wrapper, not a diagnosis. Setup stopped and wrote the real reason into its own logs a few lines earlier. Microsoft does not publish a meaning for the wrapper code, so open the setup log folder, find the inner error, and fix that instead.
explorer "%ProgramFiles%\Microsoft SQL Server"
- In
<nnn>\Setup Bootstrap\Log, openSummary.txtfrom the folder itself, not from a subfolder. Read the Product features discovered section to see which feature reports a failure. - Now open the timestamped subfolder named for the failure time. It holds
Detail.txt, the per-feature MSI logs andSystemConfigurationCheck_Report.htm. - Search
Detail.txtfor “Failed” and read from the end backwards. Not every hit is fatal; the last one before setup gave up is the one that matters. - Match the inner code:
0x80070002is file not found,1638means another version of the product is already installed,0x8007054Fis an internal Windows error whose surrounding lines matter more than the number. - Clear the blocker, reboot if anything asked for one, and rerun setup from a local folder rather than a mounted image or a network share.
Microsoft’s own list of media-corruption symptoms includes setup error 2337, a corrupt Sql.cab, “Setup.exe badimage” and “Error reading from file”. If you see any of those, stop diagnosing and get the media again.
If setup completes you are done. If not, the next section explains why the wrapper code tells you nothing and what the log structure is actually recording.
Why it happens
SQL Server setup is a controller that runs many separate installers in sequence: rule checks, shared feature packages, per-instance packages, and configuration work that runs after the files land. When one of those fails, the controller stops and reports its own generic failure rather than passing the component’s error upwards. 0x84B10001 is that generic failure and 0x84BB0001 is another of the same shape. Microsoft publishes no meaning for either, which is itself the point: they are not codes to look up.
Everything is written to disk as it happens, and the structure matters more than most people realise. Summary.txt sits in the Log folder itself and gives the overall result, the system properties, the features already installed and the rule status. Each attempt then gets its own folder named yyyyMMdd_HHmmss, holding a machine-specific summary, Detail.txt, a log per MSI package, the system configuration check report and a Datastore folder of XML snapshots. Microsoft’s documented reading order is Summary first, then the timestamped folder, then Detail searched for “Failed”.
The inner codes are ordinary Windows and Windows Installer codes rather than SQL Server ones. 0x80070002 is the HRESULT form of system error 2, the system cannot find the file specified. 0x8007054F is system error 1359, an internal error occurred, which tells you nothing on its own and everything in context. 1638 is Windows Installer refusing because another version of the product is already installed.
A pending reboot is blocking the rule checks
You have this one if Setup stops during rule checking, before it copies any files, and the rule report mentions a restart being required.
- Reboot and rerun setup. In most cases that is the whole fix.
- If the rule still fails, read
SystemConfigurationCheck_Report.htmin the timestamped folder to see exactly which rule failed rather than guessing. - Let Windows Update finish first. An update mid-cycle is the most common source of a pending restart nobody remembers scheduling.
Editing the registry values Windows uses to track pending restarts can leave a genuine update half applied. Reboot first, twice if necessary, before touching anything.
The media is damaged, incomplete, or goes away mid-install
You have this one if Detail.txt names a package or cabinet file that could not be opened, or you see one of Microsoft’s documented corruption messages.
- Copy the whole ISO contents to a local folder rather than running from a mounted image, a share or an optical drive. Microsoft names installing from a local drive as the fix for the network-read failures specifically.
- Confirm the copy completed rather than assuming it did, then rerun setup from that folder.
- If it fails on the same file from a verified local copy, download the media again from the original location.
Microsoft’s documented corruption list includes error 2337, “The cabinet file ‘Sql.cab’ … is corrupt”, “Setup.exe badimage”, “The system cannot open the device or file specified” and “Setup.rll is either not designed to run on Windows or it contains an error”.
Another version of the product is already installed
You have this one if 1638 appears in the trace, or a feature you are adding is greyed out because setup believes it is already present.
- Run the installation centre’s Tools page and take the installed features discovery report. It lists what this machine genuinely has.
- Compare that against what you are installing, remembering that shared components are versioned separately from instances.
- Remove genuinely orphaned entries through the supported uninstall route rather than by deleting folders, and never remove a shared component another instance still depends on.
Setup cannot write where it was told to
You have this one if An access-denied or internal Windows failure appears in Detail.txt around a path, a service creation or a registry write.
- Run setup elevated, as a genuine local administrator. Microsoft states this as a prerequisite for local installations, and for a remote share the account needs read permission on the share.
- Check the target drive exists, has free space, and is not a mapped drive or removable device.
- Confirm the temporary folder is writable, pause on-access scanning for the install window, and rerun.
Full reference
What is in the log folder, and what each file answers
| File | Where | What it answers |
|---|---|---|
Summary.txt |
The Log folder itself | Did it fail, which features were discovered, and what the rules said |
Summary_<MachineName>_<date>.txt |
The timestamped folder | The same for that one attempt |
Detail.txt |
The timestamped folder | The ordered trace of every action, with dependencies |
<Feature>_<Arch>_<Interaction>.log |
The timestamped folder | The MSI log for one package, written by msiexec |
SystemConfigurationCheck_Report.htm |
The timestamped folder | Which rule failed, when setup never got past the checks |
ConfigurationFile.ini |
The timestamped folder | Exactly what the wizard was asked to do |
Datastore |
The timestamped folder | XML snapshots of configuration state per phase |
The folder pattern is %ProgramFiles%\Microsoft SQL Server\<nnn>\Setup Bootstrap\Log, where <nnn> is the numeric release folder. For an unattended install the logs go to %temp%\sqlsetup*.log instead. Everything in a run folder is also archived into a Log*.cab in the same place, which is the file to send when someone asks for the logs.
Reading an inner code
| Inner code | What it is | What to do |
|---|---|---|
0x80070002 |
System error 2, ERROR_FILE_NOT_FOUND | Find the path in Detail.txt. Incomplete media or a path that disappeared mid-install |
0x8007054F |
System error 1359, ERROR_INTERNAL_ERROR | Meaningless alone. Read the twenty lines above it |
1638 |
Windows Installer: another version of this product is already installed | Take the discovery report before removing anything |
2337 |
Setup error Microsoft lists under damaged media | Get the media again |
0x84B10001 / 0x84BB0001 |
Setup wrapper codes with no published meaning | Ignore them and read the inner error |
The 0x8007 prefix
A code of the form 0x8007xxxx is a Windows system error wrapped as an HRESULT: strip the 0x8007, read the remaining four hex digits as a Win32 error number, and look it up in Microsoft’s system error codes reference. 0x0002 is 2, the system cannot find the file specified. 0x0005 is 5, access is denied. 0x054F is 1359, an internal error occurred. That one substitution turns most of what setup writes into something you can look up rather than guess at.
Repairing rather than reinstalling
Where an existing installation is the thing that is broken – a missing cached installer file, a component that will not patch – Microsoft’s documented first option is a repair rather than an uninstall: setup.exe /ACTION=REPAIR /INDICATEPROGRESS=TRUE. It is a great deal less disruptive than removing an instance, and on a machine hosting several instances it is the only sensible starting point.
Rules that stop setup before it installs anything
A failure during rule checking is different in kind from a failure during installation, and it is worth recognising because nothing has been written yet. The system configuration check report in the timestamped folder lists every rule that ran and its status, which is far quicker to read than the trace. The rules that block most often are a pending restart, an account that is not a genuine local administrator, a target path that is not local fixed storage, and a machine that has not met the operating system or framework prerequisites for that release. Clear the rule rather than looking for a way past it: setup is refusing for the same reason the install would fail later, and more expensively.
- Read
SystemConfigurationCheck_Report.htmfirst when setup stopped early. It names the rule in plain language. - A rule failure leaves the machine unchanged, so there is no partial state to clean up before retrying.
- The hardware and software requirements page for the release you are installing is the authority on prerequisites; check it before assuming the rule is wrong.
ConfigurationFile.iniin the same folder records exactly what the wizard was asked for, which is what to compare against a server where the same install worked.
When the checks pass and it still fails
- Take the installed features discovery report from the installation centre’s Tools page and compare it against a working server.
- Install from a local folder. Microsoft names running from a network location as the cause of the read failures specifically.
- Use a configuration file. An unattended install is not more reliable, but it is reproducible, so you can diff a failing server against a working one line by line instead of comparing wizard screens from memory.
- Keep the Log*.cab from each attempt. Comparing two failures is often quicker than reading one.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0x84B10001 |
A generic SQL Server setup failure wrapper. Microsoft publishes no meaning for it; the specific reason is the inner error in the setup logs | not published by the vendor |
0x80070002 |
The HRESULT form of system error 2, ERROR_FILE_NOT_FOUND: the system cannot find the file specified | Microsoft Learn |
1638 |
Windows Installer ERROR_PRODUCT_VERSION: another version of this product is already installed | Microsoft Learn |
0x84BB0001 |
Another setup wrapper code of the same family, with no published meaning; read the inner error | not published by the vendor |
0x8007054F |
The HRESULT form of system error 1359, ERROR_INTERNAL_ERROR: an internal error occurred | Microsoft Learn |
Confirm the fix worked
Summary.txtfor the final run reports a successful result rather than a failure.- The instance appears in SQL Server Configuration Manager and its service starts and stays running.
SELECT @@VERSION;returns from a new connection to the instance.- The installed features discovery report lists every feature you expected.
- Reboot the machine and confirm the service comes up on its own.
Questions people ask about this
Do I need new media or a new key because of this?
No. This is a local installation failure and it costs nothing to fix. Setup usually has not reached the point of validating a key at all, and your entitlement is untouched by a failed install.
What does 0x84B10001 actually mean?
Nothing you can look up. Microsoft publishes no meaning for it, and no acceptable source does either. It is the controller reporting that something inside the installation failed, and the real code is a few lines earlier in Detail.txt.
Can I just run setup again and hope?
One retry after a reboot is reasonable, because a pending restart is the most common blocker. Repeating it without reading Detail.txt reproduces the same failure and leaves more partial state behind each time.
Where exactly does setup write its logs?
%ProgramFiles%\Microsoft SQL Server\<nnn>\Setup Bootstrap\Log, where <nnn> is the numeric release folder. Summary.txt is in that folder; each attempt also gets a yyyyMMdd_HHmmss subfolder with Detail.txt and the per-package MSI logs. Unattended installs write to %temp%\sqlsetup*.log.
Would an unattended install be more reliable?
It is more reproducible, which is not the same thing. A configuration file records exactly what was requested, so you can compare a failing server against a working one instead of comparing recollections of wizard screens.
