-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Archived Topics
- Notebooks Archive
- [SOLVED] Windows 10 - Laptop won't go into sleep mode

Create an account on the HP Community to personalize your profile and ask a question

08-14-2015 11:31 AM - edited 08-14-2015 11:35 AM
@DanG82 wrote:For the record, while this sounds like it could potentially be a remedy, it is NOT a replacement for an actual fix. Millions of users across hundreds and hundreds of various desktop and laptop models upgrade through the prompts provided by Windows. If that process somehow leads to this issue, Microsoft or HP still needs to come up with a fix for those who upgraded in this manner.
Telling everyone to revert to Windows 8.1 and then re-upgrade to Windows 10 using a different method would NOT be a satisfactory response from either company.
I agree completely. This "solution", if it is actually a solution, is not a solution (how's that for making no sense??). What I mean is the AVERAGE USER is simply not going to be bothered with all of this bunkola in order to get what should be a simple upgrade UPGRADED.
Again, I still do not understand logically WHY one process over another would actually be the root cause of this issue. There were a number of things I did in between that MAY HAVE contributed to a resolution (IF it is one -- I still remain unconvinced and won't be for a few days AT THE VERY LEAST).
One thing I am watching for is what happens AFTER Windows Update runs and then, tries to slam my Intel Video Chipset Driver into submission. Current at 4256 when, on the previous attempt it was 4256 then downgraded to 4248. At this point, all I can do is offer educated guesses.
However, this is not a GUESS...this is a fact: HP has done a very poor job of communicating with its customers on this maddening issue. Regardless of the resolution that may come in the days/weeks ahead it will be the classic case of "too little - too late". I am disgusted and I have advised users to write the VP (link posted awhile back) and let him know that this is simply not the way to take care of the people that keep him employed (and others).
08-14-2015 11:40 AM
Just to keep everyone in the LOOP. Sleep continues to work at 5.5 hours. I have never gone this long before with successful sleep commands.
I won't keep mentioning it in order to avoid annoying those who are still struggling. Again, I still remain unconvinced and will not be unless I can say the same thing as above in a WEEK. Stay tuned...
08-14-2015 11:45 AM
Lets see, what for me,,,,, Hp Envy 15 k102tx
08-14-2015 11:56 AM
So far so good this morning, but I'm going to have to run some more tests this evening to assure. Sleep and Shutdown were successful after an hour or so of operation and running various apps. I've yet to catch up on posts after your solution, so I'm hoping that this is a viable one. THANK YOU!
08-14-2015 12:04 PM
So far so good this morning, but I'm going to have to run some more tests this evening to assure. Sleep and Shutdown were successful after an hour or so of operation and running various apps. I've yet to catch up on posts after your solution, so I'm hoping that this is a viable one. THANK YOU!
@reverond wrote:**I have posted this in another area with the same issue**
YES!!!!! A Solution that worked. Spread the news. It has to do with the Intel Virtualization Tehnology. Didn't know what that was until this issue came up in Windows 10.
First, find out if this is your issue.
1. I installed the 'Intel Processor Identification Utility' directly from Intel.
2. After installation, open the program and go to the 'CPU Technologies' tab.
3. If it says 'YES' for Intel Virtualization Tehnology, proceed.
Solution...(at least on my system)
1. The next thing you have to do is go into the BIOS. If you have not done this before, proceed at your own risk.
You need to restart the computer and enter the BIOS (for me I hit F10 at the HP screen)
2. Within the BIOS, there is an 'Advanced Options' section
3. In this section there is a line for 'Intel Virtualization Tehnology' and it will say enabled or disabled. My computer said disabled.
4. If this is the case, change the option to 'ENABLED'; then SAVE and EXIT from the BIOS.
The Computer will restart and from that point on Shut Down, Sleep, etc. has worked. WOW this was a frustrating issue. Almost went back to Windos 8. I take no credit for this solution, I pieced it together from other posts on this issue. Hope this helps.
08-14-2015 12:41 PM
@iYousif wrote:
@bLizZaRd_95 wrote:
How's the Intel virtualize fix doing? So after all it was a graphics issue?Enabled the option from BIOS about one hour ago. Played with laptop during this time then I tried to put into sleep and it didn't work. 😕
Confirmed that this didn't work.
08-14-2015 01:27 PM - edited 08-14-2015 01:33 PM
P.S. I have not connected to internet till now, but connected only for hardly 15 secs, which got my Windows activated and then disconnected till ever.
I shall install these drivers one by one, offline, leave my laptop for 2 hours afte installing each driver and then conclude which driver is causing problem. (Had the Windows update not been forceful, I could have concluded very easily).
08-14-2015 01:41 PM
Ok well after a long, long day trying to figure out why my internet wasn't working properly, I've decided I'm going to go back to 8.1 but as a fresh install, back to factory settings. What steps do I need to take?
I'll make a note of my W10 licence key.
Back everything up that I need (obviously).
But then what?
Go through all the Windows updates and make sure my BIOS is up to date (how do I know if it is or not?)
Then go through the W10 update through the creation tool instead of the icon?
Is there anything I've missed there or anyone got anything to add before I go ahead?
08-14-2015 01:58 PM
@re4med wrote:Just to keep everyone in the LOOP. Sleep continues to work at 5.5 hours. I have never gone this long before with successful sleep commands.
I won't keep mentioning it in order to avoid annoying those who are still struggling. Again, I still remain unconvinced and will not be unless I can say the same thing as above in a WEEK. Stay tuned...
I appreciate your skepticism. Heck, its been working for me even longer and I'm still a skeptic. Still, glad so see so far it's still working for you.
by the way, I'm still at 10.18.15.4256 on my graphics driver. Nothing has tried to change that.
I can't imagine a problem of this nature was in all the beta versions without dramatic notice being taken of it so my guess is there's something small flawed about the windows update process (rather than directly getting it from microsoft's website).
I remember reading that they've set up windows update so you download not only directly from microsoft but also from other people's computers- a slightly different process..
No clue really whats going on.
