Wrong Diskette in Drive Error

  • Thread starter Thread starter DGRProductions
  • Start date Start date
D

DGRProductions

Hi,

I have tried all the steps I have found outlined and still can't get my
Windows Defender to update on it's own or when I click "check for updates"
manually. What is the deal? Does anyone know how to fix this or when
Microsoft might figure out how to fix it and release a new version?

I really would like to use it, but not with 257 day old definitions or
whatever they are.

Thanks a lot!

Drew
 
Have you been to Windows Update and applied all offered critical
updates--i.e. those offered on an Express scan?

If you are on Windows 2000, you will need to do a custom scan as well, and
apply the "Root Certificates update".

Additionally, if you are on a machine which is joined to a domain, or has
been in the past, definition updates may not function unless the
administrators have chosen to distribute Windows Defender definitions over
the corporate network.

http://support.microsoft.com/kb/918355
 
Thanks for the response.

Nope, this same problem happened to me at home on my school network and here
on my school network. I do not have Windows 2k (windows xp home sp 2) and I
have tried through Microsoft Update. Download always fails from there on
definitions.

Hmm..

Drew
 
Let's try this:

First: download these two files and save them to a known location:

To bring definitions up to date from 1.0.0, if necessªry:
1) For Signature v.1.14.1708.60 & Engine V 1.1.1603.0
frºm
http://au.download.windowsupdate.co..._faeaaf1b1eb4e48c83b98c74bf3ae84991e1bfe4.exe

2) For Signature v. 1.14.1729.5 frºm
http://www.download.windowsupdate.c..._038cddd1977adf8a5ee7d3a7026d65ec12df7727.exe

Next: Go to a command prompt in the Windows Defender install
folder--typically \program files\windows defender. type:

mpcmdrun -RemoveDefinitions -All

and hit enter.

Once that completes, click on the two files you downloaded above, in
succession, allowing one update to complete before trying the next one.

That should bring the definitions to current, but it will not fix the
underlying issue of not being able to reach updates via Windows, Auto, or
Microsoft Update.

For that, I think we need to look at the tail end of WindowsUpdate.log (from
c:\windows or the equivalent on your machine)--immediately after an update
attempt:

1) In Windows Defender, do Help, about, check for update and wait a few
minutes.

2) Start, Run, Notepad %windir%\windowsupdate.log

(this can be a very large file--give it time.)

Scroll down to the very end, then scroll back up to the time of the update
attempt.

Cut and paste just the entries from the start of that update to the end of
the file, back to this message thread.

What is of interest is what server AutoUpdate is attempting to connect to.


--
 
Bill,

Is this attachment what you want??

I was unable to get the current definitions updated still, as I am not
familiar with how to get a command prompt in the windows defender installer
folder.

Are you talking of smoething related to "Run, cmd"?

However, I do think think this is the log you were looking for.

Thanks for your patience,

Drew
 
Actually, I did find out how to do the command prompt, but that didn't work
either. I attached a jpeg screenshot of the error message.

Thanks again,

Drew
 
Back
Top