Solved Duel Boot using a Win 8.1 & a non-working Win 8.1

Ok we will do our best to explain our issue.

Everything was AOK on a single boot system using Win 8.1. I apparently made some type of change in the OS to cause Win8.1 on "C" drive to fail booting into OS. I tried a few things, but the OS would not let me into the safe mode or restore system area. I tried several times, though I could see the system through the BIOS uefi boot up screen. So somewhere I must of messed maybe the MBR or something, I am not sure. It is not a virus and the system is still intact, it just is unable to initiate Windows 8.1 to take it to repairs.
So, what I did is installed Win8.1 on another disk the exact same size as the non-working system. All in hope to copy boot files over from the new system to the old non-working system. This would also give me the chance to examine the non working system files for anything out of the ordinary. When installing the new system, the install was smart enough to create a duel boot and it ask which system to boot into when starting. I have tried to allow it to boot into the bad system, but it gets stuck when handing the system to windows somewhere. I have even tried copying the registry files over from a backup in the old system, into the old system registry config folder. In hopes it would clear a possible registry problem and boot up. It did get it farther into windows, but it locks into the diagnosing your PC and does not complete the diagnosing.
I was wondering what I could do to reawake the original OS with possibly coping boot files over so it will atleast enter the restore/repair system and I can take it from there to repair the system. I have restore files available in the old system, just can't access that part to allow it to restore.
Is there a way I can pull a restore on that non working system by using the working version of Win8.1. In otherwords point the direction of the operation to the non working systems files thru the working system. or maybe find a way to manually locate the restore files and place them into the non working system to get a working system that I can work with. Again, the system is not dead, it is somehow being stopped by a possible corrupted file or setting that will not let it continue.
I have a DVD install disk and also a USB stick with the Win8.1 OS located on it. I just don't want to break the working system in this process and will have to restrain from a guess to fix it and end up crashing the working system.
MSCONFIG has a choice of items on choosing OS for boot up and it has options to chose for diagnosing. Since I run such a tight ship with my OS's, I rarely ever had to use any of this stuff because I just take good care of things on the computer. Maintaining my system is a priority and I have done it well for 20+ years, but as the saying goes, good thing don't last forever and Murphy's Law catches up to you.
SO what kind of backdoor ways can I possibly do with copying boot files or pulling old restore files and putting them in place myself, to bring the system back up. I am not afraid of registry changes or files moving and can move into correcting this with experience and computer knowledge easily.
If you need any log files or such, I can pull them from the non-working system folders to maybe capture the issue it comes to when trying to start the OS.

Thanks for the help,

post a screen shot of disk management

Sorry it took so long, my employment puts me on the road. Here is your request.
Windows C:\ drive is the working system disk.
Windows D:\ drive is the non working system disk.
It also seems after my tries on repairing when it originally happened that I have an extra system reserve disk on the computer. Would this be because I tried to repair the drive and it did not remove this reserve or is it something I can remove.


This is the inventory on the reserve disk G:


This is my system "This PC"

from a cmd prompt admin

bcdboot D:\windows

I will continue with your request and post the results below this recent message addition here, but I would like to add something here that may have a bearing on this issue I am having. Remembering back before the problem started, I can remember my Windows 8.1 was issued an update from Microsoft update notification. I followed through with the update and if I remember correctly it was an update for explorer security made on June 23rd 2015. This is the date of system corruption to the best of my knowledge. Now during the update, the system seemed to take much longer to make the update to the system. It took so long that I thought the system had given up and was stuck. There was no drive action and system seemed to stop the update operation. After waiting a reasonable time for the system to complete the update, I decided to do a reboot and check for updates again to see if the request was given by Microsoft to re-update again. Well, the system at this time refused to reboot and my troubles began on that day. I'm sorry I did not catch this earlier, but it was reminded back to me when I located this update log in Windows 8.1. I will post the info below that the update gave in the log. it may help possibly or at least give a better understanding of the reason of the system booting up to Windows 8.1 corruption.
I did try to recreate the boot process which took 3 steps, but the last command of the process refused to repair. Anyway, I hope this helps as you read through my posted information.


LOG START:

