Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted 18 days ago. Aug 05, 2019 - 00:00 UTC
The SEP Cloud client for Windows is updated periodically to provide improvements and defect fixes. The next update is scheduled to start on August 5.
What’s new In this release, the SEP Cloud client for Windows will be updated to version 22.18 to provide an enhanced protection framework and client stability.
Fixed an issue related to the OS feature on the agent, which was randomly failing with a medium severity while applying the Management policy.
Fixed an issue related to the security event: "A process modified a critical system resource." This event was erroneously displayed in the console as a threat detection/remediation event. The event is now removed and will not be displayed in the console.
Enhancement to process HTTP error 429 status code requests The SEP Cloud agent will not attempt to connect with the cloud when the 429 status code is returned, but instead, try to connect based on the timeout information. If the timeout information is not available, then the product will retry to connect in 15 minutes by default.
Impact All Windows devices that are currently enrolled in SEP Cloud will automatically be updated in the background, using LiveUpdate. This update does not affect the security of your devices. To start, the update is distributed to a small set of clients over the first seven days of the release, and then the remaining clients will get the update. If you want to update sooner, you can run LiveUpdate from the Symantec Endpoint Protection Cloud client UI.
Windows device restart All users with Windows devices will be prompted to restart their devices after the update. Even if they delay the restart, their Windows clients remain protected. If no user is logged on the device when the upgrade is made available, then the prompt is provided until the user logs on. The product update will not force the restart of the device.
Windows installation package refresh Administrators who created a Windows installation package before August 5 should create and distribute a new one after August 5 to use for new Windows package deployments.