I have just attempted to install SQL Server 2014 Express SP1 in a freshly installed windows 10.0.10240  Both Windows and SQL Server are the x64 versions.

I have also installed a new 2TB disk which seems to be causing the problem, specifically with SQL Server.  I have no problems will all of the other applications like Visual Studio and Microsoft Office to name two examples.  But everything else works, too.

*********************

Update:  I just recalled that I had previously installed SQL Server 2014 Express in Windows 10 (Episode I).  I just checked and it still works.  It was installed on my previous disk drive and then I updated to the new drive.

The problem is occurring on my Windows 10 Episode III partition on the same disk.

I am on 'Episode III' (Build 10.0.240) because of serious problems I encountered with build 10.0.532.

So the issue appears to be an installation problem, only.  The cloning of the relevant partition to the new drive did not result in a broken SQL server.  It works fine on the new disk.

From what I have gleaned from looking on the internet, this appears to be related to how my new 2T, "advanced" (whatever that means) disk reports the sector size.  It appears that SQL server would run correctly, if only the installer could get past this issue.

*********************

Here is what I have so far, including the SQL Server Installation Log:

++++++++++++++++++++++++++++++++++

SQL Server 2014 SP1 Express Installer Error Msg:
Could not find the Database Engine startup handle.

++++++++++

Relevant event log entry:

"Cannot use file 'C:\Program Files\Microsoft SQL Server\MSSQL12.X2014\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."

(Note: The statement "Move the file to a volume ... etc." is, on its face, nonsensical, given the sector sizes as they are presented.)
(Or, put less diplomatically: 3072 is less than 4096!)

++++++++++

running fsutil fsinfo ntfsinfo c: on the new hard drive returns the following:
Microsoft Windows [Version 10.0.10240]
++++++++++
NTFS Volume Serial Number :        0xfc42bd4b42bd0b80
NTFS Version   :                   3.1
LFS Version    :                   2.0
Number Sectors :                   0x000000003d08f7f8
Total Clusters :                   0x0000000007a11eff
Free Clusters  :                   0x00000000063ccfed
Total Reserved :                   0x00000000000059d0
Bytes Per Sector  :                512
Bytes Per Physical Sector :        512
Bytes Per Cluster :                4096
Bytes Per FileRecord Segment    :  1024
Clusters Per FileRecord Segment :  0
Mft Valid Data Length :            0x000000001b5c0000
Mft Start Lcn  :                   0x00000000000c0000
Mft2 Start Lcn :                   0x0000000000000002
Mft Zone Start :                   0x0000000001806a80
Mft Zone End   :                   0x0000000001812340
Max Device Trim Extent Count :     0
Max Device Trim Byte Count :       0x0
Max Volume Trim Extent Count :     62
Max Volume Trim Byte Count :       0x40000000
Resource Manager Identifier :     8E4C4407-53D7-11E5-8180-806E6F6E6963
++++++++++

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Start of the SQL Server Installation Log:
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2061893607
  Start time:                    2015-09-05 21:21:44
  End time:                      2015-09-05 22:29:40
  Requested action:              Install

Setup completed with required actions for features.
Troubleshooting information for those features:
  Next step for SQLEngine:       Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Next step for FullText:        Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Next step for Replication:     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.


Machine Properties:
  Machine name:                  CSC-VAIO-F111
  Machine processor count:       8
  OS version:                    Windows 8
  OS service pack:               
  OS region:                     United States
  OS language:                   English (United States)
  OS architecture:               x64
  Process architecture:          64 Bit
  OS clustered:                  No

Product features discovered:
  Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered  Configured

Package properties:
  Description:                   Microsoft SQL Server 2014
  ProductName:                   SQL Server 2014
  Type:                          RTM
  Version:                       12
  Installation location:         Y:\SQLServer2014SP1Setup\x64\setup\
  Installation edition:          Express

  Slipstream:                    True
  SP Level                       1

Product Update Status:
  Success: KB 3058865

Product Updates Selected for Installation:
  Title:                         Microsoft SQL Server 2014  Express Advanced SP1
  Knowledge Based Article:       KB 3058865
  Version:                       12.1.4100.0
  Architecture:                  x64
  Language:                      1033

  Update Source:                 Slipstream


