Is removing hiberfil.sys file the solution of my no longer booting, hibernated Windows 10?





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0















Short said, would removing the hiberfil.sys file from my Windows 10 partition allow it to boot again after it "got broken" due to conflict with Grub + Ubuntu?



My Windows 10 partition no longer wants to boot, after -I suppose by reading a lot on same issue- it stopped with hibernation or fast startup.



It starts by "preparing auto repair..."
It starts by "preparing auto repair..."



Then always fails on booting, allowing either Restart or advanced options.
Then always fails on booting, allowing either Restart or advanced options.



From this answer, I see ntfs-3g tool (which I discovered is installed, and a NTFS driver) has a remove_hiberfile option that would delete this file to allow read-write mount of windows partition on Ubutun again. (which is an issue but not my main issue, being, Windows no longer accept to boot at all)



   remove_hiberfile
When the NTFS volume is hibernated, a read-write mount is denied and a read-only
mount is forced. One needs either to resume Windows and shutdown it properly, or use
this option which will remove the Windows hibernation file. Please note, this means
that the saved Windows session will be completely lost. Use this option under your
own responsibility.


Before applying this solution, and taking more risk at damaging some data, do you think it could solve my broken, no longer booting windows 10?



Here is a little more details.

I have a 1To SSD with dual boot with Grub and split as:




  1. Windows 10 (main with +/-800Gb)

  2. Ubuntu 18.04.1 (+/-70Gb)


Dual boot used to work well, until windows hibernated, then no longer accept to boot again, possibly due to an intermediate boot on Ubuntu.



Some historic:




  • windows did broke when it was on an Intel i7 6700K + motherboard MSI Z170A Gaming

  • I only could start on Ubuntu by those steps: [grub (automatically appears)] > [Ubuntu]. If I choosed Windows (or Windows boot manager), Windows failed booting.

  • since recent crash of either my motherboard or cpu, I changed to a i7 9700K + motherboard MSI Z390 Gaming carbon pro

  • with this new setup, I only can boot Ubuntu after those steps: [boots on windows] > fails with debugging/starting options on a blue screen > [Device] > [Ubuntu]. Difference is, I no longer get on Grub menu by default. When I chose 2nd option from here [Hard drive], it boots saying, please insert boot media.


I try to restore it myself, trying to understand what is wrong, read a lot on same topic, but agree not to be confortable with MBR, EFI, UEFI, boot flag, etc... Some answer are about fast restart and how to disable it, on Windows, which I can't since my windows don't boot.



Here is what GParted says today:
enter image description here



We can see:





  • /dev/sda1: some windows required partition I think (récupération == recovery)


  • /dev/sda2: an EFI partition which has boot flag


  • /dev/sda3: a Windows reserved partition on /dev/sda3, but its filesystem is unknown, and used space (on a 16MB total) cannot be calculated. Looks like broken?


  • /dev/sda4: my main windows partition


  • /dev/sda[5-6]: Ubuntu


As a side note, I am not looking to mount / access my windows partition from Ubuntu, but to restore a booting Windows. I add this, since I successfully accessed my windows partition on Nautilus, in read-write mode, without doing anything.










share|improve this question

























  • Grub only boots working Windows which includes if the hibernation flag is set. And fast start up sets hibernation flag. But since UEFI install, you still should be able to directly boot Windows from UEFI boot menu, not grub menu. Then turn off hibernation and/or fast start up. If you changed hardware Windows may not work as it is licensed for only one system. You may also need Windows boot entry in UEFI, but you can add this either with Windows repairs or efibootmgr. See IV & restore Windows entry: askubuntu.com/questions/486752/…

    – oldfred
    24 mins ago




















0















Short said, would removing the hiberfil.sys file from my Windows 10 partition allow it to boot again after it "got broken" due to conflict with Grub + Ubuntu?



My Windows 10 partition no longer wants to boot, after -I suppose by reading a lot on same issue- it stopped with hibernation or fast startup.



