Jump to content
Sign in to follow this  
autobotranger

Suspicious scan results "QUICKBATCH".

Recommended Posts

Hello everyone.

Since updating Windows 10 to version 1809 and Eset Nod32 Antivirus to version 12.0.31.0 I've noticed some interesting results in the log after performing a full system scan. I'm fully aware that all results that show up in yellow text is currently in use by the OS or other programs, and should be safe, but these particular entries I'm a little suspicious about due to Eset's description of them:

14511251d1241241d1e14.thumb.png.a0cc987aa039fa6f387ee788ae2e2b75.png

The results I've marked translate from Danish to English as follows: "QUICKBATCH - error - unknown compression method."

What's interesting is that prior to yesterdays Windows 10 patch Tuesday update bringing my OS to version 17763.253, Nod32 only showed 2 of these entries in the scan logs, but now it shows 4 of them. While results shown in yellow text should be safe, it's the classification as QUICKBATCH I'm concerned about https://www.virusradar.com/en/search/all/quickbatch

Are these just harmless Windows 10  system files, hence why Eset doesn't show them in red, or is this something we should take a look at?

Thanks in advance.

 

BUMP* Turns out there was 2 other detections in the same scan log. Sorry for missing them:

123483538_2more.thumb.png.8fb23f9208f8bc9ccb584c7bd7a7a525.png

 

Edited by autobotranger
Missed something.

Share this post


Link to post
Share on other sites

Please upload the files in question to a safe location and provide a download link.

Share this post


Link to post
Share on other sites
5 hours ago, Marcos said:

Please upload the files in question to a safe location and provide a download link.

I've PM'd you the download link for the various files. If they don't work let me know and I'll upload them elsewhere.

Also it would seem that I missed 2 "QUICKBATCH" entries in the prior scan log:

675412966_2more.thumb.png.2ad36d5af9a374c16f30b0671ebc27d4.png

It turns out there is also 2 entries for "QUICKBATCH" for the two Windows10.0-KB4480116x64.cab detections.

Pretty sure that one is from yesterdays patch Tuesday update.

Sorry for missing it in my first post.

Share this post


Link to post
Share on other sites

Hello again. Do we have an update in regards to these "QUICKBATCH" detections?

It's worth noting that I have checked all the files in question on VirusTotal and they all came out green. I have always used HitmanPro to check them and the rest of the PC and it doesn't pick up anything either. 

Thanks in advance.

Share this post


Link to post
Share on other sites
2 hours ago, autobotranger said:

Do we have an update in regards to these "QUICKBATCH" detections?

Not yet. The developer will respond me when he finishes other tasks with higher priority. Looking at one of the files I assume that they were misidentified as generated by QuickBatch but for the final statement we'll need to wait for the developer.

Share this post


Link to post
Share on other sites
1 hour ago, Marcos said:

Not yet. The developer will respond me when he finishes other tasks with higher priority. Looking at one of the files I assume that they were misidentified as generated by QuickBatch but for the final statement we'll need to wait for the developer.

Thanks for the reply. Good to hear that these are being looked at.

Share this post


Link to post
Share on other sites

As I assumed, it appears to be an issue in the unpacker and engine that causes the error message on that file. We are working on a fix. There's no reason to be concerned about since the only negative effect is the error message that is displayed.

Share this post


Link to post
Share on other sites
1 hour ago, Marcos said:

As I assumed, it appears to be an issue in the unpacker and engine that causes the error message on that file. We are working on a fix. There's no reason to be concerned about since the only negative effect is the error message that is displayed.

Ah I see, then it should be fine.  Thank you for the update 😃

Would you like me to let you know if any more of these detections starts to appear in the future scan log for files?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×