-
Notifications
You must be signed in to change notification settings - Fork 381
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
__rsignal(RSIG_BOOTENGINE) returned failure, missing definitions? #103
Comments
Having the same issue |
Same here :( |
Thanks for letting me know, I'm investigating. |
Using the mpengine.dll from Aug 5 with the newer .vdm files seems to work for now (not familiar with the inner-workings of these files, but it does detect EICAR and several other virsuses correctly). Thanks for all the work that you put into this project! |
I see the issue, mpengine is doing a lot more work to validate all the signatures on the VDM, and not trusting the host system to do the verification. It might take a day or two, but I'm thinking about solutions! |
Thanks :) |
i am also troubled by this problem :( |
Same Issue, |
Looks like using the mpengine.dll from Aug 5 no longer works with the new VDM files as of this weekend. @taviso - have you been able to make any progress with this? Thanks again. |
I search another download link, it works. But I don't know why. It maybe helpful. http://download.microsoft.com/download/DefinitionUpdates/mpam-fe.exe |
Thanks for the other link. That does work, but it appears to be an outdate engine. I'm seeing the error listed in this issue on the latest version of the engine. Would love to have a fix as well! |
It works fine with older version but latest updated is not supported. |
@taviso were you able to figure out the root cause for this? |
Hello,
As of this morning it looks like MS changed something in the distribution files. Now getting the following error when trying to run mpclient:
Don't know if it's related, but compared to yesterday's files, some of the new files seem to have shrunk:
The text was updated successfully, but these errors were encountered: