Windows 10: Pure Virtual Function Call Error When Searching

When I try to search a folder I get the following error message;

Runtime Error!
Program: C:\Windows\Explorer.EXE
R6025
-pure virtual function call


and Windows Explorer then crashes??


I have tried several methods including

https://answers.microsoft.com/en-us/windows/forum/windows_7-files/pure-virtual-function-call-error-when-searching/5663f8a3-3a31-4dd2-81bd-8371287b1df2?auth=1

but in vain.


If I in Search Tools deselect "Advanced options" -> "In non-indexed locations" -> "File contents" the problem disappears.

If I select "File contents" the issue reappears.

:)

 

Error: pure virtual function call error in WCESMgr.exe

I also receive the

"Runtime Error!



Program: C:\Program Files\Microsoft ActiveSync\WCESMgr.exe



R6025

- pure virtual function call" message everytime I sync with my HTC-8900 running mobile 6 pro. I've unistalled activesync rebooted computer reinstalled rebooted and still receive error message. I'm running activesync 4.5.0 build 5096

 

Error: pure virtual function call error in WCESMgr.exe

I recently went from Active Sync 4.2 to 4.5 on Windows XP and Mobile 5. Now everytime I synch I take an error and after reporting it I get the following runtime error message from Microsfot C++:





Runtime Error!



Program: C:\Program Files\Microsoft ActiveSync\WCESMgr.exe



R6025

- pure virtual function call



Anyone else seen this? Do I need to backout the 4.5 ActiveSync and go back to 4.2? Dosen't seem very well behaved.



Thanks -ear

 

"runtim error RoxWizardLauncher15.exe, R6025 pure virtual function call".

Hello everybody,

I've some problems using roxio nxt 4 and 5 too due to "runtim error RoxWizardLauncher15.exe R6025 pure virtual function call".

I've tried to unistall/install Roxio tool and Microsoft Visual C++ without solution. On my PC I've WINDOWS 10 that works perfectly without other problems... I don't have any virus on my PC (using three different malware tools: WINDOWS tool, AVIRA and MALWAREBYTES
no malware has been found).

Thanks a lot for possible solution. Regards, Gigi

Note: also using previously Windows vertion (8), same problem was present in same way...