Jump to content

funzee

Members
  • Content Count

    7
  • Joined

  • Last visited

Posts posted by funzee

  1. 1 hour ago, Marcos said:

    In case you're able to reproduce it, it'd be great if you could generate an advanced protocol filtering log (adv. setup -> tools -> diagnostics) prior to starting update that would fail. Microsoft's communication is excluded from filtering in case of HTTPS, maybe updates were downloaded via HTTP in your case and something went wrong. The issue would require further investigation to determine the root cause of the error.

    https://drive.google.com/open?id=1_CTvV8YAFAXON67S_ziznBUC8q0OqYO0
     

    full dump is over 100mb so Ive uploaded it to gdrive.

  2. 6 hours ago, Marcos said:

    Does temporarily disabling protocol filtering in the advanced setup make a difference? If not, with this option disabled it's unlikely that ESET would interfere with http/https communication during update.

    I was unable to download any apps from win store and check updates for windows.
    disabling protocol foltering fixed 0x80245006 for me.
     

×
×
  • Create New...