Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Worry-Free Business Security (WFBS) 7.0 Patch 1 build 1435

    • Updated:
    • 12 Feb 2015
    • Product/Version:
    • Worry-Free Business Security Standard/Advanced 7.0
    • Platform:
    • Windows 2003 Enterprise
    • Windows 2003 Small Business Server
    • Windows 2008 Enterprise
    • Windows 2008 Small Business Server
    • Windows 2008 Standard
    • Windows 2011 Small Business Server Essentials
    • Windows 2011 Small Business Server Standard

This patch adds new platform support and improves the Security Agent installation flow. This patch also includes all previous critical patches as well as several frequently requested hot fixes that are related to update and performance issues.


Select a topic below to learn more about WFBS 7.0 Patch 1 build 1435.

You should install this patch release if you are currently running WFBS 7.0 with a build number lower than 1435, and you have not yet installed hot fixes later than 1435.

To download, click one of the links below:

  • Support for new platforms including Windows Small Business Server (SBS) 2011 Standard, Windows SBS 2011 Essentials (RC), Windows Home Server 2011 (RC), Windows Server 2008 R2 Service Pack 1, and Windows 7 Service Pack 1
  • Support for Internet Explorer 9.0
  • Add-ons for Windows SBS 2011 console and SBS 2011 Essentials dashboard RC are available from the Security Server's console (Preferences > Management Tools page).
  • This patch enables the Security Server console to show hot fix, critical patch, and patch information on the Help > About page.
  • This patch adds the Disable program upgrade and hot fix deployment option on the Security Settings > [Group Name] > Client Privileges page. This option works for both Security Agents of version 7.0 and Client/Server Security Agents of version 6.0 and below.
  • This patch enables WFBS to write the version numbers of Security Agent components to the registry after updates.
  • This patch allows the Security Agent to notify users to restart the computer if it is required during installation and to launch the installer automatically after the restart.
  • Support for disabling the tray icon in Terminal Servers for more efficient memory usage.
  • Users may receive the ESENT Event ID 490 notification in the Application Event Log after installing the Security Agent. (Critical Patch 1357, hot fix 1360)
  • Users may experience performance issues when saving Microsoft Office files to a shared network drive on a 64-bit server. (Critical Patch 1357)
  • The performance of some WFBS 7.0 servers may slow down after a few weeks. (Critical Patch 1357, 1347)
  • Users may experience high CPU resources usage issues when logging on to WFBS 7.0. (hot fix 1359, 1362)
  • Users may experience performance issues when processing Microsoft Office files. (hot fix 1361)
  • If multiple users log on to the same server and one of these users opens the Security Agent user interface, the client user interface of the other users will open too. (hot fix 1362)
  • Users may experience product update issues such as delays, updates occurring earlier than scheduled, and clients that will not update. (hot fix 1365)
  • Users might experience send/relay email issues when sending email messages from the email server. (hot fix 1366)
  • Users may experience the following network drive issues: (1) network drive disconnects or maps to different folders; and (2) remote applications cannot launch after upgrading from previous versions.
  • WFBS 7.0 GM build does not remind users to choose the No option in the pop-up page when they are opening the MSA configuration page. Users are unable to open the MSA configuration page if they select Yes.
  • WFBS 7.0 Live Status might display the status of the Messaging Security Agent engine as outdated after upgrading from version 6.0. (hot fix 1376)
  • When users access files on the network, WFBS attempts to scan floppy drives first, which takes a long time. (hot fix 1377)
  • Users might experience SQL Server performance issues.
  • TmProxy sometimes cannot delete streaming data in the cache located in the ..\20004\tmp directory. (hot fix 1379)
  • Frequent system processes consume kernel memory without releasing these memory resources. This causes system performance to deteriorate over time. (hot fix 1386)
  • Users may encounter performance issues with coreServiceShell.exe. (hot fix 1387)
  • An error that occurs in the application event viewer may cause coreServiceShell.exe to stop unexpectedly. (hot fix 1387, 1394, and 1405)
  • The "LoadLibraryExW Error: 0xc1" log is created in the Amsp_DebugLog.log file when users attempt to install the WFBS client. (hot fix 1395)
  • Users may experience issues that prevent them from installing the WFBS Agent. (hot fix 1395)
  • Adding to the TmProxy whitelist using "Port 0xFFFFFFFF" allows this port activity, but the registry value for this port shows "0x00000000 (block this port activity)". (hot fix 1401)
  • The computer stops responding during an AMSP driver update on Terminal Servers or other servers running a large number of remote desktop sessions. (hot fix 1402)
  • Old OTH virus patterns (Smart Scan) or LPT virus patterns (Conventional mode) might not be removed after new pattern files are downloaded. (hot fix 1406)
  • On the Preferences > Global Settings > Desktop/Server > URL Filtering > URLs to block page, the user interface allows users to specify up to 400 URLs under "Blocked URLs". However, the ofcUFABSLGblIO.dat file in the C:\Program Files\Trend Micro\Security Agent\ directory only allows up to 11 URLs. This enables users to access the 12th blocked URL in the list. (hot fix 1408)
  • Users need administrator privileges to launch AutoPcc to update WFBS 7.0 when the Security Agent is installed. (hot fix 1411)
  • The Security Agent cannot uninstall ESET NOD32 4.0.474.0. (hot fix 1412)
  • Tmevtmgr.sys registers callbacks for post cleanup operations on files. If these callbacks are called at DPC level, where some computers may have limited memory resources and operations, a blue screen of death (BSOD) occurs. (hot fix 1415)
  • After upgrading to WFBS 7.0 from version 6.0, Symantec Backup Exec 12.5 backup tasks may take more time to complete.
  • The Security Agent cannot uninstall the following:
    • Microsoft Security Essentials 2.0
    • Kaspersky Small Office Security
    • Avast! Antivirus 5.0
    • Avast! Antivirus 6.0
    • Norman Virus Control 5.99.0600
    • McAfee VirusScan 2008
    • McAfee Internet Security 2009
    • AVG Internet Security 2011
    • ESET Smart Security 4.0
  • If the Security Agent cannot connect to the Security Server during a scheduled update, the Security Agent will not be updated. (hot fix 1424)
  • Sometimes, ActiveUpdate download tasks slow down and temporary files are left in the %WinDir%\TEMP folder. (hot fix 1423)
  • When connecting to an SMB server hosted by Samba, the client computer slows down or becomes unresponsive.
  • The Microsoft Exchange 2010 Mailbox Server and Exchange 2010 Edge Transport Server folders are not excluded when the "Exclude Microsoft Exchange server folders when installed on Microsoft Exchange server" option is enabled.
  • If scans are stopped manually, decompressed archive files might be left in the ..\Trend Micro\AMSP\temp\virus\ folder.
  • If the scan mode is switched while updating the virus pattern, the virus pattern version number becomes "0.000.000".

