Padvish Base Change log, 2.10 Series

This page contains the change logs of Padvish Base 2.10 series from the last to the first version, respectively.

Version 2.10.547.9354

1. New capabilities
   • Adding new product type resulting from the integration of the Amnpardaz McAP (Service Desk and Asset Management) and Padvish antivirus
   • Padvish Corporate SD: Padvish Corporate product with Amnpardaz service desk and Asset Management
   • Padvish Corporate AM: Padvish Corporate products along with Amnpardaz Asset Management
   • Padvish Ultimate SD: Padvish Ultimate product with Amnpardaz service desk and Asset Management
   • Padvish Ultimate AM: Padvish Ultimate product with Amnpardaz Asset Management
2. Debugging
   • Fixing a bug showing the status of the previous client upgrade process in the Management Console instead of the recent upgrade process

Version 2.10.520.9249

1. Debugging
   • Troubleshooting the Device Control window freezing if the Internet Download Manager software is installed and setting advanced Device Control rules as “Unauthorized with screen lock” and connecting unauthorized devices to the system
   • Fixing the increasing of the file size of apav_007.dat in the rewards folder under specified conditions
   • Fixing the Anti-malware update to rewrite the Windows version from 2.10.450.9051 to 2.10.4489.9171. Optical Disks were defined and did not apply to optical disks under these conditions.

Version 2.10.509.9219

1. Improvements 
   • Speed up a copy of the file from a shared folder
2. Troubleshooting
   • Fixing the automatic grouping of enterprise versions in Windows 11
   • Fixing the report upgrade version instead of delete in Event Viewer in Application reports
   • Fixing BSOD bug when using RaiDrive software in the presence of Padvish
   • Fixing file leaks when the file is suspected of malware and is selected in the “Ask me” action settings, and the user selects the option to add to the list of exceptions.
   • Fixing Create.temp files if you scan compressed files containing multiple malware
   • Fixing the remaining file bug in the PadvishAV \ Temp folder while scanning the zip file if the zip file extraction failed.
   • Troubleshooting the problem of not displaying the tool control rules in the Windows Padwish user interface when the number of rules is more than 2000.

Version 2.10.490.9175

1. New capabilities
   • Adding the ability to quarantine files that are deleted or deleted during the next boot process
   • Adding hash (SHA256 File) storage capability in quarantine database
2. Improvements
   • Improving the new system UX speed after installing Antivirus
   • Removing the «Transfer to quarantine» button from the Padvish Windows user interface
   • Reducing the occupied disk space by Padvish files and processes?
   • Improving the sending information to the cloud server mechanism
   • Improving the Path Cache mechanism
3. Debugging
   • Debugging the system32 and syswow64 path files incorrectly retrieving on 64-bit operating systems
   • Debugging the duplicate file remaining in the quarantine folder after malware removal in a zip file
   • Debugging not blocking some tools such as optical disk through the tool name in the Device Control, up to 10 seconds after the first tool connection to the system, the tool name is updated
   • Debugging some types of HUAWEI phones were not blocked in Device Control
   • Debugging showing the previous offline client updates date: first, when the flash is connected to the offline client, the client status information was recorded in the flash, and then the update was performed. As a result, the date of the client signature database in the console will not be updated
   • Debugging error when executing Sysprep on the system, if the Padvish Self-Protection feature is enabled
   • Debugging: If there is an rgc file in addition to the installation file during the antivirus upgrade, an additional row was added to the list of computers under the management of the Padvish management server.
   • Debugging Timeout bug when activating a Padvish Management Server client and if Windows communicates with Domain Controller has a problem and lasts too long.
   • Debugging handles leakage problems in removing malware that is uploaded in another process (DLL).
   • Debugging the «Activate» button not working on the «Home» page after resetting the system
   • Debugging the capability to add files to exceptions if exception settings are locked by the Padvish Management Server
   • Debugging User access to all settings if enable the User Password in Padvish Management Console, but none of the access options are enabled
   • Debugging several security reported by security experts. Thanks to Mr. Amir Ahmadi (KingAmir)

Version 2.10.450.9051

1. Improvements
   • The ID extraction method to identify the client on the Padvish management server has changed
   • For more information, you can refer to the list of changes in version 1.16.277. See 5058 Padvish management server
