I tried to encrypt my entire windows installation hard drive. During the wizard, you have to restart your pc for a test. During this reboot, the display of my laptop only showed the HP logo for around 15 minutes. With encouragement from a friend I turned the power on and off. Now my laptop is displaying the "Machine is not in a commited state" warning together with the HP logo, and I can't access my laptop anymore.
I've already tried to do a system restore, but it did not work.
Is this an issue I can fix somehow with the rescue drive, or do I need to contact HP Support?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Contacting HP support is on my to-do list for tomorrow (it was already after closing time when I was working on the problem today). The problem does seem very HP-specific. From my own Googling experiences I only found out that most people who encounter this problem replaced their motherboard, and that it has something to do with a tool only HP has access to.
With my question on this forum I am hoping to find some workaround to perhaps undo whatever I did that caused this error. Whether or not such a workaround exists, I'm still also going to contact HP support.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So, I did something kind of dumb.
I tried to encrypt my entire windows installation hard drive. During the wizard, you have to restart your pc for a test. During this reboot, the display of my laptop only showed the HP logo for around 15 minutes. With encouragement from a friend I turned the power on and off. Now my laptop is displaying the "Machine is not in a commited state" warning together with the HP logo, and I can't access my laptop anymore.
I've already tried to do a system restore, but it did not work.
Is this an issue I can fix somehow with the rescue drive, or do I need to contact HP Support?
A quick Google search on "Machine is not in a committed state" shows this issue can only be resolved by contacting HP support.
Contacting HP support is on my to-do list for tomorrow (it was already after closing time when I was working on the problem today). The problem does seem very HP-specific. From my own Googling experiences I only found out that most people who encounter this problem replaced their motherboard, and that it has something to do with a tool only HP has access to.
With my question on this forum I am hoping to find some workaround to perhaps undo whatever I did that caused this error. Whether or not such a workaround exists, I'm still also going to contact HP support.