Share via

ANSWERED-FIXED "Windows Live Mail has stopped working" WLM 2011 and WLM 2012, on Windows 10 1511, Microsoft acks but cannot fix.

Anonymous
2017-01-01T06:58:48+00:00

On or about December 12, 2016, shortly after doing a windows update, I started getting the following message window,

"Windows Live Mail has stopped working" and  "A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available. [  Close program  ]"

I was using WLM 2011 on that date on Windows 10 1511 (upgraded from Windows 7 46-bit). There were two events during the update which were abnormal, but not unusual:

  1. Had to use the standalone installer to install the updates. (Not unusual for me and many other windows upgrade users).
  2. MS Malicious Software Removal Tool found 4 items and removed them. (Unusual as I am running MalwareBytes Pro and Windows Defender and am cautious user. )

Searching for solutions to the error, I have found many others, including posts in this forum, with the same problem. I have tried:

  • Restoring to an earlier time
    • Restore operation was successful.
    • This did not resolve the problem.
    • I was not able to undo the restore.
  • Repairing Window Live Essentials 2011.
    • I was not able to run the repair from Programs and Features.
  • Installed Windows Live Essential 2012.
    • Installation was uneventful.
    • Did not resolve the problem. "Windows Live Mail has stopped working"
    • Repaired Windows Live Essentials 2012. Did not resolve the problem. "Windows Live Mail has stopped working"
  • De-fragmented Hard-drive overriding this drive does not need to be defragmented message. Did not resolve problem.
  • Ran SFC /scannow to repair missing or corrupted files. 1 .DLL was unable to be copied
  • Contacted Microsoft Support and spent 4 hours plus on telephone and remote control with Microsoft Representative.
    • Briefed representative about manual updates and MS Malicious Software Removal Tool found 4 items and removed them, and my running SFC /scannow with one error, prior to stopping of WLM proper functioning.
      • Representative indicated that problem was probably due to a virus.
      • Representative told me I should not have used standalone installer for updates as I may have installed the incorrect update which might be causing the problem.
    • Representative and elevated support unable to resolve problem.
    • Representative told me the program is corrupted and cannot be fixed or recovered. I asked,' Are you telling me that a Microsoft Software Program is broken and it cannot be fixed? He replied, "yes".

I have not removed my data files for Windows live Mail seek to recover Windows Live Mail, messages, and especially my Contacts. It seems the proper way for me to do this is by exporting from Windows Live Mail which I cannot start.

Any help getting WLM working again would be appreciated.

There are numerous links citing Microsoft saying that WLM will not be supported after Jan 10, 2012. I get the feeling they stopped support a long time ago.

Windows for home | Other | Email and communications

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.

