System.DllNotFoundException
1Password (Windows) Version 7.2.617, clean installation using a fresh copy of the setup executable from the 1 Password website.
Launching the application causes an immediate crash, no user interface is displayed.
From Event Viewer:
`Application: 1Password.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.DllNotFoundException
at AgileBits.OnePassword.Native.SetCurrentLanguage(System.String)
at AgileBits.OnePassword.StringsManager.set_Locale(System.String)
at AgileBits.OnePassword.StringsManager..ctor()
at AgileBits.OnePassword.The..cctor()
Exception Info: System.TypeInitializationException
at AgileBits.OnePassword.The.get_Console()
at AgileBits.OnePassword.App.CurrentDomain_UnhandledException(System.Object, System.UnhandledExceptionEventArgs)
`
1Password Version: 7.2.617
Extension Version: Not Provided
OS Version: Windows 10.0.17134 Build 17134
Sync Type: Not Provided
Referrer: forum-search:System.DllNotFoundException
Comments
-
Attempted (re)installing the application, as well as deleting the %appdatalocal%/1Password directory before re-installing with no affect.
0 -
I actually can't download that version of the installer (or any 7.3.x version from the release notes page for that matter).
I receive an error "Windows cannot access the specified device, path or file. You may not have the appropriate permissions to access the item." when attempting to open the installer.
And "You require permission from Everyone to make changes to this file" when attempting to move the installer.
Thanks for the quick response.
0 -
Following on from this, it appears that the access permissions for "1password.dll" are corrupt. Immediately upon loading any version of the file anywhere on the computer renders it un-readable.
I have even tried copying the DLL from a known good working PC onto the desktop of the non-working Windows PC. As soon as the DLL touches the non-working PC it cannot be read ... I'm unsure what is incorrect with the permissions as of yet. This sounds like an AV issue, but the problem persists when in safe mode with AV software disabled.
0