Can't start ms sql server, how to fix?

Question

Windows Server

LOG:

2017-06-16 23:33:01.04 Server      Microsoft SQL Server 2014 (CTP2) - 12.0.1524.0 (X64) 
  Oct  3 2013 19:00:26 
  Copyright (c) Microsoft Corporation
  Express Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )

2017-06-16 23:33:01.04 Server      UTC adjustment: 3:00
2017-06-16 23:33:01.04 Server      (c) Microsoft Corporation.
2017-06-16 23:33:01.04 Server      All rights reserved.
2017-06-16 23:33:01.04 Server      Server process ID is 8828.
2017-06-16 23:33:01.04 Server      System Manufacturer: 'Dell Inc.', System Model: 'Latitude 3330'.
2017-06-16 23:33:01.04 Server      Authentication mode is MIXED.
2017-06-16 23:33:01.04 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESSEDU\MSSQL\Log\ERRORLOG'.
2017-06-16 23:33:01.04 Server      The service account is 'NT Service\MSSQL$SQLEXPRESSEDU'. This is an informational message; no user action is required.
2017-06-16 23:33:01.04 Server      Registry startup parameters: 
   -d C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESSEDU\MSSQL\DATA\master.mdf
   -e C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESSEDU\MSSQL\Log\ERRORLOG
   -l C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESSEDU\MSSQL\DATA\mastlog.ldf
2017-06-16 23:33:01.04 Server      Command Line Startup Parameters:
   -s "SQLEXPRESSEDU"
2017-06-16 23:33:01.34 Server      SQL Server detected 1 sockets with 2 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2017-06-16 23:33:01.34 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2017-06-16 23:33:01.34 Server      Detected 8097 MB of RAM. This is an informational message; no user action is required.
2017-06-16 23:33:01.34 Server      Using conventional memory in the memory manager.
2017-06-16 23:33:01.36 Server      Error: 41000, Severity: 16, State: 0.
2017-06-16 23:33:01.36 Server      Failed to obtain the local Windows Server Failover Clustering (WSFC) handle (Error code 1753).  The WSFC service may not be running or may not be accessible in its current state.  For information about this error code, see "System Error Codes" in the Windows Development documentation.
2017-06-16 23:33:01.36 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2017-06-16 23:33:01.40 Server      Query Store settings initialized with enabled = 1, 
2017-06-16 23:33:01.40 Server      The maximum number of dedicated administrator connections for this instance is '1'
2017-06-16 23:33:01.40 Server      This instance of SQL Server last reported using a process ID of 12224 at 2017-06-16 23:32:37 (local) 2017-06-16 20:32:37 (UTC). This is an informational message only; no user action is required.
2017-06-16 23:33:01.41 Server      Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2017-06-16 23:33:01.41 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.
2017-06-16 23:33:01.42 Server      Software Usage Metrics is disabled.
2017-06-16 23:33:01.42 spid7s      Starting up database 'master'.
2017-06-16 23:33:01.46 spid7s      10 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2017-06-16 23:33:01.49 spid7s      0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2017-06-16 23:33:01.52 Server      CLR version v4.0.30319 loaded.
2017-06-16 23:33:01.58 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2017-06-16 23:33:01.61 spid7s      Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details.
2017-06-16 23:33:01.63 spid7s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2017-06-16 23:33:01.64 spid7s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2017-06-16 23:33:01.67 spid7s      SQL Trace ID 1 was started by login "sa".
2017-06-16 23:33:01.71 spid7s      Server name is 'DELL-KOMPUTER\SQLEXPRESSEDU'. This is an informational message only. No user action is required.
2017-06-16 23:33:01.72 spid15s     Error: 17190, Severity: 16, State: 1.
2017-06-16 23:33:01.72 spid15s     Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
2017-06-16 23:33:01.72 spid15s     Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2017-06-16 23:33:01.72 spid15s     Error: 17182, Severity: 16, State: 1.
2017-06-16 23:33:01.72 spid15s     TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 
2017-06-16 23:33:01.72 spid15s     Error: 17182, Severity: 16, State: 1.
2017-06-16 23:33:01.72 spid15s     TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property. 
2017-06-16 23:33:01.72 spid15s     Error: 17826, Severity: 18, State: 3.
2017-06-16 23:33:01.72 spid15s     Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2017-06-16 23:33:01.72 spid15s     Error: 17120, Severity: 16, State: 1.
2017-06-16 23:33:01.72 spid15s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

I don't know what the problem is, I couldn't find the answer in Google

Answer 1

It was necessary to select the main account when creating the server

Answer 2

https://social.msdn.microsoft.com/Forums/sqlserver...
Not your case?

Answer 3

Failed to obtain the local Windows Server Failover Clustering (WSFC) handle (Error code 1753). The WSFC service may not be running or may not be accessible in its current state. For information about this error code, see "System Error Codes" in the Windows Development documentation.

Search gives .