SQL Server 2014 will not complete install on Windows 10

Question

I have been trying to install SQL Server 2014 on Windows 10 and it hangs at the last of the install with a Prerequisite Error.

I have search through internet for suggestions and tried most to no avail.

I have reset the computer on Windows 10 several times to where Windows 10 is the only software on it and tried installing SQL Server 2014 Express again to no avail.

I have a HP Touchsmart PC IQ 846

Processor Intel Core(TM)2 Duo Cpu P7350 @ 2.00GHz

Ram 4.00 GB

64 bit operating system, x64-based processor

Windows 10 Home version 1511

OS Build 10586.36

It hangs at Installation Progress  SqlEngineDBStartConfigAction_install_configrc_Cpu64

TITLE: Microsoft SQL Server 2014 Setup
------------------------------

The following error has occurred:

Could not find the Database Engine startup handle.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%25400x4BDAF9BA%25401306%254025

------------------------------
BUTTONS:

OK
------------------------------

Answer 1

Please read completely

Could not find database engine startup handle

SQL Server is installed go to SSCM and try starting SQL Server with Local System account

---

Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

My Wiki Articles
MVP

Answer 2

1. If you have installed SQL Server then you should remove it completely through the Control Panel and restart the server.

2. When you get to the Server Configuration page as shown below, you will notice that the SQL Server Database Engine service is using the account NT Service\MSSQLSERVER.

3. Change the account from NT Service\MSSQLSERVER to NT AUTHORITY\SYSTEM by clicking on the drop-down box, selecting browse and then typing SYSTEM in Select User, Computer, Service Account, or Group window in Active Directory. Click OK to accept the new account.

4. Continue on with the installation as you normally would.

Answer 3

Another solution http://kalcik.net/2014/04/04/problems-with-the-installation-of-sql-server-2014-after-the-windows-8-1-update/

Answer 4

Ok, I have tried everyone's solutions but it still wouldn't install.  However, I now have an error log.

2016-01-09 15:01:38.45 Server      Microsoft SQL Server 2014 - 12.0.2000.8 (X64)
 Feb 20 2014 20:04:26
 Copyright (c) Microsoft Corporation
 Express Edition (64-bit) on Windows NT 6.3 <X64> (Build 10586: )

2016-01-09 15:01:38.45 Server      UTC adjustment: -6:00
2016-01-09 15:01:38.45 Server      (c) Microsoft Corporation.
2016-01-09 15:01:38.45 Server      All rights reserved.
2016-01-09 15:01:38.48 Server      Server process ID is 8392.
2016-01-09 15:01:38.48 Server      System Manufacturer: 'HP-Pavilion', System Model: 'NP233AA-ABA IQ846'.
2016-01-09 15:01:38.48 Server      Authentication mode is WINDOWS-ONLY.
2016-01-09 15:01:38.48 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2016-01-09 15:01:38.48 Server      The service account is 'WORKGROUP\HP$'. This is an informational message; no user action is required.
2016-01-09 15:01:38.48 Server      Registry startup parameters:
  -d C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf
  -e C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG
  -l C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2016-01-09 15:01:38.48 Server      Command Line Startup Parameters:
  -s "MSSQLSERVER"
  -m "SqlSetup"
  -Q
  -q "SQL_Latin1_General_CP1_CI_AS"
  -T 4022
  -T 4010
  -T 3659
  -T 3610
  -T 8015
  -d "C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Template Data\master.mdf"
  -l "C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Template Data\mastlog.ldf"
