From a week right after starting the computer, a message appears to me as in the subject with the note "the module cannot be found". I'm guessing that FRST can solve this problem, but I don't know how to fix it. Attachments files created by FRST after scanning. Thank you in advance for any suggestion and help.
Unfortunately it didn't work out. > FRST did not cope with it and I still get the same error every time I start it as in the title (in the screen attachment of this error, there is no other path there). > I have also tried to install RemoveMcAfee from the given page, but even when I do it as an administrator, it does not start the program for me.
In the attachments I send the fixlog and the above-mentioned RunDLL error screen, which it throws out, so throws.
In autoruns, disable this entry in the Tasks section: \ Microsoft \ Windows Live \ SOXE \ Extractor Definitions Update Task Windows Live Social Object Extractor Engine Microsoft Corporation c: \ program files (x86) \ windows live \ soxe \ wlsoxe.dll 2014-01-01 05:28
In Autoruns he doesn't search for this post in the filter for me: \ Microsoft \ Windows Live \ SOXE \ Extractor Definitions Update Task Windows Live Social Object Extractor Engine Microsoft Corporation c: \ program files (x86) \ windows live \ soxe \ wlsoxe.dll 2014-01-01 05:28
When I type "dll" in the filter, I find "file not found" entries, but not with the C: \ Program extension. As I indicate, to search "dll" only in "Scheduled tasks" does not find entries "file not found".
I am afraid that you will not find this entry, the more that it does not have to be the entry with the missing file, it is only missing "before and after the path, so it only shows C: \ Program.
The discussion revolves around a persistent RunDLL error indicating "the module cannot be found" after starting the computer. The user suspects that the issue can be resolved using FRST (Farbar Recovery Scan Tool) but encounters difficulties in fixing it. Various suggestions are provided, including checking specific registry paths, uninstalling Intel Security True Key, and using tools like Autoruns to identify problematic tasks. Despite attempts to follow these recommendations, the error persists, leading to further troubleshooting efforts. The user shares logs and screenshots to assist in diagnosing the issue, but a definitive solution remains elusive. Summary generated by the language model.
