I am trying to install SQL Server SP1 Express on a fresh windows 10.0.10240.  I've tried several times.  In the last attempt, I changed the SQL Server Engine's login to SYSTEM, but to no avail.

The installer returns this error:

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

This just means that the main engine service will not start.  There is more than one possible cause for this.

The relevant event log entry is:
"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."

Sometimes, it is a bad user account being used by the service that prevents the main engine service from starting.

In my case, it is the fact that I have a new 2TB disk drive with "Advanced" something or other.  This is causing SQL Server to think that the sector size is 3072 bytes.  It is 512 bytes, if you can believe "fsutil fsinfo ntfsinfo c:" which returns:

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
++++++++++

I don't see a 3072 anywhere in the list!  Unless, of course, you subtract 1024 (Bytes Per FileRecord Segment) from 4096 (Bytes per Cluster).

But, if this is how windows managed to come up with 3072, then they forgot to multiply that result by their shoe size in centimeters and then divide that result by the mass of their left butt-cheek in mg!

I have found many posts that complain of the same problem, some of which are several years old!

Does anyone know how to correct this BUG?  It is NOT a problem with my hardware.  It is a problem with Windows 7, 8, 10 and to the Windows Server products, as well.  But mostly, it is a problem with the SQL Server Installer, not at all limited to SQL Server 2014.

Thanks in advance for any assistance you may provide.

Have you made sure that firmware version of hardware if up-to-date? In one of my case, issue was resolved after upgrading firmware.

Also read https://support.microsoft.com/en-us/kb/926930 and http://blogs.msdn.com/b/psssql/archive/2011/01/13/sql-server-new-drives-use-4k-sector-size.aspx

I believe fsutl is reporting incorrect value.

I just bought this disk drive.  It's brand new.

I did check the driver and windows reported that the latest driver was already installed.

New Info: I did manage to get the installation completed successfully by changing the location of the data files to an external USB3 mass storage device as part of the installation process.  Funny thing is fsutl returns the same values for both drives!

Also, I had installed SQL Server 2014 on my old disk drive previously and when I cloned everything to the new drive, that instance of SQL server works fine on the new disk drive!

Copying the files back to the new internal drive, changing the SQL configuration accordingly, unfortunately, results in the same error.

So, I really don't understand what is happening.  SQL Server runs on the new drive.  I just can't install it on the new drive.

I've now got good files.  If I could just learn how to convert them to work on this new drive.