Loading...

Knowledge Center


VMDK to IMG conversion stops responding, and displays "Converting image...." indefinitely in the Advanced Threat Defense Manager
Technical Articles ID:   KB90508
Last Modified:  4/19/2018

Environment

McAfee Advanced Threat Defense (ATD) 4.2.2

Problem

You create a VM image in VMware, and start to upload the VMDK image file to convert it to IMG format. But, when you select the VMDK image file and start the conversion process in the ATD Manager, the Manager indefinitely displays: 

Converting image.... 

Cause

The conversion process fails in the ATD backend without updating the process status in the Manager.

Solution

Detection package 4.2.2.180301 addresses this issue. The fix is not cumulative in the following newer detection packages. If automatic update feature is enabled on your ATD, your ATD has already installed the detection package. If the automatic update feature is disabled, or your network does not allow ATD to access the update server, download the detection package, and then manually upload it to the ATD appliance.

McAfee product software, upgrades, maintenance releases, and documentation are available from the Product Downloads site at: http://www.mcafee.com/us/downloads/downloads.aspx.

NOTE: You need a valid Grant Number for access. KB56057 provides additional information about the Product Downloads site, and alternate locations for some products.


To manually upload the detection package:
  1. Log on to the ATD Manager using admin credentials.
  2. Select Manage, Image & Software, Content Update, Detection Pkg.
  3. For Upload File, click Browse and select the detection package.
  4. Click Upload.
FAQs:
How do I handle the browser window that indefinitely shows the progress message?
You can safely close the browser window that indefinitely shows the progress message, and then log on the ATD Manager in a new browser screen.

There are detection packages newer than 4.2.2.180301. I have already installed 4.2.2.180301. Does installing a newer detection package overwrite and erase the fix?
No. Newer detection packages do not touch the file that 4.2.2.180301 addresses. Installing a newer detection package does not break the fix.

I skipped the detection package 4.2.2.180301, and installed a newer one. Does the newer detection package address the problem?
No. Detection packages newer than 4.2.2.180301 do not touch the file that 4.2.2.180301 addresses. If you skip 4.2.2.18030, the affected file remains and causes the issue.

I skipped the detection package 4.2.2.180301, and installed a newer one. How do I install 4.2.2.180301 to my ATD appliance?
Download detection package 4.2.2.180301 and upload it to the appliance as documented above.

Rate this document

Beta Translate with

Select a desired language below to translate this page.

Glossary of Technical Terms


 Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.