0 comments

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2017-01-04T00:09:18+00:00

    Firedog. I hope this reply is posted chronologically.

    Found a Fix/workaround. Running WLM 2012 in compatibility mode for windows 7 .

     ( Recall I am using . . . Windows 10 1511 (upgraded from Windows 7 64-bit)

    Of course, others getting  "Windows Live Mail has stopped working" when trying to start would set their WLM to run in the compatibility mode for the last windows version they were running.

    The compatibility check would just run until I cancelled it. Then tried it anyway.

    You mentioned KB3205386, which was released on 13 December. This seemed like a good candidate as the cause and I tried to remove it in normal mode and SAFE mode. Was unable to do so (received an error message).

    Running WLM in compatibility mode for WIN 7 circumvents problems caused by the WIN 10 update.

    (Also, recall that I Ran SFC /scannow to repair missing or corrupted files. 1 .DLL was unable to be copied)

    I ran SFC /scannow again and this time Windows Resource Protection found corrupt files and successfully repaired them. 

    I then changed WLM to run in normal mode and it works. I have everything back in WLM, contacts, accounts, messages, everything! So the fix in this case was:

    1. Set WLM to run in the compatibility for the last windows version with which WLM successfully worked.
    2. Open WLM and it should now work.
    3. Run SFC /scannow [start command prompt running as administrator and type SFC /scannow with space before the /
    4. Set WLM to run in the normally for your current windows version i.e., uncheck [ ] run this program in compatibility mode.
    5. Open WLM again and it should now work.

    Thank again for your advice ¡Firedog. Bob

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2017-01-01T17:44:26+00:00

    A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.

    Whenever this happens, a crash report will be generated and written to the event log. It will tell you what's going wrong. To find the crash report,

    1. Press Windows key  + R, type eventvwr and press Enter. This should open Event Viewer.
    2. Expand Windows Logs in the left-hand pane and select Application to see events raised by programs.
    3. In the right-hand Action pane, click Filter current log, then in the Filter Current Log dialogue, select the Error check box and click OK. The list of events in the middle pane should now populate with the most recent hangs and crashes, marked .
    4. In the Source column of this listing, look for Application hang or Application error around the time of the last crash, then click on it to reveal details of the error in the lower pane. Find the one that refers to wlmail.exe, then click on Copy towards the bottom of the Action pane and select Copy details as text.
    5. Paste into your reply here.

    There are numerous links citing Microsoft saying that WLM will not be supported after Jan 10, 2012. I get the feeling they stopped support a long time ago.

    I think you mean 2017, and you're quite right: there has been no support since 2010.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2017-01-02T16:16:29+00:00

    Thank you for your response.

    I sent you 5 event logs for errors occurred every time I tried to start WLM.

    You mentioned, "the problem is triggered by an access violation (0xc0000005) in UIRibbon.dll . . . ." This was in log 1(ONE). 

    Note that log 3(THREE) contains another with the same exception for a different module:

    Faulting module name: UXCore.dll, version: 16.4.3528.331, time stamp: 0x533a3fdc

    Exception code: 0xc0000005

    I was unaware that Exception code: 0xc0000005  was an access violation as in researching the code most of the references to it dealt with XP and WIN 7 and referred to it as having numerous causes - most over my head - like:

    • bad or outdated drivers;
    • processor trying to access unmapped memory
    • the processor does not know how to handle the instructions
    • stack frame corruption
    • You may be using an outdated or corrupted video driver
    • System files on your PC may be corrupt or mismatched with other files
    • You may have a Virus or Malware infection on your PC
    • Some applications or services running on your PC may be causing

    I included other error logs that might be related to the problem only to give you more info to help with your troubleshooting my issue. I wasn't looking for help with Windows Search andMicrosoft Messaging issues I thought they might have some bearing on the WLM issue.

    Regarding your question, "Is there any particular reason why you aren't running the Anniversary Update to Windows 10 (v. 1607)? There were numerous issues with the Anniversary Update including Windows Update not working, antivirus programs stopped working (Symantec Endpoint Protection), Drivers working under 7 and 10 v 1511 not working . . . ) I wanted to make sure I had a stable v.1511 before I went to v.1607).

    You mentioned KB3205386, which was released on 13 December. This seemed like a good candidate as the cause and I tried to remove it in normal mode. Was unable to do so (received an error message). Haven't tried removing it in SAFE MODE.

    At this point I am not sure what to do. It looks like my options are:

    • Go to safe mode and try removing KB3205386  Tried, still got "error, some updates not uninstalled"
    • Try Running WLM  in Compatibility Mode  WORKS (See next post in thread)
    • Installing a commercial registry fixer~~.~~  Not necessary. Resolved
    • Reverting to WIN 7  Not necessary. Resolved
    • Use Thunderbird as my Mail Client (already using it just have to reassemble my contacts)  Not necessary. Resolved

    Thank you again for your assistance.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-01-02T13:17:33+00:00

    Thanks. I think the first one would have been enough! You really need a Windows expert to tell you what these reports reveal; the one thing I notice, though, is that the problem is triggered by an access violation (0xc0000005) in UIRibbon.dll, which is the Windows Ribbon Framework that programs use to generate and handle the command ribbons in their user interfaces. I've no idea why this might be happening, but since this is a UI issue, it would be sensible to check whether your graphics drivers are up to date.

    I see that this version of the library was installed with KB3198586 released on 8 November. Could this match the time you started seeing this fault? Or perhaps KB3205386, which was released on 13 December?

    Is there any particular reason why you aren't running the Anniversary Update to Windows 10 (v. 1607)? 

    PS I'm afraid you'll have to take your Windows Search and Microsoft Messaging questions to more appropriate forums.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2017-01-01T23:16:35+00:00

    Thank you in advance for any assistance you might provide. Yes, I meant 2017 and I was referring to WLM 2012. I am using WIN 10 event viewer so I am giving you what I think you are looking for. Five (5) events are logged when I try to start WLM 2012 I am giving you them in chronological order with odd logs in bold :

    ______________________________________  ONE

    Log Name:      Application

    Source:        Application Error

    Date:          1/1/2017 3:13:15 PM

    Event ID:      1000

    Task Category: (100)

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      Admin-PC

    Description:

    Faulting application name: wlmail.exe, version: 16.4.3528.331, time stamp: 0x533a3fce

    Faulting module name: UIRibbon.dll, version: 10.0.10586.672, time stamp: 0x580ee763

    Exception code: 0xc0000005

    Fault offset: 0x00105200

    Faulting process id: 0x2148

    Faulting application start time: 0x01d26473dd6f49ee

    Faulting application path: C:\Program Files (x86)\Windows Live\Mail\wlmail.exe

    Faulting module path: C:\WINDOWS\system32\UIRibbon.dll

    Report Id: 116d90bc-9be5-4f6c-9986-83cc1444a96a

    Faulting package full name:

    Faulting package-relative application ID:

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

    <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2017-01-01T21:13:15.631873600Z" />

    <EventRecordID>19047</EventRecordID>

    <Channel>Application</Channel>

    <Computer>Admin-PC</Computer>

    <Security />

    </System>

    <EventData>

    <Data>wlmail.exe</Data>

    <Data>16.4.3528.331</Data>

    <Data>533a3fce</Data>

    <Data>UIRibbon.dll</Data>

    <Data>10.0.10586.672</Data>

    <Data>580ee763</Data>

    <Data>c0000005</Data>

    <Data>00105200</Data>

    <Data>2148</Data>

    <Data>01d26473dd6f49ee</Data>

    <Data>C:\Program Files (x86)\Windows Live\Mail\wlmail.exe</Data>

    <Data>C:\WINDOWS\system32\UIRibbon.dll</Data>

    <Data>116d90bc-9be5-4f6c-9986-83cc1444a96a</Data>

    <Data>

    </Data>

    <Data>

    </Data>

    </EventData>

    </Event>

    ___________________________________ TWO

    Log Name:      Application

    Source:        Windows Error Reporting

    Date:          1/1/2017 3:13:23 PM

    Event ID:      1001

    Task Category: None

    Level:         Information

    Keywords:      Classic

    User:          N/A

    Computer:      Admin-PC

    Description:

    Fault bucket , type 0

    Event Name: APPCRASH

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: wlmail.exe

    P2: 16.4.3528.331

    P3: 533a3fce

    P4: UIRibbon.dll

    P5: 10.0.10586.672

    P6: 580ee763

    P7: c0000005

    P8: 00105200

    P9:

    P10:

    Attached files:

    C:\Users\Admin\AppData\Local\Temp\WER93D3.tmp.appcompat.txt

    C:\Users\Admin\AppData\Local\Temp\WER9460.tmp.WERInternalMetadata.xml

    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_wlmail.exe_a920ecab7a3dcd8786d70ef70f2417dc49dfa_36d2d92d_cab_00ee948d\memory.hdmp

    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_wlmail.exe_a920ecab7a3dcd8786d70ef70f2417dc49dfa_36d2d92d_cab_00ee948d\triagedump.dmp

    These files may be available here:

    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_wlmail.exe_a920ecab7a3dcd8786d70ef70f2417dc49dfa_36d2d92d_cab_00ee948d

    Analysis symbol:

    Rechecking for solution: 0

    Report Id: 116d90bc-9be5-4f6c-9986-83cc1444a96a

    Report Status: 4

    Hashed bucket:

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="Windows Error Reporting" />

        <EventID Qualifiers="0">1001</EventID>

        <Level>4</Level>

        <Task>0</Task>

        <Keywords>0x80000000000000</Keywords>

        <TimeCreated SystemTime="2017-01-01T21:13:23.426239100Z" />

        <EventRecordID>19048</EventRecordID>

        <Channel>Application</Channel>

        <Computer>Admin-PC</Computer>

        <Security />

      </System>

      <EventData>

        <Data>

        </Data>

        <Data>0</Data>

        <Data>APPCRASH</Data>

        <Data>Not available</Data>

        <Data>0</Data>

        <Data>wlmail.exe</Data>

        <Data>16.4.3528.331</Data>

        <Data>533a3fce</Data>

        <Data>UIRibbon.dll</Data>

        <Data>10.0.10586.672</Data>

        <Data>580ee763</Data>

        <Data>c0000005</Data>

        <Data>00105200</Data>

        <Data>

        </Data>

        <Data>

        </Data>

        <Data>

    C:\Users\Admin\AppData\Local\Temp\WER93D3.tmp.appcompat.txt

    C:\Users\Admin\AppData\Local\Temp\WER9460.tmp.WERInternalMetadata.xml

    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_wlmail.exe_a920ecab7a3dcd8786d70ef70f2417dc49dfa_36d2d92d_cab_00ee948d\memory.hdmp

    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_wlmail.exe_a920ecab7a3dcd8786d70ef70f2417dc49dfa_36d2d92d_cab_00ee948d\triagedump.dmp</Data>

        <Data>C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_wlmail.exe_a920ecab7a3dcd8786d70ef70f2417dc49dfa_36d2d92d_cab_00ee948d</Data>

        <Data>

        </Data>

        <Data>0</Data>

        <Data>116d90bc-9be5-4f6c-9986-83cc1444a96a</Data>

        <Data>4</Data>

        <Data>

        </Data>

      </EventData>

    </Event>

    _____________________________________ THREE

    Log Name:      Application

    Source:        Application Error

    Date:          1/1/2017 3:13:23 PM

    Event ID:      1000

    Task Category: (100)

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      Admin-PC

    Description:

    Faulting application name: wlmail.exe, version: 16.4.3528.331, time stamp: 0x533a3fce

    Faulting module name: UXCore.dll, version: 16.4.3528.331, time stamp: 0x533a3fdc

    Exception code: 0xc0000005

    Fault offset: 0x0009c7a0

    Faulting process id: 0x2148

    Faulting application start time: 0x01d26473dd6f49ee

    Faulting application path: C:\Program Files (x86)\Windows Live\Mail\wlmail.exe

    Faulting module path: C:\Program Files (x86)\Windows Live\Shared\UXCore.dll

    Report Id: dcce6bae-93fc-4712-ad8d-9de50cf4e810

    Faulting package full name:

    Faulting package-relative application ID:

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

    <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2017-01-01T21:13:23.579392200Z" />

    <EventRecordID>19049</EventRecordID>

    <Channel>Application</Channel>

    <Computer>Admin-PC</Computer>

    <Security />

    </System>

    <EventData>

    <Data>wlmail.exe</Data>

    <Data>16.4.3528.331</Data>

    <Data>533a3fce</Data>

    <Data>UXCore.dll</Data>

    <Data>16.4.3528.331</Data>

    <Data>533a3fdc</Data>

    <Data>c0000005</Data>

    <Data>0009c7a0</Data>

    <Data>2148</Data>

    <Data>01d26473dd6f49ee</Data>

    <Data>C:\Program Files (x86)\Windows Live\Mail\wlmail.exe</Data>

    <Data>C:\Program Files (x86)\Windows Live\Shared\UXCore.dll</Data>

    <Data>dcce6bae-93fc-4712-ad8d-9de50cf4e810</Data>

    <Data>

    </Data>

    <Data>

    </Data>

    </EventData>

    </Event>

    _______________________________________ FOUR

    Log Name:      Application

    Source:        Windows Error Reporting

    Date:          1/1/2017 3:13:24 PM

    Event ID:      1001

    Task Category: None

    Level:         Information

    Keywords:      Classic

    User:          N/A

    Computer:      Admin-PC

    Description:

    Fault bucket 108629490353, type 1

    Event Name: APPCRASH

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: wlmail.exe

    P2: 16.4.3528.331

    P3: 533a3fce

    P4: UIRibbon.dll

    P5: 10.0.10586.672

    P6: 580ee763

    P7: c0000005

    P8: 00105200

    P9:

    P10:

    Attached files:

    C:\Users\Admin\AppData\Local\Temp\WER93D3.tmp.appcompat.txt

    C:\Users\Admin\AppData\Local\Temp\WER9460.tmp.WERInternalMetadata.xml

    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_wlmail.exe_a920ecab7a3dcd8786d70ef70f2417dc49dfa_36d2d92d_cab_00ee948d\memory.hdmp

    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_wlmail.exe_a920ecab7a3dcd8786d70ef70f2417dc49dfa_36d2d92d_cab_00ee948d\triagedump.dmp

    These files may be available here:

    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_wlmail.exe_a920ecab7a3dcd8786d70ef70f2417dc49dfa_36d2d92d_1622b6fa

    Analysis symbol:

    Rechecking for solution: 0

    Report Id: 116d90bc-9be5-4f6c-9986-83cc1444a96a

    Report Status: 0

    Hashed bucket: 382fd839ddf86dfe42a736e948890f3d

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="Windows Error Reporting" />

        <EventID Qualifiers="0">1001</EventID>

        <Level>4</Level>

        <Task>0</Task>

        <Keywords>0x80000000000000</Keywords>

        <TimeCreated SystemTime="2017-01-01T21:13:24.945457600Z" />

        <EventRecordID>19050</EventRecordID>

        <Channel>Application</Channel>

        <Computer>Admin-PC</Computer>

        <Security />

      </System>

      <EventData>

        <Data>108629490353</Data>

        <Data>1</Data>

        <Data>APPCRASH</Data>

        <Data>Not available</Data>

        <Data>0</Data>

        <Data>wlmail.exe</Data>

        <Data>16.4.3528.331</Data>

        <Data>533a3fce</Data>

        <Data>UIRibbon.dll</Data>

        <Data>10.0.10586.672</Data>

        <Data>580ee763</Data>

        <Data>c0000005</Data>

        <Data>00105200</Data>

        <Data>

        </Data>

        <Data>

        </Data>

        <Data>

    C:\Users\Admin\AppData\Local\Temp\WER93D3.tmp.appcompat.txt

    C:\Users\Admin\AppData\Local\Temp\WER9460.tmp.WERInternalMetadata.xml

    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_wlmail.exe_a920ecab7a3dcd8786d70ef70f2417dc49dfa_36d2d92d_cab_00ee948d\memory.hdmp

    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_wlmail.exe_a920ecab7a3dcd8786d70ef70f2417dc49dfa_36d2d92d_cab_00ee948d\triagedump.dmp</Data>

        <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_wlmail.exe_a920ecab7a3dcd8786d70ef70f2417dc49dfa_36d2d92d_1622b6fa</Data>

        <Data>

        </Data>

        <Data>0</Data>

        <Data>116d90bc-9be5-4f6c-9986-83cc1444a96a</Data>

        <Data>0</Data>

        <Data>382fd839ddf86dfe42a736e948890f3d</Data>

      </EventData>

    </Event>

    _______________________________________ FIVE

    Log Name:      Application

    Source:        Windows Error Reporting

    Date:          1/1/2017 3:13:32 PM

    Event ID:      1001

    Task Category: None

    Level:         Information

    Keywords:      Classic

    User:          N/A

    Computer:      Admin-PC

    Description:

    Fault bucket 73208693833, type 1

    Event Name: APPCRASH

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: wlmail.exe

    P2: 16.4.3528.331

    P3: 533a3fce

    P4: UXCore.dll

    P5: 16.4.3528.331

    P6: 533a3fdc

    P7: c0000005

    P8: 0009c7a0

    P9:

    P10:

    Attached files:

    C:\Users\Admin\AppData\Local\Temp\WERB2F2.tmp.WERInternalMetadata.xml

    These files may be available here:

    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_wlmail.exe_4c272f22da8885aef02a396cdee199ddbe6abf8_36d2d92d_115ad649

    Analysis symbol:

    Rechecking for solution: 0

    Report Id: dcce6bae-93fc-4712-ad8d-9de50cf4e810

    Report Status: 0

    Hashed bucket: 17bf7c90f0c13c6ba8fa08b0397e0d63

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

    <System>

    <Provider Name="Windows Error Reporting" />

    <EventID Qualifiers="0">1001</EventID>

    <Level>4</Level>

    <Task>0</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2017-01-01T21:13:32.971550000Z" />

    <EventRecordID>19051</EventRecordID>

    <Channel>Application</Channel>

    <Computer>Admin-PC</Computer>

    <Security />

    </System>

    <EventData>

    <Data>73208693833</Data>

    <Data>1</Data>

    <Data>APPCRASH</Data>

    <Data>Not available</Data>

    <Data>0</Data>

    <Data>wlmail.exe</Data>

    <Data>16.4.3528.331</Data>

    <Data>533a3fce</Data>

    <Data>UXCore.dll</Data>

    <Data>16.4.3528.331</Data>

    <Data>533a3fdc</Data>

    <Data>c0000005</Data>

    <Data>0009c7a0</Data>

    <Data>

    </Data>

    <Data>

    </Data>

    <Data>

    C:\Users\Admin\AppData\Local\Temp\WERB2F2.tmp.WERInternalMetadata.xml</Data>

    <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_wlmail.exe_4c272f22da8885aef02a396cdee199ddbe6abf8_36d2d92d_115ad649</Data>

    <Data>

    </Data>

    <Data>0</Data>

    <Data>dcce6bae-93fc-4712-ad8d-9de50cf4e810</Data>

    <Data>0</Data>

    <Data>17bf7c90f0c13c6ba8fa08b0397e0d63</Data>

    </EventData>

    </Event>

    _____________________ Just Prior to my having problems with WLM there was another WLM event:

    Log Name:      Application

    Source:        Microsoft-Windows-Search

    Date:          12/14/2016 8:13:32 PM

    Event ID:      3037

    Task Category: Gatherer

    Level:         Warning

    Keywords:      Classic

    User:          N/A

    Computer:      Admin-PC

    Description:

    Crawl could not be started on content source <C:[99ae59f3-4a65-4463-b247-d7ae9cbcff74]\Users\Admin\AppData\Local\Microsoft\Windows Live Mail&gt;.

    Context:  Application, SystemIndex Catalog

    Details:

        The URL was already processed during this update. If you received this message while processing alerts, then the alerts are redundant, or else Modify should be used instead of Add.  (HRESULT : 0x80040d0d) (0x80040d0d)

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="Microsoft-Windows-Search" Guid="{CA4E628D-8567-4896-AB6B-835B221F373F}" EventSourceName="Windows Search Service" />

        <EventID Qualifiers="32768">3037</EventID>

        <Version>0</Version>

        <Level>3</Level>

        <Task>3</Task>

        <Opcode>0</Opcode>

        <Keywords>0x80000000000000</Keywords>

        <TimeCreated SystemTime="2016-12-15T02:13:32.123515100Z" />

        <EventRecordID>10326</EventRecordID>

        <Correlation />

        <Execution ProcessID="0" ThreadID="0" />

        <Channel>Application</Channel>

        <Computer>Admin-PC</Computer>

        <Security />

      </System>

      <EventData>

        <Data Name="ExtraInfo">

    Context:  Application, SystemIndex Catalog

    Details:

        The URL was already processed during this update. If you received this message while processing alerts, then the alerts are redundant, or else Modify should be used instead of Add.  (HRESULT : 0x80040d0d) (0x80040d0d)

    </Data>

        <Data Name="URL">C:[99ae59f3-4a65-4463-b247-d7ae9cbcff74]\Users\Admin\AppData\Local\Microsoft\Windows Live Mail&lt;/Data>

      </EventData>

    </Event>

    _________________________________ First event ( 12/15/2016) of WLM (then 2011) not starting below

    Log Name:      Application

    Source:        Application Error

    Date:          12/15/2016 8:59:59 PM

    Event ID:      1000

    Task Category: (100)

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      Admin-PC

    Description:

    Faulting application name: wlmail.exe, version: 15.4.3555.308, time stamp: 0x4f59707e

    Faulting module name: UIRibbon.dll, version: 10.0.10586.672, time stamp: 0x580ee763

    Exception code: 0xc0000005

    Fault offset: 0x00105200

    Faulting process id: 0x2700

    Faulting application start time: 0x01d2574877cfbd61

    Faulting application path: C:\Program Files (x86)\Windows Live\Mail\wlmail.exe

    Faulting module path: C:\WINDOWS\system32\UIRibbon.dll

    Report Id: 095b43e1-935e-4a79-bf15-dd34d9c0f02f

    Faulting package full name:

    Faulting package-relative application ID:

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

    <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2016-12-16T02:59:59.692586000Z" />

    <EventRecordID>10872</EventRecordID>

    <Channel>Application</Channel>

    <Computer>Admin-PC</Computer>

    <Security />

    </System>

    <EventData>

    <Data>wlmail.exe</Data>

    <Data>15.4.3555.308</Data>

    <Data>4f59707e</Data>

    <Data>UIRibbon.dll</Data>

    <Data>10.0.10586.672</Data>

    <Data>580ee763</Data>

    <Data>c0000005</Data>

    <Data>00105200</Data>

    <Data>2700</Data>

    <Data>01d2574877cfbd61</Data>

    <Data>C:\Program Files (x86)\Windows Live\Mail\wlmail.exe</Data>

    <Data>C:\WINDOWS\system32\UIRibbon.dll</Data>

    <Data>095b43e1-935e-4a79-bf15-dd34d9c0f02f</Data>

    <Data>

    </Data>

    <Data>

    </Data>

    </EventData>

    </Event>

    ____________________________

    ALSO getting this errors consistently and frequently

    Log Name:      Application

    Source:        Microsoft-Windows-Immersive-Shell

    Date:          12/15/2016 7:22:40 PM

    Event ID:      5973

    Task Category: (5973)

    Level:         Error

    Keywords:      

    User:          Admin-PC\Admin

    Computer:      Admin-PC

    Description:

    Activation of app Microsoft.Messaging_8wekyb3d8bbwe!ppleae38af2e007f4358a809ac99a64a67c1 failed with error: The application cannot be started. Try reinstalling the application to fix the problem. See the Microsoft-Windows-TWinUI/Operational log for additional information.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="Microsoft-Windows-Immersive-Shell" Guid="{315A8872-923E-4EA2-9889-33CD4754BF64}" />

        <EventID>5973</EventID>

        <Version>0</Version>

        <Level>2</Level>

        <Task>5973</Task>

        <Opcode>0</Opcode>

        <Keywords>0x2000000000000000</Keywords>

        <TimeCreated SystemTime="2016-12-16T01:22:40.229433800Z" />

        <EventRecordID>10855</EventRecordID>

        <Correlation />

        <Execution ProcessID="7104" ThreadID="6408" />

        <Channel>Application</Channel>

        <Computer>Admin-PC</Computer>

        <Security UserID="S-1-5-21-1688672369-560665978-2355779204-1000" />

      </System>

      <EventData>

        <Data Name="AppId">Microsoft.Messaging_8wekyb3d8bbwe!ppleae38af2e007f4358a809ac99a64a67c1</Data>

        <Data Name="ErrorCode">-2147009284</Data>

      </EventData>

    </Event>

    Thank You Again

    Was this answer helpful?

    0 comments