> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-software/troubleshoot/command-centre-errors/command-centre-errors-unable-to-install-sql-win11.md).

# Unable to install SQL on Windows 11

[Command Centre - Errors](/knowledge-hub/products/cc-software/troubleshoot/command-centre-errors.md) › Unable to install SQL on Windows 11

Occurs only on systems where the system disk sector size is greater than 4 KB (essentially PCs, servers, or VMs with a Solid State Drive). It can present itself after a reboot, so it is possible to install SQL, have services start, then have them never start again after the reboot. It can also occur on a fully functional Windows 10 deployment after the machine is upgraded to Windows 11.

The root cause is discussed at [Troubleshoot OS 4KB disk sector size (Microsoft Learn)](https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/database-file-operations/troubleshoot-os-4kb-disk-sector-size).

## Resolution options

* Downgrade or migrate the system to Windows 10.
* Migrate to a supported Windows Server edition.
* Install the SQL databases on a second drive with a sector size that meets the restriction (a traditional hard drive, not an SSD).
* Patch Windows 11 with a registry key that forces the sector size to be compatible with SQL, then reboot. **However**, once you have a broken SQL instance, every reboot initiates a consistency check that will fail. Uninstall every SQL instance that was installed before the registry change, then reinstall SQL after the machine has been rebooted.

To add the registry value, open a command prompt **As Administrator** and run:

```
REG ADD "HKLM\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device" /v "ForcedPhysicalSectorSizeInBytes" /t REG_MULTI_SZ /d "* 4095" /f
```

Validate it was added:

```
REG QUERY "HKLM\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device" /v "ForcedPhysicalSectorSizeInBytes"
```

Or in PowerShell (Administrator):

```powershell
New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device" -Name "ForcedPhysicalSectorSizeInBytes" -PropertyType MultiString -Force -Value "* 4095"
```

Validate:

```powershell
Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device" -Name "ForcedPhysicalSectorSizeInBytes"
```

**Reboot after this registry change.**

> **Note:** This is not a Command Centre issue but an operating system issue. Microsoft recommends running SQL on a Windows Server operating system; Windows 11 is strictly a desktop environment.

***

🔗 **Related**

* [Command Centre - Errors - Microsoft SQL Server Express Setup failed and rolled back with the error code 222](/knowledge-hub/products/cc-software/troubleshoot/command-centre-errors/command-centre-errors-microsoft-sql-se.md). Another SQL install failure during Command Centre setup.
* [Databases - Considerations](/knowledge-hub/products/cc-software/configure/databases-an-overview-of-command-centr/databases-considerations.md). SQL version and platform planning.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/products/cc-software/troubleshoot/command-centre-errors/command-centre-errors-unable-to-install-sql-win11.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.