ChangeIcon MFC Application has stopped working.

Anonymous
2014-09-16T14:01:52+00:00

Since the last set up updateson 16/09/2014 for "Update for WIndows 8.1 for x64-based Systems (KB2976719), (KB2989647) and (KB2984006)", I have been getting an error everytime I start up my computer stating that "changeicon MFC application has stopped working". It states the issue as an "app crash" and that the relevant program is "UMonit64.exe".

I traced to program to its directory and ran all my virus/malware/etc scans on it and they all said it was fine. I then attempted to run the program and it came up with the same error that pops up on startup and a second error message saying it wasn't able to run because "ustor.dll" was missing.

I did a system restore to before I did the windows update and sure enough everything worked fine. I then ran the windows update again after restarting to complete the update the "changeicon MFC application has stopped working" error message started popping up again.

So my questions are:

  1. What is UMonit64.exe/ChangeIcon Application?
  2. Did my windows update cause the issue?
  3. How do I stop the error message from popping up everytime I start up?
  4. Do I need UMonit64.exe? I haven't noticed any programs malfunction when I click the "close program" option when the error message pops up.
  5. If I do need it, should I download the missing DLL file to fix it? If so where would be a safe place to download the replacement dll file?
  6. Anything else I need to know to fix the issue or whether future windows updates will fix it for me and I should just ignore it for the time being.
Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

78 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2014-12-11T02:07:45+00:00

    Seems that  a new update, KB3013769 is also causing this issue as of December 10th. Uninstalled and error went away...

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-12-10T02:48:25+00:00

    Microsoft, what is your response to subsequent comments about uninstalling other updates (in addition to Update (...4006)? 

    Why don't you use your vast resources to determine the cause of this problem and offer a free fix via this community site?  It would seem that there must be hundreds, no, thousands, no, millions of people who are struggling with this issue.  You MUST know what is happening here.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-11-28T20:36:08+00:00

    The only thing I can think of is to look for the other updates I have listed:

    1. KB 2995388
    2. KB 3000850

    If you have them, uninstall and hide them.

    Good Luck!!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-11-28T20:29:04+00:00

    Curious.  Like you, I installed 3000850 and found the error came back and a simple uninstall "fixed" the problem.  This happened on my laptop.  When I installed the same update on my Surface Pro today, I did not get the error on the machine!??  No problems so far but I'll post any problems.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-11-27T23:54:24+00:00

    SOLVED: (already tried clean boot; clean boot it unnecessary)

    1. Go to "Programs and Features." (via right-clicking on what the "Start Menu" used to be.)
    2. Select "View Installed Updates" on left-hand side.
    3. Find "Update for Windows 8.1 for x64-based Systems (KB2984006)."  (It is an optional update.)
    4. Right-click and Uninstall it.
    5. Contact Microsoft and have them pay me for doing their job for them.

    Additionally you and can tell Windows Update to hide it for the rest of your life next time you see it there.

    I used this method to fix the problem as well. Worked like a charm, and I hid the KB2984006 update. Everything was fine, then a few weeks later, this update came out:

    http://support.microsoft.com/kb/3000850

    Note that KB2984006 is still hidden.

    Anyway, 3000850 brought the problem back. I went as far as uninstalling 3000850, and the problem went away again. But 3000850 is a significant update, and I felt I should reapply it and put up with the ChangeIcon MFC error.

    Any ideas how I can fix the error without removing the 3000850 update?

    Thanks,

    Mark

    Was this answer helpful?

    0 comments