This is the mail archive of the
mailing list for the Cygwin project.
Re: Setup 2.693 unable to replace files through reboot
On Apr 7 10:27, Corinna Vinschen wrote:
> On Apr 6 14:24, Christopher Faylor wrote:
> > On Tue, Apr 06, 2010 at 07:23:08PM +0300, Matthias Andree wrote:
> > >Greetings,
> > >
> > >I have observed multiple times, and reproduced, that Setup 2.693
> > >overwriting "in-use files" and rebooting WILL NOT replace those in-use
> > >files. Notably cygwin1.dll.
> > >[...]
> > It works fine on Windows XP. I can't test Windows 7 easily. Corinna
> > do you have time to test this?
> I'll have a look.
I can confirm the problem on W7.
The mechanism in setup apparently works fine at the first glance. After
the call to MoveFileEx, a new registry entry "PendingFileNameOperations"
in the "Session Manager" key has been created, as expected. The content
After reboot, the PendingFileNameOperations entry has disappeared from
the registry, but the Cygwin DLL hasn't changed. I can reproduce the
same issue with any other file on the C: drive. MoveFileEx works, but
the file is not renamed after reboot.
Here's the catch. Per the documentation in
an additional registry value "AllowProtectedRenames" to set, if WFP
protected files have to be replaced on reboot, apparently already
starting with Windows Server 2003 R2, or 2003 SP1. I was surprised that
this covered all files on the C: drive, but looking into the "System
Protection" tab in the "System Properties" dialog shows that the entire
C: drive is under protection by default.
That means, if we want the replacement mechanism to work, we must
also create the "AllowProtectedRenames" value in the "Session Manager"
registry key every time the MoveFileEx is called successfully.
I'll create a patch in the next couple of days if nobody beats me to it.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple