Windows Defender Offline definitions out of date

It is difficult to imagine how this problem could be unintentional. The DATE information on the MEDIA USB is updated with each update, as is the version number of the MPAM file, as seen on its PROPERTIES >DETAIL screen. 

The indication that the definitions are out of date, is much more likely due to an UNCONDITIONAL  branch in the program, than from a real comparison of the date on the USB to the system clock. After all, the USB information is refreshed with each run of the mssstool. From version to version and date to date.

If Microsoft has decided to discontinue this tool for Windows 7, please alert your users. Your lack of attention to this problem is causing many to waste considerable time and energy. 

If it has not been discontinued, please offer a solution soon. Many rely upon it in dire situations, and many have machines that will not update to Windows 10.   Pentium 4 for instance.       THANKS

Reply to all. I am glad to see that there has finally been some interest displayed for this problem. However, Windows 10 solutions are not relevant. As I understand it the WDO program is handled by the OS in Windows 10. Not so in Windows 7.

This failure (The definitions are out of date) is occurring on both 32bit and 64bit machines with all different manner of security programs. The same machines that ran this program just fine until recently. As for outside influences affecting its function, the only influence that is different now is the DATA that is downloaded from Microsoft when the MSSSTOOL is run to create the MEDIA USB. As can be seen, the version number of the MPAM-fe file is at the CURRENT level when created on the USB. Although it is not the same as the internal Windows Defender anymore, it IS at least as high or higher.

Since the system is BOOTED from the USB, only the date WITHIN the USB is available to compare to the system clock. This must be how the program determines the viability of the definitions. The date ON the MPAM file on the USB is CORRECT.  Yet, it still reports that the definitions are out of date. Therefore, the date INFORMATION IN the USB that is used for comparison MUST BE CORRUPTED. Mr. Microsoft Moderator, please consider my conclusions as you define and correct this problem. I apologize in advance if I am all wet.     Thanks

I have exactly the same issue and I use Norton

It has been my experience when using Windows Defender Offline (WDO) over several years that when I try to use a boot CD created several days prior I get kicked out for having out of date definitions. When I try to update while still booted from the CD, sometimes it updates, sometimes it does not. CD’s are cheap, I just go to a different computer and create a new boot CD with the latest definitions and I am back in business on the suspected to be infected computer.

Not any more, for the last two or more months. Now when I create a new boot CD, from the latest tool download, with the latest definitions, the system boots to WDO, but I immediately get a message that the definitions are out of date. And, when I throw my hands up in frustration and press the update button it is again rejected as definitions out of date. NOT with the usual message that the tool cannot access the definition update server due to no connection. Just a flat statement that the tool cannot be updated.

This used to be a really good and reliable tool. Have used it to bring many machines back from the edge of the abyss. The Microsoft support website says that Windows 7 will be supported for security until 2020. Did that commitment just get changed? This is an important security tool for Windows 7.