[FIXED] Can't Restart or Shut down my PC- Windows 10 insider build 18999 Fast Ring

[HotCakeX]

UPDATE 10/18: We have released 20H1 Build 19002.1002, which includes a fix for the issue causing some devices to get stuck during shutdown or restart.

https://blogs.windows.com/windowsexperience/2019/10/17/announcing-windows-10-insider-preview-build-1...

After upgrading to 18999 from 18995, I can't restart my computer or shut it down anymore. when I attempt to do any of them, the computer gets stuck forever in either "shutting down" or "restarting" state with the loading icon circling.

also the CPU usage goes up and I can tell it by reading the CPU temp number showin on my motherboard and CPU fans getting loud.

I have to hard reset or hard shut down by either pressing the reset button on my case or holding the power button.

the scary part is that it's not listen under the known issues in here:

https://blogs.windows.com/windowsexperience/2019/10/08/announcing-windows-10-insider-preview-build-1...

anyone else having the same problem?

my specs:

i7 7700K

16GB RAM DDR4 3200Mhz

IGPU graphic card

SSD M.2

Feedback to upvote:

https://aka.ms/AA67uo7

[#2]

Thanks,
so many fixes in this build, could you give us some hints about when we are going to see big changes in fast ring builds? a new big feature or change, for example the return of Windows SETS or something like that? 🙂

[#3]

Doenst work here either. Still doesnt shutdown. @Iain Fielding 

[#4]

After the Windows update finished download and installing the update, I couldn't restart because it got stuck again, so I had to force reset using button on the case and after Windows loaded up, quickly restarted again from the start menu and only then I could get Windows to start finishing and installing the new build.
build 19002 was delayed 9 days (2 more days than the usual period between each new build) and yet it has a lot more known issues than the previous one. and it's all happening while there is absolutely No new feature added.
so one would think that when they fix 1 bug, they create 2 more somewhere else. it's like a never ending cycle..

[#5]

@HotCakeX 

Nothing to share right now.  🙂

[#6 · Accepted solution]

@HotCakeX Cumulatvie Update 19002.1002 has been released in the Fast Ring to resolve the restart issue.  We appreciate your patience!

-Eddie

[#7]

Great news, thank you very much!

[#8]

Yes I am, the latest version of windows 10 insider update just sticks on restart on me. It's been doing that since more than 24 hours ago. I keep killing the power and it starts up fine it's just when it tries to update, the required restarting the computer sticks. I didn't know if it's my computer going bad or the latest windows insider has problems.

[#9]

@Eddie Leonard 

Confirmed, all solved with Cumulative Update 19002.1002 !

[#10]

@MDM-1 

Good

[#11]

@RonSmithJr 

go to Windows update and click check for updates.

also see the top of this post, it's fixed

https://techcommunity.microsoft.com/t5/Windows-Insider-Program/FIXED-Can-t-Restart-or-Shut-down-my-P...

https://blogs.windows.com/windowsexperience/2019/10/17/announcing-windows-10-insider-preview-build-1...

[#12]

It's not fixed.

[#13]

Hi,
just to be sure, you did install the new update that was released After build 19002, right? which bumps your Windows version to 19002.1002.

[#14]

Same here, cumulative update fixed it for me.

[#15]

That's good to know,
cheers!

[#16]

Unfortunately it introduced a horrible video lag (MPC-HC+madVR) in full-screen!

Had that before on several builds during the years, and same bugs magically reapers after x months...

[#17]

Is it using Hardware Acceleration? (GPU) ?

[#18]

No, and not important as all worked in previous build, same settings and all.

As soon as I go full-screen the fps drop sharply and stuttering begins, if I only go to the seek bar (thus same resolution rendering), all works again in max fps (I have Fury GPU, that has more than enough strength for my madVR setting).

P.S.

But this is a wrong topic for this, should start e a new tread.

Just wanted to mention it...

[#19]

Yeah well I think you have to create a feedback too and do a problem repro while that bug is happening 🙂

[#20]

The suggestion to restart immediately after getting a successful restart solved my problem. Thanks @HotCakeX 

[#21]

That's good, but how about installing the latest update that fixes this problem entirely?