It starts by "preparing auto repair..."
It starts by "preparing auto repair..."



Then always fails on booting, allowing either Restart or advanced options.
Then always fails on booting, allowing either Restart or advanced options.



From this answer, I see ntfs-3g tool (which I discovered is installed, and a NTFS driver) has a remove_hiberfile option that would delete this file to allow read-write mount of windows partition on Ubutun again. (which is an issue but not my main issue, being, Windows no longer accept to boot at all)



   remove_hiberfile
When the NTFS volume is hibernated, a read-write mount is denied and a read-only
mount is forced. One needs either to resume Windows and shutdown it properly, or use
this option which will remove the Windows hibernation file. Please note, this means
that the saved Windows session will be completely lost. Use this option under your
own responsibility.


Before applying this solution, and taking more risk at damaging some data, do you think it could solve my broken, no longer booting windows 10?



Here is a little more details.

I have a 1To SSD with dual boot with Grub and split as:




  1. Windows 10 (main with +/-800Gb)

  2. Ubuntu 18.04.1 (+/-70Gb)


Dual boot used to work well, until windows hibernated, then no longer accept to boot again, possibly due to an intermediate boot on Ubuntu.



Some historic:




  • windows did broke when it was on an Intel i7 6700K + motherboard MSI Z170A Gaming

  • I only could start on Ubuntu by those steps: [grub (automatically appears)] > [Ubuntu]. If I choosed Windows (or Windows boot manager), Windows failed booting.

  • since recent crash of either my motherboard or cpu, I changed to a i7 9700K + motherboard MSI Z390 Gaming carbon pro

  • with this new setup, I only can boot Ubuntu after those steps: [boots on windows] > fails with debugging/starting options on a blue screen > [Device] > [Ubuntu]. Difference is, I no longer get on Grub menu by default. When I chose 2nd option from here [Hard drive], it boots saying, please insert boot media.


I try to restore it myself, trying to understand what is wrong, read a lot on same topic, but agree not to be confortable with MBR, EFI, UEFI, boot flag, etc... Some answer are about fast restart and how to disable it, on Windows, which I can't since my windows don't boot.



Here is what GParted says today:
enter image description here



We can see:





  • /dev/sda1: some windows required partition I think (récupération == recovery)


  • /dev/sda2: an EFI partition which has boot flag


  • /dev/sda3: a Windows reserved partition on /dev/sda3, but its filesystem is unknown, and used space (on a 16MB total) cannot be calculated. Looks like broken?


  • /dev/sda4: my main windows partition


  • /dev/sda[5-6]: Ubuntu


As a side note, I am not looking to mount / access my windows partition from Ubuntu, but to restore a booting Windows. I add this, since I successfully accessed my windows partition on Nautilus, in read-write mode, without doing anything.










share|improve this question

























  • Grub only boots working Windows which includes if the hibernation flag is set. And fast start up sets hibernation flag. But since UEFI install, you still should be able to directly boot Windows from UEFI boot menu, not grub menu. Then turn off hibernation and/or fast start up. If you changed hardware Windows may not work as it is licensed for only one system. You may also need Windows boot entry in UEFI, but you can add this either with Windows repairs or efibootmgr. See IV & restore Windows entry: askubuntu.com/questions/486752/…

    – oldfred
    24 mins ago
















0












0








0








Short said, would removing the hiberfil.sys file from my Windows 10 partition allow it to boot again after it "got broken" due to conflict with Grub + Ubuntu?



My Windows 10 partition no longer wants to boot, after -I suppose by reading a lot on same issue- it stopped with hibernation or fast startup.



It starts by "preparing auto repair..."
It starts by "preparing auto repair..."



Then always fails on booting, allowing either Restart or advanced options.
Then always fails on booting, allowing either Restart or advanced options.



From this answer, I see ntfs-3g tool (which I discovered is installed, and a NTFS driver) has a remove_hiberfile option that would delete this file to allow read-write mount of windows partition on Ubutun again. (which is an issue but not my main issue, being, Windows no longer accept to boot at all)



   remove_hiberfile
