-
×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-13-2015 12:08 PM
@Luke_Duckwalker wrote:
@re4med wrote:Transcript of my chat with the tech....
I've read that many of you have had an online chat with the tech support. How can I get there? The only information that I found is the support call center, which was not very helpful...
Through the HP Support Assistant >> Support >> Chat.
...and BLAST THEM! 🙂
08-13-2015 12:27 PM
@gwb1 wrote:I tried that "Disable and Stop" Intel Rapid Storage Technology fix previously mentioned and can confirm that this fix..like all the others..Does Not Work! I think what people are doing is that they try the fix and then immediately put the computer to sleep and this usually happens. However the real problem is that the computer will not go into sleep mode after it was used for over one hour straight. So far none of the many previous Fixes actually work. Period.
Looks like different laptops have different workaround. My colleague's problem temporarily got solved by this step, after conducting a successful shut down after 1 hours and 45 minutes approx. He is using Toshiba laptop though, but as his issue was exactly the same as that of ours, and his problem seemed to be solved by this(well, we haven't tested it running for more than 3 or 4 hours though), so I though lets give it a shot to my laptop. But the very same step failed on my laptop and that too just within 45 minutes, on my HP envy laptop.
Seriously,don't know whats wrong actually, but I think, its we who have to find out, because MS and HP have stopped providing support and its been nearly 3 weeks of release of the faulty OS. Why are they not pulling back their OS. Too much ego(of MS).:smileymad:
Well, I shall post the status of my colleague's laptop tomorrow(after 10 hours, as its night 12 at my place now), as this will conclude who is at fault. If his laptop works correctly, then HP should take some action. If his laptop too fails like that of us, then MS is a big egoistic giant and its all MS fault(as such issues are also seen in other laptops, but i see sledom comments in their forums)
08-13-2015 12:48 PM
08-13-2015 01:07 PM
@bLizZaRd_95 wrote:
Not all the laptops have the option for online chat, it's either for the new models or the new devices. Because I can do that on my envy 15 which is about a year old abut not on my dv6 which is 6 years old now
Try to update HP support assistant if you have this problem.
08-13-2015 03:06 PM - edited 08-13-2015 04:25 PM
@re4med wrote:
@space_ghost wrote:I've been checking these forums for the last couple weeks since I installed this abomination of an operating system. Now that there is 83 pages, has anyone actually found a real fix? I am about to try that "Intel Rapid Storage" fix to see if I am one of the lucky few.
No. No REAL solution. There have been some limited and very minor success stories from reversion - update BIOS - install from ISO to Win10 but many of us think that is an overblown process.
Please report back on the IRST check and results.
I'd really REALLY appreciate it if you stop saying "install from ISO", because it's confusing. I NEVER burned an ISO. I used a tool that CAN create an ISO, but I did NOT do that..
So, one last & final time- this has worked for 4 people here, and NONE have CLEARLY stated it did not work, though you may or may have not meant it:
We converted back to 8.1 (& updated Bios tho I don't think that matters)
We went here:
http://www.microsoft.com/en-us/software-download/windows10
We clicked on this: (Download Tool Now)
Then, run the program, click this: (Upgrade this PC now)
And thats ALL. NO ISO.
08-13-2015 04:24 PM
"I'd really REALLY appreciate it if you stop saying "install from ISO", because it's confusing. I NEVER burned an ISO. I used a tool that CAN create an ISO, but I did NOT do that.."
ISO is simply shorthand for the optional file format compared with the Windows Update format. If that confuses you than I am sorry. We call it an ISO because you have the option with the DOWNLOAD TOOL (happy now??) to burn an ISO image and install from USB or CD. In other words...you need the DOWNLOAD tool to make an ISO or install directly from the download (which, by the ay, uses all the files in the ISO image that you would burn. Good grief, I cannot believe I am actually wasting time explaining this...
...So, now that you have been educated on the language. Get over it. We are not going to constantly type "Download Tool" every time we need to refer to it. Maybe we should just call it the DT instead of ISO and further confuse people.
08-13-2015 04:28 PM
**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.
