PC-3000 Express - Windows 10 - destination drive write error

[Nick_CT]

I had PC3K Express running on my old Windows 7 machine for years flawlessly. Now that I've moved to Windows 10 I'm getting destination drive write errors.

It's strange as I'm using the same USB docks, same destination drives. This is now even happening sometimes if I'm cloning a drive to task files, not even to another drive.

I've asked ACE and none of their suggestions really helped - any ideas please?

Here's an example of cloning use task files: LBA = 60187473 - Destination drive write error! (Catastrophic failure) [TThread_WriteSectors.Msg]

Like I said, same issues with writing to destination drives. Destination will be OK for say 5 or 10 minutes and then have write failures. Destination drives have been zeroed. I have no 3rd party anti virus, just Windows Defender.

[pcimage]

I had PC3K Express running on my old Windows 7 machine for years flawlessly. Now that I've moved to Windows 10 I'm getting destination drive write errors.

It's strange as I'm using the same USB docks, same destination drives. This is now even happening sometimes if I'm cloning a drive to task files, not even to another drive.

I've asked ACE and none of their suggestions really helped - any ideas please?

Here's an example of cloning use task files: LBA = 60187473 - Destination drive write error! (Catastrophic failure) [TThread_WriteSectors.Msg]

Like I said, same issues with writing to destination drives. Destination will be OK for say 5 or 10 minutes and then have write failures. Destination drives have been zeroed. I have no 3rd party anti virus, just Windows Defender.

Are you running one instance of PC3K and utilising separate channels thorough that?

I used to get that issue all the time until I started separate instances of PC3K (using shortcuts) for each task. That seems to have more or less resolved it for me.

[northwind]

I had the same problem. I stopped using USB docking stations and turned to SATA. Problem gone.
Now, when I see such error, it will mean that the drive is actually having problems.

[pclab]

When I get that I found out it was problems on my destination drives (they also fail heheheh).

I don't think windows 10 have something to do with it, which can be a miracle

[pcn]

I have this too sometimes when pluggin in new destination drives on esata docks on running tasks. But when I resume task its all fine.

[HddDonorMarket]

Same occure for me (using MRT ) . Problem mostly about destination drive in bad condition. Have you ever tried with another drive to target.

[digisupport]

+1 separate instances of PC3K = problem gone for me.

[Nick_CT]

I've ruled out the destination drives and USB docks, even replaced them with new ones. It's happening to task files too. Something is just generally fishy with this new Win10 machine for a number of reasons.

Once I've got the current jobs off it, I'm going to reboot and image 2 or 3 known perfect drives and see what happens.

Have always had PC3K instances separate, so that isn't something that I can try either. Will update the post when I figure out what is causing this - thanks for the suggestions.

[Amarbir[CDR-Labs]]

I've ruled out the destination drives and USB docks, even replaced them with new ones. It's happening to task files too. Something is just generally fishy with this new Win10 machine for a number of reasons.

Once I've got the current jobs off it, I'm going to reboot and image 2 or 3 known perfect drives and see what happens.

Have always had PC3K instances separate, so that isn't something that I can try either. Will update the post when I figure out what is causing this - thanks for the suggestions.

Hi ,
I think i know what the issue is ,If you can video conference with me monday to saturday 10:30 to 2:30 and 3.00 to 7.00 PM Indian Time I Can Share My Experience

[Nick_CT]

I've enabled cache control in DE and disabled Windows Defender and replaced it with Kaspersky and everything working like a dream now, imaging to USB drives, SATA drives or task files is now error-free.

Thanks guys, seems Windows Defender was perhaps the main issue.

[HddDonorMarket]

Strange case solution ))