Upgrading a possible(?) corrupt Windows 8.1 into Windows 10


  1. Posts : 3
    Windows 8.1
       #1

    Upgrading a possible(?) corrupt Windows 8.1 into Windows 10


    It all started with that certain Windows update which downloads the software responsible for upgrading my Windows 8.1 into Windows 10. BUT, little did I know that I didn't plug in my charger and so my laptop went dead, and the update was interrupted.

    Thus when I opened my Windows 8.1, it would get a blank screen with a blinking cursor, the same issues (possibly) with these:

    http://www.vmwareandme.com/2013/10/s...l#.VcUI-7ykVC0
    http://www.eightforums.com/graphic-c...ows-8-1-a.html
    http://www.tomshardware.com/answers/...n-updates.html

    (For short: Most of them says that it is due to a graphics card driver update, i.e. with my Nvidia, being incompatible with a certain Windows update thus resulting into a blank screen.)

    Luckily, I was able to system restore at that time, BUT, IT HAPPENED AGAIN (the blank screen) when I tried my luck once again with the Windows update (for the glory of Windows 10 of course).

    Now I'm stuck with this "somehow corrupted" Windows 8.1 with the system restore, image recovery, startup repair, PC refresh AND EVEN SAFE MODE not being able to resolve the issue.

    Now I tried and exhausted all my resources and efforts on trying to restore my PC for I need my files there, (luckily I am dual-boot and have Ubuntu, but still can't access those Windows drives cause they are "corrupted"), then I came upon this Windows 10 Upgrade Tool.

    TLDR: If ever I try to upgrade my *corrupted* Windows 8.1 into Windows 10, would it work? Would my files be possibly recovered and Windows will now be accessible? And lastly, would it somehow affect my GRUB or my dual boot (Ubuntu)?
      My Computer


  2. Posts : 217
    Windows 10 Pro 64-bit
       #2

    What does Ubuntu say exactly when you try to access the Windows drive?
      My Computer


  3. Posts : 3
    Windows 8.1
    Thread Starter
       #3

    derek10 said:
    What does Ubuntu say exactly when you try to access the Windows drive?

    Unable to access "Windows" (my Local Disk C: )

    Error mounting /dev/sda4 at /media/zero/Windows: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177" "/dev/sda4" "/media/zero/Windows"' exited with non-zero exit status 14: Windows is hibernated, refused to mount.
    Failed to mount '/dev/sda4': 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.
    Last edited by anobilisgorse; 08 Aug 2015 at 15:38.
      My Computer


  4. Posts : 1,221
    Windows 8.1, Win10Pro
       #4

    That means you have FastStartup (NOT the same as Fast Boot) enabled on Win8.1. That puts the PC into hibernation even when you shut it down, keeping the open partitions still mounted, thus preventing a Linux distro from mounting them.
      My Computer


  5. Posts : 3
    Windows 8.1
    Thread Starter
       #5

    Mark Phelps said:
    That means you have FastStartup (NOT the same as Fast Boot) enabled on Win8.1. That puts the PC into hibernation even when you shut it down, keeping the open partitions still mounted, thus preventing a Linux distro from mounting them.
    I see. Then does that mean my Windows 8.1 files are not actually corrupted, only that my Nvidia driver is causing some blank screen issue?
      My Computer


  6. Posts : 1,221
    Windows 8.1, Win10Pro
       #6

    anobilisgorse said:
    I see. Then does that mean my Windows 8.1 files are not actually corrupted, only that my Nvidia driver is causing some blank screen issue?
    While they might be corrupted, all that message means is that the partitions are hibernated and can't be accesses outside of Win 8.1. So, the historical process of mounting the partitions using a Linux distro is not going to work.

    And yes, the blank screen issue is most likely caused by an NVidia driver problem. You should do searches in the forum -- I think there are some other threads dealing with the Nvidia problem.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 16:05.
Find Us




Windows 10 Forums