Microsoft distributes Microsoft SQL Server 2012 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release.
Consider the following scenario:
You install Windows 7 or Windows Server 2008 R2 on a computer that has a processor-group aware feature enabled.
You run the Microsoft SQL Server 2012 Setup program on the computer.
You enable the FileStream configuration on the Database Engine Configuration page of the SQL Server 2012 Setup wizard.
In this scenario, the following error may be logged in the SQL Server error log file:
<Date><Time> server Error: 17883, Severity: 1, State: 0 <Date><Time> server Process 0:0:0 (0x1f78) Worker 0x00000004F3FD8160 appears to be non-yielding on Scheduler 3.
Cumulative update information
SQL Server 2012
The fix for this issue was first released in Cumulative Update 1 for SQL Server 2012. For more information about how to obtain this cumulative update package for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
To work around this issue, use one of the following methods:
Do not enable the FileStream configuration when you run the SQL Server 2012 Setup program. You can use SQL Server Configuration Manager to enable the configuration after SQL Server 2012 is installed.
Use the following command to disable the processor-group aware feature. Then, restart the computer, and run the SQL Server 2012 installation.
bcdedit.exe /set groupaware off
For more information about processor groups, visit the following Microsoft website: