--- title: "July 2018 - Windows Agent 4.16" slug: "july-2018-windows-agent" description: "Enhanced stability for APM, optimized app change detection, added .NET Core support in AWS Elastic Beanstalk. Bug fixes and more. Learn details in our documentation." updated: 2018-09-13T13:39:30Z published: 2018-09-13T13:39:30Z canonical: "docs.stackify.com/july-2018-windows-agent" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.stackify.com/llms.txt > Use this file to discover all available pages before exploring further. # July 2018 - Windows Agent 4.16 ## Release Overview **Release Date: 7/25/2018** **Improved Stability around APM Related Issues** Improvements were made around how the profiler performs, specifically around handles async requests. This should enhance overall stability in profiling application requests. **New Support for .NET Core hosted in AWS Elastic Beanstalk** Documentation has been updated to include support for .Net Core: [https://docs.stackify.com/v1/docs/aws-installation-windows-aws-elastic-beanstalk-net-deployment](https://docs.stackify.com/v1/docs/aws-installation-windows-aws-elastic-beanstalk-net-deployment) ## Release Enhancements **Optimized App Change Detection** - App change detection has been optimized to improve overall performance in the agent **Minor Updates to the App Service Site Extension, Stackify Middleware, and Stackify Module** - Site Extension: changes were made to support Azure’s new format. Added some configurability support - Middleware/Module: Added some changes to allow support for future new features coming soon. **Added Support for Handling Cloud Service Scaling Events** - Support for Auto-removal of Servers in Retrace when an EC2 (or EBS) Instance scales down. See: [https://docs.stackify.com/v1/docs/auto-scaling-with-aws](https://docs.stackify.com/v1/docs/auto-scaling-with-aws) ## Bug Fixes - Fixed an issue with parsing MySQL stored procedure calls in the profiler - Addressed an issue in the profiler related to Async requests - Fixed a bug with overriding App Name for Services - Removed ACS authentication logic in the agent so it uses the preferred SAS method - Fixed a couple issues around AppName overrides configured in configuration files, namely for Java Web Apps and Windows services ## Known Issues - None at this time