Jump to content
JeffB

Enpass Password Manager Crashing on newest 17134.81

Recommended Posts

After today's update to April 2018 (17134.81) Enpass PM stops working regularly without any interactions.

 

 

Share this post


Link to post
Share on other sites

Enpass was updated on 22/5 with no problems the following days.

This morning Cumulative Update W10 1803 KB4103729 was installed on my PC. My guess is that it's related to this.

Share this post


Link to post
Share on other sites
9 hours ago, JeffB said:

Enpass PM stops working regularly without any interactions.

Yep, crashes out of the blue.

Really annoying, no let's call this blocking!

Share this post


Link to post
Share on other sites

I just keep feeding the information queue.

Enpass now really crashes a lot. That is with or without having entered the master password.

Share this post


Link to post
Share on other sites

Hey @StephanP

Sorry for the mess you're going through. I can only wonder how annoying this must be.

We're looking into this issue as a high priority. It'd be a great help if you can try installing the traditional desktop version of Enpass from our website and let me know if the same happens there too.

Your cooperation is appreciated.

  • Like 1

Share this post


Link to post
Share on other sites

Desktop version 5.6.9 now installed. Wait and see.....

Just to avoid possible conflicts: UWP version uninstalled

Edited by StephanP

Share this post


Link to post
Share on other sites

1 more user seeing the same issue of 5.6.17 (5428) crashing with no interaction, shortly after starting the app. Running on latest Windows 10 cumulative update.

image.png.f64ba45befcc3a50203f8c481cc99454.png

 

image.png.350b176b7cf6bfcab3a2d79d4b8d267b.png

Share this post


Link to post
Share on other sites

+1 

I woke up this morning to this (below):

