What's new in Faronics Anti-Executable Enterprise 5.51.2100.659
Dec 6, 2018
- Fixes:
- 24487 Resolved an issue where the keyboard and mouse stop working when Secure Boot is enabled. (Case No. RAV-194-37077, OJE-634-70524, TWN-216-31782)
- Known Issues:
- 3668 Newly created Policy should not have Files / Publishers / Folders pre-populated from the Default Policy.
- 4703 Filter is not available for blank Publishers on Central Control List and policy.
- 4704 On Policy details dialog, Alert node “Block notification message” box is overlapped on “Please wait…” message.
- 5408 Multiple confirmation prompts while adding multiple files to the Control List.
- 6237 When Faronics Core Service is restarted, the Anti-Executable Loadin DLL is not loaded properly.
- 6689 Same Domain/Local user can be added twice into the “AE Trusted” users list.
- 7385 AE and VMPlayer compatibility, sometimes BSOD after installation of Anti-Executable. (Case No. PUG-523-40514)
- 7611 Anti-Executable Enterprise uninstaller typo. (Case No.EAE-176-60020)
- 24515 Under Publishers, Faronics Core gets added under Microsoft Corporation.
New in Faronics Anti-Executable Enterprise 5.50.2100.655 (Sep 21, 2018)
- New Features:
- Monitor VB and PowerShell Scripts – monitor the execution of .vbs and .ps files and block execution of all unauthorized scripts.
- Ability to automatically update the Faronics Code Signing Certificate and any other certificate thumbprints on the fly.
- Ability to add bin files to whitelist AE
- Fixes:
- Resolved an issue where Anti-Executable makes network applications perform slowly. (Case No. CNR-391-54465)
- Resolved an issue where Anti-Executable is unable to display accents in the alert. (Case No. VWE-767-93274)
- Resolved an issue where DLL files are not being added during Maintenance Mode initiated from the Core Console despite DLL scanning being enabled in the policy. (Case No. DJG-156-61013)
- Resolved an issue where BSOD caused Anti-Executable whitelist to revert to blank. (Case No. SFI-268-52300)
- Resolved an issue when Anti-Executable service is hanging on machine start-up if Local Execution list has more that 10K entries in it. (Case No. DKF-906-85852)
- Resolved an issue where OpenOffice is unable to launch (bin files blocked) after Anti-Executable is installed. (Case No. SMM-711-78721)
- Resolved an issue where Anti-Executable is causing random BSOD when switching into Maintenance mode. (Case No. VXC-558-50345)
- Known Issues:
- Newly created Policy should not have Files / Publishers / Folders pre-populated from the Default Policy.
- Filter is not available for blank Publishers on Central Control List and policy.
- On Policy details dialog, Alert node “Block notification message” box is overlapped on “Please wait…” message.
- Multiple confirmation prompts while adding multiple files to the Control List.
- When Faronics Core Service is restarted, the Anti-Executable Loadin DLL is not loaded properly.
- Same Domain/Local user can be added twice into the “AE Trusted” users list.
- AE and VMPlayer compatibility, sometimes BSOD after installation of Anti-Executable. (Case No. PUG-523-40514)
- Anti-Executable Enterprise uninstaller typo. (Case No.EAE-176-60020)
New in Faronics Anti-Executable Enterprise 5.40.2100.631 (Apr 3, 2017)
- New Features:
- Support for Windows 10
- Known Issues:
- Newly created Policy should not have Files / Publishers / Folders pre-populated from the Default Policy.
- Filter is not available for blank Publishers on Central Control List and policy.
- On Policy details dialog, Alert node “Block notification message” box is overlapped on “Please wait…” message.
- Multiple confirmation prompts while adding multiple files to the Control List.
- When Faronics Core Service is restarted, the Anti-Executable Loadin DLL is not loaded propery.
- Same Domain/Local user can be added twice into the “AE Trusted” users list.
New in Faronics Anti-Executable Enterprise 5.33.2100.621 (Nov 2, 2015)
- Fixes:
- 12008 Resolved an issue where Anti-Executable did not block programs running with OutPost Firewall Pro installed. (Case No: KDU-654-76952)
New in Faronics Anti-Executable Enterprise 5.30.2100.606 (Nov 2, 2015)
- New Features:
- Support for Windows 8.1
- Note: Support for Identifile discontinued.
- Fixes:
- 9761 Resolved Anti-Executable Policy modification error. (Case No: PQF-859-10766)
- 7313 Resolved an issue when initiating a Local Control List Scan where executables from the mounted StorageSpace were not added to control list.
New in Faronics Anti-Executable Enterprise 5.20.2100.562 (Aug 24, 2013)
- New Features:
- Support for Windows 8.
- Support for Windows Server 2012.
- Ability to open the log file directly from the UI.
- Anti-Executable is now available in Portuguese (Brazilian).
- Fixes:
- 4453 – Resolved an issue where, after adding the sysvol and netlogon folders to the Central Control List, login scripts were still being blocked.
- 5392 – Resolved an issue on standalone Faronics Core Console: if Anti-Executable Loadin was upgraded from previous release to 5.10, new reports were generated empty.
- 5404 – Resolved an issue where an incorrect report name was displayed while report was being generated.
- 6125 – Resolved an issue where Scan Progress Bar during installation did not show detailed information as it is shown when scanning files from the Anti-Executable UI.
- 6171 – Resolved an issue where deadlock exception occurred in Anti-Executable ReportingDatabaseHandler and related memory leak in Anti-Executable Loadin.
- 6238 – Resolved an issue where it was not possible to apply Anti-Executable policy to machines. (Case No: WEK-333-34999)
- 6571 – Resolved an issue where on applying “Initiate local ECL Scan” from Faronics Core, Anti-Executable Engine service hangs and files added to local ECL are not displayed.