When the NTFS volume is hibernated, a read-write mount is denied and a read-only
mount is forced. One needs either to resume Windows and shutdown it properly, or use
this option which will remove the Windows hibernation file. Please note, this means
that the saved Windows session will be completely lost. Use this option under your
own responsibility.


Before applying this solution, and taking more risk at damaging some data, do you think it could solve my broken, no longer booting windows 10?



Here is a little more details.

I have a 1To SSD with dual boot with Grub and split as:




  1. Windows 10 (main with +/-800Gb)

  2. Ubuntu 18.04.1 (+/-70Gb)


Dual boot used to work well, until windows hibernated, then no longer accept to boot again, possibly due to an intermediate boot on Ubuntu.



Some historic:




  • windows did broke when it was on an Intel i7 6700K + motherboard MSI Z170A Gaming

  • I only could start on Ubuntu by those steps: [grub (automatically appears)] > [Ubuntu]. If I choosed Windows (or Windows boot manager), Windows failed booting.

  • since recent crash of either my motherboard or cpu, I changed to a i7 9700K + motherboard MSI Z390 Gaming carbon pro

  • with this new setup, I only can boot Ubuntu after those steps: [boots on windows] > fails with debugging/starting options on a blue screen > [Device] > [Ubuntu]. Difference is, I no longer get on Grub menu by default. When I chose 2nd option from here [Hard drive], it boots saying, please insert boot media.


I try to restore it myself, trying to understand what is wrong, read a lot on same topic, but agree not to be confortable with MBR, EFI, UEFI, boot flag, etc... Some answer are about fast restart and how to disable it, on Windows, which I can't since my windows don't boot.



Here is what GParted says today:
enter image description here



We can see:





  • /dev/sda1: some windows required partition I think (récupération == recovery)


  • /dev/sda2: an EFI partition which has boot flag


  • /dev/sda3: a Windows reserved partition on /dev/sda3, but its filesystem is unknown, and used space (on a 16MB total) cannot be calculated. Looks like broken?


  • /dev/sda4: my main windows partition


  • /dev/sda[5-6]: Ubuntu


As a side note, I am not looking to mount / access my windows partition from Ubuntu, but to restore a booting Windows. I add this, since I successfully accessed my windows partition on Nautilus, in read-write mode, without doing anything.










share|improve this question
















Short said, would removing the hiberfil.sys file from my Windows 10 partition allow it to boot again after it "got broken" due to conflict with Grub + Ubuntu?



My Windows 10 partition no longer wants to boot, after -I suppose by reading a lot on same issue- it stopped with hibernation or fast startup.



It starts by "preparing auto repair..."
It starts by "preparing auto repair..."



Then always fails on booting, allowing either Restart or advanced options.
Then always fails on booting, allowing either Restart or advanced options.



From this answer, I see ntfs-3g tool (which I discovered is installed, and a NTFS driver) has a remove_hiberfile option that would delete this file to allow read-write mount of windows partition on Ubutun again. (which is an issue but not my main issue, being, Windows no longer accept to boot at all)



   remove_hiberfile
When the NTFS volume is hibernated, a read-write mount is denied and a read-only
mount is forced. One needs either to resume Windows and shutdown it properly, or use
this option which will remove the Windows hibernation file. Please note, this means
that the saved Windows session will be completely lost. Use this option under your
own responsibility.


Before applying this solution, and taking more risk at damaging some data, do you think it could solve my broken, no longer booting windows 10?



Here is a little more details.

I have a 1To SSD with dual boot with Grub and split as:




  1. Windows 10 (main with +/-800Gb)

  2. Ubuntu 18.04.1 (+/-70Gb)


Dual boot used to work well, until windows hibernated, then no longer accept to boot again, possibly due to an intermediate boot on Ubuntu.