User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      true
  AGTSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Disabled
  ASBACKUPDIR:                   Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   Config
  ASDATADIR:                     Data
  ASLOGDIR:                      Log
  ASPROVIDERMSOLAP:              1
  ASSERVERMODE:                  MULTIDIMENSIONAL
  ASSVCACCOUNT:                  <empty>
  ASSVCPASSWORD:                 <empty>
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            <empty>
  ASTEMPDIR:                     Temp
  BROWSERSVCSTARTUPTYPE:         Disabled
  CLTCTLRNAME:                   <empty>
  CLTRESULTDIR:                  <empty>
  CLTSTARTUPTYPE:                0
  CLTSVCACCOUNT:                 <empty>
  CLTSVCPASSWORD:                <empty>
  CLTWORKINGDIR:                 <empty>
  COMMFABRICENCRYPTION:          0
  COMMFABRICNETWORKLEVEL:        0
  COMMFABRICPORT:                0
  CONFIGURATIONFILE:             
  CTLRSTARTUPTYPE:               0
  CTLRSVCACCOUNT:                <empty>
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     <empty>
  ENABLERANU:                    true
  ENU:                           true
  ERRORREPORTING:                false
  FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, RS, CONN, BC, SDK, BOL, SSMS, ADV_SSMS, LOCALDB
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher$X2014
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTSQLSERVERLICENSETERMS:  true
  INDICATEPROGRESS:              false
  INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
  INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
  INSTALLSQLDATADIR:             <empty>
  INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
  INSTANCEID:                    X2014
  INSTANCENAME:                  X2014
  ISSVCACCOUNT:                  NT AUTHORITY\Network Service
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  MATRIXCMBRICKCOMMPORT:         0
  MATRIXCMSERVERNAME:            <empty>
  MATRIXNAME:                    <empty>
  NPENABLED:                     0
  PID:                           *****
  QUIET:                         false
  QUIETSIMPLE:                   false
  ROLE:                          AllFeatures_WithDefaults
  RSINSTALLMODE:                 FilesOnlyMode
  RSSHPINSTALLMODE:              DefaultSharePointMode
  RSSVCACCOUNT:                  NT Service\ReportServer$X2014
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         *****
  SECURITYMODE:                  SQL
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 NT Service\MSSQL$X2014
  SQLSVCPASSWORD:                <empty>
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           CSC-VAIO-F111\WebAccess, ccotton
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBLOGDIR:               <empty>
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SQMREPORTING:                  false
  TCPENABLED:                    0
  UIMODE:                        AutoAdvance
  UpdateEnabled:                 true
  UpdateSource:                  Slipstream
  USEMICROSOFTUPDATE:            false
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150905_212143\ConfigurationFile.ini

Detailed results:
  Feature:                       Management Tools - Complete
  Status:                        Passed

  Feature:                       Client Tools Connectivity
  Status:                        Passed

  Feature:                       Client Tools SDK
  Status:                        Passed

  Feature:                       Client Tools Backwards Compatibility
  Status:                        Passed

  Feature:                       Management Tools - Basic
  Status:                        Passed

  Feature:                       Database Engine Services
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred during the setup process of the feature.
  Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x851A0019
  Error description:             Could not find the Database Engine startup handle.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.4100.1&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025

  Feature:                       Full-Text and Semantic Extractions for Search
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x851A0019
  Error description:             Could not find the Database Engine startup handle.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.4100.1&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025

  Feature:                       SQL Server Replication
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x851A0019
  Error description:             Could not find the Database Engine startup handle.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.4100.1&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025

  Feature:                       Reporting Services - Native
  Status:                        Passed

  Feature:                       SQL Browser
  Status:                        Passed

  Feature:                       Documentation Components
  Status:                        Passed

  Feature:                       SQL Writer
  Status:                        Passed

  Feature:                       LocalDB
  Status:                        Passed

  Feature:                       Setup Support Files
  Status:                        Passed

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150905_212143\SystemConfigurationCheck_Report.htm
+++++++++++++++++++++++++++++++++++++++++

Any help you can provide will be very much apprec

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 thread:

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

Hope this helps.

Regards,

Alberto Morillo
SQLCoffee.com

Hi Alberto,

Thank you for responding, but the link you provided contains no solution, whatsoever ...  And it is closed as non reproducible!

Charles.

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/e0d4c53c-dc84-43be-9cac-4d7d0ceab0c4/sql-server-express-2014-on-win81-could-not-find-the-database-engine-startup-handle?forum=sqlsetupandupgrade

http://social.technet.microsoft.com/wiki/contents/articles/24364.sql-server-troubleshooting-could-not-find-database-engine-startup-handle-error-during-installation.aspx

Hi Jinu,

Thank you for your response. 

Unfortunately, changing the Login for the SQL Server Engine at the beginning of the installation to SYSTEM did not change the outcome at all.

In my case, there is an issue with my disk drive.  For some odd reason the SQL Server installer thinks that the sector size is 3072 instead of 512  It is 512 if you can believe the values returned by "fsutil fsinfo ntfsinfo c:".  The cluster size is 4096.