Restart Security Agents after installing this patch.

If you are installing this patch on the Security Server with build numbers lower than 1417, the Security Agent will require a restart after installing this patch. Restart Security Agents when the yellow exclamation mark appears in the system tray.

Install add-in for Windows SBS 2011 Standard/Essentials.

After installing this patch, you can install the add-in for SBS 2011 Standard/Essentials. The add-in installers can be downloaded from Preferences > Management Tools in the server console. After downloading the appropriate add-in installer to the target server, double-click on the installer and follow the instructions to complete the installation.

Disable the tray icon

By default, there are multiple tray icons (running UiSeAgnt.exe processes) on the Terminal Server for each RDP connection. This will consume memory resources. To reduce the memory usage on memory-critical computers, administrators can manually set the maximum number of running UiSeAgnt.exe processes in the registry:

  • Key: HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\UniClient\0\Install
  • Name: SeAgntMaxNum
  • Type: REG_DWORD
  • Data: 1
Always back up the whole registry before making any modifications. Incorrect changes to the registry can cause serious system problems.

Restart the Security Agent afterwards.

Check the components and pattern file versions.

After updating, check the Security Agent's components and pattern file version numbers. These can be found in the Security Agent registry below:

  • Key: HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\UniClient\1600\Component
  • Name: <Component or pattern ID>
  • Type: REG_SZ
  • Data: <version number>

The registry can be monitored by third party network management tools.

Trend Micro recommends that you update your scan engine and virus pattern files immediately after installing the product.


When Internet Explorer 9 is installed on the same computer as theSecurity Server, the content of the PDF reports becomes empty.

Workaround: Users can still view the HTML version of reports by clicking the (HTML Version) link on the right side of the report name.


Issue 1: Users may experience slow network performance when the Security Agent is installed on SBS 2011 Standard/Essentials.

Workaround 1: Install the corresponding Microsoft hot fix. Refer to the following article: Slow Network Performance on SBS 2011.

Issue 2: Instant Messenger Content Filtering does not support AIM and MSN2011.


The manual scan process bar is not fully synchronized with the "Files scanned" count-based scan mechanism.

Trend Micro Security for Mac (TMSM)

The Mac Security Agent cannot register to TMSM if the Security Server is installed on SBS 2011.

Install; Update
Solution Id:
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.