Some historic:




  • windows did broke when it was on an Intel i7 6700K + motherboard MSI Z170A Gaming

  • I only could start on Ubuntu by those steps: [grub (automatically appears)] > [Ubuntu]. If I choosed Windows (or Windows boot manager), Windows failed booting.

  • since recent crash of either my motherboard or cpu, I changed to a i7 9700K + motherboard MSI Z390 Gaming carbon pro

  • with this new setup, I only can boot Ubuntu after those steps: [boots on windows] > fails with debugging/starting options on a blue screen > [Device] > [Ubuntu]. Difference is, I no longer get on Grub menu by default. When I chose 2nd option from here [Hard drive], it boots saying, please insert boot media.


I try to restore it myself, trying to understand what is wrong, read a lot on same topic, but agree not to be confortable with MBR, EFI, UEFI, boot flag, etc... Some answer are about fast restart and how to disable it, on Windows, which I can't since my windows don't boot.



Here is what GParted says today:
enter image description here



We can see:





  • /dev/sda1: some windows required partition I think (récupération == recovery)


  • /dev/sda2: an EFI partition which has boot flag


  • /dev/sda3: a Windows reserved partition on /dev/sda3, but its filesystem is unknown, and used space (on a 16MB total) cannot be calculated. Looks like broken?


  • /dev/sda4: my main windows partition


  • /dev/sda[5-6]: Ubuntu


As a side note, I am not looking to mount / access my windows partition from Ubuntu, but to restore a booting Windows. I add this, since I successfully accessed my windows partition on Nautilus, in read-write mode, without doing anything.







dual-boot grub2 18.04 windows-10 hibernate






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 1 hour ago







el-teedee

















asked 1 hour ago









el-teedeeel-teedee

1178




1178













  • Grub only boots working Windows which includes if the hibernation flag is set. And fast start up sets hibernation flag. But since UEFI install, you still should be able to directly boot Windows from UEFI boot menu, not grub menu. Then turn off hibernation and/or fast start up. If you changed hardware Windows may not work as it is licensed for only one system. You may also need Windows boot entry in UEFI, but you can add this either with Windows repairs or efibootmgr. See IV & restore Windows entry: askubuntu.com/questions/486752/…

    – oldfred
    24 mins ago





















  • Grub only boots working Windows which includes if the hibernation flag is set. And fast start up sets hibernation flag. But since UEFI install, you still should be able to directly boot Windows from UEFI boot menu, not grub menu. Then turn off hibernation and/or fast start up. If you changed hardware Windows may not work as it is licensed for only one system. You may also need Windows boot entry in UEFI, but you can add this either with Windows repairs or efibootmgr. See IV & restore Windows entry: askubuntu.com/questions/486752/…

    – oldfred
    24 mins ago



















Grub only boots working Windows which includes if the hibernation flag is set. And fast start up sets hibernation flag. But since UEFI install, you still should be able to directly boot Windows from UEFI boot menu, not grub menu. Then turn off hibernation and/or fast start up. If you changed hardware Windows may not work as it is licensed for only one system. You may also need Windows boot entry in UEFI, but you can add this either with Windows repairs or efibootmgr. See IV & restore Windows entry: askubuntu.com/questions/486752/…

– oldfred
24 mins ago







Grub only boots working Windows which includes if the hibernation flag is set. And fast start up sets hibernation flag. But since UEFI install, you still should be able to directly boot Windows from UEFI boot menu, not grub menu. Then turn off hibernation and/or fast start up. If you changed hardware Windows may not work as it is licensed for only one system. You may also need Windows boot entry in UEFI, but you can add this either with Windows repairs or efibootmgr. See IV & restore Windows entry: askubuntu.com/questions/486752/…

– oldfred
24 mins ago












0






active

oldest

votes












Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1134518%2fis-removing-hiberfil-sys-file-the-solution-of-my-no-longer-booting-hibernated-w%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1134518%2fis-removing-hiberfil-sys-file-the-solution-of-my-no-longer-booting-hibernated-w%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

GameSpot

日野市

Tu-95轟炸機