Normally this will not happen, but my disk drive is 2TB and has something called "advanced" about it and there is a component somewhere in windows that is errantly reporting that it has a sector size of 3072.

I need to identify that component and replace it with one that has no such defect.  This problem has been around for several years now.

I don't really know anything about sectors and clusters and, apparently, I am not the only one.

I guess this is a problem with newer, larger disks that are "advanced."  Usually it imposes no problems, but it sure does when it comes to the SQL Server Installer.

Charles. 

Did you tried the installation first time on ur windows10 ?

Did u tried the workarounds section in

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

What workarounds?

Charles.

Workaround for SQL Server Originally Formatted with Sector Size 4092 Now 3072

In short: Create and attach a .VHD, permission it, attach a mount point, and drag your .mdf and .lfd files

downstream of the mount point.

Recently, I have been working with Windows Server 8 Beta, wherein I installed SQL Server 2012, and other

products, then used the new ADK (replaces AIK) to build an answer file and sysprep the build.

While everything worked fine applying it (Imagex) on nodes with identical drives (dual 160 GB SATAs, RAID 0,

Intel Matrix Controller), I ran into trouble on nodes with larger drives (Seagate SATAs in the terabyte

range).

I played with format commands, partition sizes, strip sizes, raid configuration in general, all to no avail,

just kept getting massages like this:

Cannot use file 'C:\Program Files\Microsoft SQL Server\MSSQL11.yourInstance\MSSQL\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.

Needless to say, the SQL instance would not start.

I was able to build a workaround for this issue (Not a perfect solution, a workaround).

High Level Steps:

1. Starting in Windows 7 / Server 2008 R2 you can easily create and attach .vhd files in diskmgmt.msc or

DISKPART; make a .vhd that suits you.

2. Initialize the disk just like you would a real one in DISKPART or diskmgmt.msc

3. Create a volume on the disk, just like you would with a real one... format NTFS, Unit size = 4096, etc.,

but don't assign a drive letter.


4. (Permissions are a pain across mount points, so) Right click the .vhd file and give NT SERVICE\MSSQL

$YourInstance <--(your instance name) permissions as they were in the original location

5. Do the same for the volume or volumes you create on top of the .vhd disk (I created two volumes, one for

SQLs Dbs, and one for my Dbs); you can do the permissioning in diskmgmt.msc by right-clicking the volume--

>properties-->security tab (I got so propagation errors when I did it, but it worked inspite of it).

6. Rename the old data folder (C:\Program Files\Microsoft SQL Server\MSSQL11.YourInstance\MSSQL\DATA\ to

something like .\DATA_Original

7. Create a new empty .\DATA folder in the original location (this will become our mount point).

8. Mount a newly-created volume to the newly created folder, and copy the original .mdf, .ldf files into it.

9. Make sure NT SERVICE\MSSQL$YourInstance has permission on the files... remember, they don't natively

inherit across mount points.

10. You'll need to use the same approach on your personal databases (that's why I created that other volume

on my .vhd... I can mount it somewhere else.

11. Start SQL Instance.

Disclaimer: I understand all that about separating log and data files, multiple spindles, etc. --this is just

to get you past the problem; put your data wherever you want.

Helpful URLs:

http://connect.microsoft.com/SQLServer/feedback/details/569895/installation-of-sql-server-2008-r2-on-mount-

points-fails

https://connect.microsoft.com/SQLServer/feedback/details/733652/service-inicialization-failled-by-corrupted-

system-resource-in-windows-8-client

http://forums.seagate.com/t5/Momentus-XT-Momentus-Momentus/SQL-server-says-the-st9750420-sector-size-is-3072

-and-can-t/td-p/156309

Hi Jinu,

Wow, that's really interesting.  Your solution appears to address my exact problem with my larger (2TB) disk drive.  I'll try it out a little later.

Thank you very much for this advice!  I'll get back to you once I've tried this.

Charles.

Hi Jinu,

Ok, I went ahead and followed your advice and it works great!

First, I created the vhd file and created a mount point at my chosen folder location.  I then, temporary, added the 'Everyone' user with full control to the folder, because the SQL server created users don't exist yet.

I then installed SQL Server 2014 SP1 Express, changing the Root Data Folder to the vhd mounted folder as part of the installation choices.

The installation went quickly and perfectly.  I see that I must explicitly mount the vhd whenever I reboot, but that is not a problem.  I know I can create a .bat file to do this and then add a task to task scheduler to execute the .bat file whenever the computer is booted, which I'll probably do next ...

By the way, I am running windows 10.0.10240.  This problem DOES NOT exist in windows 10.0.10532!  That is the case with my disk, at least.  I tested this today.

Thank you for your excellent a