F5F Stay Refreshed Software Operating Systems Transferring ISO files across two NTFS partitions causes inconsistencies in data.

Transferring ISO files across two NTFS partitions causes inconsistencies in data.

Transferring ISO files across two NTFS partitions causes inconsistencies in data.

P
PlayForCC
Member
Find
217
10-24-2023, 02:23 AM
#1
Hi, I'm trying to transfer ISO files from my hard drive to a USB stick. Both drives use NTFS, so I expected everything to copy correctly. When using Windows Explorer and checking with HashMyFiles, the hashes don't match. I thought the format change might be causing issues, but the 32-bit ISO isn't being verified by FreeFileSync either. Could you suggest why this is happening?
Reply
Reply
P
PlayForCC
10-24-2023, 02:23 AM #1

Hi, I'm trying to transfer ISO files from my hard drive to a USB stick. Both drives use NTFS, so I expected everything to copy correctly. When using Windows Explorer and checking with HashMyFiles, the hashes don't match. I thought the format change might be causing issues, but the 32-bit ISO isn't being verified by FreeFileSync either. Could you suggest why this is happening?

Reply
Reply
O
okA_
Member
Find
141
10-24-2023, 09:32 AM
#2
Have you considered switching to another USB flash drive? Windows 10 also comes with a built-in command-line tool named Certutil for checking checksums.
Reply
Reply
O
okA_
10-24-2023, 09:32 AM #2

Have you considered switching to another USB flash drive? Windows 10 also comes with a built-in command-line tool named Certutil for checking checksums.

Reply
Reply
C
Cute_Ari
Member
Find
68
10-24-2023, 10:35 AM
#3
File managers can retain or modify these items based on configurations, but the explorer usually updates automatically. However, content shouldn't shift, so the checksum must remain identical. Consider using a file comparison utility to verify.
Reply
Reply
C
Cute_Ari
10-24-2023, 10:35 AM #3

File managers can retain or modify these items based on configurations, but the explorer usually updates automatically. However, content shouldn't shift, so the checksum must remain identical. Consider using a file comparison utility to verify.

Reply
Reply
T
THE_KILLER_
Member
Find
72
10-30-2023, 02:15 PM
#4
Thanks to you both, I'm starting to think it might be related to the USB3.1 driver or ports. I have one x1 USB3.1 and a USB3.1 type C, with the rest being USB3.0. When copying files through the 3.0 ports there was no issue, but when switching back to 3.1 I encountered a bizarre problem: the ASMedia port driver came from the motherboard website (Gigabyte GA-Z170XP-SLI). Anyone have any suggestions? I'm thinking about skipping the driver and letting Windows install its own version.
Reply
Reply
T
THE_KILLER_
10-30-2023, 02:15 PM #4

Thanks to you both, I'm starting to think it might be related to the USB3.1 driver or ports. I have one x1 USB3.1 and a USB3.1 type C, with the rest being USB3.0. When copying files through the 3.0 ports there was no issue, but when switching back to 3.1 I encountered a bizarre problem: the ASMedia port driver came from the motherboard website (Gigabyte GA-Z170XP-SLI). Anyone have any suggestions? I'm thinking about skipping the driver and letting Windows install its own version.

Reply
Reply
F
FuzzyMug
Senior Member
Find
476
10-30-2023, 09:17 PM
#5
Some fast USB devices avoid adapters or overly long cables at times. This could be the issue you're facing.
Reply
Reply
F
FuzzyMug
10-30-2023, 09:17 PM #5

Some fast USB devices avoid adapters or overly long cables at times. This could be the issue you're facing.

Reply
Reply
D
Demonsss91
Posting Freak
Find
767
10-30-2023, 10:15 PM
#6
Most of the cables are short (under 1m), but I need to keep that in mind. At the end I deleted the USB 3.1 driver and let Windows set its own, and it worked out. I've done several tests now and there are no more issues. My main worry is whether other files got damaged by this driver.
Reply
Reply
D
Demonsss91
10-30-2023, 10:15 PM #6

Most of the cables are short (under 1m), but I need to keep that in mind. At the end I deleted the USB 3.1 driver and let Windows set its own, and it worked out. I've done several tests now and there are no more issues. My main worry is whether other files got damaged by this driver.

Reply
Reply