New
#51
Windows Mail mshtml.dll crash
-
-
New #52
Okay thanks tk, wish I could see your before and after of what you actually did to the IO settings.
...anyway, interesting 'it seems' that a few of you have the problem and I don't.
..running an i7 here with latest internal GPU not that it matters; you said you have 660Ti
I need to have your setup to test and isolate it, iow, I need to have an issue to track it down.
I even transfered Your .eml to my wifes nVidia 6600GT P4 setup but it opened and displayed
fine there too; that says something.
Let me think about it for a bit. I just got home from a long day.
-
New #53
It's a bit strange for me to see such opinion, but anyway, I will try to explain as many details as possible. First of all, the forum policy forbids to attach the *.eml files, so I had a few options: post the text in the message directly (it's short), attach the text file, attach the zip archive. I decided that attaching the *.txt file is most convenient way, so user should only remove the added .txt extension. If it's not the best choice, then OK, but please give an explanation. I am a new writer here and may not know some details.
Now about the content. This is not a html file from the point of its structure. This is a typical container with html content packed with base64 encoding (as from Booking.com, the case of Quoted Printable encoding may be more easily to fix). Message usually contains two encoded parts: first has text/plain content and second has text/html. In my example, I kept only text/html part. But eventually this file is not important.
This bug can be reproduced more easily without any test files. Follow these steps:
1. Open the Windows Mail, Create Mail.
2. For new message, select the Rich Text (HTML) format in the menu Format.
3. Add any recipient, subject (it doesn't matter) and write a single line, e.g. "Crash test for Windows Mail."
4. Switch to Source view (Source edit should be enabled in the View menu).
5. Find the line like <BODY bgColor=#ffffff> and replace it with <body style="font-family: sans-serif"> (as in the mails from Booking.com)
6. Close the message window; you will be asked whether you want to save changes, press Yes.
7. New message will be placed in the Drafts folder. Try to view it immediately...
How to circumvent this bug. You cannot avoid the crash until Microsoft will have fixed the DLL, but you can try to remove the cause manually.
1. After the crash, run the mail program again and point at the message with problem, then program will show "Windows Mail did not shutdown correctly" in the preview window. But better to switch off the preview (View, Layout, clear "Show preview pane"), this will allow to work with messages without the crash.
2. Save this message (File, Save As...) in *.eml and/or *.html format.
3. Delete the message in original folder and in Deleted Items folder.
4. Format *.html allows to read the mail in any browser, if you need only read the content.
5. It would be better to fix the message in *.eml format, if possible. Open the message in Notepad.
a) Quoted Printable encoding. Find and replace the line like <body style=3D"font-family: sans-serif"> with <body>
b) Base64 encoding. You need to decrypt base64 parts, fix them, encode them back and replace the appropriate parts in the original message. I used Total Commander (Decode file, Encode file options). It creates the files like mime000.bin and mime001.bin, which are in fact text/html files and can be edited with Notepad as I mentioned above. Then TC encodes them to mime000.b64 and mime001.b64, you need to take the encoded parts (text blocks) and insert them in the original body of mail message.
6. Open the message as *.eml and move it to appropriate mail folder (File, Move to Folder...).
I hope this could help somehow :)
-
New #54
Slavic said: How to circumvent this bug. You cannot avoid the crash until Microsoft will have fixed the DLL, but you can try to remove the cause manually.
Thanks for the details Slavic. You got right to the core issue.
WinMail reinstated on Win7 is a workaround. MS does not support WinMail and hasn't for quite a while, the tutorial tries to make that clear to members who are accustomed to WinMail and decide to try to make it work on Win7.
The core issue: MS isn't going to "fix" it - that needs to be amplified.
Thank you for taking the time to explain your experiences with the issue. I'm sure that will help someone if they have the same problem.
-
-
New #55
Hello Slavic, Good Morning,
First of all welcome to the Seven Forums.
Last night I had taken your attachment and just renamed it to crashtest.txt
My reply to you was rushed last night being in a hurry, and I see I misunderstood what you said till I re-read it just now this morning realizing I had misinterpreted what you said, which was to rename crashtest.eml.txt to crashtest.eml ...sorry for that misunderstanding.
Okay yes your crashtest.eml attachment opened for me just fine, when this time I renamed it correctly :)
I also did try your test this moment and created an email just as you outlined, saved it to Drafts, and then went to my Drafts folder and opened it, but my WinMail ''Did Not crash'' ..it opened correctly and displayed just as it was suppose to.
-
New #56
@ tktk88 and others,
I wanted to just mention I run 32 bit Windows 7 not that it matters, however to cover all bases just wanted to put it out there.
Since my client does not crash, for those that use 32 bit I wanted to make sure we are all using the same files within our "C:\Program Files\Windows Mail" folder of WinMail, here is what's in mine for comparison for files properties match. (remember I'm looking in the 32 bit folder)
jpg screenshot attachedLast edited by endeavor; 26 Jan 2014 at 13:02. Reason: smaller kb size
-
New #57
Good idea endeavor. Since I "removed" Winmail a while ago (did not reinstate it) all I can offer is what Win7 has as a base.
I'm Win7 x64, so you get both Pgm files - but..... they are the base.
msoe.dll is what really allows WinMail to run on Win7, that and a number of reg imports and some manual changes to Control Panel Default Programs.
I boxed msoe.ddl on the snips to make it easier. I also sort by version (ascending)
Make sure you're looking at the explorer bar when comparing (one is Program Files, the other is Program Files (x86)
These are directory listings of the BASE WinMail files on win7 x64
-
New #58
Well, I also attach here the screen of my Windows Mail x64 files. I decided to keep the original msoe file, only renamed it to msoe_w7.dll, while the working msoe.dll 6.0.6002.18197 is from Vista SP2. Other details are almost the same like endeavour has. But msoe.dll might be updated later in Vista (not in Windows 7), I cannot check that. If the Vista x64 user with up-to-date system could check these files, it would be nice.
-
New #59
I know Slartybart, thanks
The reason why I posted the properties of the whole folders files, is that since I also have WinMail installed on Windows 8 and because on Windows 8 you change out the 'entire' folder of files with this one; and besides since we know that the problem others are having with the mshtml.dll crash, you know the events that say that, sometimes ends up to be something else involved. In the end it will turn out to be with a simple this or that, and so my detailing seemingly insignificant things is because I've learned in order to get to the bottom of any nit problem you never leave any stone unturned, and is why I detail everything. It's what you don't expect, that is.
If I was experiencing this crash myself on my own setup, you could bet I would restore dated images or file/registry snapshots backwards to find and/or isolate the answer to the current problem, I would succeed, of which I excel at those techniques; but since my WinMail client is working without mishap, I cannot troubleshoot what I cannot see as broken. I can only ask others what do you have installed that I don't, and try to extrapolate the difference.
It's when others start installing different email clients on top of it, and other such softwares, that muddy/complicate up the final investigation of facts which 'may' make it more difficult. My entire installs on my Windows 7 (or 8) are Windows Mail true.
-
New #60
This problem seems to be caused by imbedded links in the offending email. I had a friend whose email caused the crash edit out parts of the message until we discovered that a link caused the crash.
If you have Outlook on your machine you can go to the store folder, locate the message and double click (or "open with") and see the message.
Quote
Related Discussions