ResScan.exe

[tlbitner]

When I close the ResScan program, I get a dialog box that reads "Assertion Failed:True".
Is there an easy fix for this?
Thank you.

[srlevine1]

Programmers use assertion statements to check for certain conditions, one of which is to ensure that a pointer to a file name or shared object is valid.
Without further using the debug routine to provide further details, it is most likely that a file is missing, an object name has been corrupted, or the object is no longer valid.

The issue appears to be a shared pointer to an object (program or file) that does not exist or has been deallocated.

Since it occurs on a program close, it could be a rights and permissions error -- have you attempted to run the program as an administrator?
Did you rename or move any of the data or program files or directories? Are you running multiple programs simultaneously?

If this is a new install, did you install the new program over the existing program without removing the old program first, this can cause file naming/mismatch issues? It is a preferred practice to remove the old program before reinstalling a new version.

Since this is ResScan, your system is likely to be Windows-based, did Microsoft recently update your program which could inadvertently corrupt a C++ redistributable or erase a critical file?

You can check the system files by running Microsoft's system file checker to scan system programs by entering the command sfc /scannow (there is a space between sfc and the forward slash) in a command prompt screen with administrator privileges. This takes a while to run, so be patient. You may also want to check your disk - google check disk for errors windows (enter your version) for a detailed procedure.

You might wish to first back-up your system to preserve its present state, and then remove the ResMed program and then reload the Resmed program to eliminate any missing or corrupted program files. If this appears to remedy the issue, it was probably a missing or corrupted file name being called from a program or an internal inconsistency.

You may also wish to ensure that an uncommanded erasure of files, renaming of directories, or other such system mischief has not occurred.

There are other causes, but a system scan followed by a program reload would be my first attempt at remedying the program.

I am sure that other forum users will have additional ideas.