Hi All, Just checked and can confirm MS update for .NET framework breaks Mailwasher v7.11.0
Application Error Event ID 1000
Faulting application name: MailWasherPro.exe, version: 2017.7.11.0, time stamp: 0x592493fc
Faulting module name: KERNELBASE.dll, version: 6.1.7601.23807, time stamp: 0x5915f98e
Exception code: 0xe0434352
Fault offset: 0x0000c54f
Faulting process id: 0x520
Faulting application start time: 0x01d2e5e4aaf50c19
Faulting application path: C:\Program Files (x86)\Firetrust\MailWasher\MailWasherPro.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: e8f74883-51d7-11e7-b0af-cc9fff2d14a2
.NET Runtime Event ID 1026
Application: MailWasherPro.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.COMException
at MS.Win32.Penimc.UnsafeNativeMethods.CoCreateInstance(System.Guid ByRef, System.Object, Int32, System.Guid ByRef)
at MS.Win32.Penimc.UnsafeNativeMethods.CreatePimcManager()
at MS.Win32.Penimc.UnsafeNativeMethods..cctor()
Exception Info: System.TypeInitializationException
at MS.Win32.Penimc.UnsafeNativeMethods.CreateResetEvent(IntPtr ByRef)
at System.Windows.Input.PenThreadWorker..ctor()
at System.Windows.Input.PenThreadPool.GetPenThreadForPenContextHelper(System.Windows.Input.PenContext)
at System.Windows.Input.PenThreadPool.GetPenThreadForPenContext(System.Windows.Input.PenContext)
at System.Windows.Input.StylusWisp.WispTabletDeviceCollection.UpdateTabletsImpl()
at System.Windows.Input.StylusWisp.WispTabletDeviceCollection.UpdateTablets()
at System.Windows.Input.StylusWisp.WispTabletDeviceCollection..ctor()
at System.Windows.Input.StylusWisp.WispLogic.get_WispTabletDevices()
at System.Windows.Input.StylusWisp.WispLogic.RegisterHwndForInput(System.Windows.Input.InputManager, System.Windows.PresentationSource)
at System.Windows.Interop.HwndStylusInputProvider..ctor(System.Windows.Interop.HwndSource)
at System.Windows.Interop.HwndSource.Initialize(System.Windows.Interop.HwndSourceParameters)
at System.Windows.Window.CreateSourceWindow(Boolean)
at System.Windows.Window.CreateSourceWindowDuringShow()
at System.Windows.Window.SafeCreateWindowDuringShow()
at System.Windows.Window.ShowHelper(System.Object)
at System.Windows.Window.Show()
at MailWasherPro.Splasher.ShowSplash()
at MailWasherPro.Startup.Main(System.String[])
Mailwasher Broken After Microsoft .NET Framework 4.7 for Windows 7 and Windows Server 2008 R2 for x64 (KB3186497)
- TrustFire
- βeta Tester
- Location: 127.0.0.1
Post
Re: Mailwasher Broken After Microsoft .NET Framework 4.7 for Windows 7 and Windows Server 2008 R2 for x64 (KB3186497)
I'm running the 7.11.0 on Windows 8.1 (.NET Framework 4.7 — as obvious also on my signature) without any issue.
The only difference is that instead of Windows Update, I had used the offline redistributable — you may try it (if you wish.)
The only difference is that instead of Windows Update, I had used the offline redistributable — you may try it (if you wish.)
MailWasher Pro (βeta) | Windows 11 Enterprise LTSC (22H2) | The Bat! Professional (βeta) | Windows 10 Firewall Control (βeta) | ESET Endpoint Antivirus (βeta) | nVIDIA GeForce (GTX 1060) | WebView2 Runtime (118.0.2088.61) | .NET Framework (4.8.1)
- rusticdog
- Firetrust Monkey
Post
Re: Mailwasher Broken After Microsoft .NET Framework 4.7 for Windows 7 and Windows Server 2008 R2 for x64 (KB3186497)
There's a post here too with a user having the same issue with Quicken https://getsatisfaction.com/quickencomm ... 4-7-update
Are you able to start MailWasher if you Run As Administrator ? Assuming you've not uninstalled that update.
Are you able to start MailWasher if you Run As Administrator ? Assuming you've not uninstalled that update.
- excalibre
- Rattled Rabbit
Post
Re: Mailwasher Broken After Microsoft .NET Framework 4.7 for Windows 7 and Windows Server 2008 R2 for x64 (KB3186497)
The .Net update also broke my Corsair link software so guessing MicroTwits , I mean Soft lol screwed something up