Windows 8.1 won't shut down

[DualCitizen54]

Hi,

This one's been driving me crazy, and I've had a number of minor annoyances on my Windows system that my gut tells me might be related to the corruption.

I've run sfc /scannow and dism many times in the last 6 weeks, but even though I get messages that all the problems were found & fixed, the next time I try to shut down, I can't.

I just tried an SFCFix run, and it did find a couple errors that could not be fixed:

SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-07-27 19:31:18.925
Microsoft Windows 8.1 Update 3 - amd64
Not using a script file.








AutoAnalysis::
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\utc.app.json
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\telemetry.ASM-WindowsDefault.json




SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 2
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2015-07-27 19:39:38.361
----------------------EOF-----------------------

Help, please!

 

[Digerati]

How are you trying to shutdown and what happens when you try to shutdown? Any errors?

What happens when you select "Restart"?

And sadly, you told us absolutely nothing about this computer. We don't even know if a PC or notebook!

 

[DualCitizen54]

Hi,

No error messages, just the status "Shutting Down", with the spinner.

When I select "Restart", the status message changes to "Restarting"

Sorry on the lack of hardware config. It's an Intel 4930 on a ASUS Rampage IV Black Motherboard, 32G RAM. System Drive is a 1T Samsung EVO 840 SSD.

I should add two pieces of information:

1. A couple months back, I cloned my 128G Samsung SSD to the 1T SSD.
2. I also tried a repair install, but the error message was that the drive that Windows installed on is "locked." I've seen no other signs of a problem with my c: drive.

 

[Digerati]

When I select "Restart", the status message changes to "Restarting"

And does it restart?

I should add two pieces of information:

1.A couple months back, I cloned my 128G Samsung SSD to the 1T SSD.

And the problem started immediately after that?

You may need to go into Task Manager and see what is running and start ending non-Microsoft programs first and see what happens. This is most likely a program or driver.

 

[Tekno Venus]

It might be worth turning on verbose shutdown info and seeing if it tells you what it's stalling on: Enable Verbose or Highly Detailed Status Messages In Windows 7 | 8

 

[DualCitizen54]

The best I can tell you is that it was roughly in that timeframe.

However, I did find a bunch of people with the same problem, here:

Microsoft-Windows-Unified-Telemetry-Client files corrupted - Microsoft Community

Unfortunately, there are, as yet, no successful solutions.

I will take your advice re: Task Manager.

 

[DualCitizen54]

So, I have good news, and bad news.

First the good news. I decided to try the suggestion from Tekno Venus above, and turned on verbose status messages. Wouldn't you know it? The first time I tried to shut down, the process ran perfectly (with status messages showing no errors). I've used the shutdown and reboot processes several times each without any problems. You'll recall in my first post:

​

"I've had a number of minor annoyances on my Windows system that my gut tells me might be related to the corruption."
​

One of those problems was that the shutdown & reboot options on the charms menu were not working (I have an app with the same options that was working). The charms menu versions started working after the verbose message change.

Now for the bad news:

1. I have no idea why the message setting cleared the problem.
2. sfcfix.exe continues to report the same message as in my original post...two corrupted files (like many other people whose posts I've found at the microsoft and other sites) However, now I'm not seeing any system limitations or symptoms.

With Windows 10 availability commencing tomorrow, I'm wondering if this problem will go away as a result of the migration. I'm going to wait a bit to actually migrate, because I have some audio-related USB drivers that I want to be sure are working before I put my audio work at risk.