Windows 10: Broke raid, booted to W7 instead of w10

Ok, so, I got to W10 from W7 or, so I thought. It was super slow and doing 100% disk usage so, I thought, maybe it was due to my Raid disks not being synched. So, I looked for IRST, but it wasn't there so, I tried to install it, but I got a message saying something about needing a newer version.

When I tried to install the new version, it said I had to reboot so I did.

When I rebooted, the little balls kept spinning all night so, obviously something is stuck.

I turned the computer off and back on and got the message on the raid screen that one of the drives was "bad" (don't remember the actual word used). So, I decided that I didn't need Raid and due to some of the other problems I've had, figured that the disk really was bad.

So, I broke the raid on both disks and rebooted.

So, both disks this time were good and, believe it or not, it booted to W7!!!!! WTF

I detached one of the disks (I think the one that was listed as "bad" before and turned the machine back on. This time it's trying to boot to W10, but the balls have been spinning for the past five minutes and I'm concerned it will never come back. On the optimistic side, I think I hear the disk spinning so, *maybe* it will eventually come up?????

Anyone that can tell me why the heck the above happened?????

:)

 

W10 corrupts W7 hard drive

W8.1 was working fine as a removable hard drive. W7 installed on a RAID array as multi partitions. Works fine and both OS can be booted and W8.1 reads the RAID array when booting as W8.1

W10 upgrade completed on removable 8.1 drive, but then checked RAID drives for errors and changed them.

W7 on raid no longer boots. After severel hours W7 finally re-installed on RAID array. (data is on other partition so ok.) Tested working all data recovered.

Here's the kicker.

As soon as I boot from W10 it says "reboot required to fix drives" then corrupts the Windows 7 install... Which doesn't need fixed!!

The drive containing W7 OS becomes unreadable although other data partitions on the RAID array are OK.

W7 recovery tries to fix the hard drive then fails.

W10 changed drive letters first attempt, so I thought this an easy fix, but in fact every fresh W7 install is corrupted as soon as I boot from W10.

This is a major problem. Why is W10 changing the drive parameters on a completely seperate fully operational operating system?

 

W7 access of W10 share

On my home network W10 systems can access shares on other W10 systems, and W10 can access W7 shares. However, when W7 tries to access a W10 share, it wants a network password. I give it the user/pswd I use to log in on the W10 but that doesn't help.

I found one place:
https://www.thewindowsclub.com/cannot-access-shared-folder-windows
that suggested setting HKLM...Lsa\restrictanonymous to 1
but that didn't seem to help.

TIA!

 

W10 corrupts W7 hard drive

(For any query related to Windows Operating System, feel free to post on Microsoft Community.)

Is this not a W10 operating system problem?

Anyway, Turns out corruption is caused by a service in W10 switched on by default. This causes W10 to run a disk check. Other forums seem aware of this and have been suggesting for quite some time it's switched "off" by default.

Still don't understand why w10 uses chkdisk on a raid Array, or why W10 chkdsk corrupts the drive, but switching it off resolves the problem and prevents many hours of reloading W7.