Thank you all for your timely replies... I did hear back from Smith Micro. Apparently there is a conflict between the executable file and a new Windows update, specifically KB3132372. Smith Micro suggested removing the update, and that seems to have worked.