2015-06-15 08:30:24:113 1804 11bc Misc =========== Logging initialized (build: 7.9.9600.17831, tz: -0700) ===========
2015-06-15 08:30:24:113 1804 11bc Misc = Process: C:\Windows\Explorer.EXE
2015-06-15 08:30:24:113 1804 11bc Misc = Module: C:\Windows\system32\wucltux.dll
2015-06-15 08:30:24:113 1804 11bc WUApp WARNING: RegNotifyChangeAUXKeyValue, error=0x00000000
2015-06-17 04:43:35:159 1804 2e70 Misc =========== Logging initialized (build: 7.9.9600.17831, tz: -0700) ===========
2015-06-17 04:43:35:159 1804 2e70 Misc = Process: C:\Windows\Explorer.EXE
2015-06-17 04:43:35:159 1804 2e70 Misc = Module: C:\Windows\system32\wucltux.dll
2015-06-17 04:43:35:159 1804 2e70 WUApp WARNING: RegNotifyChangeAUXKeyValue, error=0x00000000
2015-06-23 02:51:55:096 2524 718 Misc =========== Logging initialized (build: 7.9.9600.17831, tz: -0700) ===========
2015-06-23 02:51:55:102 2524 718 Misc = Process: C:\Windows\Explorer.EXE
2015-06-23 02:51:55:102 2524 718 Misc = Module: C:\Windows\system32\wucltux.dll
2015-06-23 02:51:55:096 2524 718 WUApp WARNING: RegNotifyChangeAUXKeyValue, error=0x00000000
2015-06-23 03:20:17:089 2524 1298 WUApp No EULA acceptance needed
2015-06-23 03:20:17:137 3892 dfc Misc =========== Logging initialized (build: 7.9.9600.17831, tz: -0700) ===========
2015-06-23 03:20:17:137 3892 dfc Misc = Process: C:\Windows\system32\wuauclt.exe
2015-06-23 03:20:17:136 3892 dfc AUClnt Launched Client UI process
2015-06-23 03:20:17:162 3892 dfc Misc =========== Logging initialized (build: 7.9.9600.17831, tz: -0700) ===========
2015-06-23 03:20:17:162 3892 dfc Misc = Process: C:\Windows\system32\wuauclt.exe
2015-06-23 03:20:17:162 3892 dfc Misc = Module: C:\Windows\SYSTEM32\wucltux.dll
2015-06-23 03:20:17:162 3892 dfc CltUI AU client got new directive = 'Progress Ux', return = 0
2015-06-23 03:25:26:173 2524 1298 CltUI WARNING: GetAutoRebootInXDays: Auto-reboot time not found(hr = 80070002). Nothing to do here
2015-06-23 03:25:26:174 2524 1298 CltUI WARNING: GetAutoRebootInXDays: Auto-reboot time not found(hr = 80070002). Nothing to do here
2015-06-23 03:25:26:388 2524 1298 CltUI WARNING: GetAutoRebootInXDays: Auto-reboot time not found(hr = 80070002). Nothing to do here
2015-06-23 03:29:33:596 2524 1298 CltUI WARNING: GetAutoRebootInXDays: Auto-reboot time not found(hr = 80070002). Nothing to do here
2015-06-23 03:29:33:596 2524 1298 CltUI WARNING: GetAutoRebootInXDays: Auto-reboot time not found(hr = 80070002). Nothing to do here
2015-06-23 03:29:33:596 2524 1298 WUApp WARNING: Call to GetInteractiveInstallProgress failed, hr=8024000C
2015-06-23 05:04:34:169 2524 1298 AU WARNING: Attempt to allow auto firmware installs at next shutdown failed, hr=80070005
2015-06-23 05:04:34:171 2524 1298 Misc WARNING: SUS Client is rebooting system.
2015-06-25 07:12:37:353 1924 1134 Misc =========== Logging initialized (build: 7.9.9600.17831, tz: -0700) ===========
2015-06-25 07:12:37:377 1924 1134 Misc = Process: C:\Windows\Explorer.EXE
2015-06-25 07:12:37:377 1924 1134 Misc = Module: C:\Windows\system32\wucltux.dll
2015-06-25 07:12:37:352 1924 1134 WUApp WARNING: RegNotifyChangeAUXKeyValue, error=0x00000000
2015-06-25 07:12:50:739 1924 fdc WUApp No EULA acceptance needed
2015-06-25 07:12:50:935 4560 11d4 Misc =========== Logging initialized (build: 7.9.9600.17831, tz: -0700) ===========
2015-06-25 07:12:50:935 4560 11d4 Misc = Process: C:\Windows\system32\wuauclt.exe
2015-06-25 07:12:50:935 4560 11d4 AUClnt Launched Client UI process
2015-06-25 07:12:51:018 4560 11d4 Misc =========== Logging initialized (build: 7.9.9600.17831, tz: -0700) ===========
2015-06-25 07:12:51:018 4560 11d4 Misc = Process: C:\Windows\system32\wuauclt.exe
2015-06-25 07:12:51:018 4560 11d4 Misc = Module: C:\Windows\SYSTEM32\wucltux.dll
2015-06-25 07:12:51:018 4560 11d4 CltUI AU client got new directive = 'Progress Ux', return = 0
2015-06-25 07:21:29:087 1924 fdc WUApp WARNING: Call to GetInteractiveInstallProgress failed, hr=8024000C
2015-06-25 07:21:41:561 1924 fdc WUApp No EULA acceptance needed
2015-06-25 07:21:41:621 3372 474 Misc =========== Logging initialized (build: 7.9.9600.17831, tz: -0700) ===========
2015-06-25 07:21:41:622 3372 474 Misc = Process: C:\Windows\system32\wuauclt.exe
2015-06-25 07:21:41:621 3372 474 AUClnt Launched Client UI process
2015-06-25 07:21:42:028 3372 474 Misc =========== Logging initialized (build: 7.9.9600.17831, tz: -0700) ===========
2015-06-25 07:21:42:028 3372 474 Misc = Process: C:\Windows\system32\wuauclt.exe
2015-06-25 07:21:42:028 3372 474 Misc = Module: C:\Windows\SYSTEM32\wucltux.dll
2015-06-25 07:21:42:028 3372 474 CltUI AU client got new directive = 'Progress Ux', return = 0
2015-06-25 07:25:08:231 1924 fdc WUApp WARNING: Call to GetInteractiveInstallProgress failed, hr=8024000C
2015-06-25 07:25:08:231 1924 fdc WUApp WARNING: Call to DeserializeInstallResults failed, hr=80243003
2015-06-25 07:25:08:231 1924 fdc WUApp WARNING: Unable to display installation results, hr=80243003

