PoorlyPCNigel

Happy to report that FRST + the fixlist.txt you supplied have resolved this issue. I can use this elsewhere ( once I have generated a fresh fixlist.txt ) and fix this without needing to reinstall Emsisoft. Excellent and many thanks !

Thanks for that. I'll work through those steps on Monday and report back.

OK cool - the log files are attached. Addition.txt FRST.txt

I am preparing the FRST output files but not sure of the content and whether I should be posting them in a public forum. Can I get them to you in another more secure way ?

No joy, I'm afraid. Completed these steps ( adding an extra restart at the very end ) and still Windows doesn't see Emsisoft as a security provider.

Well spotted - Emsisoft isn't even reported as a security provider even though it is installed and active.

Situation the same after completing these steps, unfortunately.

Two screen shots attached. This is on a customer system and I have the same behaviour on another machine too. Both are Windows 10 Pro x64 running 1909.

Thanks for the update, at least I can now plan accordingly.

Is this on the development roadmap at Emsisoft ? I use my G suite account SMTP settings to deliver email notifications for events and my understanding is this will soon no longer be possible. Any application needing to access accounts in this way will need to support OAUTH 2.0 - is this planned for Emsisoft ?

Many thanks for the reply. As we are now out the end of February, I'll just hang on for the official release of 2018.2 Cheers, Nige

Seen this a couple of times now. When performing a malware scan on a new Emsisoft install the scan gets stuck with xinputhid.sys - after about 10 minutes I normally just stop the scan and move on. Anyone else seen this or any way to work around it ( other than excluding that file before I do the first scan ? ) This is on Windows 10 Pro with Emsisoft 2018.1.1.8439. Thanks, Nige

Thanks, Jeremy. Couldn't see for looking !

Following this thread (can't find a way to do this without a post ! )