Jump to content

TheSkymanDC

Members
  • Posts

    86
  • Joined

  • Last visited

Posts posted by TheSkymanDC

  1. In this case I believe that pending reboot is indicated by the presence of PendingFileRenamOperations.  When I delete this key I can successfully install ESET. 

    We have seen several cases where programs have left or constantly create this key preventing installation.

    Since they are not Windows OS related why should ESET care.  This is causing a lot of un-necessary work for us.

  2. When attempting to install 7.0.2073.1 I get a failure "There is a pending reboot on the target".  Further investigation show there indeed an PendingFileRename in the registry. (See attached)

    The file is an HP printer configuration XML file that gets created each time I boot the machine.  I have tried deleting the file and the registry entry to no avail.   I have yet to figure out what is creating it or why.

    My question is why does ESET care about an HP configuration file?  Shouldn't it just be ignored?

    Any help would be appreciated.

     

     

    PendingFileRename.png

×
×
  • Create New...