Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

“Error downloading kickstart file…” appears when installing InterScan Web Security products using an external USB drive

    • Updated:
    • 24 Nov 2016
    • Product/Version:
    • InterScan Web Security Virtual Appliance 5.6
    • Platform:
    • Virtual Appliance N/A

When booting from an external USB drive to install InterScan Web Security Virtual Appliance (IWSVA) or Advanced Reporting and Management for InterScan Web Security Suite (ARM), something similar to the following error message appears:

"Error downloading kickstart file…"

This issue occurs because of Anaconda's inability to obtain the ks.cfg file from the USB CDROM. This may be caused by a timing issue when the external USB drive is detected in conjunction with the drive that is trying to read the location of the ks.cfg.


If you receive this error message, do the following:

  1. Wait for about 30 seconds and then remove or disconnect the USB drive or USB cable of the external drive from the server.
  2. Wait for about 5 seconds and reinsert the USB drive or cable of the external drive into the server's USB port.
  3. Click OK to allow the installation program to continue. This will allow the server to detect the external USB CDROM drive and the installation program should continue.

Please refer to the following documents for further installation instruction for your product:

Alternatively, you can use any of the two methods below to resolve the issue:

Method One

  1. When the error message appears, use Alt + F2, Alt + F3, etc. to switch to another terminal screen.
  2. Review the log messages on the screen and see if there is any information indicating which drive is the external USB drive or USB device that contains the installation media.

    For example, it may be identified as "/dev/sda, /dev/sdb or /dev/sdc".

  3. Switch back to the error message console and then select OK to retry the installation path and enter a new location for the ks.cfg file as identified by the log messages.

    Example: hd:sda:/ks.cfg or hd:sdb:/ks.cfg to replace the original setting cdrom:/ks.cfg and try again

Method Two

  1. If an external CDROM drive is being used, you can also extract the ks.cfg from the installation disk and copy it to a USB flash disk (formatted as FAT32) and retry the installation using the external CDROM with the USB flash disk connected to the server.
  2. When the error message appears, switch to another terminal screen and see which device is representing the USB stick from the log messages.
  3. Once identified, switch back to the installation screen and change the ks.cfg file location from "cdrom:/ks.cfg" to "hd:sda:/ks.cfg" (or hd:sdb:/ks.cfg, etc.).
  4. Retry the installation to see if the installer identifies the ks.cfg on the USB flash disk.
Solution Id:
Did this article help you?

Thank you for your feedback!

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.