Peter2150 45 Report post Posted May 28 I just got 9469. No issues so far here on Win 7 Pro Share this post Link to post Share on other sites
stapp 130 Report post Posted May 28 Win 10 pro 1903 via autoupdater and a restart. No issues so far. Share this post Link to post Share on other sites
stapp 130 Report post Posted May 28 On a different 1903 machine via autoupdater I saw this. I didn't see it on my other machine (that one has dark mode for slides.) Download Image Share this post Link to post Share on other sites
JeremyNicoll 57 Report post Posted May 28 On Win 8.1, I got a dark version of this "remind me again" screen. I was busy doing something else so didn't look very close, though I did see some sort of text bleeding through the area to the right of the "1h" part. I also tried clicking the drop-down arrow, and there was only one option "1 hour". Share this post Link to post Share on other sites
Frank H 91 Report post Posted May 28 that remind me again thing is a little gui bug that sits in version 2019.4 and is fixed in 2019.5. Pls note that 2019.4 requires the restart. Share this post Link to post Share on other sites
stapp 130 Report post Posted May 28 2 minutes ago, Frank H said: Pls note that 2019.4 requires the restart. We noticed :) Share this post Link to post Share on other sites
Peter2150 45 Report post Posted May 28 Was hard to miss. I saw the same thing as Stapp on my win 7 machine. My win 10 Pro 1903 VM updated fine. Share this post Link to post Share on other sites
GREGORY 5 Report post Posted May 28 No issues so far. Share this post Link to post Share on other sites
Peter2150 45 Report post Posted May 28 I saw something strange on one machine. Am watching. I got a pop up saying I need to install a windows update for compatibility. I checked in windows update and didn't see the kb mentioned but I brought the machine current. Got the popup again so this time so this time I downloaded the KB from the catalog. WHen I went to install it I got a message that this machine didn't need that update. Hmm Share this post Link to post Share on other sites
Frank H 91 Report post Posted May 29 @Peter2150 hi, We implemented this check for Windows 7 & 2008 R2 machines only. Can you start CMD as admion and run this command: wmic QFE list full > c:\info.txt and pls send me that file ? thanks Share this post Link to post Share on other sites
Peter2150 45 Report post Posted May 29 PM'd PS. What was the KB, as I think I got the wrong one. Share this post Link to post Share on other sites
Peter2150 45 Report post Posted May 29 For anyone interested the above KB is already installed and have sent the logs Share this post Link to post Share on other sites
JeremyNicoll 57 Report post Posted May 29 Peter, you know that MS sometimes re-issue updated versions of some updates, with the same KB number as earlier versions? Eg: KB890830 comes around every month (the MSRT). But it does happen also with fixes they rework. Share this post Link to post Share on other sites
Peter2150 45 Report post Posted May 29 I tried re installing and it said the KB was already on the system. Share this post Link to post Share on other sites
Frank H 91 Report post Posted May 30 @peter2150 does EAm still warn you to install that KB or is all fine now Share this post Link to post Share on other sites
Peter2150 45 Report post Posted May 30 Hi Frank It's far from all fine. I waa seeing a strange artifact on reboot. System brought to a halt by very heavy disk activity that last almost a minute plus. Turns out it was trustedinstaller.exe and it was scrolling thru all the install KB's. When I killed it I then got the EAM compatibility alert. Using autoruns i blocked all the EAM components from loading at boot and now all is well. Pete Share this post Link to post Share on other sites
Frank H 91 Report post Posted May 31 @peter2150 thanks. Share this post Link to post Share on other sites
Peter2150 45 Report post Posted May 31 Hi Frank I am seeing the notice every morning on the other machine, but that doesn't get rebooted often so it's not as much of a bother. Let me know if you need somthing tested before release. Pete Share this post Link to post Share on other sites
Frank H 91 Report post Posted May 31 Thansk @Peter2150, we are testing a fix and will release a 2nd beta this weekend most probably. Share this post Link to post Share on other sites
Peter2150 45 Report post Posted June 1 Great. I'll turn EAM back on and wait. Share this post Link to post Share on other sites
Frank H 91 Report post Posted June 1 @Peter2150 we have just released Emsisoft Anti-Malware 2019.5.0.9476 beta which includes improvements regarding the KB4474419 check. The KB should now correctly be detected. Share this post Link to post Share on other sites
Peter2150 45 Report post Posted June 1 Initial test looks good. Have to update the other machine and live with it a day. Thanks guys Share this post Link to post Share on other sites
Frank H 91 Report post Posted June 2 EAM performs the check at program startup, so if you won't see it the first time, you'll never see it ;=) Share this post Link to post Share on other sites
Peter2150 45 Report post Posted June 2 Hi Frank Spoke to soon. Only change I am seeing is now if I kill trusted installed. Honestly I am kind of disappointed in that there could have been a much better solution. Let me give you an example. 1. Test for a special file in the emsisoft area. 2. If it is not there then run the scan first alerting the user you are going to do so and that it's a one time thing 3. If the KB is present generate the file I mentioned above. If the KB isn't there either download the KB for the user or at least give him a link. 4. If the special file is there your done. The special file doesn't have do contain anything. Pete Share this post Link to post Share on other sites
Frank H 91 Report post Posted June 2 Thanks for your feedback Pete. We have to check each time EAM starts as users can delete installed KB's. When we 'assume', because we set some tag somewhere, that the KB is installed and just start EAM, it will just stop working, as this KB is a mandatory, rendering user's system unprotected. which is a no go. Share this post Link to post Share on other sites
Peter2150 45 Report post Posted June 2 Okay, thanks for explaining. But isn't there a simpler way of checking. That sure is resource intensive at boot. Share this post Link to post Share on other sites
