At last I got round to updating gpg4win 2.2.0 to 2.2.1 The downloaded file verified ok. Installing on Windows 7-64.
Installation stopped with ‘error opening file for writing’ libksba-8.dll Three options given : retry, skip this file, abort. I retried 3 times then skipped that file.
A few seconds later, same error with scdaemon.exe : 1 retry seemed to be ok this time. And installation completed. Both the ‘troubled’ files were present in C\program files(x86)\gnu\gnupg\ and kleopatra started ok
Just in case, I repeated the download of the gpg4win 2.2.1 and repeated the installation. Exactly the same 2 events occurred and in the same detail.
GPA and Kleopatra seem to work ok. Windows task manager shows the scdaemon.exe running once kleopatra has been started.
What does the file libksba-8.dll do ? And what could be the consequences of the glitch with this file during installation ?
libksba is a CMS and X.509 access library. Afaik it was not changed between 2.2.0 and 2.2.1 so you should experience no problems if it could not be overwritten by the installer.
To better understand your problem you could use something like handle ( http://technet.microsoft.com/en-us/sysinternals/bb896655.aspx ) to figure out which process holds the lock on libksba and scdaemon.
Because if all gpg4win processes are killed, the Installer should be able to write it and scdaemon should be killed during installation when gpg-agent is asked to quit so it is a bit strange that this problem occurs.
Do you use a smartcard or have a smartcard reader attached to your system?
Thank you André for this info. I don’t have any smart card reader. Come to think of it, I’m not sure that all the gpg processes were killed before the installation. I’ll try another install tomorrow - I’ve got to dash off to meetings right now.
I did a re-install immediately after start-up, having checked that no gpg processes (at least that I could recognise) were running. The install killed the dirmngr process and then ran right through without a hitch.
I must have forgotten to check the processes before making the first attempts.