Bugs in Video Studio 19.5.0.35 64 bit Pro

[jch39]

VS was able to play the newly captured video file last night.
Today, VS locked up when I right-moused on the new HD capture file to see properties. Bad manners, I thought.
I restarted VS and tried to play the file in the Preview window got the blue circle, which locked up VS again. I powered down after waiting about 5 minutes.
Restarted VS again, clicked on capture file icon, got error: File does not exist. Tried to relink, discovered Relink window can't see the capture disk (D).
Terminated VS, Rebooted Win10, which found drive D - but when i restarted VS and clicked on capture file I got the nasty blue circle again, which locked up VS again.
After rebooting Win10, discovered that File Explorer gets the nasty blue circle and locks up when i click on the capture file - so now the capture file is corrupt on the D disk....

Now I'm in trouble...

Does this seem like the start of a new bag of bugs?

[aljimenez]

I suspect something wrong with your "capture disk". If this is a USB drive, unplug for a minute or so and plug in back again. If it is not a USB drive, run chkdsk to check the disk for errors.

[Ken Berry]

I do all my captures from camcorder to an external hard USB disk, and have not had the type of problem you mention. The only thing I have ever had to look out for is Windows-related rather than specific to VS, and that is when, after a reboot, Windows assigns a new drive letter to the external drive. This often happens if I have other USB devices connected at the same time. VS will then not be able to find a file (clip or project) on the drive which now bears the old external drive letter. But it usually would bring up a message saying you need to Relink. Then it is just a matter of navigating to the new drive letter and finding the clip. Relinking one clip will then usually automatically relink the rest of the clips in the project.

You can, of course, also use Windows Administrative Tools to assign a drive letter permanently to an external drive.

[jch39]

CHkdsk gave the D: internal drive a clean bill of health but it ran all day and over night to complete.

Prior to running chkdsk, I tried several times to access the capture file with the win10 File Explorer and each time it went into a looong delay. I finally decided the capture file must be corrupt but was able to delete it only by deleting its folder. It also took a iooong time to flush out of the Recycle Bin. Only then did File Explorer settle down and let me browse the rest of the capture disk with usual speed and response time. Weird.

If the capture file was indeed corrupt, it must have gotten so sometime after VS played it for a few minutes in the previous evening....

Will try another capture later.