Encountering problem on Server 2012

[NewsArchive]

Hi all,

We've started getting a bunch of support calls regarding server 2012
(and possibly 2008) stating that many of the dll's that should be
replaced are being marked for removal but upon reboot are not being
replaced. If we simply rename the install folder and install fresh
everything works fine.

We are currently not doing code signing and I'm not sure it is even
related, however, has anyone seen anything like this? I verified that
the installer has dll's set to replace every time, so I'm open to
suggestions.

Thank you,
Ken

[NewsArchive]

Ken,

IMO, the following happens. Your installer tries to replace "in-use" DLLs.
Because the files are "locked", Windows queues the files to be replaced at
the next restart/reboot.

BTW, Windows writes the original/target file information to this registry
key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Session
Manager\PendingFileRenameOperations

In this key you can very easily see which files were "locked" during the
file installation process.

At the end of the installation, the setup.exe asks to reboot the server.
Windows (and not your installer) handles the file replacement in this case.

The recommended way in a server environment is to check (before the file
installation process takes place) if all files can be "written" (e.g. "Check
In-use file..." and/or "Check In-use Folder Tree..." functions). This can
help to avoid a reboot.

Friedrich