Broken system disk after data copy on another pc.

Welcome to the forum. What folder did you copy data from and have you got show hidden and system files

Samuria said:

Welcome to the forum. What folder did you copy data from and have you got show hidden and system files

Thank you :)

Basically it`s all about a broken system disk after connecting it to another win host pc but yes - show hidden and system files are enabled. It is not about hidden files somewhere. Data are just my personal docs, pics etc.

Also thread title "Broken system disk after connecting it to another win host pc and allowing to read it.." probably would fit more.. (can`t change it tho or can I?)

Its about the folder it came from if itsin a profile it has special permission which may effect it do you connect it as a slave to a win10 or win7 pc

Samuria said:

Its about the folder it came from if itsin a profile it has special permission which may effect it do you connect it as a slave to a win10 or win7 pc

Wait the problems starts when I allow to read the connected disk. Yes it is slave if you asking me this in terms of OS I don`t boot the system from that connected disk I boot the system from host pc disk. It`s just not only about copied files all the profile/system? is f* up just after allowing to read the connected disk. System is f* up without any file copying thing if I put it back into the laptop.

Why did you remove the disk and swap to another computer to move over your personal data?

Would it have been better and easier to put the files on USB drive or copy over Ethernet?

I would start over....

farrellart said:

Why did you remove the disk and swap to another computer to move over your personal data?

Would it have been better and easier to put the files on USB drive or copy over Ethernet?

I would start over....

SATA3 6Gb/s interface is far more faster than 100 Mb/s ethernet or USB. In my case these are not just a few files but tons of GB.
But again that`s not about how to copy files. The topic is about when I connect one win10 system disk to another host win10 desktop pc, it f* up the connected disk in a way when you put the disk back in a laptop windows is broken.. something to do with permissions I believe..
The thing is it has never happened before. Also have never done it before on the latest and "greatest" (not very sure about that anymore) win 10 which is version 1903 now. All I can say is a big thanks to Microsoft or maybe there is some valid explanation to this let`s define it as phenomenon which I don`t know about.

OK........eSATA drives are great for that sort of thing.

There is nothing wrong on the procedures you did. I also do the same between my Win 7 and Win 10 disks.
Did you run check disk on the laptop disk?
Open a CMD window as administrator and type:
chkdsk C: /f
If you run it from the laptop it will say that the disk is in use and if you want to schedule on next start = Yes
Reboot.
Pay attention on the results, specially bad blocks, bad clusters etc

farrellart said:

OK........eSATA drives are great for that sort of thing.

I know, but I`ve got no eSATA interface.. but thanks :)

- - - Updated - - -

Megahertz said:

There is nothing wrong on the procedures you did. I also do the same between my Win 7 and Win 10 disks.
Did you run check disk on the laptop disk?
Open a CMD window as administrator and type:
chkdsk C: /f
If you run it from the laptop it will say that the disk is in use and if you want to schedule on next start = Yes
Reboot.
Pay attention on the results, specially bad blocks, bad clusters etc

Yes I know. But again there`s nothing to do with bad blocks or any sort of this. Both disks are in perfect working order, the laptop`s disk is even brand new which I have also checked. Also I have done the same scenario with another laptop meaning completely another hw including disk. Same problem.

I`m just now thinking maybe because my host desktop pc is upgraded from ver 1809 to the latest 1903... Have never liked upgrades, but Microsoft now release a big ones so often that I am not very keen to do fresh install every single time when they release it. But 99% I want to believe that`s not the issue otherwise it would be really stupid if it is What I need to do is more tests to find it out because it is very embarrassing to know you can`t just quickly pop the disk in and copy data because the host f* the system.. I just need to do same with fresh 1903 install on the host, if it doesn`t help go back with older win 10 and see how that will work.

If someone knows the answer please let me know. But in general what I`m thinking about MS is too far with their clever and ridiculously advanced super permission system which I have never fully understood. But maybe that`s not the case. Don`t know yet.