Trend Micro Worry Free client systems are unresponsive after Windows 10 defender update on 5/2017 - KB890830

Since this is a Windows Defender update it cannot be easily rolled back. User experience slowness that makes the PC appear to be not working as even the simplest tasks take significant amounts of time to complete. It is like your PC is working but at 1% of its speed.

The problem is that Windows Defender update severely conflicts with Trend Micro Worry Free Agents using a local management server. The Worry Free Saas product appears unaffected by the issue. Trend Micro support is aware of the problem and working on a fix to Microsoft’s update. In the meantime the temporary fix is to disable Windows Defender active scanning following the steps below.

Note: You can uninstall Trend Worry Free Agent however then you are leaving your systems vulnerable. Using the server console to remove the Trend agent will not work effectively and you will have to manually remove the agent on each system which could take 30 minutes or more per system due to the performance issues.

Caution: it’s the registry you break it you bought it…  

On the impacted Windows 10 workstations open regedit:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender

New, click DWORD (32-bit) value and then name it as DisableAntiSpyware.

Set Value at 1 and restart the system

That will disable Windows defender and should keep it from restarting itself and stop the conflict with Trend Agent.

Reboot the system and test

Note: this can be done as well via GPO to stop further deployment issues. however it will take a significant amount of time on systems already effected.

Trend Micro Agents should work fine in normal mode with real time scanning enabled once this fix is deployed. If you have not already I would recommend installing Trend Worry Free 9 Service Pack 3 as well.

Comments

Post a Comment

Popular posts from this blog

Office 365 Deployment Tool Office Download fails “Could not Install”

Image
Problem: you run the setup.exe /download download.xml and fails immediately with “Couldn’t install” You make sure all the settings are correct (see other blogs) and find nothing wrong Solution: Change drives and run it as an administrator again. For example above i am in the F:\OfficeDeploy directory which is the same directory I have the download.xml directing the download to. If i Change to the c: and run the same command again it works The Office Data folder was created and updated as shown below:
Read more

FRS to DFSR Post Cleanup “File Replication NtFrs Stopped”

Image
After successfully migrating from FRS to DFSR you get the File Replication NtFrs service is Stopped error on the local servers AD DS Services list. In the Event logs you may see Event id 13575 13577. You can confirm your migration completed by opening a cmd prompt as administrator and typing in: dfsrmig /getmigrationstate After your migration to DFSR is completed and you have given your servers ample time to propagate this service is no longer required. Since it is set to “Automatic”, as shown below” it shows in logs as a false positive error. Edit the File Replication Service and change it to “Disabled”, as shown below: Once it is listed as “Disabled” it will no longer show in the Console as an “error” Note : it may take some time to clear from the active view
Read more

Domain Migration SubinACL /Migratetodomain How To:

Caution : DO NOT run this on Domain Controller C:\ and only run on roaming profiles folders, or my docs shares day of migration to avoid ownership change issues. Confirm Domain trust is in place and users and groups have been migrated Test ping of olddomain.org from new domain Test ping of newdomain.org from olddomain Add newdomain.org domain controller host records to olddomain.org including reverse DNS records Confirm the user running the app is a domain admin in BOTH domains Download SubinACL here: http://www.microsoft.com/en-us/download/details.aspx?id=23510 /Migratetodomain- command will add the permissions of the new user to the old files and folders for example if jimbob@olddomain.org was migrated to the new domain jimbob@newdomain.org and you run the command below any file or folder in that path that has jimbob@olddomain.org will add Jimbob@newdomain.org with the exact same permissions. This is a safer way to migrate by keeping the old and new permissions intact while a
Read more