Can not access Windows file from Linux since 1511 &1607

Home Built PC running dual boot Windows Pro 10 and Ubuntu 16.04

I used to be able to access Windows files from Linux, but now I cannot, see errors next :-

28/09/16


Error mounting /dev/sda2 at /media/richard/8AA62C62A62C50CD: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000" "/dev/sda2" "/media/richard/8AA62C62A62C50CD"' exited with non-zero exit status 14: Windows is hibernated, refused to mount.
Failed to mount '/dev/sda2': Operation not permitted
The NTFS partition is in an unsafe state. Please resume and shutdown
Windows fully (no hibernation or fast restarting), or mount the volume
read-only with the 'ro' mount option.


Windows Pro 10 has just done update 1607 and my problem has come back.

I sorry but I am not very familiar with Windows.
I know that it is something to do with either fast start up or hibernation but can't remember how to get to the correct settings.


Windows Pro 10 has just done update 1607 and my problem has come back.
I sorry but I am not very familiar with Windows.
I know that it is something to do with either fast start up or hibernation but can't remember how to get to the correct settings.

Can you help please.

For this very reason is why I don't dual boot anymore....once there's a major update from MS or Linux....the MBR or Grub can become corrupted. The only sure fire way is to remove the Linux boot and make sure that your windows boot is working correctly.

Most of us enthusiast out there like to do a variation of the dual boot, it's called multi boot. This is where you use separate HDD's and install the OS on a individual HDD. Then using the F12 key at the post beep when starting or restarting the PC invokes the boot menu order with out having to go into the BIOS and change the boot order manually. Then select the HDD with what OS you want to run.

The key to this is to remove any HDDs installed and just have the clean HDD installed and then install the OS. Once that is done then you can reinstall (generally just unplug and replug in the power/SATA cables) and all your other OS's are still intact and the MBR and Grub are intact.

Under Power Options, you have to disable both Fast Boot and Hibernation options - they leave the filesystem mounted.

Thank you Plankton & Valihrach.

What a good idea Plankton, I have been thinking along those lines too, just purchase another 480gb ssd, so I could use windows on my original 120gb ssd and have linux and others on my new 480gb ssd.

Valihrach I have repeatedly under power options disable both fast boot and hibernation etc this did work the first time after 1511 update but not after the 1607 update.

Thank you both for your input.

You could try powercfg -h off from elevated command prompt (search for cmd, right click and run as administrator) in Windows and reboot. That will remove the hibernation file and permanently turn off hibernation and fastboot.

I dual boot and it really doesn't work with hibernation at all. You should disable it even if you are running Linux from another disk as if you if you mount Windows r/w and change anything the file system will not be the same as the hibernation image was based on.

I have the same issue as @Plankton with major upgrades disrupting the bootloader - I use rEFInd not grub though and just have to re-register it.

powercfg -h off This did not seam to do anything ?

Richard1942 said:

powercfg -h off This did not seam to do anything ?

It deletes C:\hiberfil.sys file which is used for hibernation. It doesn't say anything it just does it.

It is described a bit more fully in step 4 here Hibernate - Enable or Disable in Windows 10 - Windows 10 Forums

You can check if it has been removed with dir c:\ /a - if the file isn't there then your hibernation and fast startup are disabled.

If you disable fast startup and it reverts back after some time, it is probably set via group policy. Try to disable it in group policy using value "HiberbootEnabled" as described here: windows 10 - How to disable Fast Startup using a Group Policy? - Server Fault