Release Notes

Easy2Patch 4.0.5 - Release Notes (‎Thursday, ‎May ‎15, ‎2025 8:21:46 AM)

  • Resolved Duplicate Deployment Issues in SCCM Tracking Addressed an issue where applications were being resent due to corrupted or faulty SCCM tracking scenarios. This ensures more accurate deployment tracking and prevents redundant deployments.

  • Silent Install Parameter Inheritance Resolved

    A long-standing issue where the silent installation parameter was not correctly inherited by newly published packages has now been resolved.

    • All packages published via Easy2Patch 4.0 will now retain the defined silent install arguments consistently across updates and new versions.

    • This fix ensures more reliable unattended deployments in both SCCM and Intune environments.

  • Major Performance Improvements Significant performance optimizations have been implemented in the core update engine:

    • Faster metadata processing and publishing workflows

    • Improved responsiveness in large catalogs with hundreds of products

    • Reduced load times and memory usage in the UI and backend services

Easy2Patch 3.1.14 - Release Notes (‎Tuesday, ‎May ‎13, ‎2025 2:36:55 PM)

  • Resolved Duplicate Deployment Issues in SCCM Tracking Addressed an issue where applications were being resent due to corrupted or faulty SCCM tracking scenarios. This ensures more accurate deployment tracking and prevents redundant deployments.

Easy2Patch 3.1.13 - Release Notes (‎Monday, ‎May ‎5, ‎2025 6:51:38 PM)

Improvements and Fixes

  • Enhanced Auto-Update Configuration The automatic update functionality has been redesigned based on the Easy2Patch MSI package. After updating to this version, users can optionally enable the Auto Self Update feature from Settings > General Settings. When activated, Easy2Patch will automatically update itself when a new version is released.

  • Fixed Random SUSDB Update Prompts Intermittent warnings related to "update failed" in SUSDB have been resolved. These were caused by database access delays and bottlenecks. Performance optimizations have been implemented to eliminate this issue and improve overall database responsiveness.

Last updated

Was this helpful?