Restart instead of shutdown

[daamii]

Hello,

Since Windows 10 my laptop (i5 2410, HD3000+7400M) doesn't shutdown: it goes blank and in the best case it restarts (sometimes 1 in 10, it stops correctly).
It does this with a NEW Windows without any drivers from Internet or installed by myself.
It is fine when starting in safe mode (even with network).

What I tried:
- changing the Intel driver (tested version 7, 9, 10)
- disabling fast boot
- turning off hibernate
- disabling devices in "device manager"
- uninstalling drivers of those devices
- changing the registry value of PowerDownAfterShutdown
- disabling in BIOS all the devices, less the CDdrive which has the SSD, from which I boot
- disabling in BIOS wakeup on lan
- disabling in BIOS some other power parameters
- disabling in BIOS second videocard.

The drivers and the BIOS were updated to the last version.
No "question marks" in Device Manager


In Ubuntu it stops properly.

 

[bgunner]

Did the laptop come with windows 10 installed?

 

[kango69]

Has the power button setting been altered
http://www.windows10compatible.com/blog/how-to-configure-windows-10-action-when-power-button-is-pressed/

 

[daamii]

The laptop came initially with Suse.
I've used the start button to shutdown the laptop, as well CMD; the physical button is properly set.

BIG QUESTION: for sure there is a default Windows driver(-s) which creates this issue (as when I boot in safe-mode, the laptop works fine).
Any idea how to track it down quickly ?
After installing Win10, there is an automatic RESTART (to finish the installation). In my case it didn't restart. I tested 2 images (Win10 & Win10 anniversary) and it was the same issue.

 

[bgunner]

Does it happen when in a clean boot state?

Clean boot: in run type MSCONFIG and pres enter. Select services tab and at the bottom click hide all windows services. Now disable any thing that is left. NEXT: start task manager and select startup tab. Disable all programs in start up and restart the PC. This puts the PC into a Clean Boot state.

EDIT: Also try this: Open a command window with administrator rights and type without quotes "SFC/Scannow" and press enter.
If this finds items it can not repair on its own you can run this command without quotes " dism /online /cleanup-image /restorehealth ". The first one checks the integrity of the OS files and repair them But the second one will replace any ones the first can not but will do it from an image stored from a MS server so you will need online access when this one is run.

 

[daamii]

In this case, a clean boot works in the same way as a normal boot; I already specified:
It does this with a NEW Windows without any drivers from Internet or installed by myself.
I also disabled all the services I could disable; these are the only ones which cannot be disabled by default:

In Safe-Mode, the active services were these:

When I'm in safe-mode the laptop stops perfectly; so, what else is disabled in this mode ?

 

[bgunner]

So is the answer to the question put forward a yes or a no? OR was a clean boot not tried?

Have you run the System File Check that was also recommended to be run? If so what were the results?

 

[hydranix]

Does the laptop use a UEFI implementation or legacy BIOS?

