MFC42U.DLL problem || pointer wrap loss

Not very tidy but as if in a position to be undone by whatever did it. The question is who is 'whatever': MS or something else which may spot that you've 'corrected' the situation? Let us hope it was the former and that is an end to the matter.

 

You could have a trojan scan to be sure: Go here.

 

Yippee!,

I see you got your msinfo back. To bad that the particulars will have to remain a mystery. I sure hope it isn't viral in nature. As pointed out, it's system exploratory, clean-ups and system tools that these Nasties like to disable and impersonate. Anything that may enable you to catch, detect, disable or remove these guys are prime targets. (Definitely worth watching with a suspicious eye is the mystical appearence of the smaller duplicate version of msinfo32).

More likely scenario: The fix was accomplished by some combination of the all the things you had previously done to get your msinfo32 function back.

As for the duplicate files: Perhaps running sfc to "replace msinfo32" or running the "refresh msinfo32 install" procedure (provided by June) or the attempted "repair of office" placed a copy of msinfo32.exe in one of the two directories.

Additional steps of the placement of the correct msinfo32 in the correct directory and the removal of mfc42u.dll, the replacement of mfc42.dll, throw into the pot... a possible missed or mistimed reboot (that finally kicked in and did what it was supposed to).....and on and on....all supposition at this point???

I wonder if the blame should not be placed on the borrowed applications botched install and uninstall.

I hope this is going to be the only problem you'll have, as a result, and you can finally put this behind you.

Thanks for updating your post with what I hope is the final outcome and your most welcome. Don't forget to trojan scan as suggested by gammaepsilon. It's better to be safe than sorry and... that put's an end to this ramble fest.

 

On a final note, for those of you who managed to make sense out of my File Verification project then it may be worthwhile to include msinfo32.exe in the MD5Exit key - I have. If the file is changed in any way during a Windows session then you'll be alerted on the next Restart/Shutdown.