3050279 causes crash for me on boot: Code: 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WINLOGON_FATAL_ERROR (c000021a) The Winlogon process terminated unexpectedly. Arguments: Arg1: ffffc0015a9b3f20, String that identifies the problem. Arg2: ffffffffc0000428, Error Code. Arg3: 0000000000000000 Arg4: 000000145b070000 Debugging Details: ------------------ ERROR_CODE: (NTSTATUS) 0xc000021a - {B EXCEPTION_CODE: (NTSTATUS) 0xc000021a - {B EXCEPTION_PARAMETER1: ffffc0015a9b3f20 EXCEPTION_PARAMETER2: ffffffffc0000428 EXCEPTION_PARAMETER3: 0000000000000000 EXCEPTION_PARAMETER4: 145b070000 ADDITIONAL_DEBUG_TEXT: initial session process or BUGCHECK_STR: 0xc000021a_Session_c0000428_Terminated DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: smss.exe CURRENT_IRQL: 0 ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre LAST_CONTROL_TRANSFER: from fffff8037a05ad81 to fffff80379dd9870 STACK_TEXT: ffffd000`209b8698 fffff803`7a05ad81 : 00000000`0000004c 00000000`c000021a ffffd000`231153f8 ffffe000`4bf9b3d0 : nt!KeBugCheckEx ffffd000`209b86a0 fffff803`7a04bddc : ffffe000`4a895300 ffffd000`209b87e0 ffffd000`209b87e0 00000000`00000000 : nt!PopGracefulShutdown+0x2c5 ffffd000`209b86e0 fffff803`79de3e63 : 00000000`00000004 00000000`00000004 00000000`c0000004 ffffd000`209b8900 : nt!NtSetSystemPowerState+0xd70 ffffd000`209b8860 fffff803`79ddc700 : fffff803`7a28261f 00000000`00000001 ffffd000`209b8a78 00000000`c0000004 : nt!KiSystemServiceCopyEnd+0x13 ffffd000`209b89f8 fffff803`7a28261f : 00000000`00000001 ffffd000`209b8a78 00000000`c0000004 00000000`00000000 : nt!KiServiceLinkage ffffd000`209b8a00 fffff803`7a1b3b87 : 00000000`001b7602 00000000`0026a7cb 00000000`00000000 fffff803`7a03e300 : nt! ?? ::NNGAKEGL::`string'+0x6034f ffffd000`209b8ac0 fffff803`79d4f0de : ffffe000`4a895040 00000000`00000001 00000000`00000000 fffff803`7a03e300 : nt!PopPolicyWorkerAction+0x63 ffffd000`209b8b30 fffff803`79d73c49 : 00000000`00000001 fffff803`79d4f01c fffff803`79f88780 ffffe000`00000000 : nt!PopPolicyWorkerThread+0xc2 ffffd000`209b8b70 fffff803`79caca6f : ffffe000`49ac47c0 00000000`00000080 fffff803`7a03e300 ffffe000`4a895040 : nt!ExpWorkerThread+0xe9 ffffd000`209b8c00 fffff803`79dde926 : ffffd000`24e4b180 ffffe000`4a895040 ffffe000`49a77040 2520f33b`ce97c888 : nt!PspSystemThreadStartup+0xef ffffd000`209b8c60 00000000`00000000 : ffffd000`209b9000 ffffd000`209b3000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!NtSetSystemPowerState+d70 fffff803`7a04bddc cc int 3 SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!NtSetSystemPowerState+d70 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 5503bb96 BUCKET_ID_FUNC_OFFSET: d70 FAILURE_BUCKET_ID: 0xc000021a_Session_c0000428_Terminated_nt!NtSetSystemPowerState BUCKET_ID: 0xc000021a_Session_c0000428_Terminated_nt!NtSetSystemPowerState ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0xc000021a_session_c0000428_terminated_nt!ntsetsystempowerstate FAILURE_ID_HASH: {ba39a8ab-61ed-97c5-fe69-a7c8369bae60} Followup: MachineOwner ---------
Outlook 2013 and Outlook 16 Preview might not index new emails/3053902/ http_s://support.microsoft.com/en-us/kb/3053902/ You cannot enable Hyper-V after performing a clean install of Windows 10 Technical Preview Build 10049, nor after upgrading to Build 10049 from a build that did not have Hyper-V enabled http http_s://support.microsoft.com/en-us/kb/3053902/
not till may atleast from looks of it microsoft has said before windows 10 server version wont be out till 2016
I wouldn't expect there to be. Those on 10041 should have already updated to 10049. Having anyone remain on 10041 completely defeats the purpose of the technical preview. There are updates for build 9926, as this is the build that includes Server Technical Preview. The Server preview is less important for them to push at the moment, seeing a large amount of issues for the consumer preview also cover the Server preview. I'm thinking they may even consider the build 9926 of the server preview a mistake in releasing, probably wishing they left it until at least a Release Candidate for the consumer Windows was released. Any reason why you haven't updated? There was a build from 10 April that belonged to the Impressive branch. It's possible there will be a new build in the next week. Microsoft are only likely to release one more build until the 'Release Candidate' is ready at the end of April/early May, to be shown at the BUILD conference. Keep in mind the 'Release Candidate' in this sense means feature complete, and not necessarily a build intended for actual release.