QuickTimeVRAuthoring.qtx IS IT FALSE POSITIVE? [SOLVED by db 1081]

[enoskype]

QuickTime 7.7.1 (1680.42)

 

 

IObit Malware Fighter

OS: Windows 7

Version: 1.2.0.16

Define Version: 1079

Time Elapsed: 00:22:19

Objects Scanned: 63892

Threats Found: 1

Save Time: 11/16/2011 11:26:02 AM

|Name|Type|Description|ID|

Trojan.Generic, FILE, C:\Program Files\QuickTime\QTSystem\QuickTimeVRAuthoring.qtx, 4104165

 

 

 

VirusTotal Analysis Report

File name: QuickTimeVRAuthoring.qtx

Submission date: 2011-11-16 09:27:44 (UTC)

Current status: finished

Result: 0/ 42 (0.0%)

MD5 : a8046764e94202a255091be4ad0dc6a0

SHA1 : b619f880750347bb75da5117c4b9d471460da162

SHA256: c71e9674a835f2b5aee1063995426cd374b946318a1763ed91216696c9581a0a

 

IObit Cloud

Cloud Scan: SAFE

File Name:quicktimevrauthoring.qtx

File Size : 732 KB (749,568 Bytes)

File MD5 : a8046764e94202a255091be4ad0dc6a0

File SHA1 : b619f880750347bb75da5117c4b9d471460da162

File SHA256 : N/A

File Type:dll

 

Cheers.

[hxin]

QuickTime 7.7.1 (1680.42)

 

 

IObit Malware Fighter

OS: Windows 7

Version: 1.2.0.16

Define Version: 1079

Time Elapsed: 00:22:19

Objects Scanned: 63892

Threats Found: 1

Save Time: 11/16/2011 11:26:02 AM

|Name|Type|Description|ID|

Trojan.Generic, FILE, C:\Program Files\QuickTime\QTSystem\QuickTimeVRAuthoring.qtx, 4104165

 

 

 

VirusTotal Analysis Report

File name: QuickTimeVRAuthoring.qtx

Submission date: 2011-11-16 09:27:44 (UTC)

Current status: finished

Result: 0/ 42 (0.0%)

MD5 : a8046764e94202a255091be4ad0dc6a0

SHA1 : b619f880750347bb75da5117c4b9d471460da162

SHA256: c71e9674a835f2b5aee1063995426cd374b946318a1763ed91216696c9581a0a

 

IObit Cloud

Cloud Scan: SAFE

File Name:quicktimevrauthoring.qtx

File Size : 732 KB (749,568 Bytes)

File MD5 : a8046764e94202a255091be4ad0dc6a0

File SHA1 : b619f880750347bb75da5117c4b9d471460da162

File SHA256 : N/A

File Type:dll

 

Cheers.

 

Dear enoskype

 

After investigation, we have assured that it's a false positive. Sorry for the trouble we have caused to you.

 

We will solve this issue in our later update definition 1081.

 

Thanks for your support.