Windows 10: XP failed after upgrading win7 to win 10 of dual boot with XP

Several weeks ago I upped to windows 10 on a dual boot system running windows 7 and XP. Win7 and XP are on different partitions. Over the last week, the XP would not boot unless it was directed to the last successful configuration. I attempted system restore from XP with no success. Then I booted XP in safe mode and did a system recovery "successfully", sort of. Now XP will not boot in either normal mode or safe mode even after letting it sit all night, so I cannot undo the system restore.

I cloned and activated the hard disk before upgrading. I scanned for viruses before system restore.

I was wondering what the best option might be. I could copy the XP partition back from the clone and reactivate if it will let me or I could secure erase the hard drive with the win 10 up and XP and revert to the clone.

Two other questions.

1.) Any other options?

2.) What could have caused this?

GS

:)

 

Dual boot windows xp sp3/ win 7 sp1 to xp/win 10 dual boot

I have a desktop with dual boot windows xp sp3/ win 7 sp1. I have some older software (only used a few times a year) that will not run on win7 so I have the xp partition. Will the new windows 10 upgrade allow the install to have xp/win 10 dual boot.

 

ual boot system upgrade to windows 10

Thanks Jessen for the hint. I was expecting a yes or no answer, since I already have a dual boot system(xp+win7), and if I upgrade win10 from win7 boot, would win7 be replaced by win10 and becomes a (xp+win10) dual boot system?

But it looks more complicated than I thought, should I check current system has xp and win7 are installed in DIFFERENT partitions, otherwise xp would be gone after win7 is upgraded to win10 if xp and win7 are in SAME partition?

 

Just curious. Is fast boot enabled on the Win 10 install? As I understand things, this should not explain what you are experiencing. It could conceivably cause corruption of the Win 10 partition if XP is booted and the 10 partition is written to in its hibernated state. But it should not cause corruption of the XP partition. In any case, you might try turning it off anyway if enabled.

 

Mike, I am not familiar with fast boot. The PC boots slower than either the windows 7 or windows XP boots.
I will check about the fast boot, but I have never left the PC on long enough to hibernate. I shut it down. The XP has been left up over night however and I have put the XP on standby.
The way the 10 bootloader works is weird. I have never had a system that reboots when instructed to boot other than the primary boot. They have always gone right to the other OS.

 

There's a tutorial here which explains fast boot:

https://www.tenforums.com/tutorials/4...dows-10-a.html

 

I have never liked hibernate on a PC. It seems that every time I try it the machine locks in just about every OS I have used. A common error that I have encountered is "delayed write failed".
I think understand the principle in the tutorial. I wonder how big the hiberfile is. Hibernate is a low energy state, kind of like pre-loading a shell and waiting for the go signal. The hybrid writes the hyberfile and shuts down. It boots to the hyberfile and instead of adjusting the kernel, it writes directly to memory. I suppose the boot to information is temporarily written to the boot sector? ...or into the initiation file?

 

I really think fast startup may be your responsible for your XP volume getting clobbered. Your description of having to boot twice to get to XP rings true:

http://social.technet.microsoft.com/...f-windows.aspxImpact to Windows Boot Scenarios

When a system with multiple versions of Windows installed is resumed from a Hybrid Boot state, the boot process will fully restore Windows 8 and remount previously active volumes before providing a selection screen to choose another version to boot. If the user selects an alternate version, the system is rebooted (which allows for active file systems to dismount and in turn downgrade the log file structure and version to one that is compatible with all prior versions of Windows) and the system will load the desired version. In most scenarios, this will not result in a previous version of Windows mounting a NTFS volume with an unrecognized log file structure and version number.
However, as part of the design of Hybrid Boot, the Windows 8 kernel is not fully shutdown unless a restart is requested, thus any mounted file systems do not have an opportunity to dismount when the machine is Hibernated. As a result, active file systems will not be down-graded to the compatible log version 1.1 after the Hibernate. Thus, removing a physical drive containing active file systems from a Windows 8 machine after the system is Hibernated, and connecting that drive to a prior version of Windows will result in the volume being marked as corrupted. A full chkdsk run will be required to clear the corrupted state of the volume, which will return it to a healthy state.
If you anticipate that you will be physically moving storage devices with a caching policy set to “Optimize for Performance”, or storage devices attached through SATA or SAS between Windows 8 and a prior version of Windows, it is recommended that you either disable Hybrid Boot, or to set a registry key to prevent NTFS from upgrading the Logfile structure and version number to 2.0 upon mount. Details on how either of these procedures, how you can determine if your volume has been upgraded to the new Logfile structure, and how to determine your storage device’s caching policy follows in this article.

 

Add the XP entry with EasyBCD

 

I reverted to the archive copy of my hard drive. The same problem appeared. I tried minimal recovery and that did not work. I removed the most recently installed programs and was successful. I think it was an ancillary app from my new Epson Printer. I removed all unnecessary software that came with the printer and the computer booted properly. I did a search on the application and only one post came up. Unfortunately I did not log the name of the app. So, the problem was apparently due to the ancillary software. XP trashed when I tried a deeper recovery to an earlier date. I will check on the link later.

Thanks,