Win10 Downgraded Win8.1 Pro To Home Edition

DustSailor · 10 Oct 2015

Yes, windows 8, 8.1, and even 7 I think

spapakons · 10 Oct 2015

The computer probably was in standby mode (sleep), not completely off. So some event (like Windows Update) woke it up. Another explanation would be setting a specific hour to switch on automatically at the BIOS, but since you didn't do that the first case is more probable.

Omega1 · 16 Oct 2015

DustSailor said:

Yes, windows 8, 8.1, and even 7 I think

This is the first time I've had it happen.... and I've never heard of it happening before...

spapakons said:

The computer probably was in standby mode (sleep), not completely off. So some event (like Windows Update) woke it up. Another explanation would be setting a specific hour to switch on automatically at the BIOS, but since you didn't do that the first case is more probable.

I don't know if it would have been in sleep mode or not, but I do know I was clicking on Power/Sutdown and the computer would, I'll say, shutdown....

But as I said it was an easy fix, I just disabled it under Device Manager/Network Adapters/Power Adapters... and it's fine ever since...

At some point today or tomorrow, I'm going to try a clean install of Windows 10...

DustSailor · 16 Oct 2015

Omega1 said:

This is the first time I've had it happen.... and I've never heard of it happening before...

I currently have two computers that exhibit similar behavior. One sometimes won't turn on after going to sleep (force restart), and a different computer entirely will not shut down. I've spent many hours on the two. The kicker is a have matched each of them to many identical computers in hardware and software (in a business), and the other computers work flawlessly.. just not those two.

I can only guess something went wrong with their hardware, but too far gone to RMA. The behavior is the same when a new OS is installed.

I guess blaming ol' MSoft is probably not the way to go in my case.

spapakons · 16 Oct 2015

Have you tried updating the chipset drivers? Maybe some device doesn't work properly because of Microsoft generic drivers. Try updating the chipset drivers directly from Intel/AMD and see if that makes any difference.

DustSailor · 16 Oct 2015

^Thanks mate. But yea, all the latest drivers.

Ztruker · 16 Oct 2015

DustSailor said:

I currently have two computers that exhibit similar behavior. One sometimes won't turn on after going to sleep (force restart), and a different computer entirely will not shut down. I've spent many hours on the two. The kicker is a have matched each of them to many identical computers in hardware and software (in a business), and the other computers work flawlessly.. just not those two.

I can only guess something went wrong with their hardware, but too far gone to RMA. The behavior is the same when a new OS is installed.

I guess blaming ol' MSoft is probably not the way to go in my case.

I have not read this whole thread so this may have already been suggested, but turn off Fast Startup. It can negatively affect both shutdown and startup.

Fast Startup - Turn On or Off in Windows 10 - Windows 10 Forums

DustSailor · 16 Oct 2015

Ztruker said:

I have not read this whole thread so this may have already been suggested, but turn off Fast Startup. It can negatively affect both shutdown and startup.

Fast Startup - Turn On or Off in Windows 10 - Windows 10 Forums

You know, I kept reading about that on this forum, don't know why I never thought to try it out on these computers. So far got one off of fast startup, but kept secure boot enabled (using UEFI). The other will have to wait till I find an appropriate time to restart the computer. Thanks for the tip!

I'll mention if I notice any changes.