2017-12-05, 12:05 AM
It may just be a coincidence in timing, but since this issue came up when I updated to v4.0.4, I'm wondering if there is a way I could get my hands on the previous release (I believe i had v3.9.2)? If nothing else, it might at least rule out a problem related to v4.0.4. I have run "SFC /scannow" and found no corrupted files. Short of FDisking the drive and starting from scratch (obviously time consuming), I don't know what else to do at this point.
Dave
Dave