Defender Scan



Win2000 system loaded Defender and ran updates then started scan, gets partly
through and error message pops-up "MsMpeng.exe no disk in
drive\device\harddisk1\Dr2" then you get the stadard option screen of
continue, retry or cancel which does not work. Even going to Task Manager
will not shut-down application, have to shut-down machine. Any thoughts, I
hope it was not a mistake to load on machine?



Bill Sanderson

Wierd. I've seen similar, also on Windows 2000, but hitting the A
drive--and I've seen a couple pf posts of similar import here.

I don't have a fix.


I experienced a similar situation this AM on a PIII with a Promise - ultra66
controller card - Win2K OS. Not clear if drive issue was due to a Zip Drive
that had no disk in it or possibly due to a multiple listing of removable

Will have to see if it (problem or drive error for no media) re-appears to
test other options but was unable to clear error messages and only after
forcing a rather shutdown was I able to get rid of it.

Did not re-experience problems or reoccurrence on re-boot of system so could
have been a scan related issue as scan was/had been slated to run earlier
this AM.

Prior to running another or a full scan on this system after re-boot I also

On reboot -had examined system and found a listing in Computer Management -
Storage - Removable Media for a second or duplicate Iomega Zip 100. Computer
Management was showing 2 listings - one connected or present and one
disconnected or not present for same drive (display for the disconnected
drive was similar to what appears for a USB device that was/had been
previously connected to the system but was not connected at this/that time).
Deleted the disconnected or not present physical location that was also using
or referring to Device by same name: \\. \PhysicalDrive0.

Proceeded - without system reboot - to run a Full system scan in Defender -
elapsed time - >90 minutes - Objects scanned >344,000.

During Scan which began at 10:16 AM on 02/27/2006 - experienced the
following events and actions:

02/27/2006 11:04 AM - MsMpEng.exe - No Disk - Error message
"There is no disk in the drive. Please insert a disk into drive

The above error message appeared while scanning was running and scanner
stalled or paused on:

Could not clear message window or popup using Continue/Cancel/Try Again
options - repeated each multiple times.

Re-inserted Zip Disk into Drive - Clicked Continue - observed that scanning
then resumed/continued on system and popup window disappeared from view.

After resumption of scanning - scanner observed to continue scanning and
evaluting files on C - Fixed, D - Fixed and E - Removable Zip drives.
Allowed scanning to continue for several minutes.

02/27/2006 11:14 AM - ejected Zip Disk (E - Drive) while Defender was
scanning files on D - Fixed Drive.

02/27/2006 11:48 AM - Full system scan completed:
Start: 10:16 AM
Time elapsed: 01:30:45

As scanner is set to run daily - will update info as situation warrants.



The only work around I have found is to insert disk to A:, hit continue, and
move on. It does return after a while, and is on the screen when I come in
(after a nightly scan). The error is only on 2000pro, not on XPpro...


Yes, situation repeated itself again today - system call as noted previously:

"There is no disk in the drive. Please insert a disk into drive -

Inserted Zip Disk in drive and did not remove for rest of scan - scans
resumes and completes without further problems.

OS Win2K



I am adding the following supplement to my prior post:

03/02/2006 08:06 AM - No problems experienced today with Microsoft Defender
- did not even notice that program had or was running because was either
using system or I "as user" had left Zip Disk in drive.

03/02/2006 08:07 AM - Went into Defender setup and selected:
General Settings - Advanced Options
Added "E:\" drive as path to exclude from scanning.

03/03/2006 - no record of problems - not clear if resolved or that disk had
been left in drive - scan was to have run earlier this date and apparently
did run without interruption.

03/04/2006 05:28 AM - "MsMpEng.exe - No Disk" error. Repeated attempts to
use "Continue" "Try Again" or "Cancel" do not resolve issue.

03/04/2006 05:30 AM - Inserted Zip Disk into Drive Bay.

03/04/2006 05:31 AM - No system response to inserted disk.

03/04/2006 05:32 AM - "Continue" button in warning or error screen retried -
warning error box removed from system. MsMpEng.exe began using system
resources (CPU) in excess of 80%.

Note: Other than observing system utilization via CPU utilization via Task
Manager processes screen - there is little or no "evidence" or "access" to or
by user to this program while it is running. The ongoing system scan does
not appear in the Applications list or as a process evident in the Task Bar
or as an icon representing an active program in the Systray. Personally I
consider this a design flaw. At any point in time, the user or system owner
should be able to readily identify a process that is running and that "may"
be responsible for user input or monitoring.

As a rule of thumb I would suggest that Microsoft should ensure that no
program they develop and if possible - any program that runs on a user's OS
that can or will consume more than 5% of system resources - e.g. CPU at any
point of time is represented in at least one of the following:
Applications - Windows Task Manager

What is the "difference" in how Microsoft has designed this application to
interface with a User's OS and "run in the background" and third-party
attempts to embed - software to "track keystrokes" "open and access ports" or
otherwise inject operational code onto or into a user's OS to perform tasks
that are relatively invisible or go undetected.

To me this represents a "conceptional flaw" in the overall design of the
program and its intended operation and benefit to the user.

I should also note that if "user" accesses program via a user-defined
shortcut e.g.:
"C:\Program Files\Windows Defender\MSASCui.exe"
Then program can be readily accessed via Taskbar icon and "Windows Defender"
is represented within the Windows Task Manager - "Task" list for Applications.

03/04/2006 05:53 AM - System scan continues to run for a Full System Scan
that was started at 4:01 AM and has currently been operational for in excess
of 1 hour and 53 minutes. During system scan user cannot access via Windows
Defender (Beta 2) screen any of the following:
Scan - cannot access any of the options via drop down menu.

During system scan user can access via Windows Defender (Beta 2) screen the
? - "Help" - Drop-down menu is accessible.

03/04/2006 06:06 AM - Scan completed - Status shows Last scan start date and
time but does not include eiher elapsed time - or time completed.

I also note and/or recall that History menu does not or will not show any
evidence or previously performed or completed scans - even though it contains
to statement "See all Windows Defender activity". Provides for recall of
problems or warnings via "Allowed items" or "Quarantined items" links but no
scan log for user to document if and when a "scan" had run at all or to log
how long it takes/has taken for scans to run over time - other than the last
or "most recently completed" scan event and then does include or report the
time scan was completed or scan duration.

03/04/2006 06:12 AM - Confirmed post scan that drive setting to exclude "E"
or Zip Drive was still there. As such scan was suspended during operation
due to no disk in "drive 0" call for this the "E" drive which was to be
"excluded" during scanning.



Bill Sanderson

Thanks. I see this myself, with the floppy drive, on a Windows 2000 pro

One way to see the pattern of scans on a system, and the time involved, is
to run the eventviewer:

start, run ,eventvwr.msc <enter>

and filter the System event log on source WinDefend. You can then move up
and down and see the pattern of scans on a machine and the start and end

I understand that you would prefer to see this recorded in the UI--just
stating that it is possible to get a good look at this information, using
the system log.



Mon, 3/06--4 Win2000 pro machines had same error. Error occurs after a scan.
Only solution I have found is to leave a floppy in drive. This also means
that if computer is set for auto 2000 updates, and downloads come
automatically, and then need an auto reboot, then reboot cycle will not



Bill Sanderson

Yuck--hadn't thought that far ahead.

This is a bug that needs to get fixed, I agree.

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question