IP Library Granted Patent US 12,244,610
Granted Patent B2
US 12,244,610 · App. 18/403,402 · Granted Mar 4, 2025

Method to improve anti-malware scan responsiveness and effectiveness using user symptoms feedback

Inventors: Ritesh Kumar (Santa Clara, CA); German Lancioni (Cordoba, AR)
Assignee: McAfee, LLC
H04L63/14G06F3/04847G06F16/285G06F21/554G06F21/56
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,244,610
App. No.
18/403,402
Granted
Mar 4, 2025
Kind
B2
Abstract

Apparatus, systems, articles of manufacture, and methods for improving anti-malware scan responsiveness and effectiveness using user symptoms feedback are disclosed. An example method includes detecting a performance issue on a computing device, presenting a user interface on a display of the computing device requesting user feedback regarding the performance issue, and synthesizing user input related to the performance issue to identify, on the computing device, a scan parameter associated with the performance issue. The example method further includes, in response to failing to identify the scan parameter on the computing device, transmitting the user input to a symptom analysis server to identify the scan parameter based on anti-malware scans from other computing devices, and, in response to determining the scan parameter, performing a targeted anti-malware scan on the computing device.

Claims (32)

1. An apparatus comprising:

interface circuitry;

machine-readable instructions; and

at least one processor circuit to be programmed by the machine-readable instructions to at least:

identify a symptom associated with a performance issue on a computing device based on input to the computing device, the input corresponding to highlighting an area of a display associated with the performance issue;

identify a portion of files on the computing device for a targeted anti-malware scan, the portion of files identified based on positive results of malware scans from other computing devices that experienced the symptom; and

trigger the targeted anti-malware scan of the computing device based on the portion of files.

2. The apparatus of claim 1 , wherein the positive results include results from one or more of the malware scans that addressed the performance issue.

3. The apparatus of claim 1 , wherein the input is first input, and wherein one or more of the at least one processor circuit is to determine whether the targeted anti-malware scan addressed the performance issue based on second input to the computing device.

4. The apparatus of claim 3 , wherein one or more of the at least one processor circuit is to, in response to determining that the targeted anti-malware scan did not address the performance issue, trigger a full anti-malware scan of the computing device.

5. The apparatus of claim 3 , wherein one or more of the at least one processor circuit is to, in response to determining that the targeted anti-malware scan did not address the performance issue, provide results of the targeted anti-malware scan to a third party.

6. The apparatus of claim 1 , wherein one or more of the at least one processor circuit is to identify the portion of files based on a scan parameter received from a symptom analysis server.

7. The apparatus of claim 6 , wherein one or more of the at least one processor circuit is to provide results of the targeted anti-malware scan to the symptom analysis server.

8. At least one non-transitory machine-readable medium comprising machine-readable instructions to cause at least one processor circuit to at least:

identify a symptom associated with a performance metric on a computing device based on input to the computing device, the input corresponding to highlighting an area of a display associated with the performance metric;

identify a portion of files on the computing device for a targeted anti-malware scan, the portion of files identified based on affirmative results of malware scans from other computing devices that experienced the symptom; and

initiate the targeted anti-malware scan of the computing device based on the portion of files.

9. The at least one non-transitory machine-readable medium of claim 8 , wherein the affirmative results include results from one or more of the malware scans that remediated the performance metric.

10. The at least one non-transitory machine-readable medium of claim 8 , wherein the input is a first input, and wherein the machine-readable instructions are to cause one or more of the at least one processor circuit to determine whether the targeted anti-malware scan remediated the performance metric based on second input to the computing device.

11. The at least one non-transitory machine-readable medium of claim 10 , wherein the machine-readable instructions are to cause one or more of the at least one processor circuit to, in response to determining that the targeted anti-malware scan did not remediate the performance metric, initiate a full anti-malware scan of the computing device.

12. The at least one non-transitory machine-readable medium of claim 10 , wherein the machine-readable instructions are to cause one or more of the at least one processor circuit to, in response to determining that the targeted anti-malware scan did not remediate the performance metric, provide results of the targeted anti-malware scan to a third party.

13. The at least one non-transitory machine-readable medium of claim 8 , wherein the machine-readable instructions are to cause one or more of the at least one processor circuit to identify the portion of files based on a scan parameter received from a symptom analysis server.

14. The at least one non-transitory machine-readable medium of claim 13 , wherein the machine-readable instructions are to cause one or more of the at least one processor circuit to provide results of the targeted anti-malware scan to the symptom analysis server.

15. A method comprising:

identifying a symptom associated with a performance error on a computing device based on input to the computing device, the input corresponding to highlighting an area of a display associated with the performance error;

identifying, by at least one processor circuit programmed by at least one instruction, a portion of files on the computing device for a targeted anti-malware scan, the portion of files identified based on positive results of malware scans from other computing devices that experienced the symptom; and

triggering the targeted anti-malware scan of the computing device based on the portion of files.

16. The method of claim 15 , wherein the positive results include results from one or more of the malware scans that addressed the performance error.

17. The method of claim 15 , wherein the input is a first input, and further including determining whether the targeted anti-malware scan addressed the performance error based on second input to the computing device.

18. The method of claim 17 , further including, in response to determining that the targeted anti-malware scan did not address the performance error, triggering a full anti-malware scan of the computing device.

