What’s New in Windows Group Policy Preferences Debug Logging

Hello again — this is Potti Tagore Nadh from Directory Services team.

When troubleshooting Windows components, administrators often rely on enhanced logging to diagnose issues quickly and accurately. Group Policy Preferences (GPP) provide verbose debug logging capabilities for each client-side extension (CSE). Traditionally, these settings were available only through domain-based Group Policy Objects (GPOs).

With the release of February 2026 preview updates on Windows 11 24H2 and 25H2, this is changing—and it’s becoming much easier. 
Note: When the Server operating system update becomes available, we will update this article accordingly.

What’s New in Windows 11 24H2, 25H2?

GPP Debug Logging Now Available in Local Group Policy

Starting with:

• Windows 11 24H2
• Windows 11 25H2
• And via Windows Updates from February 2026 Preview onward

Administrators can now enable Group Policy Preferences debug logging directly from Local Group Policy—not just domain GPOs.

This enhancement allows troubleshooting directly on client devices without relying on domain controllers, centralized GPO administration or manually moving Administrative Template files.

This is a major quality-of-life improvement for IT pros who frequently debug GPP issues.

Group Policy Preferences Debug Logging – Visual Overview

First, let's start off with some examples of the settings we are talking about.

Figure 1. Group Policy Preferences Debug Logging using Local Group Policy

How to Enable Group Policy Preferences Logging and Tracing using Local Group Policy Editor (Gpedit.msc)

You can enable logging and tracing for each individual preference CSE. These settings allow you to configure:

• What level of events are logged (Informational, Warnings, Errors, or All) (Typically, the most Verbose logging helps pin down difficult issues.)
• Whether trace logging is enabled
• Where trace logs are saved
• Maximum trace file size 

Steps to Configure GPP Logging and Tracing

1. Open Local Group Policy Editor using gpedit.msc.
2. Navigate to:
   Computer Configuration → Policies → Administrative Templates → System → Group Policy → Logging and Tracing
3. Select the desired Preference CSE (e.g., Drive Maps, Files, Shortcuts, Printers).
4. Set the policy to Enabled.
5. Configure:
• Event logging: Informational, Warnings, and Errors
• Tracing: Enabled
• User trace path:
• %COMMONAPPDATA%\GroupPolicy\Preference\Trace\User.log
• Maximum file size: 1024 KB (increase if logs roll over too quickly)
• Computer trace path:
• %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Computer.log
6. Click Apply and OK.

Figure 2. Preference Logging and Tracing Policy Settings

Understanding Trace File Locations

The default trace directory for all GPP CSEs is:

%COMMONAPPDATA%\GroupPolicy\Preference\Trace

While %COMMONAPPDATA% is not a standard Windows environment variable, it is recognized and expanded internally by the GPP CSEs.

Equivalent physical path:

%SYSTEMDRIVE%\ProgramData\Microsoft\

Note: This folder is hidden by default. You can type the path directly into File Explorer.

If you choose a custom folder, Windows requires:

• Full access permissions for the SYSTEM account
• No restrictive ACLs that block service-level writes

Figure 3. Required Permissions for Custom Log Folder

When configuring a custom trace log folder for Group Policy Preferences (GPP) Client‑Side Extensions (CSEs), the SYSTEM account must have Full Control on the directory.

GPP CSEs run under Local System, not the user context.
If SYSTEM lacks permissions:

• Trace files will not be created
• Logging will silently fail

Conclusion

The introduction of Group Policy Preferences CSE logging to client-side Local Group Policy in Windows 11 24H2/25H2 and later is a meaningful upgrade for administrators.

This enhancement:

• Simplifies troubleshooting
• Reduces dependency on domain or GPO administrators
• Provides a more flexible and scalable diagnostic workflow
• Brings client, server-level policy debugging features directly to client devices

If you’re working with Group Policy Preferences regularly, this update will help you analyze issues faster and more independently.

Article for original release of Preference Debug Logging:

Enabling Group Policy Preferences Debug Logging using the RSAT | Microsoft Community Hub