
sys files listed in the registry files below

In the lower pane, open the context (right-click) menu for the left panel for the disk for the EBS volume.Locate the new drive (listed as offline).Launch Administrative Tools > Computer Management > Disk Management.Attach this volume to the second instance (using a different EBS block name), e.g.Detach the C: drive volume on the first instance.Create an image from the current instance (or use a new server instance).You have a running EC2 instance with ESET 6.5.

Then you can safely uninstall ESET 6.x using the Control Panel and install a clean version of ESET 7.x.

So the solution we found that works is to detach the root volume, attach to another running EC2 instance and then delete the three files that are part of ESET HIDS. There is a standalone removal tool provided by ESET by that requires that you run Windows Server in 'safe mode' which is not possible with AWS EC2. The problem is that when you try and uninstall ESET 6.5 from a Windows Server image running under AWS the installation is blocked by the HIDS (intrusion detection) which prevents the installer from removing ESET for security reasons.
