Jump to content

Leigh Glaus

Members
  • Posts

    6
  • Joined

  • Last visited

About Leigh Glaus

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    South Africa

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I have just pushed out an ERA policy turning it back on, I am running 9 Windows 10 1803 test machines on the network, so I will let you know the results on Monday or as soon as the error pops up again, Thanks @Marcos for all your technical assistance so far!
  2. All my issues were on x86, but I haven't tested x64 as all our network workstations have to run 32-bit. @Marcosworkaround by disabling HIPS Protected Service seems to be working fine in the interim.
  3. I can confirm that disabling the HIPS protected service works. @Marcos advice is working. I pushed that setting out via an ERA policy to all computers on the network and all my 1803 x86 machines are not giving that error anymore. I have been running error free for the whole week. I hope to see a patch / fix from MS soon, I can also confirm that the latest 1803 Windows update DOESN'T fix this issue.
  4. Yes, I am having the same issue since updating to 1803. Network is running Windows 10 Pro, 32-Bit on a Windows Server 2012 R2 Domain and ESET Endpoint Antivirus 6.6.2072.4 and running as a standard Windows user - rebooted multiple times, did you manage to get your issue resolved?
×
×
  • Create New...