ChangeIcon MFC Application has stopped working.

Question

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.

Answer 1

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

Answer 2

I have uninstalled KB2984006 but still getting the error. Any fix ?

Answer 3

Here is a list of updates (important and optional) that I have found to cause this problem:

1. KB 2984006
2. KB 2995388
3. KB 3000850 (this just installed today, 22 Nov, 2014)

I have uninstalled these updates.  As a previous poster said, once you uninstall them, set them as "hidden" so they won't show up as updates that need to be installed.

Since I don't need these updates to "fix" an issue, there has not been any problems on my computer.  However, what does one do when you need one of their "fixes" and this or any other error comes up?  Does Microsoft review these errors and correct them?  Do I need a previous update before the new ones are installed?  Note: I have applied all updates except the ones listed above.  Can a moderator comment?

Answer 4

Maybe this will help

Problem signature:

  Problem Event Name: APPCRASH

  Application Name: UMonit64.exe

  Application Version: 13.0.0.0

  Application Timestamp: 52007056

  Fault Module Name: ustor.dll

  Fault Module Version: 6.3.9600.17415

  Fault Module Timestamp: 54504b0d

  Exception Code: c0000135

  Exception Offset: 000a36e5

  OS Version: 6.3.9600.2.0.0.768.101

  Locale ID: 1033

  Additional Information 1: 1abe

  Additional Information 2: 1abee00edb3fc1158f9ad6f44f0f6be8

  Additional Information 3: 1abe

  Additional Information 4: 1abee00edb3fc1158f9ad6f44f0f6be8

Answer 5

I am still having the issue after the uninstall, any other fix?