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.
ChangeIcon MFC Application has stopped working.
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:
- What is UMonit64.exe/ChangeIcon Application?
- Did my windows update cause the issue?
- How do I stop the error message from popping up everytime I start up?
- 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.
- 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?
- 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.
78 answers
Sort by: Oldest
-
Anonymous
2014-11-28T20:29:04+00:00 -
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:
- KB 2995388
- KB 3000850
If you have them, uninstall and hide them.
Good Luck!!
-
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.
-
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...
-
Anonymous
2014-12-11T04:38:46+00:00 FYI, had the problem, removed aforementioned update (...4006), appears problem solved. Apparently, the update(s) are creating the problem and removing them solves the problem.
My personal thanks to all who persevered and shared the solution.