urist

I'm seeing the same error when upgrading from 4.5.12011 to 4.5.12015 under control of ERA 5.1.34.0 on all my Windows Server 2003, 2008 and 2008R2 VMs. Running the upgrade by hand has been successful on 2008 and 2008R2, but on my sole remaining 2003 server it broke things and forced me to restart in safe mode and use the ESET Uninstaller. Upgrading my workstations from EES 4.0.2126 to 5.0.2214 and from 5.0.2214 to 5.0.2225 has generally been working normally. I've seen one (7,3), one (7,-112), two broken clients that needed safe mode & the ESET Uninstaller and two clients that ERAS mistakenly thought were new after the upgrade, but the failure rate is not unusual and I doubt it's related to this problem. I haven't filed a support request on this since it looks like ESET is already aware of the problem, but if it'd be useful, I should be able to do so.