howardagoldberg

Members
  • Content count

    106
  • Joined

  • Last visited

  • Days Won

    1

howardagoldberg last won the day on February 12

howardagoldberg had the most liked content!

Recent Profile Visitors

636 profile views
  1. Is ESET blocking KB4058258 (Windows 10 16299.214)?

    For what it is worth -- all of today's updates (Windows 1709 build .248, the office security patches, malicious software removal tool) all came down without issue on my primary Win10 system. As far as I can tell and according to the Adobe flashplayer guidance page, there is no Flash update for any platform being released today. Have not run WU on my other Win10 system for today's patches, but this morning, the "missing" .214 and Flash updates came down with no issue. For those still having trouble, certainly make sure that ESET is up to date with the latest modules, but you may also now need to begin exploring other additional conflicts as well (are you running other security software concurrently, for example). Good luck everyone. Keep us posted. I will update my findings, if I find anything new ;-). UPDATE: My other Win10 system also is pulling down the .248 update and the malicious software removal tool. So far, so good.
  2. Is ESET blocking KB4058258 (Windows 10 16299.214)?

    @Phoenix There you go! Of course stand by, because patch Tuesday starts in 5 minutes!
  3. Is ESET blocking KB4058258 (Windows 10 16299.214)?

    @Phoenix There must be another issue at play, and I suspect it is this: To get the .192 build that was released in early January that started the Spectre/Meltdown patching madness, you had to have a registry key set by an AV vendor or manually, otherwise the update would not be pulled by Microsoft (see MS's own notes on this). In order to get builds released beginning in January 2018, at least that key needs to be set. You may need to let Defender do its thing for a bit (update definition, etc.), or enter the key yourself. Otherwise, install ESET. Make sure you get the latest AV and anti-stealth modules (as detailed in this thread), which update the needed registry keys, and try to pull the updates again. That's your issue :-) With a new install today, I would actually expect the exact behavior you described (as annoying as that behavior is). ESET has already acknowledged that there was an issue which was resolved with the anti-stealth module that was released this morning.
  4. Is ESET blocking KB4058258 (Windows 10 16299.214)?

    @Peter Randziak Thank you for this update, and the explanatory information. I am surprised by the fact that yet another registry key had to be set for the .201 and future updates. I had not seen anything about that via Microsoft or the regular channels I monitor/participate in (such as the patch-management listserv). Out of pure curiosity, why was the first registry key set through the anti-virus engine module, while the next key needed to be set through the anti-stealth module? Are you aware of any issues we should anticipate with today's updates (I assume there will be another cumulative update along with other security updates for Office products)? @Peter Randziak @Marcos Was yesterday's program update to 11.0.159.9 related to these issues at all? Every system I have ESET on has been updated from 11.0.159.0 to 11.0.159.9 via the regular update channel. I thought this was interesting, as such updates do not generally contain changes, except to have the latest modules as part of the install package for new installs.
  5. Is ESET blocking KB4058258 (Windows 10 16299.214)?

    @Marcos @Peter Randziak This morning upon booting my system ... Anti-Stealth module 1124 came down via the regular update channel, and Windows did pull the latest Flash update and the .214 cumulative update. Unless there is any issue with today's "Patch Tuesday" updates, this will likely be my last post in this thread That said, I still think it would be a very good idea for ESET to post a support article regarding this incident, as I suggested above.
  6. Is ESET blocking KB4058258 (Windows 10 16299.214)?

    @itman ... While there may indeed have been some conflict/miscommunication between ESET and Microsoft, I do not think that Mircosoft has any intention to harass third party vendors by risking customer safety. That would not be good for Microsoft, even if their intentions are not 100% benevolent. It is highly unlikely Microsoft made some major change to how WU on win10 functions, that would affect AV vendors, that they did *not* announce, and left 3rd party AV providers unknowingly unproductive of their customers. More likely, a bug was introduced into the Anti-Stealth module by ESET. Bugs happen. Software is not perfect. It is fair to say this past month has been particularly challenging on the security front for everyone involved. That said, security software providers have an extra-added obligation to make sure that the software they provide "does no harm," and to communicate transparently with their customers when something does go wrong. If MS is responsible, let ESET say so. Otherwise, ESET should publish a support article making their users aware of what happened and why, and what is being done to remediate the situation and prevent it from occurring again. Most users have WU set to automatically update, and most users would not know where to begin in terms of updating manually, and keeping track of what updates are available and applicable.
  7. problem with Windows Update

    @iamsaanvi ... you may want to look at this thread: https://forum.eset.com/topic/14624-is-eset-blocking-kb4058258-windows-10-16299214/. There is actually an issue with the Anti-Stealth module which was blocking Windows updates on (at least some) Windows 10 systems. ESET is now aware of the issue, and a fix seems to be coming this week.
  8. Is ESET blocking KB4058258 (Windows 10 16299.214)?

    @Peter Randziak @Marcos ... Likely having nothing to do with anything being discussed here, but just in case it matters: ESET Antivirus just updated itself from version 11.0.159.0 to 11.0.159.9 on the two systems (Win10 1709 and Win7) I am currently sitting in front of. The anti-stealth module is still at 1123, and WU on Win10 is still not pulling anything. Should I assume this product update has nothing to do with the discussion in this thread?
  9. Is ESET blocking KB4058258 (Windows 10 16299.214)?

    @itman @Peter Randziak That was exactly my point above. There has been nothing from Microsoft indicating that a new registry key was needed, so the current issue does not have anything to do with the earlier Antivirus/antistealth module update that flipped the registry key and allowed for the .192 update on 1709 to be installed.
  10. Is ESET blocking KB4058258 (Windows 10 16299.214)?

    @Peter Randziak Thank you for your prompt reply. I actually only have two Win10 machines on my network (small home office), so depending on the procedure involved, it would not necessarily be difficult for me to update just the Anti-Stealth module manually. Of course, I would need the file(s) and the instructions on how to accomplish this task. I certainly do understand that proper testing is needed, and it is laudable that ESET is working to ensure no additional harm is done. However, if I do not receive tomorrow's cumulative update, which is going to include over a dozen security updates according to the Microsoft advsory, it means that I am 3 cumulative updates "behind" due to ESET's "protection" until 1124 is pushed out. Assuming no issues are found today, will the 1124 module be pushed out in time for Patch Tuesday at 1:00 p.m. Eastern tomorrow (02/13/2018)? Regarding, "When it comes to the recent security updates, MS decided not push it to the machines with AV installed until the AV will signalize it is full compatible with it by setting a special reg value as the updates bring quite a serious changes under the hood and didn't want to cause trouble to customers, which showed to be a very wise decision,..." ESET already provided that registry key in early January (https://support.eset.com/ca6643/), and I am on the .192 release of Windows 1709 which initially addressed Spectre/Meltdown. I have visually confirmed that the needed registry key is present. So, unless there is *another* registry key that was needed for .201, .204, and the Flash update (unlikely), the current situation has nothing to do with the registry key you are referring to. The registry key you mentioned was part of the Antivirus and antispyware scanner module that was released in early January several days before the emergency Spectre/Meltdown patch for Windows was released by Microsoft. That Windows patch (.192 for 1709) came down without an issue. The current situation, to the best of my understanding, is not related to that at all, especially since you are saying that the affected module is the Anti-stealth module. I cannot underestimate the amount of damage that has been done here, at least for me, regarding the trust I have put into ESET. First, I was told by another ESET staff member that I was wrong, and now it seems two separate issues are being conflated. Further, given that is seems likely that all customers not on pre-release updates have not received Windows 10 Updates in nearly a month (at least for 1709), it would be reassuring to see a support article published by ESET acknowledging the issue and detailing the resolution. This was a major bug; for the sake of customer trust, this issue should not be downplayed. Therefore, again I ask: 1) what was the issue with the module that resulted in Windows Update failing to pull down *all* (non-Office) patches (including Flash updates) without so much as an error message, and 2) what is being done to prevent such an occurrence in the future? Please advise. Thank you. As an addendum: My Windows 7 system does not seem to be affected by this issue, as updates have been coming down as expected. I have not tested my Win8.1 machine (it is used rarely). Both my Windows 10 machines are on 1709, so I cannot confirm if the issue is present in Windows 10 1703 and earlier releases.
  11. Is ESET blocking KB4058258 (Windows 10 16299.214)?

    @Daedalus That is encouraging news!
  12. Is ESET blocking KB4058258 (Windows 10 16299.214)?

    @Peter Randziak @Marcos @itman @cyberhash Peter, thank you for following up and following through on this. Given the urgency of the issue, and with Patch Tuesday on the horizon tomorrow, is there any possibility of moving module 1124 to the normal release channel in an expedited manner? I do not necessarily want/need to receive pre-updates for other modules, but I do want to have Windows fully patched. Of course, I understand that 1124 needs to be tested in the field before going out to the entire ecosystem, but please advise on the time-lining of this. Is there a way of installing 1124 without shifting to the pre-release updates? When I first posted the question regarding Windows Updates and ESET on Win10, it was more-or-less dismissed by ESET as it being highly unlikely that ESET could be involved in any way. The same was true when I posted about the certificate pop us issue over a year ago for a which a solution was finally offered by another user (https://forum.eset.com/topic/14563-fixed-certificate-pop-ups-an-application-on-this-computer-is-trying-to-communicate-over-a-channel-encrypted-with-an-untrusted-certificate/). My immediate concern is this - given the true urgency of the issue, the fact that it has been an issue since module 1123 was released (probably before the .201 cumulative update was issued), and the fact that my report was originally dismissed by ESET - 1) what was the issue with the module that resulted in Windows Update failing to pull down patches without so much as an error message, and 2) what is being done to prevent such an occurrence in the future? I depend on ESET to protect my system. In this case, at a certain level, ESET was actually working against that goal. With that said, again, I sincerely thank you for looking into this matter and pushing out a solution. I will be curious to hear back from others who test the 1124 module to see if that does in fact resolve the issue!
  13. Is ESET blocking KB4058258 (Windows 10 16299.214)?

    [ To comment on this story, visit Computerworld's Facebook page. ] He goes on to say: Servicing Stack updates are bundled with cumulative updates in version 1709. You may notice that the 1709 SSU has a distinguished version (i.e. 16299.122.1.0), not the generic version like other updates before (i.e. 10.0.1.2). Servicing Stack updates won’t be listed in Windows Update history, but you can find it in Installed Updates @itman ... and to your point, it looks as if the lack of the servicing stack update can have an impact on whether future cumulative, etc. updates come down. It is also not listed in my "installed updates," so it simply has not been "seen" or installed by WU. Also, the link you provided for "He goes on to say ..." does not seem to have anything to do with this issue.
  14. Is ESET blocking KB4058258 (Windows 10 16299.214)?

    @itman ... No, you do not need to manually install it. Read the release notes: https://support.microsoft.com/en-us/help/4074608/servicing-stack-update-for-windows-10-version-1709-january-30-2018. They clearly state that Method 1 is to install it via Windows Updates: "Method 1: Windows Update | This update will be downloaded and installed automatically."
  15. Is ESET blocking KB4058258 (Windows 10 16299.214)?

    @itman ... every cumulative update is a replacement for the previous update(s). That does not necessarily mean that it is "corrective" or only aimed "at certain installations." On the release notes page for 1709, there is no indication from Microsoft that .201 or .214 was only released to a sub-set of users. In the past, when an update has only been targeted to a subset of users, the release notes clearly indicated that fact