Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Saturday, November 18, 2017 11:33 PM
Sigh. Just when I start hoping that maybe, somehow, Microsoft has adequately tested the updates they're pushing out to solve Fall Creators Update problems, I run into yet another problem.
This is on Windows 10 Professional 64 bit. The problem only started to appear after the KB4048955 Cumulative Update for Windows 10 was installed.
Windows 10 goes to sleep as per usual. When you jiggle the mouse or tweak the keyboard, assuming you've set those to be able to wake the system (which I have), it begins to power back up.
And then it stalls, with nothing but a black screen and the system case power LED on. Nothing else happens. Even after waiting an hour (thank ghu I had some gardening to do).
There is almost no information in the system log. Here is the last entry before the system went to sleep:
Log Name: System
Source: Microsoft-Windows-Kernel-General
Date: 11/18/2017 12:11:10 PM
Event ID: 16
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: Muddlehead
Description:
The access history in hive \?\C:\ProgramData\Microsoft\Provisioning\Microsoft-Desktop-Provisioning-Sequence.dat was cleared updating 0 keys and creating 0 modified pages.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-General" Guid="{A68CA8B7-004F-D7B6-A698-07E2DE0F1F5D}" />
<EventID>16</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2017-11-18T20:11:10.714250500Z" />
<EventRecordID>4269</EventRecordID>
<Correlation />
<Execution ProcessID="6116" ThreadID="13272" />
<Channel>System</Channel>
<Computer>Muddlehead</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="HiveNameLength">85</Data>
<Data Name="HiveName">\?\C:\ProgramData\Microsoft\Provisioning\Microsoft-Desktop-Provisioning-Sequence.dat</Data>
<Data Name="KeysUpdated">0</Data>
<Data Name="DirtyPages">0</Data>
</EventData>
</Event>
And then nothing is recorded until I do a hard reset -- and I mean a cut-the-power-and-restart-the-whole-shebang kind of hard reset, nothing else, not even hitting the reset key on the case will suffice.
There is this entry in the log:
Log Name: System
Source: EventLog
Date: 11/18/2017 3:23:15 PM
Event ID: 6008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Muddlehead
Description:
The previous system shutdown at 12:31:35 PM on 11/18/2017 was unexpected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6008</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-11-18T23:23:15.925682900Z" />
<EventRecordID>4281</EventRecordID>
<Channel>System</Channel>
<Computer>Muddlehead</Computer>
<Security />
</System>
<EventData>
<Data>12:31:35 PM</Data>
<Data>11/18/2017</Data>
<Data>
</Data>
<Data>
</Data>
<Data>2405</Data>
<Data>
</Data>
<Data>
</Data>
<Binary>E1070B00060012000C001F0023006800E1070B000600120014001F0023006800600900003C000000010000006009000001000000B00400000100000000000000</Binary>
</EventData>
</Event>
which is interesting because it's recording an unexpected system shutdown 20 minutes after the last event recorded before the system went into whatever never never land it got itself into. I have never known Windows to log >>nothing<< for 20 minutes in the system log.
Thoughts on how to diagnose this? Or, better yet, resolve it?
- Mark
All replies (4)
Sunday, November 19, 2017 4:05 PM | 1 vote
Okay, a possible theory/workaround...
In its infinite wisdom, Microsoft added a feature that uses your sign-in info to automatically finish setting up your device after an update or restart.
Of course, this being the new Microsoft -- the one which doesn't bother to adequately test its OS updates -- this option, which is enabled by default without asking you if that's what you want (another aspect of the new Microsoft), has already been the basis of a number of errors and weird behaviors. Starting with getting a blue screen warning, before you log on, that your login credentials are invalid.
When I finally got around to resolving >>that<< problem -- by disabling the option -- not only did the blue screen warning go away, my system >>appears<< to be able to wake from sleep without going through a cold restart. Which is a convenient thing to avoid, when possible.
Message to Microsoft: if you've decided to move Windows towards being a free or ad supported OS, I guess I might understand this sudden lack of focus on releasing solid products. Freeware is often permanently in beta, and, if one uses it, one has to accept all the annoying frustrations that come along with crap being pushed out the door before its ready, as the price of getting new features.
But if you're planning on continuing to charge customers for your product...you need to figure out what's gone wrong lately, and fix it. Right now the train is rocking off the rails. It wouldn't take much of an unexpected curve to throw it right off the tracks.
Monday, November 20, 2017 12:56 PM
Hi,
Considering the Update is released recently, if the issue persists, you could try the built-in "Feedback" tool to submit the issue on your side. And thank you for your feedback of our product. I will forward this information to the appropriate department through our internal channel. Both the Microsoft Product Team and Development Team take into consideration all suggestions and feedback for future releases.
Thank you for your understanding and cooperation.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, February 5, 2018 3:16 PM
Hi!
I'm having the same issue. But I'm not sure what I need to disable to workaround this!
Could you please help me to clarify which settings did you disabled?
Thank you!
Best regards,
Wilmer BZ.
Wílmer Bravo Zapata
Tuesday, February 6, 2018 2:28 AM
I had the same wake-up issue mentioned by ChairmanMAO after installing the Fall Creators Update. His workaround seems to have helped. Much obliged. Wilmer, I can't post any link yet but if you Google: disable "Use my sign in info to automatically finish setting up my device after an update", you should get a Microsoft link on how to do this.
I have set my Windows update branch readiness to Semi-Annual Channel, hoping I could avoid these time-consuming stuff-ups. Pity that nearly three months onward this issue still has not been fixed.