Disable Legacy Mode in firmware setup. Ensure windows is installed in UEFI mode, and that safe boot is disabled (if applicable, a laptop with Linux preinstalled might not have Microsoft's keys installed for safe boot, if implementing safe boot at all). Since it's a Linux laptop, ensure that the hardware is supported by Windows 10.

From Linux issue the command in terminal:

sudo lspci -n

Copy all the PCI vendor and device IDs of crital hardware (or everything if need be). They look like this: 12ef:ab34 (two 16 bit integers in hexadecimal separated by a colon)

Then search out each device and ensure Wndows 10 supports it.

Can you provide the laptop manufacturer and model information?

 

[daamii]

A clean boot did nothing; it behaved exactly as a normal boot, meaning that the OS didn't shutdown properly.
About the System File Check I forgot to add that I did it yesterday, two times and without any errors.

I also disabled "Automatically restart" in Startup and Recovery and disabled some "Wake-s" in Advanced properties of my LAN card.

 

[bgunner]

A clean boot did nothing; it behaved exactly as a normal boot, meaning that the OS didn't shutdown properly.
About the System File Check I forgot to add that I did it yesterday, two times and without any errors.

I also disabled "Automatically restart" in Startup and Recovery and disabled some "Wake-s" in Advanced properties of my LAN card.

Does the Laptop's manufacture supply Windows drivers for this laptop? My worry is that the Laptop does not support Windows 10. IF this is the case it would be the reason safe mode works and regular wont since safe mode restricts most things from running.

 

[hydranix]

It's kind of funny seeing this issue the way you're describing it.

In several years of Linux experience, this is a problem that was always one with Linux not shutting down or restarting or hibernating correctly, and Windows shutting down properly.

 

[daamii]

No, but it doesn't explain why sometimes it works and it doesn't explain why Ubuntu works.
I'm sure that if I disable "something" in Windows, the laptop will work flawlessly ..but I don't know what.
Or at least to know the cause of this problem and I could look for some other drivers.

Also, "Power Troubleshooter" found no error.

 

[hydranix]

No, but it doesn't explain why sometimes it works and it doesn't explain why Ubuntu works.
I'm sure that if I disable "something" in Windows, the laptop will work flawlessly ..but I don't know what.
Or at least to know the cause of this problem and I could look for some other drivers.

Also, "Power Troubleshooter" found no error.

Which post are you responding to?

Linux and Windows NT are two extremely different kernels. They also don't support all of the same hardware.

No windows drivers being available is very good reason to suspect there might be incompatibility with the hardware.

 

[daamii]

Sorry, I didn't see all the replies:

@bgunner
It is no more supported, but this shouldn't be the answer.
The first step in solving this issue is to understand why it doesn't work properly. I run Windows 10 on an Atom with 2G of RAM. If that Laptop works then I guess this one should work too.

@hydranix
"Does the laptop use a UEFI implementation or legacy BIOS?"

It is a 2011 model, HP 4530: i5 2410, 8GB RAM, 750 SSD in DVD caddy as primary + 640 HDD. I have MBR partitions, so it should be BIOS.
Everything has been reinstalled. I haven't keept the initial OS; I have several partitions (those with Linux at the end, ext4). There is no problem with booting (never had one); it works perfectly; the problem is with shutdown process.

In order to activate my license I had to update from Win8.1 to Win10; Windows 10 said that the laptop checks all the requirements.

In order to have access to Linux, either I have to fix the grub (because I've reinstalled Win10) or to boot from a Live pendrive.
There are no question marks in device manager (in Win), in theory, all the drivers work perfectly fine: this is what Windows tells me.

I think with Windows 10, they added some low-power functions which messed up the things.

 

[bgunner]

Just because one machine can run a certain OS does not mean a different one will.

Looking up the laptop HP did release that laptop with windows 8.1 installed, along with other OS's also, So many of the 8.1 Drivers should work in Win 10. While they did discontinue support on that laptop and didn't release Win 10 drivers because Win 10 is based heavily off of Win 8 the drivers will be compatible.

Have you installed the chipset driver? Out of all the drivers for your laptop this would be the only one that could cause the issue... If it is a driver issue.

What happens when you type "Shutdown -s" in a command prompt? it should bring up a window saying you will be logged out and windows is shutting down in a few moments... then shuts down.

 

[helpstar]

have a look at the intel managment engine interface

try updating drivers of it for your laptop

try post#13: https://www.tenforums.com/general-support/23897-windows-10-doesnt-shut-down-properly-2.html

try uninstalling the management engine in device manager and restart

try disabling the interface completely

 

[kango69]

I know its not a solution but I would revert back to the Windows version that came with the laptop
You just have to browse these forums to see how many people are having problems with systems after installing Windows 10
Even new builds with all the latest tech are struggling with this new OS.

 

[helpstar]

In the meantime windows 10 is running pretty well, when it comes to new hardware. Old hardware was not built for win10 and therefore it will always be luck if it works fine or not.

By the way, which laptop make and model is it?

 

[hydranix]

Sorry, I didn't see all the replies:
I run Windows 10 on an Atom with 2G of RAM. If that Laptop works then I guess this one should work too.

But before you can under stand potential problems, you have to cast away flawed logic. An different processor and amount of RAM on a completely different machine does not in any way say that your other laptop should should work correctly.

It is a 2011 model, HP 4530: i5 2410, 8GB RAM, 750 SSD in DVD caddy as primary + 640 HDD. I have MBR partitions, so it should be BIOS.

Excellent, now we can do some digging to find out what might be wrong.

In order to activate my license I had to update from Win8.1 to Win10; Windows 10 said that the laptop checks all the requirements.

Unfortunately the checks that the upgrade performs are notoriously less than thorough, and obviously every corner case could not be predicted. Which could be your problem.

In order to have access to Linux, either I have to fix the grub (because I've reinstalled Win10) or to boot from a Live pendrive.

You can prevent Windows from nuking grub, but you have to manually install it with dism or imagex, and then configure the bootloader and bcd accordingly. Not that this is at all important to your problem.

There are no question marks in device manager (in Win), in theory, all the drivers work perfectly fine: this is what Windows tells me.

Generic drivers that severely limit hardware functionality will not show any errors or problems. Same goes for drivers that are buggy and unreliable, or outright wrong, but have the right entries in the INF file.

I think with Windows 10, they added some low-power functions which messed up the things.

What makes you think that?


-- I'm looking into information on your laptop's hardware and hopefully will find the answer you want to or might not want to hear.

-edit-

That laptop is a few years older than Windows 8, and several years older than windows 10. I can already see there being issues. Especially with the more-than-likely outdated BIOS. Update the BIOS, and perhaps you'll have fixed the issue.

Here, these links are to HP's support site which provides the BIOS and firmware drivers you probably need. Double check I've specified the correct laptop before installing.

Intel MEi firmware

Intel MEI

BIOS update

UEFI upgrade

 

[daamii]

@bgunner
The last drivers I have (some of them 3Dguard and SDreader are not installed by Windows) are for Windows 8.1

I downloaded many versions of "Intel Management Engine Components Driver"; the following are those which I could install, to no avail: 7.1.40.1161, 9.xx and 10.0.30.1072.
I used Intel Driver Update Utility Installer and it downloaded Intel Chipset Device 10.1.1.14 and on Internet I found Intel Chipset Drivers for Microsoft Windows 10.1.1.38. Nothing fixed this problem.

"Shutdown -s" ?: it works as if I select the "normal" shutdown. I also tested "shutdown -s -t 00"

@helpstar
I did that; maybe there is one which I haven't tested. I was tracking them on google with "SUPERSEDES:SPXXXX". It didn't worked those for Lenovo, Asus, etc.
Clean Widnows, with no updates (no Internet connection) and no external driver, doesn't stop.

@kango69
I have a Win8.1 pendrive in standby. Two days ago I shutdown the laptop in order to connect the pendrive and install Win8.1. That time, the laptop stopped properly.
So, maybe there is still a chance for Win10.


@helpstar
True about the new and old hardware. I have access to a HP 450G2. The problem with the shutdown was solved by changing the Intel and the restart by updating the BIOS. Now, I have an issue with the headsets (it doesn't switch between speakers and headsets, and new Win10 with or without updates. Linux works properly).


@hydranix
There is always a solution if the culprit is identified. The big question is which driver ? I have disabled most of the hardware in Computer management and what I found in BIOS; still nothing.
The last drivers are for Win8.1 and the last BIOS is F.61 Rev.A 10 May 2016, which is already updated.

 

[u2desire420]

Try disabling Fast Boot under Power Options. I believe this setting is found under "Choose what the power buttons do". I know this caused a problem with my laptop fully shutting down so it maybe the cause of your problem. This did not cause my system to restart but it did cause it not to fully shutdown.

 

[bgunner]

Out of pure curiosity since you have the 8.1 on a flash drive, Is it bootable? and does the laptop shut down properly with 8.1 running?

 

[kango69]

Did you try disabling wifi before you shut down or better still remove the wifi card and see if makes a difference.

 

[daamii]

I tested several Intel Chipset Drivers (I kept 10.1.1.42 20170119) and Intel Management Engine Components Drivers (I kept 11.0.5.1189 even though all over the Internet seems to be the cause of the problem; for my laptop doesn't make any difference).
I found that if I activate the Fast Startup (again, on Internet disabling this function should cure the problem) the laptop turns off "acceptably fast" (80-90% of times) , but it never restarts.

Any other ideas are welcomed.

 

[u2desire420]

With my old laptop I went through EVERY device in Device Manager and manually checked online for updates. Windows did find some updates that were not being installed or updated doing a regular update even the Anniversary update required me to do this to get some of the updates. Specifically you want to do this to everything under System Devices. Hopefully it will find an update that solves your problem. I am thinking it could be ACPI related driver causing this issue.