locked
Dual-Boot Vista/Win10 messed up by Win10 update RRS feed

  • Question

  • Hi everyone,

     - Start with Vista 64-bit SP2 on PC with two drives - OS on Disk0 - working fine for years
     - Downloaded Win10 64-bit English-International ISO image from MS on 23 March
       UPDATE:  this was   Win10_1607_EnglishInternational_x64.iso
     - Installed on Disk1 as Home edition on 24 March
    All works fine with dual boot Vista/Win10

     - Win10 Update arrived on 25 March (I think Win10 Cumulative Upate, but can't be sure)
     - Update installed with Shut Down on 25 March

    Now fails at dual-boot time:
      PC/Device needs to be repaired
      Required device isn't connected or can't be accessed
      Error code:  0xc000000e

    Fortunately F9 boots Vista correctly.  I conclude that either the dual-boot is messed up OR it recognises that the Win10 OS is messed up.

    I'm a hesitant to go further without expert advice as I'd hate to mess up the Vista possibilty ! ! !

    Many thanks for any help - David

    (P.S.  Duplicate of post in Vista forum - Sorry)




    • Edited by DaPiForFun Thursday, March 30, 2017 6:52 AM
    Saturday, March 25, 2017 2:55 PM

Answers

  • Its been a long time - I needed to get work done rather than debugging this (being a boot problem, sometimes with CHKDISK, every test is very slow).

    The latest Win10 update (vsn 1703) went in on 14 July and two things were instantly evident:  the boot menu went back to graphics mode and, when the boot failed, it gave a diagnostic  0xc000000e  which apparently means device corrupted or not ready.  I repeat that Win10 (on Disk1) and Vista (on Disk0) work perfectly once booted and no errors have been reported for either of the disks.  My only hypothesis now is that Disk0 and Disk1 start up at different speeds, and fluctuations in the timing cause Disk1 not to be ready when needed.  This of course may be total nonsnse.

    I bit the bullet, freed up space on Disk0 (not as much as I wanted) and installed Win10 there (with the applications etc etc:  about a day's work).

    (I hope I'm not tempting fate!)  Since then I've probably booted 15-20 times; everyone perfect.

    I consider the problem as "worked around" rather than "solved".


    • Edited by DaPiForFun Tuesday, August 1, 2017 3:35 PM
    • Marked as answer by DaPiForFun Wednesday, August 2, 2017 9:33 AM
    Tuesday, August 1, 2017 3:22 PM

All replies

  • I should add that all partitions on both disks are accessible from the Vista boot.
    Sunday, March 26, 2017 5:49 PM
  • Further update - EasyBCD gives the following:

    Windows Boot Manager
    --------------------
    identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
    device                  partition=C:
    description             Windows Boot Manager
    locale                  en-GB
    inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
    default                 {6d73f4c0-10c1-11e7-853f-e40c2ce2f618}
    resumeobject            {6d73f4bf-10c1-11e7-853f-e40c2ce2f618}
    displayorder            {6d73f4c0-10c1-11e7-853f-e40c2ce2f618}
                            {98bbf539-17e8-11de-a117-00248c145def}
    toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}
    timeout                 30
    resume                  No
    
    Windows Boot Loader
    -------------------
    identifier              {6d73f4c0-10c1-11e7-853f-e40c2ce2f618}
    device                  partition=J:
    path                    \Windows\system32\winload.exe
    description             Windows 10
    locale                  en-GB
    inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    recoverysequence        {6d73f4c1-10c1-11e7-853f-e40c2ce2f618}
    recoveryenabled         Yes
    allowedinmemorysettings 0x15000075
    osdevice                partition=J:
    systemroot              \Windows
    resumeobject            {6d73f4bf-10c1-11e7-853f-e40c2ce2f618}
    nx                      OptIn
    bootmenupolicy          Standard
    
    Windows Boot Loader
    -------------------
    identifier              {98bbf539-17e8-11de-a117-00248c145def}
    device                  partition=C:
    path                    \Windows\system32\winload.exe
    description             Microsoft Windows Vista
    locale                  en-us
    inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    recoverysequence        {572bcd55-ffa7-11d9-aae2-0007e994107d}
    recoveryenabled         Yes
    osdevice                partition=C:
    systemroot              \Windows
    resumeobject            {98bbf53a-17e8-11de-a117-00248c145def}
    nx                      OptIn

    Does that mean that only Windows10 needs repairing?

    Will this leave the dual boot intact?

    TIA - David

    Sunday, March 26, 2017 9:06 PM
  • YOU CAN'T MAKE THIS UP !

    Switched on USB connected scanner & printer - boots OK

    Switched off USB scanner & printer - restarts OK

    Restart again - FAILS !

    F9 Boot into Vista (OK)

    Restart again - FAILS !

    F9 Boot into Vista (OK)

    Switched on USB connected scanner & printer - restarts OK

    As they say around here: WTF ? ! ? !

    Sunday, March 26, 2017 9:11 PM
  • I may have a solution prompted by the above.

    I was surprised to see that he dual boot is controlled by DRIVE LETTER as seen by the Vista environment.  (What I'd seen in the past was by physical address e.g. dual Win/Linux).  I'd allowed the new partition for Win10 to take its default letter J: - which was alphabetically AFTER the letters assigned to the built-in USB card reader.  I guess that means that the existance of J: depends on the satuts of the USB - yes?

    Action taken has been to change the drive letter in Vista to be before the USB drives (miraculously the Boot Loader entry gets updated) and first boot, with USB scanner & printer off, has worked correctly.




    • Edited by DaPiForFun Monday, March 27, 2017 5:13 PM
    Monday, March 27, 2017 7:20 AM
  • Well that didn't do any good.  So I conclude that

    THE PROBLEM IS INTERMITTANT  (5H1T)

    looking to see if I have any disk problems.
    Monday, March 27, 2017 5:13 PM
  • Hi, 

    It's hard for us to check the intermittent. 

    According to your information, I consider if there is any incompatible issue on your computer which cause the unstable issue. 

    Please check the model of your computer and find it on the manufacturer's website, see if it has been tested for Windows 10.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, March 28, 2017 8:30 AM
  • Hi Kate,

    Thanks for your response.  Yes, intermittent bugs are the pits!

    The machine is a  HP Pavilion p6005ch, which I installed around 2010.  Unfortunately HP doesn't show Win10 compatibility for models before 2013.  With 4GB RAM, 4-core processor and plenty of disk, I didn't look any further for potential problems, particulary as Win10 is claimed to be more efficient than Vista.  There seem to be no problems with device drivers - either Win10 found them automatically or the old ones work fine.

    I must add that the Win10 is not "Activated" yet.  I was looking for some degree of certainty before shelling out $120  :)

    Once booted, both Vista and Win10 work perfectly - I was running Win10 all day yesterday with no problems at all.  It's ONLY the boot sequence that is causing problems.

    At various moments in my messing around (sorry, I didn't keep a log book!) Startup Recovery (in Safe Mode?) was executed - it didn't do anything - and CHKDSK was forced on all volumes - no problems found.  UPDATE: Disk checking from inside Win10 shows no errors either.

    I'll continue to post evidence as I find it.

    TIA - David

    • Edited by DaPiForFun Wednesday, March 29, 2017 1:42 PM
    Wednesday, March 29, 2017 8:51 AM
  • To be perfectly clear the problems arise AFTER the Boot Manager screen (no longer graphical but now looking like the image below, of course with Win10 and Vista as the boot options).

    Wednesday, March 29, 2017 1:41 PM
  • Its been a long time - I needed to get work done rather than debugging this (being a boot problem, sometimes with CHKDISK, every test is very slow).

    The latest Win10 update (vsn 1703) went in on 14 July and two things were instantly evident:  the boot menu went back to graphics mode and, when the boot failed, it gave a diagnostic  0xc000000e  which apparently means device corrupted or not ready.  I repeat that Win10 (on Disk1) and Vista (on Disk0) work perfectly once booted and no errors have been reported for either of the disks.  My only hypothesis now is that Disk0 and Disk1 start up at different speeds, and fluctuations in the timing cause Disk1 not to be ready when needed.  This of course may be total nonsnse.

    I bit the bullet, freed up space on Disk0 (not as much as I wanted) and installed Win10 there (with the applications etc etc:  about a day's work).

    (I hope I'm not tempting fate!)  Since then I've probably booted 15-20 times; everyone perfect.

    I consider the problem as "worked around" rather than "solved".


    • Edited by DaPiForFun Tuesday, August 1, 2017 3:35 PM
    • Marked as answer by DaPiForFun Wednesday, August 2, 2017 9:33 AM
    Tuesday, August 1, 2017 3:22 PM
  • Four weeks later it's still working fine.
    Tuesday, August 29, 2017 12:21 PM