-
×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
- Sleep and Shutdown issues after upgrading to Windows 10

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

12-31-2015 02:40 AM
Dear all,
I have a Spectre x360 4103ng with WIN10 pre-installed and I cant downgrade to v9 or v10.. The versions are not compatible with my device (thats what displayed when I want to install over v11).
Anyone has a suggestion on how to downgrade? I read that uninstalling the v11 driver, and restarting might work, but I dont want to risk anything.. Will this procedure only work with automatic updates enabled? Or not? A bit confusing..
Thanks a lot,
kind regards,
Johannes
12-31-2015 09:26 AM
@jojojojojojo wrote:Dear all,
I have a Spectre x360 4103ng with WIN10 pre-installed and I cant downgrade to v9 or v10.. The versions are not compatible with my device (thats what displayed when I want to install over v11).
Anyone has a suggestion on how to downgrade? I read that uninstalling the v11 driver, and restarting might work, but I dont want to risk anything.. Will this procedure only work with automatic updates enabled? Or not? A bit confusing..
Thanks a lot,
kind regards,
Johannes
Proceed at your own risk... but uninstalling v11 shouldn't cause any issue. Keep automatic updates enabled for that part of the process; only disable them when you go to install v9 or v10 (at the point the steps say to do so).
That said, I haven't heard much about this issue on devices that came pre-installed with Windows 10, so I'm not certain it's the same issue. Is HP selling laptops that have this issue out the gate?!
01-01-2016 07:45 AM
Thanks for the reply. Might try then..:)
As I understand, the issue with v11 is nothing they can really avoid, other than installing older versions. But since none of the previous versions (9, 10) seems to work on this laptop, the only one left is 11..
01-01-2016 10:47 AM
@jojojojojojo wrote:Thanks for the reply. Might try then..:)
As I understand, the issue with v11 is nothing they can really avoid, other than installing older versions. But since none of the previous versions (9, 10) seems to work on this laptop, the only one left is 11..
No prob! I suspect uninstalling v11, restarting to allow it to automatically reinstall, and then proceeding with the steps I posted may still work for you... but like I said, proceed at your own risk. 🙂
Happy New Year all!
01-10-2016 10:45 AM - edited 01-10-2016 10:46 AM
Last year I upgraded windows 8.1 to windows 10 and subsequently had the common issue with my computer unable to wake up from sleep mode. It was fixed with downgrading Intel Management Engine to earlier version.
Yesterday my computer did an automatic windows 10 update and now I am again faced with the same issue. This time I can not fix the sleep mode issue with the above fix. I just got off the phone with Microsoft and the tech suggested I wait for Intel to release an updated version of Intel Management Engine that is compatable with lastest Windows 10 update.
If I attempt to use the prescribed fix I get an error message during the installation that the earlier version is not compatible with the computer. The tech tried to work around that using compatibility mode and it failed.
Any suggestions?
01-10-2016 10:50 AM
@STEVEKAY wrote:If I attempt to use the prescribed fix I get an error message during the installation that the earlier version is not compatible with the computer. The tech tried to work around that using compatibility mode and it failed.
Any suggestions?
Try uninstalling v11, restarting your computer (which should prompt an automatic reinstall), and then following the steps again from the beginning.
01-10-2016 11:16 AM
If I uninstall the driver, it is reinstalled during the boot up. As I recall that was the mistake I made after the initial windows 10 upgrade. The original fix worked only by restarting AFTER v.9 install, not before,
