Windows Defender Offline on Windows 7 machines DEFINITIONS OUT OF DATE

Anonymous
2017-05-31T08:59:20+00:00

Windows Defender Offline has stopped recognizing UPDATED Definitions on W7 machines,  Again.

Immediately after updating the Media USB, using the MSSSTOOL, attempts to boot from the USB fail,

indicating that the Definitions are out of date. On both 32bit and 64bit machines.

 This same failure occurred in 2016, on multitudes of W7 machines, between January and July.

Microsoft eventually fixed it by releasing a new version of the MSSSTOOL. 4.9.0221.0  (872kb).

The failure with WDO on W7 machines in 2016 began to occur shortly after problems showed up in

Windows Defender on W10 machines, and was probably the result of fixing the W10 machines.

We may now have the same thing occurring again. After the CREATOR update to W10, it appears they

are having problems with WDO.   And now WDO is broken for W7 machines.

MICROSOFT, if you have modified the configuration of the definitions or the WDO program data in an

effort to repair the problems in W10 machines, please release an updated version of the MSSSTOOL

that will allow W7 machines to accommodate those changes.    Thanks,  Glen

Windows for home | Previous Windows versions | Security and privacy

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2017-08-20T01:47:10+00:00

GREAT NEWS !

Windows Defender Offline is working once again on Windows 7 machines.

There has been a change made to the Windows Defender Offline Program.

It no longer updates definitions before running.

In order to take advantage of this FIX, it will be necessary to format your

USB before you run the mssstool. This will ensure that a fresh copy of the

Program is installed on the USB.

Don't know why we were not notified!  I just happened to discover this change,

while examining a WDO problem on Windows 10. There, it is possible track

the operation, using the Event Viewer. I couldn't believe my eyes.

Happy Scanning,  Glen

Was this answer helpful?

2 people found this answer helpful.
0 comments

41 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2017-06-24T07:55:38+00:00

    The 64bit MSSSTOOL is now downloading definitions (1.247.56), and the WDO program, to a media USB

    as it should. However, booting from the media USB still gives the Definitions Out Of Date red screen.

    On my 3847 64bit Ethernet connected machine, the definitions do not eventually get up to date, as they

    do on my old 8300 32bit Ethernet connected machine.

    Clicking on the Update Definitions button still fails, as it has, giving error code 0x80072EE7. There is obviously no internet connection.  The 8300 is different in this regard. It does connect and downloads the

    definitions, not to the USB, but to the loaded WDO program. Kind of like Windows 10 would do it !!

    The DOWNLOADS for the MSSSTOOLS have not been fixed. They are still at version 4.9.0221.0  872kb.

    Can anyone produce a media USB that will function normally on Windows 7 using these MSSSTOOLS ??

    Regards,  Glen

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-06-23T20:00:48+00:00

    Hi Josef;

      Thanks for your response, but I'm afraid that you may have me confused with someone else. I have no

    separate post on May 3rd.  I have no problem with my Windows 10 machine.

    My problems involve WDO on Windows 7 machines.

    I started this thread and have another started prior to this, re;

    "Windows Defender Offline on Windows 7 Machines  DEFINITIONS OUT OF DATE"

    The only Moderator response to that thread was made by someone unfamiliar with WDO on Windows 7,

    and considered the problem to be a "slight glitch".  The problem is in fact solid, and can only be

    circumvented on one of the five Windows 7 machines that I have access to.  An old DELL 8300 P4 32bit.

    Please give that thread some consideration as well.

    Thanks,  Glen

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-06-23T18:56:45+00:00

    Same here. The 32 bit version works, the 64 bit version spits that error.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-06-23T10:20:32+00:00

    Hi Glen,

    It seems you have a separate post date 3rd of May and it seems you are getting the same error. What we suggest for now is sending a feedback via the Feedback Hub as it will be checked by our Developers and Engineers.

    In order to submit new feedback, please follow these steps:

    1. On a Windows 10 device, search for 'Feedback Hub" in Cortana search, then launch the app. If not, please download the app via the Windows store.
    2. Navigate to Feedback in the left menu, then press Add new feedback.
    3. Select the Problem, and share any details you think are relevant, and choose an appropriate category and subcategory.
    4. Important: If possible, reproduce the problem(s) after clicking Begin Monitoring (or Start Capture) near the end of the form; Stop Monitoring when you're done.
    5. Once you've completed the form and monitoring, click Submit.
    6. Click Continue using Feedback Hub.
    7. Click My feedback at the top, then find the item you submitted (it may take a while to appear).
    8. Open the item you submitted, then click Share.
    9. Click Copy link, then paste the link here in your response (it will look like https://aka.ms/<unique link>).

    Was this answer helpful?

    0 comments