Windows 10: Dual-Boot System upgraded to Windows 10, now Win7 gives LogON error

Hi - By the way, I believe that previous post about the drive letters not changing may be incorrect. When I booted on to Win7 and ran the cmd to fix the Not Genuine issue, it had to be from C: So I think the system did change from G to C on that boot - since I can't actually see the My Computer, I really didn't think it had changed.

Any chance running a sfc /scanow would help?

Jumping ahead, what is the correct process for installing Windows 7 "after" Windows 10 if I have to format that partition on HDD-1 and reinstall clean?

Thanks

 

Running sfc /scannow might help. Certainly would not hurt.

Have you tried a new (temporary) user account to see if that changes anything?

If it has been less than 30 days since upgrading to Windows 10, you can revert HDD-0 back to Windows 7. If that fixes the problem then you have confirmed that the problem is the sharing of some files between the two Windows 7 partitions.

To do a clean install of Windows 7, you will boot from the Windows 7 DVD. Select custom install option which will give you a list of hard drives and partitions. Select the Windows 7 partition on HDD-1 and reformat it then install to it. It will automatically keep the dual boot menu.

 

Hi - Actually, I don't know how to create a new user account when I can only seem to run the Task Manger.

I'll run the sfc /scannow - got nothing to loose.

And with the difference in the number of files and folders in the Windows.old vs. what's in the Windows folder in the Win7, I'm not sure I even what to think about that roll back.

 

If you want to keep an installation of Windows 7, I think your best course of action is a clean install.

 

At this point, I agree. Probably wasted a lot of time on this already.

Is this just by using the Windows 7 Pro upgrade disk? Will it give me a choice as to which partition I want the Win7 to reside? Will I need to change boot manger or will that happen automatically?

Still bugs me that everything seems to run, just not the login.

 

Solved - sort of. Found that I had an image of the Win7 HDD-1 partition. It was not current, but rather than doing a new install, I figured at this point it would be worth having Macrium restore that partition from the image. Booted just fine.

I still have no idea what happened during the Windows 10 upgrade of the Win7 HDD-0 partition that would have affected the other location. Obviously something clobbered files since scf /scannow found damaged files but could not repair them.

Thanks for sticking with me during this issue. Much appreciated advice.

 

Glad you got it fixed!