WLM 2012 Started Crashing when Sending Emails

Ok, here's the revised RedistMv.bat file: Download RedistMv.bat

You can run it or just move all of the files dated 11/07/2007 8:00 AM to a safe place until you're certain there aren't any hooks to those files. You'd know fairly quickly - things won't work well that rely on the files, I don't think there will be any issues though ... very few programs of that era were x64 and the misplaced files are from a 2005 msvcrt x64 install.

The batch file creates a folder in your Downloads folder named zMSvcrt2005 and moves the misplaced files on c:\ to that folder. If moving the files from C:\ causes other issues, just COPY everything in %USERPROFILE%\Downloads\zMSvcrt2005 back to C:\

---

Adobe updater: You're not alone! See: search results
Acrobat Help / Update errors | Windows simply states uninstall / reinstall.

A more interesting approach states that different versions of Acrobat and Reader installed on the same machine causes a conflict. Their solution was to uninstall Reader, afterwards Adobe updater worked without the issue reoccurring.

There are a few other references that state - just turn off notifications. I would probably suggest, at a minimum, checking that "Do not show this msg again" box.

There was an issue a while back with Adobe flash options: check for update. For changes to that option to "stick", you had to launch the flash control panel with elevated privileges (Run as Administrator). If there is a control panel for Adobe Standard, you might try configuring it as admin. Turn off auto updates, restart the machine, turn on auto updates.

Personally, I disable, uninstall, or turn off ALL auto updaters and manually check for updates.

If you don't get anywhere with the above suggestions, I suggest a new SevenForums thread for that issue (or wait on Adobe's response)

Bill
.

Reversing the subjects in your last post, Acrobat seems to be working normally since the uninstall/reinstall. I hadn't mentioned it in my post on the Adobe website, but I did find Reader ver 10 also installed. I didn't even know it was there. So I uninstalled it too and left it off. So far, no updater popup messages.

Now back to the redists. I will probably wait until the weekend to move those files. I have a 2nd partition for seldom used files so I'll probably make a folder there and move the files manually.

What about the msdia80.dll file? I've found several forum topics about it being placed there. I looked on my system and found the same filename but different dates & sizes in 2 folders:

C:\Program Files (x86)\Common Files\microsoft shared\VC
C:\Program Files (x86)\Common Files\microsoft shared\VC\amd64

Here's one forum topic: msdia80.dll directly on my other hard drive?

+EDIT

Never mind. I downloaded your bat file and it told me everything I needed to know. Since I also reinstalled the redists on my laptop, I'll try moving those files now and see what happens.

Cool - a twofer!

Adobe updater seems to be behaving after uninstalling Reader - most Adobe products carry the updater with them (Flash, Reader, etc) and it gets installed with the product. There is an apparent updater version conflict - I'm glad it was an easy fix after working the main issue of the thread with you ... I'm not always as lucky as I've been with both issues.

Today is one of those days! This issue required good old-fashioned log reading - finding the log to read took the most time. Once you turned on WLM logging and provided the WER info, the rest was easy (and somewhat of an educated guess). We circled around this fairly early, but no system dump was produced (FYI-I'm no dump reader). To be honest, there wasn't much left that could cause the issue (you ran all of the repair options for WLM and the system). But the log and WER info pointed to msvcrt OR .NET (a wrapper to 'c' calls).

Why or how the redists became 'corrupted' is beyond the scope of a trouble shooting forum - I take the approach "If I can help you fix an issue, great! Just don't ask me to do forensic analysis on the cause." Many times, the cause is discovered during the troubleshooting session, but not in this case - I'm stumped as to why or how. If pressed, I'd probably point my finger at AdBlock Plus.

Re: redist files on C:\ - I think you answered your own concern. The difference in A Guy (Bill)'s response in the link you posted is that the files belong in
C:\Program Files (x86)\Common Files\microsoft shared\VC\amd64
as they are on your system.

That threw me too in the beginning - the reference documents aren't clear, so I just went with where the install placed the files. It was early in reference to x64 apps, so MS decided (I guess) to put the x64 in the x86 program files in a VC\amd64 folder. Normally on Windows x64 machines,
x64 programs go in the %SystemDrive%\Program Files hierarchy and
x86 programs go in the %SystemDrive%\Program Files (x86) hierarchy.

You can always mark a thread solved or unsolved - just letting you know that you can always come back to this thread if the beast rears it's ugly head again. Although, it's often better to start a new thread - this makes it easier for all members to follow and offer suggestions. I don't expect any further complications with regards to this issue and WLM, but ... you never know.

'til next week then.

Bill
.

You did all of the heavy lifting, I was but a guide. Your wife was a real trooper through all of our troubleshooting - I never heard one complaint the entire time.

Consider this my gift to you and yours. I already opened my gifts from you - thanks for the +rep and for marking the thread solved.

Bill

---

Merry Christmas
~ and ~
Happy New Year!