Why does a Retry work for booting up error "1Password couldn't complete its update" / Error: 5-Perm.
As suggested in another forum answer, I just added an exclusion in Windows Security for %LOCALAPPDATA%\1Password. (it resulted in a full path with my user name included)
But since this common bootup error is cleared when I click Retry button, isn't this a timing conflict with the installer? Or does my manual Retry have a different process account since I was the one clicking the button.
I see today in windows_starter_rCURRENT.log many entries like these:
INFO 2024-11-14T06:59:08.651+00:00 main(ThreadId(1)) [1P:op-windows-starter\src\transaction.rs:133] renaming C:\Users<redacted-username>\AppData\Local\1Password\app to C:\Users<redacted-username>\AppData\Local\1Password\previous
ERROR 2024-11-14T06:59:08.668+00:00 ThreadId(8) [1P:foundation\op-install\src\windows\mod.rs:95] Error Win32(0x00000005): Access is denied.__
(I was blocked by the forum from attaching the log file having .log extension.)
I have added the exclusion, but I am confused about why that would work in this case.
The app now claims to be up to date now, since my manual retry didn't result in an error.
1Password for Windows 8.10.52 81052025 is what I was updated TO. Log says Updating from 81046026 to 81052025
Windows 10 Home 22H2
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Win 10 Home 22H2
Browser: Chrome