[netrate]

I assumed it it from the EasyBCD that has been installed.

[Advertisements]

See my previous post, I think it is Windows Manager.

[iammykyl]

See my previous post, I think it is Windows Manager.

[netrate]

I am ok with leaving the boot manager as it is. So what is my next step?

[iammykyl]

Good choice.

Doing some checks.

 

You have a backup set up for Data?

You have MR system recovery images for both drives?

 

What you need to keep.

The last MR RE USB created with all drives connected.   You don't need the other USBs with the individual W7/W10 RE.

You also need to keep the installation media, (USB or DVD) for both OSs in case you need to repair or reinstall them, also the codes.

 

Next time you start W10, allow disk check to complete > restart to W10.

Does disk check run again?

[netrate]

I will check and post back.  My concern is that as soon as Win 10 does it's check, then win 7 will want to suddenly do the same check, but only one way to find out.  I will post back.

[iammykyl]

How are things going?

[netrate]

Sorry, it's been a crazy couple of weeks.  I am back at my second job since lockdown has been partially lifted.  As soon as I get the FAITH drive Imaged (I need to buy a new drive for backup), I will test the dual boot.  Thanks for checking in.  I should have something to report by the end of this week.

[iammykyl]

I will look out for that.

[netrate]

Sigh, ok. It seems one thing gets fixed, another thing goes back to square one. 

• Dual boot - Win 10/Win 7 connected.
• Boot to win 10.
• I ran the scan disk on FAITH 
• After it booted to win 10 - shut down normally.
• Removed Win 10 - only win 7 connected
• Booted
• Scan disk on both Win 7 and Faith now.

 What the heck is going on with this thing?  why is is doing that?

[iammykyl]

I think, because if you removed a drive, booting with 2 drives, the boot configuration is not what windows expects, a scan is run to see/fix the problem.\With dual boot set up, you should no longer need to figgle with drive connections.

[netrate]

I almost had a panic attack today doing the chk dsk.  On boot to win 7 (win 10 not connected), I let it run and "76 reparse records processed" and "deleting corrupt attribute record from file record segment"

I am glad I did a macrium image on the weekend - but it booted fine after the scandisk chk, and I have no idea what any of that stuff means.  Going to make another image and then hook up the win 10 drive together with the win 7 and see what happens.