Boot files successfully created....per your request.

Prepared for the Next Step! :thumb:

I'll keep checking back for the Next Step.

where you able to boot the old version of windows via boot menu (F12)

Well I have some good news and some weird news, lol.

For some strange reason the system booted up and it came after an update. It booted into what looked like an older version of the duel boot menu. It listed the 2 systems, But it renamed the old broken system drive letter that was presently on D: to Windows 8.1 on C:\. Then it removed the edition word PRO from the system version identification.
This weirdness doesn't stop here.
After the reboot from updating some Windows updates on the C:\ drive system and entering the older duel boot menu choices, I chose the Windows 8.1, not the pro version. It rebooted to the broken system like nothing ever happened. LOL. It was strange, but hey It started up. :thumb:
Now when it started up, it somehow renamed the D:\ hard drive to C:\WINDOWS 8.1. In other words it must still think it is on the C:\ drive because I never had the chance to change it from D:\Windows 8.1. Follow me?
Somehow when I boot into the old broken system, it is renaming the drive D:\ that it is on to C:\ and renaming my new install system from C:\ to D:\.
This must be the registry causing this because the old system thinks it's still running as a single operating system on C:\ and makes the correction being D:\ to C:\ during boot up. When it does this, it also plays games with my user account and I have to reinstate Administrative security to it and for each system as I decide on the system and boot from it.
Here is some details on the 2 systems.

New C:\ drive ( system )
User: xxxxxxx



Old C:\ drive ( original system ) that was moved to D:\ and is now booting up.
User: xxxxxxx

Please note the gap in the user name: xxxxxxx & xxxxxxx
Please note the gap in the system name of the drives C:\WINDOWS 8.1 & D:\WINDOWS 8.1

Just so your aware of how closely they are related and I didn't want to confuse you when I talked about the old or new system.

So, here is my plan at this point, since you got my system up again. First off let me say thank you very much for the CMD info you posted and for making it a direct and quick repair to get it working again. I appreciate that you took the time to help me out.


Now, since the broken system is accessible now...I need to start moving some important programs over to the newer install disk and format the old system disk before I get stupid and forget which system I am using. As it is now, each time I boot to either system...it thinks that it is the default system and puts the registries into a workout. I definitely do not want either system to make a mistake and cross the user name or hard drive name during a boot up and be back at square one. So, I guess I better get this taken care of soon.
Just FYI, when the broken system booted... I had to re-activate windows and reinstate my user name. Then when I returned back to the new system, I again had to reinstate my user. Strangely I did not have to enter my password. So, as you can see things are not acting as they should when the old system boots up and it wants to make changes that I don't want to allow.

The bottom line is, it's working and as long as I am careful during the move, It should be AOK. Do you have any references to programs that make transfers for programs and stuff to a new install system? it would be helpful to have something like this instead of reinstalling and re-entering passwords, ect ect.

Once Again, Thank You for your time. You did good!!!

Brad

windows will always assign the letter C to the booted OS

any ideas or suggestions?

Bradmph said:

Do you have any references to programs that make transfers for programs and stuff to a new install system? it would be helpful to have something like this instead of reinstalling and re-entering passwords, ect ect.

Click to expand...