Member Avatar for Techno22

Xp Machine is very slow to boot.
I notice that MsMpEng.exe is using up a huge amount of memory
during start up process.
It goes from about 150,000k to 15,000k.
When it reaches the lower figure - which takes some time - things then start
to make progress.
Also, I frequently get a message to say a script may be busy, and a report
often goes back to Microsoft talking about a "Queue" error.
Can anyone throw any light on this, please.

  • 2 Contributors
  • 4 Replies
  • 211 Views
  • 4 Days Discussion Span
  • Latest Post Latest Post by Techno22

Dani AI

Generated

reported MsMpEng.exe rising to ~150,000K at boot then falling to ~15,000K and causing “script may be busy” / queued error — that pattern fits the Microsoft Malware Protection Engine (Antimalware Service Executable) doing heavy real‑time or initial/boot-time scanning. It’s normal for the engine to work harder while many files are accessed at startup, which can delay other processes. (learn.microsoft.com)

A few practical checks that build on ’s msconfig suggestion:

  • Verify the process is genuine by checking its image path (typical XP/MSE path: C:\Program Files\Microsoft Security Client\Antimalware\MsMpEng.exe or C:\Program Files\Windows Defender\MsMpEng.exe). Use Sysinternals Process Explorer to see the full path and properties. If the path is unusual, treat it as suspicious. (learn.microsoft.com)

Targeted, low‑risk fixes that often remove the startup stall without turning protection off:

  • Do a clean‑boot (msconfig) to isolate a conflicting startup item or service; re-enable items one at a time until the culprit appears. (learn.microsoft.com)
  • Adjust Defender/MSE scheduled scans so they only run when the PC is idle (Task Scheduler → Windows → Windows Defender → Scheduled Scan → Conditions → “Start only if idle”), and avoid “Run with highest privileges” for that task. That prevents long scans during interactive startup. (learn.microsoft.com)
  • Add targeted exclusions (folder/process) for large backup folders or the AV’s own folder rather than disabling real‑time protection. Use exclusions sparingly. (support.microsoft.com)

If those steps don’t stop the long memory hold: capture a short Process Monitor or Windows Performance Recorder trace and run the Defender performance analysis to see which files/processes trigger scans; traces point to either a noisy third‑party component, leftover AV remnants, or a corrupted engine. For stubborn uninstall/reinstall problems, use Microsoft’s Program Install/Uninstall troubleshooter or vendor removal tools rather than permanently disabling real‑time protection. (learn.microsoft.com)

Caution: permanent disabling of real‑time protection leaves an XP system especially exposed; prefer scheduling, exclusions, or a clean reinstall/alternative AV if necessary.

Recommended Answers

All 4 Replies

Member Avatar for PhilliePhan

I notice that MsMpEng.exe is using up a huge amount of memory
during start up process. . . .
When it reaches the lower figure - which takes some time - things then start
to make progress.

MsMpEng.exe monitors/scans a lot of processes on boot, so there will be some slowdown.
It could be in conflict with perhaps another scanner or program - if this behavior started recently, you could check recently installed software. Or, use msconfig to weed out a startup that is causing MsMpEng.exe to hang.
You could also use a startup manager to disable unnecessary items --> http://www.mlin.net/StartupCPL.shtml

I would leave MsMpEng.exe alone as it is a vital cog in system defense....

Cheers :)
PP

Member Avatar for Techno22

Many thanks, PP.
Will work on your recommendations.

Member Avatar for PhilliePhan

Many thanks, PP.
Will work on your recommendations.

You're welcome :)

Member Avatar for Techno22

Seems to be working well now.
Sincere thanks.
Will close the thread now.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.