New
#11
Now this is interesting. Before the Windows 10 upgrade the drives were labled:
C: Win7 (HDD-0), D: WinXP, G: Win7 (HDD-1) with the C Drive being flagged with the Windows 7 Icon.
If I booted into WinXP the drives were relabled:
C: WinXP, G: Win7 (HDD-1) no change, and J: Win7 (HDD-0) with C Drive being flagged with the Windows XP Icon.
And if I booted into the HDD-1 copy of Windows 7:
C: Win7 (HDD-1), D: WinXP and J: Win7 (HDD-0)
So, booting changed the drive of the desired OS to C: each time and moved the OS that was C to another drive letter.
After the Windows 10 upgrade the drives are labeled:
C: Win10, D: WinXP, G: Win7
Booting to Win10 and WinXP does change the active OS to C.
But booting to Win7 does not rearrange the drive letters; in other words, Win7 stays G: not C:
I don't know why, the boot manger looks correct (from EasyBCD 2.3):
There are a total of 3 entries listed in the bootloader.
Default: Windows 10
Timeout: 10 seconds
Boot Drive: C:\
Entry #1
Name: Windows 10
BCD ID: {current}
Drive: C:\
Bootloader Path: \WINDOWS\system32\winload.exe
Entry #2
Name: Microsoft Windows 7 1-Win7
BCD ID: {f510424d-7031-11e4-8421-00219b205fea}
Drive: G:\
Bootloader Path: \Windows\system32\winload.exe
Entry #3
Name: Microsoft Windows XP
BCD ID: {f510424e-7031-11e4-8421-00219b205fea}
Drive: D:\
Bootloader Path: \NST\ntldr
Thoughts as to why Win7 does not get the C: drive letter when I boot to it and it appears to run but with the LogonUI error.
As an aside, I no longer have the "not genuine" message - I ran a Cmd of slmgr -rearm and "maybe" that resolved the Build 7601 issue. But I still have a black screen right after the Error of LogonUI.exe and then the blue Welcome screen, it goes black with another LogonUI error.