Maximum Application Log Size
Sets the maximum size of the Application event log.
- Policy path
- Computer Configuration > Windows Settings > Security Settings > Event Log
- Supported on
- Windows 10, Windows 11, Windows Server 2016 and later
Sets the maximum size of the Application event log. Security baselines recommend setting it to 256 MB or larger.
Description
Maximum Application Log Size is a Windows Group Policy setting located under Computer Configuration > Windows Settings > Security Settings > Event Log. It applies to the Computer Configuration branch and is classified as a Informational-level policy in the Event Log category.
Sets the maximum size of the Application event log.
Microsoft sets the default value to 20 MB while industry security baselines (CIS, NIST, DISA STIG) recommend 256 MB or larger.
Under the hood, this policy is enforced through the Windows registry at HKLM\System\CurrentControlSet\Services\EventLog\Application using the value name MaxSize. Modifying the value directly through regedit.exe or PowerShell produces the same effect as configuring the GPO, but going through Group Policy is preferred so that the setting is centrally managed and survives reboots, image rebuilds, and policy refresh cycles.
In-depth explanation
This is primarily an operational or user-experience setting. It does not directly raise or lower the security posture, but it standardizes behavior across the fleet, which is important for predictable support, training, and troubleshooting in an MSP-managed environment.
The policy is grouped under Event Log, which means it is typically applied through a domain-wide GPO linked at the OU level. In a multi-tenant MSP context, scope it through WMI filters or security group filtering rather than linking at the domain root, so that you can roll out progressively (pilot OU → wider rings → all production).
The setting takes effect after the next Group Policy refresh (gpupdate /force for immediate testing, or by default within ~90 minutes for workstations and ~5 minutes on domain controllers). For computer-side policies a reboot may be required; for user-side policies, a sign-off/sign-on cycle is enough.
Use cases
- Apply organization-wide hardening of event log on all domain-joined Windows endpoints.
- Roll out a CIS Benchmark-aligned baseline targeting 'Maximum Application Log Size' via a dedicated GPO.
- Reduce attack surface for accounts that handle privileged credentials or sensitive data.
- Standardize the configuration across multiple customer tenants for an MSP-managed fleet.
Security implications
This control is primarily about consistency and supportability rather than security. The main risk of leaving it unconfigured is divergence between machines, which makes troubleshooting and standardized imaging harder, especially across multiple customer tenants in an MSP context.
How to configure
- Open Group Policy Management Console (
gpmc.msc) on a domain controller or a workstation with RSAT installed. - Create or edit a GPO linked to the OU containing the target computer configurations. We recommend a dedicated baseline GPO (e.g. SEC – Event Log) instead of editing Default Domain Policy.
- Navigate to
Computer Configuration > Windows Settings > Security Settings > Event Log. - Open Maximum Application Log Size and set it to
256 MB or larger. - Click OK and close the editor.
- On the target endpoint, run
gpupdate /force(or wait for the next refresh cycle), then verify withrsop.mscorgpresult /h report.html.
Direct registry path: HKLM\System\CurrentControlSet\Services\EventLog\Application\MaxSize. You can apply the same change with PowerShell:
New-Item -Path 'HKLM\System\CurrentControlSet\Services\EventLog\Application' -Force | Out-Null
Set-ItemProperty -Path 'HKLM\System\CurrentControlSet\Services\EventLog\Application' -Name 'MaxSize' -Value <value> -Type DWordRegistry mapping
HKLM\System\CurrentControlSet\Services\EventLog\ApplicationMaxSizeREG_DWORD256 MB or larger20 MB