J jeffsmithy New Member Feb 22, 2016 #1 When I turn on my Surface Book, it gets stuck on the "Surface" screen and doesn't go any further. I have to push and hold the power button to turn it off, then turn it back on again to get it to boot properly. Any ideas?
When I turn on my Surface Book, it gets stuck on the "Surface" screen and doesn't go any further. I have to push and hold the power button to turn it off, then turn it back on again to get it to boot properly. Any ideas?
leeshor Well-Known Member Feb 22, 2016 #2 Does it do that every time exactly as you described it? Are you actually shutting down then having to start twice to get back to a desktop?
Does it do that every time exactly as you described it? Are you actually shutting down then having to start twice to get back to a desktop?
M MrHanky New Member Feb 23, 2016 #5 Is this really a known issue? Started for me just yesterday (possibly due to updates coming in drips...) Whenever my PC hibernates, I cannot turn it back on as it just hangs at the 'Surface' screen. I can force a BSOD by detaching the screen and turning it on - then I usually get INTERNAL_POWER_ERROR followed by a clean, cold-boot. Any workaround? This has basically bricked my device for day-to-day usage (shutting down is impractical..)
Is this really a known issue? Started for me just yesterday (possibly due to updates coming in drips...) Whenever my PC hibernates, I cannot turn it back on as it just hangs at the 'Surface' screen. I can force a BSOD by detaching the screen and turning it on - then I usually get INTERNAL_POWER_ERROR followed by a clean, cold-boot. Any workaround? This has basically bricked my device for day-to-day usage (shutting down is impractical..)
Nuspieds Active Member Feb 23, 2016 #6 Yes, I have been experiencing this issue on both my original and replacement SB.
S stanman98075 New Member Feb 23, 2016 #7 A real pain! Started after 'system update' a few days ago. Tried to roll back, but this update isn't listed.
A real pain! Started after 'system update' a few days ago. Tried to roll back, but this update isn't listed.