(FOUND FIX) PC Will NOT Shut Down, NOR Restart Anymore!

[LucianAndries]

Hello!

I have Windows 10 Pro 64Bit, and it is an Upgrade from Windows 7.
I've been using it since last winter, and everything worked perfect! Until two weeks ago... 🙁((((((

Almost two weeks ago Windows made some updates to itself:
- 2017-07 Security Update for Adobe Flash Player for Windows 10 Version 1703 for x64-based Systems (KB4025376)
- 2017-07 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4025342)

I don't remember doing anything else(nor software nor hardware) at that time, so I don't even know what to troubleshoot for. :|
I don't know if it's directly the update's fault or not, but it was arround that time, when the problem started...

After these updates, my PC DOESN'T shut down, NOR restart anymore. It just freezes/stays in the bluescreen with "shutting down/restarting" message... I left the PC until morning and still nothing.
And the only way to reboot or shut down, is to press the physical power and reset buttons on the case. 🙁(


I TRIED ALL THE FOLLOWING:

1. Clean Startup boot.
2. Booted in Safe Mode.
3. Reset BIOS/UEFI settings.
4. Checked RAM sticks.
5. Checked PSU(with another PSU).
6. Checked system files with "sfc /scannow" in Command Prompt.
7. Ran a freaking "Scan Disk".
8. Checked and repaired Registry entries with CCleaner.
9. Tried restarting/shuting down while holding down the Shift key(a stupid recommendation).
10. Tried a Repair with a Windows Installation Disk. It said "it could not fix any system files"....... Does that mean they weren't broken, or just too broken to even be fixed??
11. Checked the settings in the Power Options. Just reset them a couple of times...
12. Someone else with the exact same problem, even tried a CLEAN INSTALL, and still didn't help. Windows would just install again those BAD SYSTEM UPDATES. 🙁(((((

NONE OF THIS WORKS!!! So why do people keep telling me to do them??? 1 + 1 will always equal 2 !!

I don't understand this at all, for half a year it worked flawlessly! I would understand if this would happen exactly after a fresh Windows install... But not after 7+ months!!

If someone had this exact problem and managed to fix it, PLEASE teach me how you did it! I really don't want a failed fresh install................... 🙁(


My PC:
- AMD FX 8320 - 8 Core CPU
- Evga GeForce GTX 1080 Ti SC Black
- Asus M5A99X EVO R2.0
- ADATA Premier PRO SP900 - 128Gb SSD
- Kingston HiperX 16Gb RAM
- Windows 10 Pro 64Bit - Version 1703 - OS Build 15063.540 (With all drivers up to date. Even the Windows updates).


Thank you!


EDIT:

I finally found the FIX to this rare issue! At least for me... A Microsoft level 2 support named Carlito helped me. Thank you man!!
You have to check for two things, and make sure they are set as I say below:

1. Go to Device Manager -> Network adapters -> Network Card -> right click -> Properties -> Power Management -> Make sure the first two boxes are checked, then apply and exit.

2. Windows Key + R -> gpedit.msc -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> find this entry "Shutdown: Clear virtual memory pagefile" -> right click -> Properties -> check "Disabled", then apply and exit.

After this, your PC should Restart and Shut Down with no issue.

 

[LucianAndries]

Search for reliability monitor in cortana and see what it reports, it may give a clue and is slightly easier to understand than the event viewer

try making this on another PC: http://www.howtogeek.com/howto/windows-vista/use-ubuntu-live-cd-to-backup-files-from-your-dead-windows-computer/ - not to save files as such, but to see if you get same reaction shutting down pc in liinux. That will tell you for sure if it is Windows and not hardware

Hey.

Sorry for the long wait, I was busy.

I tried the following:
- sfc /scannow in Command Prompt.
- a scan disk on C:\.
- checked and cleaned the registries with CCleaner.
- a mod recommended to check my RAM. But I have to take out the damn cooler first........ So I said beep that!!
None of the above helped.

To your recommendations:
1. I don't have Reliability Monitor, Just Reliability History.. Maybe it's the same thing?
Ok, I ran it and checked for the past weeks or so. It was interesting... I had one program that was giving me critical issues every day, it was the SSD's manager software... I uninstalled it, and still nothing. 🙁
I had other criticals in the past, connected directly to windows, but it didn't say anything concrete, a file, program, etc. 🙁
By the way, I still don't know how Event Viewer works.......... I don't know if I should laugh or not. So I'll cry instead. 🙁((

2. Is that like a Virtual Machine that I boot with it? And try to restart and/or shut down to see the reaction? So, if it will restart, then it is a software issue, right?

PS: I heard that a new "Creator's Update" or something, is comming in the fall... So I'm betting on that update to clean up my system files and registries. Though, it might not... 🙁

 

[Saga Lout]

If this is an update based problem, go into c:\windows\softwaredistribution\downloads and delete all the files in that folder. Any update that didn't complete or properly install itself will come down in a new batch when you restart. Empty the Recycle Bin and you've gained a lot of free space - possibly enough to turn on System Restore when all this is history and to help you in case it happens again.

Open Task Manager and click on the heading of the CPU column to see what's taking any resource then right click and select End Task.

If you can't shut down properly at that stage, I would suggest rescuing your data and reinstalling Windows 10 from a freshly downloaded ISO.

 

[Sammy_11]

I have the very same problem. Tried everything you tried, and even did a clean install. Nothing helps. Restart and shutdown still freeze on machine. Happened after the 2017-07 update. Did you ever find a solution that worked. I haven't.

 

[LucianAndries]

I have the very same problem. Tried everything you tried, and even did a clean install. Nothing helps. Restart and shutdown still freeze on machine. Happened after the 2017-07 update. Did you ever find a solution that worked. I haven't.

Hey.

Thanks for your reply.

So this won't go away even with a clean install??! Jesus, I hate Microsoft even more!!!

No, I haven't found a fix yet, either. 🙁
I'm hoping they will fix it, with the new creator's update in the fall...
We can't even contact Customer Support anymore! Microsoft Answers is just a forum, not a customer support page, with actual technicians! Why do they send us there now? 🙁(((

 

[LucianAndries]

FIX:

I finally found the FIX to this rare issue! At least for me... A Microsoft level 2 support named Carlito helped me. Thank you man!!
You have to check for two things, and make sure they are set as I say below:

1. Go to Device Manager -> Network adapters -> Network Card -> right click -> Properties -> Power Management -> Make sure the first two boxes are checked, then apply and exit.

2. Windows Key + R -> gpedit.msc -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> find this entry "Shutdown: Clear virtual memory pagefile" -> right click -> Properties -> check "Disabled", then apply and exit.

After this, your PC should Restart and Shut Down with no issue.

PS: So how can I chose myself as the Solution? Can someone else do it for me?

 

[Saga Lout]

Happy to oblige and hopefully there are no hard feelings.

 

[johnbl]

I know you found the solution but you could have enabled verbose status messages on shutdown to see what the system was trying to do.
https://superuser.com/questions/426029/how-can-i-display-additional-boot-and-shutdown-information-on-the-windows-7-welc

it is just a registry key setting. I would hope it would show that the system was attempting to clear the pagefile on shutdown and could not.

 

[Saga Lout]

We can all be wiser after the event, johnbl but LucianAndries deserves better consideration for taking the time and trouble to come back and round things off for future readers of this thread.

There was plenty of time to post your suggestion but happily, that facility is turned off. Windows is annoying with its "working on it" message. Most of us prefer a blank screen while we wait for Windows to catch up with us.

Anyway, it's thread closing time now.