2016-01-09 15:01:38.85 Server      SQL Server detected 1 sockets with 2 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2016-01-09 15:01:38.85 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2016-01-09 15:01:38.85 Server      Detected 4095 MB of RAM. This is an informational message; no user action is required.
2016-01-09 15:01:38.85 Server      Using conventional memory in the memory manager.
2016-01-09 15:01:38.86 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2016-01-09 15:01:38.90 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2016-01-09 15:01:38.92 Server      Query Store settings initialized with enabled = 1,
2016-01-09 15:01:38.92 Server      The maximum number of dedicated administrator connections for this instance is '1'
2016-01-09 15:01:38.92 Server      This instance of SQL Server last reported using a process ID of 4336 at 1/9/2016 2:58:38 PM (local) 1/9/2016 8:58:38 PM (UTC). This is an informational message only; no user action is required.
2016-01-09 15:01:38.92 Server      Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2016-01-09 15:01:38.93 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2016-01-09 15:01:38.94 Server      Database Mirroring Transport is disabled in the endpoint configuration.
2016-01-09 15:01:38.94 Server      Software Usage Metrics is disabled.
2016-01-09 15:01:38.94 spid9s      Warning ******************
2016-01-09 15:01:38.94 spid9s      SQL Server started in single-user mode. This an informational message only. No user action is required.
2016-01-09 15:01:38.95 spid9s      Starting up database 'master'.
2016-01-09 15:01:38.95 spid9s      Error: 5178, Severity: 16, State: 1.
2016-01-09 15:01:38.95 spid9s      Cannot use file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Template Data\master.mdf' because it was originally formatted with sector size 4096 and is now on a volume with sector size 3072. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
2016-01-09 15:01:38.96 spid9s      Error: 5178, Severity: 16, State: 1.
2016-01-09 15:01:38.96 spid9s      Cannot use file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Template Data\master.mdf' because it was originally formatted with sector size 4096 and is now on a volume with sector size 3072. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
2016-01-09 15:01:38.98 spid9s      Error: 5178, Severity: 16, State: 1.
2016-01-09 15:01:38.98 spid9s      Cannot use file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Template Data\mastlog.ldf' because it was originally formatted with sector size 4096 and is now on a volume with sector size 3072. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
2016-01-09 15:01:38.98 spid9s      Error: 5178, Severity: 16, State: 1.
2016-01-09 15:01:38.98 spid9s      Cannot use file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Template Data\mastlog.ldf' because it was originally formatted with sector size 4096 and is now on a volume with sector size 3072. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.

I've not done this fix before.  Some help please?

Answer 5

Hello,

“Microsoft SQL Server supports disk drives that have standard native sector sizes of 512 bytes and 4 KB.”

Source: https://support.microsoft.com/en-us/kb/926930

I have read about users reporting this issue after upgrading to Windows 10. They have solved the issue by updating the storage drivers for drivers compatible with Windows 10.

Alternatively, you may want to try the workaround posted in the following threads:

https://connect.microsoft.com/SQLServer/feedback/details/733652/service-inicialization-failled-by-corrupted-system-resource-in-windows-8-client

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/9de4dddc-624e-4a0b-a539-7d1e6c94b946/cant-open-database-after-upgrading-to-windows-10?forum=sqldatabaseengine

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/94d62e2a-7a9b-4ba0-a408-8e30e7fe47f4/sql-server-2008-r2-installation-error-5178?forum=sqlsetupandupgrade

Hope this helps.

Regards,

Alberto Morillo
SQLCoffee.com

Answer 6

I would prefer not to do a work around on this and RAID is not installed on this PC.  I can't find any updated Microsoft Storage Controller Drivers.  The one that is installed dates back to 2006.  Any suggestions?

---

CZPitcher

Answer 7

Can you manually run Windows Update? Make sure you get the optional updates also, storage controller drivers are usually rated optional unless there's some security or corruption bug. If you don't find it there, your machine might have some type of system management software from HP that can install/update software and drivers. Check there.

The problem lies with the Intel storage manager that's reporting incorrect data. IIRC, it used to be Intel matrix storage manager which then evolved into Intel Rapid Storage Technology. Your machine probably has the older Intel matrix storage manager. Note that there's a dependency on the Intel chipset utility so you'll have to install that first (if not already done). Pop over to the HP site to find the relevant drivers and firmware updates for your machine and get them all up on the latest version (assuming Windows update did not find them) then install SQL Server.

---

No great genius has ever existed without some touch of madness. - Aristotle