Windows 10: Interesting question here about bricking older hdd's :/

Good tip,
You may have missed the point,
7 can not make changes to 10 is my interpretation of the built in install of 10 meaning 10 is a restrictive alpha,
Cheers.

 

That's less clear. Exactly what were you trying to do?

 

I'm not trying to do anything :/
It's just an observation I found out accidently
7 can not access 10 but 10 can access 7 without the same prompt
Cheers.

 

If your in WinRE from either platform, you can see the different OS's but it won't list system restore points which I guess is expected.

 

Thrash zone, windows 7 should be able to read & write to windows 10. When window 7 is running windows 10 is not in control. It is just the way windows 7 handles ntfs folders. Really simple fix, there is a registry file called take ownership. Merge that file. In windows 7 only, right click on the drive that has windows 10 installed, then click on take ownership and choose run as administrator. This may take a few minutes to run.

 

That's really meant for use on system files. I used that on a bunch of files in W7 some time ago.

 

Yea I don't believe taking ownership of an os is a good idea
But it does show 10 takes ownership of 7 on installs so it can boot after installing updates that is known,
It's yet to be noticed if 7 does the same keeping in mind my preference was 7 default os and I never had any issues installing updates on 7 during the tour of 10TP,

Me accessing 10 from 7 had no purpose nor do I want too it just confirmed 7 isn't able to without a error message but 10 had no issue at all which I did not access anything in any folders I just noticed I could to the limited extent I saw

Yes drives are drives I would expect a different result similar to 7's message in 10 because it is a system not personal data only = very different environment *Wink
Cheers.

 

Due to the way that both modern OS's work, and the way that NTFS file permissions work I would expect the same error message from both Win7 and TP, it's interesting to hear that TP does not give the message. This would suggest the the first administrative account on TP has full rights, ( not token controlled ), or at least more that a normal Administrator.

BTW, in dealing with dual boot systems I have always found that Taking Ownership is not the way to proceed, as it may cause issues with the workings of things such as Trusted Installer Etc. It's normally possible to just add the main administrator from system A to the permissions of System B and cascade them down which gives access without excessive risk *Smile

 

I must of misunderstood your post. I didn't say to take ownership of the os. I know from the way I had it on my system. Windows 7 can see windows 10 drive. Windows 10 can see the windows 7 drive. What I was saying is you boot to windows 7, then select the windows 10 drive, then select take ownership. Also, you might able to this as well. Boot to windows 10, then select the windows 7 drive, then select take ownership. Both ways does not take the ownership of the os.

However, one side note I just thought of. If you are using windows 10 boot manager to boot windows 7, then in that case. I wouldn't take ownership of the either root drive.

Boot to windows 7, open up windows 10 drive, select all folders in the 10 drive except windows (Make sure all folders are unhidden) then right click and choose take ownership. Don't select the files in the root drive.

Boot to windows 10, open up windows 7 drive, select all folders in the 7 drive except windows (Make sure all folders are unhidden) then right click and choose take ownership. Don't select the files in the root drive.

 

Yep well I'm not at all sure why you keep giving instruction on how to take ownership of files *Confused
Please stop I know full well how to if I wanted too,
Cheers.

 

This was your previous post. I agree with it but I didn't say that. Then I also remember some people use the window 10 boot manager to boot to windows 7. That why I added my modified instructions.

You keep thinking I am saying boot to windows 7 and use take ownership on windows 7, I am not saying that at all. That is a bad idea and will do damage or least it did with me. I guess I am just running into a brick wall. Also, you don't have to listen to advice here, I don't always. I don't post saying I am going to ignore your advice that would be rude.

unsubscribing from this thread.

 

Second post here seems to address the bricking issue :/
build 9879 bricking drives!!!! - Microsoft Community

 

This is odd, I have a dual boot set up with Win7/Win10 and I can easily access files on Win10 from Win7. In fact, I just copied files from Win10 from Win7 and all I have to do was confirm my administration by clicking OK.

*Huh