2. Debugging
   • Eliminate the dependence of device name and device ID in advanced rules for controlling tool uppercase and lowercase letters
   • Debugging an issue with incomplete program control information collecting when the setting is off
   • For this purpose at the time of upgrading the version (If the previous version is one of the intermediate versions 2.10.234.7993 to 2.10.360.8918). The collected data file of the reprogram control is created from scratch.
   • Debugging an engine crash OLE Parser
   • If a suspicious file was scanned and the cleanup option was selected at the next boot, and after the boot, another suspicious file was scanned again, the cleanup option at the next boot was disabled this bug was fixed.
   • Enter the Sensitivity intensity fields value and the scan type in the threat report for the threats detected by the registry scan engine, WMIC, and process scanner.
   • Debugging handle leakage under special conditions in the processor scanner. Fixing the bug of not displaying server-side applied firewall policies on the Offline client’s UI.

Version 2.10.386.8918

1. New capabilities
   • Simultaneous connection of multiple Padvish management servers to McAP servers.
   • Adding the Padvish version and icon to the Padvish Uninstaller
2. Enhancement
   • Network card MAC address extraction mechanism
   • Increasing WMIC scan speed
   • A file will not be scanned if it extracted from a compressed file with more than 500 Mb size
   • Enhancing performance on RDS servers
   • Enhancing the performance of the Application Control module
   • Adding “Purple Fox” malware detection to the anti-rootkit module.
3. Debugging
   • Padvish Management Server crashed when sending logs from Padvish 2.10 to Padvish Management server 1.15 or older.
   • In the idle scan corresponding log, the “Deny Access” action was displayed by mistake.
   • If you right-clicked on the “threats” logs of a threat and chose “Run Disinfection for Selected Items”, you will view an empty field for the “Action” field.
   • There was a crash when scanning a compressed file containing a folder named “.”.
   • If you were choosing “Ignore” on scanner settings, then the scanned malware file was deleted by the user in the “Scan Detail” section, and the file size would be zero in “threats” logs.
   • In the idle scan corresponding logs, you were viewing the “User” field empty.
   • If you were choosing the “Ask me” action from “If you are suspicious of the file”, you couldn’t perform the “delete with disinfection” on the heuristic files.
   • If you were decompressing an infected compressed file and Real-Time Protection was detecting it, you will view no logs if you were decompressing it for the second time, despite Padvish detecting it and preventing any access.
   • If immediately, after Padvish activation (in a few seconds), you were restarting the system, it was possible to interrupt the boot process.
   • There was a disruption in Veeam Backup when Padvish was executing
   • In Windows Server 2003, you couldn’t view the Domain name choosing window when logging in to a domain-member client.
   • Windows 11 revision did not display on the list of server management-based client
   • The “The code execution cannot proceed because opengl32.dll was not found” error would be displayed if you were installed Padvish on Windows Server Code.
   • If Padvish repeatedly crashed and we wanted to uninstall it, the uninstallation was not successful, which is fixed by changing the Uninstaller structure.
   • In some of the McAP configuration observer clients, the client information was not returning to Padvish Management Server.
   • If you were editing the “input connection default” and “output connection default” and putting them in the question mode, you will view “outgoing” and “incoming” phrases instead of the program name for each connection, by mistake.
   • When you were activating the single-user license, the “Program Rules” order of the firewall would have changed unintentionally.
   • When defining the advanced rule of device control, if one of the ID values or device names was entered correctly and the other was entered wrongfully, the advanced rule of device control would have been applied to the desired device.
   • If you define an advanced rule for “scanner” and set the “Device Name” on “All” and “Device ID” on “Exactly”, the mentioned rule did not apply to the “scanner”.
   • If you defined two advanced rules for a single device, the second one would not be applied.
   • If you defined a device as trusted and applied the “unauthorized except trusted devices” rule on this device, the device would have been blocked by mistake.
   • Devices that Padvish cannot detect will be classified as unknown devices in the log section.
   • When you were accessing MBR on systems containing fat16 system files, there would be a false alarm.
   • If there were Persian words in the client setting files and you would recover the file, an error would be displayed, and there would be no recovery.
   • Debugging the incorrect UI element uploading in Padvish SE
   • If you were installing Padvish on Windows Server Core without any UI, the Padvish UI process would not be executed.
   • When displaying registry corresponding threat logs, the Padvish UI would be crashed.

