Our support manager sent me a message, commenting that some of our
dlls (like CLARUN.DLL) are mysteriously disappearing. Then we received
some additional information from the customer, where the installer was
run:

>Being curious, I checked Task Manager, and sure enough, I see:
>iesrel.1805.130.exe is still running, under IESADMIN, and is using
>20-25% of the CPU.
>
>It looks to me like your update program never fully closes, and when
>the reboot forces it to close, it removes whatever files it was using.

Note that iesrel.1805.130.exe is the installer. The reboot is an
automatic one that occurs at 4am Sunday morning.

I don't know whether it looks to them like the installer actually
finished. I've asked for clarification on that.

If the installer was "finished", but got hung up before exiting (for
some mysterious reason), would a forced reboot cause any of the
installed files to be deleted?

Does this make any sense? Would it be helpful if I sent you the script
to check it out? How easy is it to turn on logging, so that I can
determine what's happening inside the script?

Mike Hanson
www.boxsoft.net