Windows 10: Windows 10 + SSD = No Shutdown

Hi,

I bought a new Sandisk SSD Plus and installed Windows 10 x64 (10.0.10586) on it.
Now when I click to shutdown or restart it won't happen. The animation goes forever and nothing happens.



I plugged the SSD in another PC running Windows 10 (same build) and the same happens.
Although It looks like the SSD is poisoned, it is not. It is brand new.
Any help please?

:)

 

Windows 10 Unexpected shutdown on start up

HI,

I already checked with SCF and DISM, but this also didn't help.

Is there a possibility to check what is going wrong in the process of fast startup (shutdown and startup) or Hibernate. It looks like it is going wrong during shutdown, resulting in a crash during startup

 

Windows 10 Unexpected shutdown on start up

Same issue here when using fast Startup.

I hope this post will be followed up and someone can actually help.

 

Hello Martinz Welcome back to TF! Sorry to hear that a new drive is stuffing up on you!

I do however have to suspect the 10 media used may be the problem unless by chance the new drive has a defect. You may want to try it on Port #2 instead of Sata port #1 in case the first port used the most is seeing a problem as well as trying a different cable to rule those items out.

The Windows stalling at shutdown however does tend to lean towards an OS glitch for the most part where you can try a few things out first. Driver or app hanging at shutdown is the most common problem. If you saw a bad install for some app you may end up seeing an error for that suddenly start appearing which would be a separate item entirely.

The first few steps however before assuming anything you can take would be reviewing what you have installed so far in addition to 10 as far as anything 3rd party you can try disabling in the Startup tab of the Taskmanager there. The msconfig utility is also still available for use on 10 in it's new form however. When clicking on the Startup tab there that will see the Taskmanager>Startup tab window open right up.

If it is a 3rd party program disabling anything non vital will help isolate a problematic software install. If on the other hand the updated delivered the wrong driver set for a hardware a quick fix may be reverting to a Win 8.1 update instead.

 

Hi Hawk,
All the hardware parts are ok. (cable, ssd, install media). No cheap hardware used.
Everything goes fine but after a couple reboots the problem happens.

 

Then it would either be software or OS related. I had that suspicion but needed to be able to rule out the rest. Have you been seeing this right from the start or after additional updates were going on? If something didn't go on fully during the 10 install that may be able to fixed up fast by a quick run of the System File Checker tool. I doubt you had 10 on long enough to worry too much about disk errors especially since this is pointing to something not being able to shutdown properly.

The first rec here would be to open up the Command prompt(admin) option in the Start button's right click menu. Then simply type in the "sfc /scannow" command and hit enter to get that going. The final results being displayed will indicate if the tool did need to fix something and whether or not it found something it couldn't fix. Often the advise given for the older versions was to have the Windows dvd in the drive in case the tool needed to extract any replacement files. When run a second time you would have then tossed the disk in the drive to watch the tool finish the repair work.

The other thing you can look over would be the Task manager's Startup tab as well as the Processes tab>Memory column to see if anything is showing too much memory for one item other then mapping. Often unused memory will have a habit of being mapped a bit.

Here without any softwares other then the av problem prompting the heck out of me at the moment following the upgrade from 14279 to the 14291 Insider build just out the only memory hog? would be the 313.7mb being used by Firefox 45.0.2 at the moment.

Once you bring up the small window when either right clicking on the main taskbar or hitting the Ctrl-Alt-Del combination and selecting the Task manager option on the blue screen there you simply click on the more details option to see everything appear with the major changes seen with compared to what was seen in 7.





At first sight you will generally only see a couple of items on the small box type window until seeing the main TM options screen appear. A simple highlight by single to right click on each item in the Startup group now seen there no longer found in the msconfig will feature the enable, disable, Open file location, search online, and properties items in that right click menu. By hand picking the 3rd party items to selectively disable one or more at a time which can take a few restarts you might spot the culprit having a hang up issue if this is software related.

The advantage of the msconfig however was the disable all option was seen there where if the problem was corrected immediately you would then re-enable only a few items at a time until the problem came up again. Then you would know which one or more to be looking at. In the TM seen now you simply click to highlight and then click the Disable/Enable button in the lower right hand corner for each item separately for the one at a time isolation.

After all that is done you will likely find however it will be only one simple thing that needs to be repaired! You will likely end up thinking to yourself "how could be just that one little thing only?". One little urk in Windows.

 

Go to computer managment (right click on "This PC" and then "Manage").
Under "Device Managment", search for "Intel(R) Management Engine Interface".
Right click on it > and then "Disable". Restart the PC afterwards.

I had this problem too (with Intel 535 SSD and WIN10), and this solved it.
It has no evident effect on performance so you don't need to worry about doing this.