Version 2.10.273.8341

1. Enhancements
   • Emerging with the last version of McAP configuration observer.
   • Previously, the MBR Protection was off until the Padvish service booted, but on the new version, it is on.
   • Previously, the Padvish Tamper Protection was off until the Padvish service booted, but on the new version, it is on.
2. Debugging
   • After installing Padvish on Windows Server 2003 due to its excessing processor consumption, the Padvish UI process did not boot
   • In the firewall, when removing an unauthorized rule, it removes the rule in the upper row, by mistake.
   • Padvish icon did not correctly display in Windows 8 and 8.1
   • If you were defining a network rule, choose its decision as “Unauthorized” and enter an IP range in the section of “output address”, accidentally only some of these IPs would have been blocked.
   • If you were defining an advanced rule of “unauthorized by reporting” for a device, setting the “Device Name” field as “Exactly” and connecting an undefined device to the client, this device would have been detected as unauthorized, by mistake.
   • If you were defining an advanced rule of “unauthorized by screen lock” and the rule is applied, then you would edit the rule without removing it and set it on “unauthorized except trusted devices”, the screen would have been locked again.
   • If you set the block rule on devices that are displayed on the “Device Manager” window in device control such as webcam, scanner, printer, etc. you could view the block on the Padvish UI but there would be no blocking.
   • Padvish Icon has not been displayed in the Windows 10 Taskbar due to its colors.
   • Padvish UI was not opening through the Start menu, and you have only opened it through System Tray.

Version 2.10.249.8051

1. New capabilities
   • Adding Windows vulnerability scanning: you can detect the vulnerabilities through these capabilities and view the point of vulnerabilities based on their criticality.
   • Adding the Alternative Data Streams Scan: you can scan all streams of a file and hidden malware through this capability.
   • Adding the automatic backup of the ReFS system file to Padvish DataCop.
   • Preventing any tampering through shared folders.
   • Adding the capability of creating a whitelist in the Web Control module. You can define a list of authorized websites which can block access to addresses out of this list.
   • Emerging and integrating with Padvish Cloud Server.
     • Activating the SANA through Padvish Management Console
     • SANA data is designated with a public key through each client and will send back to SANA URL.
   • New Padvish Cloud addresses are:
     • cloud2.padvish.com
     • cloud2.padvish.ir
   • Adding the license type for the new Padvish Corporate
     • Note: first, to upgrade the Ultimate to Corporate you have to upgrade from the older version of Ultimate to its newest version, then perform the “Change License” task from the Managed Computer section through Management Console to change the Ultimate to Corporate.
2. Enhancements
   • The Device Control performance mechanism is enhanced, and the process consumption rate by this module is decreased.
   • Increasing the security level of the Uninstaller: if it doesn’t have admin access when executing, the error will be displayed, and there will be no uninstallation.
   • Enhancing the disinfection engine performance by decreasing the RAM consumption rate.
   • There is a change in the Command Line Scanner performance mechanism to enhance the malware detection
   • You couldn’t extract the signature of the file when scanning.
   • Enhancing the file copying performance in quarantine by increasing the speed and performance of the quarantine.
   • Previously, you could extract and scan a zip file in the C:/windows/temp path. The scan path of zip files is changed and will extract in the Padvish installation path. This path is protected, and malware cannot infect them.
   • Due to there being no need for device type when sending information to the server and when extracting new devices information, the device type is not extracted.
   • The link of attackers’ blacklist settings moved from AntiCrypto settings to IPS settings.
3. Debugging
   • The oldest Padvish icon is used for the system tray in Windows 7 and older.
   • Some users reported that the Device Control thread is hanging when they set the rule to devices such as disks.
   • The number of the System tray is changed from 1399 to 1400
   • Fixing the possibility of Blue Screen error, if VBS is active in apkhelpher drive
   • Fixing the possibility of Blue Screen error when the file is destroyed through ++notepad
   • After Padvish is uninstalled, the Padvish NDIS driver will have remained on the network card.
   • When Padvish was scanning a file, and the user was excluding it, there would be a crash.
   • If Padvish and Kaspersky were installed on a system at the same time, Kaspersky would detect the .crypto.backup files as malware which it changed to .padvish.backup.stt to fix this problem.