We use Pegasus 4.80 over a network, several users, nothing that complicated IMHO, although we have been using Pegasus a long time now... Server and clients are mostly Win 10 Pro.
Since updating to 4.80, there have been a very few emails where, if you click on Reply or Forward, Pegasus instantly crashes. Bounces however are no problem.
I've tried the same from several user's accounts and devices, and get the same result, so it's not likely to be an OS issue.
Is it attachments? Some of the emails have attachments, but not all.
Is it the addressee? No, we can email them ordinarily, and even reply to other emails, so it appears to be something that only occurs when the specific odd email is replied to.
In the headers of the emails, I can see some common factors that indicate the sender uses Office365/Outlook, perhaps in conjunction with Exchange. No idea if these are relevant or interesting, but I'll share some if someone thinks it might help.
Finally, the crash usually produces a couple of entries in Event Viewer:
=======
Log Name: Application
Source: Application Error
Date: 01/09/2022 15:07:57
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: SUPPORT14
Description:
Faulting application name: winpm-32.exe, version: 4.8.0.1028, time stamp: 0x61e3dbc2
Faulting module name: winpm-32.exe, version: 4.8.0.1028, time stamp: 0x61e3dbc2
Exception code: 0xc0000409
Fault offset: 0x001c2613
Faulting process ID: 0x2720
Faulting application start time: 0x01d8bd0ec0dac55d
Faulting application path: \Fs2019\Pegasus\Programs\winpm-32.exe
Faulting module path: \Fs2019\Pegasus\Programs\winpm-32.exe
Report ID: 3b33a0e8-c78a-4526-9924-98b0e80b1a25
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>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-09-01T14:07:57.0771079Z" />
<EventRecordID>176559</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>SUPPORT14</Computer>
<Security />
</System>
<EventData>
<Data>winpm-32.exe</Data>
<Data>4.8.0.1028</Data>
<Data>61e3dbc2</Data>
<Data>winpm-32.exe</Data>
<Data>4.8.0.1028</Data>
<Data>61e3dbc2</Data>
<Data>c0000409</Data>
<Data>001c2613</Data>
<Data>2720</Data>
<Data>01d8bd0ec0dac55d</Data>
<Data>\Fs2019\Pegasus\Programs\winpm-32.exe</Data>
<Data>\Fs2019\Pegasus\Programs\winpm-32.exe</Data>
<Data>3b33a0e8-c78a-4526-9924-98b0e80b1a25</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
===========
Log Name: Application
Source: Windows Error Reporting
Date: 01/09/2022 15:08:06
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: SUPPORT14
Description:
Fault bucket 1327807070259735361, type 5
Event Name: BEX
Response: Not available
Cab Id: 0
Problem signature:
P1: winpm-32.exe
P2: 4.8.0.1028
P3: 61e3dbc2
P4: winpm-32.exe
P5: 4.8.0.1028
P6: 61e3dbc2
P7: 001c2613
P8: c0000409
P9: 00000000
P10:
Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C20.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EAF.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4FBA.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4FC8.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5036.tmp.txt
These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_winpm-32.exe_ed53637fe059866abffbf929e62235dbd83b1358_bc21b527_cad656ff-56ba-4e7a-88cc-e82c5cf29495
Analysis symbol:
Rechecking for solution: 0
Report Id: 3b33a0e8-c78a-4526-9924-98b0e80b1a25
Report Status: 268435456
Hashed bucket: c422e79174d111dbd26d517ed1156b41
Cab Guid: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-09-01T14:08:06.4418434Z" />
<EventRecordID>176560</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>SUPPORT14</Computer>
<Security />
</System>
<EventData>
<Data>1327807070259735361</Data>
<Data>5</Data>
<Data>BEX</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>winpm-32.exe</Data>
<Data>4.8.0.1028</Data>
<Data>61e3dbc2</Data>
<Data>winpm-32.exe</Data>
<Data>4.8.0.1028</Data>
<Data>61e3dbc2</Data>
<Data>001c2613</Data>
<Data>c0000409</Data>
<Data>00000000</Data>
<Data>
</Data>
<Data>
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C20.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EAF.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4FBA.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4FC8.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5036.tmp.txt</Data>
<Data>\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_winpm-32.exe_ed53637fe059866abffbf929e62235dbd83b1358_bc21b527_cad656ff-56ba-4e7a-88cc-e82c5cf29495</Data>
<Data>
</Data>
<Data>0</Data>
<Data>3b33a0e8-c78a-4526-9924-98b0e80b1a25</Data>
<Data>268435456</Data>
<Data>c422e79174d111dbd26d517ed1156b41</Data>
<Data>0</Data>
</EventData>
</Event>
===========
Any thoughts/ideas?