Like others, had also just recently installed KB4100403 (https://support.microsoft.com/en-au/help/4100403/windows-10-update-kb4100403) and rebooted about 8 hours prior. All the crashes occurred with zero interaction.

Enpass 5.6.17 (5428) Windows Desktop from Windows Store
Windows 10 x64 1803 (17134.81)

Hopefully the 5.6.9 build mentioned earlier in this thread solves the issue and can be pushed through the Microsoft (Windows) Store A.S.A.P.!

Enpass_Crash_2018-05-25_09-00-34.jpg

Edited by Anthony

Share this post


Link to post
Share on other sites

Interestingly, the problem is NOT occurring on the latest RS5 Insider build released today (17677). Something with the latest update for 17134.81.

Share this post


Link to post
Share on other sites
On 5/25/2018 at 1:07 AM, Anthony said:

+1 

I woke up this morning to this (below):

Like others, had also just recently installed KB4100403 (https://support.microsoft.com/en-au/help/4100403/windows-10-update-kb4100403) and rebooted about 8 hours prior. All the crashes occurred with zero interaction.

Enpass 5.6.17 (5428) Windows Desktop from Windows Store
Windows 10 x64 1803 (17134.81)

Hopefully the 5.6.9 build mentioned earlier in this thread solves the issue and can be pushed through the Microsoft (Windows) Store A.S.A.P.!

Enpass_Crash_2018-05-25_09-00-34.jpg

Hello,

I've got the same problem.

And the same amount of error popups...

I'll try to unistall the windows store version to install the one from the web site.

Share this post


Link to post
Share on other sites

Same issue here with latest version on Windows 10 1803 on latest update.

How it crashes is also inconsistent. Sometimes it outright closes and crash with the message, and sometimes message just pops up with the program window unaffected. I can just put the error message to the side and continue using the program without any issue, but as soon as I click on "OK" button on the error message the whole program closes itself. 

Share this post


Link to post
Share on other sites

Hey guys,

Sorry for the trouble you are going through.

On further investigating the issue we concluded that the crashes were prominent when using Enpass with " Windows 10 x64 1803 (17134.81)". So please update the latest preview OS build(17677) or either use a stable version of OS and let me know if the problem persists. 

Thanks.

Share this post


Link to post
Share on other sites
1 hour ago, Anshu kumar said:

Hey guys,

Sorry for the trouble you are going through.

On further investigating the issue we concluded that the crashes were prominent when using Enpass with " Windows 10 x64 1803 (17134.81)". So please update the latest preview OS build(17677) or either use a stable version of OS and let me know if the problem persists. 

Thanks.

Hello,

You know that the build you are refering is the laster stable build for pulic ? I'm not an insider, and I have this version too :

2062440430_2018-05-3014_29_56.thumb.png.1ccd944dc284b21bcc4db0f0c0ce76fd.png

 

So when you suggest us to use a stable version of windows, you want us to go back to a previous version ??? Or to use a preview version as an insider ?


Do you intend to fix that bug with the lastest stable version of windows 10 ?

Because just saying to use a different build of windows isn't helping... nore insinuating that Windows 10 x64 1803 (17134.81) isn't a stable build !

 

Your answer is starting to make me regret using EnPass and buying the iOS version ... 
Knowing that we are still waiting for the new version that was to arrive at the end of May ...

Quote

 Well, we admit there’s been a delay from our side but we assure you that all our team is burning the candles from both ends for Enpass 6 and we believe that at the same development-pace, the beta version would be available by the end of May 2018.

https://www.enpass.io/blog/new-avatar-of-enpass-is-on-the-way/

 

Share this post


Link to post
Share on other sites
3 hours ago, Anshu kumar said:

Hey guys,

Sorry for the trouble you are going through.

On further investigating the issue we concluded that the crashes were prominent when using Enpass with " Windows 10 x64 1803 (17134.81)". So please update the latest preview OS build(17677) or either use a stable version of OS and let me know if the problem persists. 

Thanks.

Hi. 17134.81 _IS_ the latest stable version of Windows 10 1803 with the 2018-05 updates. I hope you can get this fixed ASAP. The frequent crashes are very inconvenient.

Share this post


Link to post
Share on other sites

The issue continues, even after I've re-installed the enpass app, and made sure I'm on the latest stable build available from Windows.

OS Name    Microsoft Windows 10 Pro
Version    10.0.17134 Build 17134

Windows install is 64-bit.
 

Share this post


Link to post
Share on other sites

An observation that may help: If the Enpass Password Manager is not closed, it doesn't seem to crash. I will report if that is not totally true. And there is no going back and I don't want to move to an Insider build on my production machine. Thanks

Edited by JeffB

Share this post


Link to post
Share on other sites

Well, leaving the app running is not a total solution. It took longer than usual, but eventually stopped working. I hope that a solution can be found, or another update corrects the problem. 

Share this post


Link to post
Share on other sites

Now seeing same enpass desktop crashing on a dell XPS 13 9360 laptop running latest update of Window 10 Home 64-bit

My prior report of crashing was on a Lenovo T480 laptop running latest version of Windows 10 Pro.

PLEASE ACKNOWLEDGE AND ADDRESS THIS CRITICAL ENPASS WINDOWS DESKTOP ISSUE! ! ! !

Version details on the dell XPS 13  showing the crashing issue:

OS Name    Microsoft Windows 10 Home
Version    10.0.17134 Build 17134

Enpass version:

image.png.cc27464c28c1206b11ec9f1ad1a4fa72.png

 

Share this post


Link to post
Share on other sites

It's been crashing on my since the most recent update (pushed via the bridged win32 Windows Store app) within about 10 seconds of launch. It appears that, perhaps, disabling password sync via webdav/owncloud prevents the crash. Can anyone else verify?

Edited by jonesy16

Share this post


Link to post
Share on other sites

I'm seeing same problem. Although I have seen it at various times,  I notice it happens most consistently as I come out of hibernation. 

Don't know if this helps but windows event viewer logs show following. You probably already have all this or it contains nothing terribly useful but thought I would post just in case.

>>>>Error: 

Faulting application name: backgroundTaskHost.exe, version: 10.0.17134.1, time stamp: 0xb3ceae44
Faulting module name: mrt100_app.dll_unloaded, version: 1.4.24201.0, time stamp: 0x574e637a
Exception code: 0xc0000005
Fault offset: 0x0000e280
Faulting process id: 0x30b8
Faulting application start time: 0x01d3fb67189bc984
Faulting application path: C:\WINDOWS\SysWOW64\backgroundTaskHost.exe
Faulting module path: mrt100_app.dll
Report Id: 6dd35ef6-3589-4fa8-9b86-d944adb8d896
Faulting package full name: SinewSoftwareSystems.EnpassPasswordManager_5.6.17.0_x86__fwdy0m65qb6h2
Faulting package-relative application ID: App

>>>>Informational:

Fault bucket 2046171178654221820, type 5
Event Name: MoBEX
Response: Not available
Cab Id: 0

Problem signature:
P1: SinewSoftwareSystems.EnpassPasswordManager_5.6.17.0_x86__fwdy0m65qb6h2
P2: praid:App
P3: 10.0.17134.1
P4: b3ceae44
P5: mrt100_app.dll_unloaded
P6: 1.4.24201.0
P7: 574e637a
P8: 0000e280
P9: c0000005
P10: 00000008

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5062.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER513E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5268.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER52B4.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER52D4.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_SinewSoftwareSys_d9d8c6439e94f9265c98157998b8108e3f8c44_50057889_0ed858af

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6dd35ef6-3589-4fa8-9b86-d944adb8d896
Report Status: 268566528
Hashed bucket: 4fb56c0f8f39430b5c6575d88d53c5fc
Cab Guid: 0

>>>>   The above mentioned file contains the following: 

Version=1
EventType=MoBEX
EventTime=131725292338978354
ReportType=2
Consent=1
UploadTime=131725292345693264
ReportStatus=268566528
ReportIdentifier=1f592281-08ef-4ab7-a582-23f395fc02ef
IntegratorReportIdentifier=6dd35ef6-3589-4fa8-9b86-d944adb8d896
Wow64Host=34404
Wow64Guest=332
NsAppName=praid:App
OriginalFilename=backgroundTaskHost.exe
AppSessionGuid=000030b8-0001-0006-84c9-9b1867fbd301
TargetAppId=U:SinewSoftwareSystems.EnpassPasswordManager_5.6.17.0_x86__fwdy0m65qb6h2!App
TargetAppVer=5.6.17.0_x86_!2065//08//05:02:58:12!94bb!backgroundTaskHost.exe
BootId=4294967295
ServiceSplit=8
TargetAsId=246
IsFatal=1
Response.BucketId=4fb56c0f8f39430b5c6575d88d53c5fc
Response.BucketTable=5
Response.LegacyBucketId=2046171178654221820
Response.type=4
Sig[0].Name=Package Full Name
Sig[0].Value=SinewSoftwareSystems.EnpassPasswordManager_5.6.17.0_x86__fwdy0m65qb6h2
Sig[1].Name=Application Name
Sig[1].Value=praid:App
Sig[2].Name=Application Version
Sig[2].Value=10.0.17134.1
Sig[3].Name=Application Timestamp
Sig[3].Value=b3ceae44
Sig[4].Name=Fault Module Name
Sig[4].Value=mrt100_app.dll_unloaded
Sig[5].Name=Fault Module Version
Sig[5].Value=1.4.24201.0
Sig[6].Name=Fault Module Timestamp
Sig[6].Value=574e637a
Sig[7].Name=Exception Offset
Sig[7].Value=0000e280
Sig[8].Name=Exception Code
Sig[8].Value=c0000005
Sig[9].Name=Exception Data
Sig[9].Value=00000008
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.17134.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=2beb
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=2beba6fb4680d73a8c78ca7c24ccdb46
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=629c
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=629cfd28d622d588b693be8fe402a797
UI[2]=C:\WINDOWS\SysWOW64\backgroundTaskHost.exe
LoadedModule[0]=C:\WINDOWS\SysWOW64\backgroundTaskHost.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[4]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[5]=C:\WINDOWS\System32\combase.dll
LoadedModule[6]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[7]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[8]=C:\WINDOWS\System32\SspiCli.dll
LoadedModule[9]=C:\WINDOWS\System32\CRYPTBASE.dll
LoadedModule[10]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[11]=C:\WINDOWS\System32\sechost.dll
LoadedModule[12]=C:\WINDOWS\System32\kernel.appcore.dll
LoadedModule[13]=C:\Windows\System32\twinapi.appcore.dll
LoadedModule[14]=C:\WINDOWS\System32\RMCLIENT.dll
LoadedModule[15]=C:\WINDOWS\System32\shcore.dll
LoadedModule[16]=C:\WINDOWS\System32\user32.dll
LoadedModule[17]=C:\WINDOWS\System32\win32u.dll
LoadedModule[18]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[19]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[20]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[21]=C:\WINDOWS\System32\IMM32.DLL
LoadedModule[22]=C:\WINDOWS\SYSTEM32\mrmcorer.dll
LoadedModule[23]=C:\WINDOWS\System32\OLEAUT32.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=17134
OsInfo[3].Key=ubr
OsInfo[3].Value=81
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1033
OsInfo[7].Key=geoid
OsInfo[7].Value=244
OsInfo[8].Key=sku
OsInfo[8].Value=101
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=768
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=11497
OsInfo[15].Key=osinsty
OsInfo[15].Value=1
OsInfo[16].Key=iever
OsInfo[16].Value=11.48.17134.0-11.0.65
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=8075
OsInfo[19].Key=svolsz
OsInfo[19].Value=930
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=180410
OsInfo[22].Key=bldtm
OsInfo[22].Value=1804
OsInfo[23].Key=bldbrch
OsInfo[23].Value=rs4_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.17134.81.amd64fre.rs4_release.180410-1804
OsInfo[30].Key=buildflightid
OsInfo[30].Value=7B3F085B-AF94-4576-9A9C-9A5E41CD1FC9.1
OsInfo[31].Key=edition
OsInfo[31].Value=Core
OsInfo[32].Key=ring
OsInfo[33].Key=expid
OsInfo[34].Key=containerid
OsInfo[35].Key=containertype
OsInfo[36].Key=edu
OsInfo[36].Value=0
FriendlyEventName=Stopped working
ConsentKey=MoBEX
AppName=Background Task Host
AppPath=C:\WINDOWS\SysWOW64\backgroundTaskHost.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=EFF2933CBEFDC9C707A7B465DFD0EBCE
MetadataHash=1046433047

 

Running: Windows 10 x64 1803 (17134.81),  Enpass 5.6.17 (5428)

Share this post


Link to post
Share on other sites

Come on Enpass team - your handling of this issue is pathetic. Surely it is not hard for you to look up a build number of Windows and see that it is a release build and not a preview build. So many reports of this issue here and on your Twitter feed and yet the ONLY feedback you have given is "Try uninstalling Store app and install MSI version from Enpass website".

Pick up your game guys!

Share this post


Link to post
Share on other sites

In a post on the Windows 10 Universal app thread, someone suggested disabling the Edge extension as a fix ... so far that seems to be working for me.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×