Hello SuperSleeper (and anyone seeing the "Pure virtual function called" bug in ResScan software),
I have seen this issue (on Windows 10) for quite a while now, preventing my use of ResScan - versions 5.9, 6.0, 6.0.2 and earlier. I tried numerous workarounds, including adjusting "Compatibility" settings, clearing the registry, and reinstalling a bunch of MS C Redistributable libraries, all to no avail. Still got the "Pure virtual function called" error any time I tried to start ResScan.
Being "Stayed-at-Home" lately, I thought I'd try again and thought I'd try an experiment. I have an Administrator account on my main machine - and I've heavily "tweaked" the settings and interface to act the way I like it - and wondered whether I might have changed something in that account that led to the problem. I thought I'd see what would happen with a "clean" non-Microsoft account on the same machine. So, I created a new basic User account (Settings > Accounts > Family & other users > Add someone else to this PC > I don't have this person's sign-in information > Add a user without a Microsoft account) with a new username and password.
I just found that if I log into the new account on my Windows machine, ResScan (v. 6.0.2) fires up like a charm - no problem at all and no "Pure virtual function called" pop-up -
. Since this is the very same ResScan installation that fails when started from my other, main account, I surmise that the the problem is likely some tweak or setting that I've made in my main account - if it were something in Windows itself or in the ResScan software itself, I'd expect the error regardless of which account I was using. Unfortunately, with no particularly useful information from either the error message or from exhaustive searches for "Pure virtual function called" information, I just haven't been able to isolate where the problem lay.
In any case, I'm now able to use ResScan in my new user account, and thought this information might provide a useful workaround for others seeing he same issue.
Hope this helps and cheers to all, and thanks for the service you and the members provide with ApneaBoard.com!
SJB