Barry it sure sounds like you're runnning into the FAT32 4GB size limit. Can you format at least one of your drives with NTFS (or exFAT for a USB drive)?

If drive formatting isn't the issue, it may in fact be a limitation of the PD capture module

The C: drive is NTFS, no surprise there, capturing to my desktop.
Ill try my external, and maybe install PD14 to try.
This, if I recall is only a 17 problem as it happens on my other machine.
EDIT: A ticket has been submitted. I do not expect much, honestly, it is after all version 17,
however... better functionality and fewer sticker packs would be a better use of resources. HP Envy Phoenix/4thGen i7-4770(4@3.4GHz~turbo>3.9)
Nvidia GTX 960(4GB)/16GB DDR3/
Canon Vixia HV30/HF-M40/HF-M41/HF-G20/Olympus E-PL5.
Tape capture using 6 VCR, TBC-1000, Elite BVP4+, Sony D8 camcorder with TBC.
https://www.facebook.com/BarryAFTT

I recall answering a question about the mp4 capture from the vc-500 where the OP stated the same problem on the then current PD20/365 that Barry brought out in 2021 in this link: https://forum.cyberlink.com/forum/posts/list/85167.page and is answered by optodata in exactly the same way.

The Op stated that he will not contact Cyberlink support as he only had a few more to do and the workaround works and is of no concern to him. I was trying to get him to write the support ticket since he has the same problem in the current PD20 version that Barry reported here for PD17. No , I won’t write a ticket for someone else that has the problem that I have no interest in pursuing. I reported the PD17 then current capture issues found and it took almost a year for most of them to get fixed.

I bet it is a simple registry hack, but maybe not so simple to me!
Something is corrupted, that's my guess. HP Envy Phoenix/4thGen i7-4770(4@3.4GHz~turbo>3.9)
Nvidia GTX 960(4GB)/16GB DDR3/
Canon Vixia HV30/HF-M40/HF-M41/HF-G20/Olympus E-PL5.
Tape capture using 6 VCR, TBC-1000, Elite BVP4+, Sony D8 camcorder with TBC.
https://www.facebook.com/BarryAFTT

Registry hack or not, these problems need to be reported to Cyberlink support as forum users are not allowed to reverse engineer or hack the program. I would not ask any user to spend the time to fix it without being paid to do so.

Quote Registry hack or not, these problems need to be reported to Cyberlink support as forum users are not allowed to reverse engineer or hack the program. I would not ask any user to spend the time to fix it without being paid to do so.

Maybe registry repair/fix is the better term. HP Envy Phoenix/4thGen i7-4770(4@3.4GHz~turbo>3.9)
Nvidia GTX 960(4GB)/16GB DDR3/
Canon Vixia HV30/HF-M40/HF-M41/HF-G20/Olympus E-PL5.
Tape capture using 6 VCR, TBC-1000, Elite BVP4+, Sony D8 camcorder with TBC.
https://www.facebook.com/BarryAFTT

Well...I'm very pleased to have received a reply from Support.
They reproduced the error and are escalating to troubleshoot it (my words).
Support was clear and friendly and so we shall see if they can issue a patch.
Good for them if they issue an update for an older product version. HP Envy Phoenix/4thGen i7-4770(4@3.4GHz~turbo>3.9)
Nvidia GTX 960(4GB)/16GB DDR3/
Canon Vixia HV30/HF-M40/HF-M41/HF-G20/Olympus E-PL5.
Tape capture using 6 VCR, TBC-1000, Elite BVP4+, Sony D8 camcorder with TBC.
https://www.facebook.com/BarryAFTT

Did you ever find the fix to this? I'm having a similar problem in 365, just for larger files, for me, the 40GB-60GB mark

Quote Did you ever find the fix to this? I'm having a similar problem in 365, just for larger files, for me, the 40GB-60GB mark

What are you capturing, what is your workflow? What codec/container?
You May wish to move this conversation to the 365 forum room, but I'm still interested in hearing your feedback. HP Envy Phoenix/4thGen i7-4770(4@3.4GHz~turbo>3.9)
Nvidia GTX 960(4GB)/16GB DDR3/
Canon Vixia HV30/HF-M40/HF-M41/HF-G20/Olympus E-PL5.
Tape capture using 6 VCR, TBC-1000, Elite BVP4+, Sony D8 camcorder with TBC.
https://www.facebook.com/BarryAFTT

Quote
What are you capturing, what is your workflow? What codec/container?
You May wish to move this conversation to the 365 forum room, but I'm still interested in hearing your feedback.

I posted in the 365 room as well but thought you might be interested that I've encountered this issue on both PD14 and now PD365

Im capturing VHS tapes via a USB dongle DVDezMaker7 to AVI 640x480, and then processing them afterward to Mpeg2. Very stable desktop machine, 24GBram, Ryzen5 5800

On PD14 it was complaining when I was capturing to a USB HDD, so I could only capture to my C: drive (SATA HDD) - i successfully captured about 30 VHS tapes over 100 GB each with that setup.

Then I upgraded my C: drive SATA HDD to a SATA SSD when I started using PD365 and now I get the error on both the USB HDD and C: drive SATA SSD.

I've double checked the power settings its throwing the error well before its set to "turn off the hard drive" in Windows10-64bit

the SATA SSD is set up as NTFS file system, so i'm at a loss which might be triggering this error but looking through threads it seems to have happened to many others without any resolution posted.

I have a NVM drive on order, so that is my next hope.