ResScan?

[AlanE]

I have 2017 32 and 64 installed. No work for me.

[Crimson Nape]

There should be a "R6000" error code associated with the message "Pure virtual function called". Would someone please list the number they are receiving.

[SarcasticDave94]

I can check a bit later. Going to DME for new blower. FWIW on the 2017 edition of VC++, I clicked on one link only and then mine worked.

BTW I just remembered my Windows 10 is Home edition. Not sure if that would cause differences or not.

[Crimson Nape]

Dave,
Also check the version and build number. Here is the easy way:
Press Windows Key + R, type “winver” into the Run dialog, and press Enter.

[AlanE]

Nothing. Yes, I looked in eventvwr too.

[sonicboom]

I recently updated to Windows Creator on top of a machine originally installed with Windows 10.. I'm running ResScan 5.6.0.9419 - no issues.

[Crimson Nape]

So far I can't replicate the error.  I guess that's both good and bad.  I'm beginning to wonder if it's a .NET problem.  In viewing the program folder, I see that it is using the MFC 4.0.  This would be VC++ 2010 and .Net Framework 4.0.  Also, I noticed that the directory contained old Borland C++ libraries (bde and .bpl).   That doesn't mean anything, I just found somewhat odd to be mixing development platforms.

Here is the link for the 32 and 64 full version of .NET Framework 4.0:
https://download.microsoft.com/download/...86_x64.exe

Here's hoping for success.  

[SarcasticDave94]

Dave,
Also check the version and build number.  Here is the easy way:
Press Windows Key + R, type “winver” into the Run dialog, and press Enter.

I have version 1703 (OS Build 15063.540)

ResScan for me is 5.8.0.9556

[Crimson Nape]

Well I'm finally able to produce the error.  I found a Win 10 system that hadn't been updated to the 1703 Creator's Edition.   ResScan 5.8 worked perfectly with version 1607 but after the update to 1703 - Ka-Boom!  I got the Virtual error.  Now to see if I can find a fix.

Red

[SarcasticDave94]

Hey y'all, here's a non-sarcastic monkey wrench. The PC I use is Mom's laptop. I reported that ResScan was successful in opening despite the screen resolution warning and this includes that the error that kills ResScan is not present. Well all that is true, but only on Mom's login profile not my own. I forgot that when I applied the VC++ Redistributable 2017 I was under her login and not mine. My login still has the error and the very same link I used to get VC++ 2017 did a repair on my login but didn't fix it on my acct but it also didn't break it under hers. I'm just leaving it alone I think. I use SleepyHead to post info here anyway.