Stability Issues with the Windows Live Mail 2012 Update – KB3093594

C++ files, 2010, 2012 and 2015 was the order plus reboots when prompted probably help but miss files necessary.

Search Microsoft for C++ redistributable and do both 32 bit (and 64bit when applicable). These are MS files not vendor files and it seems that updates in win 10 os may not restore them as described. Perhaps the WLM patch is no good no matter which date. It continues still in new Win10 builds which you may not be getting yet.

They remain in the backup but never get restored in new build. Perhaps the patch removes them or some other glitch MS cannot figure out.

After copying these files (or any others that might complain) & run the repair.

I can reproduce a fix upon each new build but hey call MS support or an IT troubleshouter with more than 23 years Windows OS experience...

I am receiving the same missing .dll message ...

Which particular one? M Leary's post mentions four different ones ...

The Visual C Runtime files are installed with Windows Essentials, so a repair of the installation may correct the fault. This sort of error is quite frequent - programs bring a VC runtime along and install it, instead of checking whether it was installed already. So it's possible to have a different version from the one Windows Essentials needs, and an error is thrown.

A repair should check that all the files the program needs are present and correct and properly registered where necessary. To do this, close all running programs, then press Windows key  + R, type wlarp and press Enter. In the window that opens, select Repair all Windows Essentials programs:

When it's finished, reboot the computer and try launching Windows Live Mail.

Essentially, upon each new version or build deployed the problem reoccurs and this is how I correct things to date. Been down the road quite a bit.

Your mileage may vary with those 'restore points'. I have not done restores, nor ever intend to waste such time in troubleshooting issues. It solves nothing. You need a support IT person if you need help beyond these posts. The info is posted for anyone searching terms of this problem with search engines.

MS must solve this debacle. They are not answering this community forum post - their preferred support method - besides $$$, the method they really want from users. That costs a lot in time (like I take & Microsoft's too) and that is unfair.

Good Luck. If I find a cure, or the problem gets fixed in a new build it will be posted. Like I said I am an Insider with Fast build deployments set to test new Windows 10 that you eventually get.

I post a Yes/No evaluation on 'Ready for use' each time on the build. So far it is all NO's because of this and many more Win 10 snafus. There's a lot more Insiders who probably are working elsewhere...

I'm not even hardly an expert, but you might try going back to the restore point prior to the update.

Good luck.

Just did. Find an IT person. The instructions and links are best I can give you.