19. The method of claim 17 , further including, in response to determining that the targeted anti-malware scan did not address the performance error, providing results of the targeted anti-malware scan to a third party.

20. The method of claim 15 , further including identifying the portion of files based on a scan parameter received from a symptom analysis server.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 8, 2024
From: KUMAR, RITESH; LANCIONI, GERMAN
To: MCAFEE, INC.
Reel/Frame 069134/0861 →
CHANGE OF NAME Recorded Oct 8, 2024
From: MCAFEE, INC.
To: MCAFEE, LLC
Reel/Frame 069137/0986 →
Continuity (3)
Continuation 17039520 · Sep 30, 2020
Continuation 15392867 · Dec 28, 2016
Related Publication 20240137370A1 · Apr 25, 2024
References Cited (42)
US 5621879A · Kohda · 1997 [cited by applicant]
US 7392544B1 · Pavlyushchik · 2008 [cited by applicant]
US 8533608B1 · Tantiprasut · 2013 [cited by applicant]
US 8904538B1 · Glick et al. · 2014 [cited by applicant]
US 10162693B1 · Contino et al. · 2018 [cited by applicant]
US 10826914B2 · Kumar et al. · 2020 [cited by applicant]
US 20020093525A1 · Asauchi · 2002 [cited by applicant]
US 20020147506A1 · Eryurek et al. · 2002 [cited by applicant]
US 20040267750A1 · Aaron · 2004 [cited by applicant]
US 20050038697A1 · Aaron · 2005 [cited by applicant]
US 20050038827A1 · Hooks · 2005 [cited by applicant]
US 20080034060A1 · Fisher · 2008 [cited by applicant]
US 20080177994A1 · Mayer · 2008 [cited by applicant]
US 20100077008A1 · Davis et al. · 2010 [cited by applicant]
US 20120041840A1 · Georgis et al. · 2012 [cited by applicant]
US 20120084859A1 · Radinsky et al. · 2012 [cited by applicant]
US 20130007527A1 · Petukhov et al. · 2013 [cited by applicant]
US 20150067590A1 · Lee et al. · 2015 [cited by applicant]
US 20150163233A1 · Liu · 2015 [cited by applicant]
US 20160028749A1 · Murynets et al. · 2016 [cited by applicant]
US 20160099960A1 · Gerritz et al. · 2016 [cited by applicant]
US 20160239487A1 · Potharaju et al. · 2016 [cited by applicant]
US 20170024228A1 · Chen et al. · 2017 [cited by applicant]
US 20170206530A1 · Jang et al. · 2017 [cited by applicant]
US 20170269988A1 · Alfaro Bergueiro et al. · 2017 [cited by applicant]
US 20170289179A1 · Dubuc et al. · 2017 [cited by applicant]
US 20180137152A1 · Reichert et al. · 2018 [cited by applicant]
US 20180183813A1 · Kumar et al. · 2018 [cited by applicant]
International Searching Authority, “International Search Report,” issued in connection with International Patent Application No. PCT/US2017/068644, mailed on Mar. 1, 2018, 3 pages. [cited by applicant]
International Searching Authority, “Written Opinion of the International Searching Authority,” issued in connection with International Patent Application No. PCT/US2017/068644, mailed on Mar. 1, 2018, 7 pages. [cited by applicant]
United States Patent and Trademark Office, “Non-Final Action” issued in connection with U.S. Appl. No. 15/392,867, on Oct. 5, 2018, 14 pages. [cited by applicant]
United States Patent and Trademark Office, “Final Action” issued in connection with U.S. Appl. No. 15/392,867, on May 16, 2019, 11 pages. [cited by applicant]
International Searching Authority, “International Preliminary Report on Patentability,” issued in connection with International Patent Application No. PCT/US2017/068644, dated Jul. 2, 2019, 8 pages. [cited by applicant]
Wikipedia Entry for “Antivirus Software”, archived by the Internet Archive on Aug. 28, 2019, and retrieved on Aug. 24, 2023 at https://web.archive.org/web/20190828023046/https://en.wikipedia.org/wiki/Antivirus_software,… [cited by applicant]
United States Patent and Trademark Office, “Non-Final Action” issued in connection with U.S. Appl. No. 15/392,867, on Sep. 30, 2019, 10 pages. [cited by applicant]
United States Patent and Trademark Office, “Final Action” issued in connection with U.S. Appl. No. 15/392,867, on Apr. 16, 2020, 7 pages. [cited by applicant]
United States Patent and Trademark Office, “Notice of Allowance” issued in connection with U.S. Appl. No. 15/392,867, on Jul. 15, 2020, 8 pages. [cited by applicant]
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 17/039,520, dated Dec. 22, 2022, 10 pages. [cited by applicant]
United States Patent and Trademark Office, “Final Office Action,” issued in connection with U.S. Appl. No. 17/039,520, dated Jun. 13, 2023, 10 pages. [cited by applicant]
United States Patent and Trademark Office, “Advisory Action,” issued in connection with U.S. Appl. No. 17/039,520, dated Aug. 29, 2023, 3 pages. [cited by applicant]
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in connection with U.S. Appl. No. 17/039,520, dated Oct. 3, 2023, 8 pages. [cited by applicant]
United States Patent and Trademark Office, “Advisory Action,” issued in connection with U.S. Appl. No. 15/392,867, dated Aug. 20, 2019, 8 pages. [cited by applicant]