I have the restart shutdown problem. When at the desktop, do the old school, Alt + F4 and restart or shutdown from there. this works for me.
This method did not help me. So far it only works like this: Ctrl+Alt+Del - Lock - Restart / Shut down.
I really wish ms would issue a fix for this issue, I guess in their opinion it's not important enough. :-(
It's working fine here, have you tried to do this manually? I have done the tests in this way: I open the Power Options page, change from High performance to Balanced, then press the "shut down" button (it shuts down without problems), when turning on the computer again, I open the Power Options page and change from Balanced to High performance, then I change from High performance to Balanced again and press the "shut down" button, I have done this several times in a row and the computer shuts down without any problem. As I said, in my case it works with the shortcuts in the Start menu, but you can do tests to see if it works manually.
Patients is a requirement with insider. I just turned off the power switch on the power supply. After it spent all night installing new features since me being tired, I went to bed. When I woke up 5 hrs. later it was doing nothing. I hit the switch at PS, rebooted and everything is fine. But, I'm still getting ESENT errors 636, 640 & 642 doubling up on the 642's. Other than that Winbloz is working well enough. Then again my grandson tells me that the Logitech H800 wireless headphones don't work. Fixed: It was the Logitech Bluetooth Service in CM Services. My 8 year old grandson can push you to the brink. When he has some silly YouTube video going very loud. That alone keeps you on your toes and if you can't fix it he will not give you a break (or peace of mind).
Well I don't whether it's a feature or a bug as on my computer on boot up if I don't press enter quite soon, when the picture comes up, to get to the next bit to enter my password then I can't get in without rebooting.. BUT found a way around it by ctrl alt del and then I can get in to enter my password.
im having the same issue...the hanging issue hopefully will be fix in the next release in the mean time just deal with it
This build took telemetry and "cloud experience" to a whole new level - I have not seen such amount of noise until now. It went so far as to cause race conditions between the various logging and quite a few times lead to the 100% disk usage bug - a modest machine will most likely become unresponsive and need a power cycle. I waited two times and it recovered, but had to reset on two more occasions. [Note that I willingly submitted myself to the horror that Home edition is, with no "tweaks"] Without all that crap, it would probably be the snappiest Windows 10 since Threshold. Funny that I did not experience the shutdown bug. But there is something wrong with defender + cpu vulnerabilities mitigations, too - I have disabled them and stability improved s**tload, but not quite there yet. If you have old hardware (<2018) - might want to stay away from it. I will get back to a more sane build (1809) with the first chance I get.