GPRESULT Command Guide - Display Group Policy Results in Windows

The gpresult command is a Windows Command Prompt utility that displays the Resultant Set of Policy (RSOP) for a user or computer—showing which Group Policy settings were applied, from which GPOs, and in what order. Use gpresult /r for a summary or gpresult /h report.html for a detailed HTML report—essential for IT administrators troubleshooting policy application, auditing compliance, and documenting effective configuration for users and computers.

Whether you're diagnosing why a policy isn't taking effect, verifying that a new GPO was applied correctly, or generating compliance reports for auditors, gpresult provides the authoritative view of effective policy. System administrators rely on this command after gpupdate, when troubleshooting "policy not applied" issues, and for documenting configuration across enterprise environments.

This comprehensive guide covers gpresult syntax, all parameters including /r, /v, /z, and /h, practical examples for common scenarios, troubleshooting tips, related commands, and frequently asked questions. By the end, you'll confidently use gpresult to verify and document Group Policy application.

What Is the GPRESULT Command?

The gpresult command queries the Group Policy engine to retrieve and display the effective policy for a user or computer. It shows which Group Policy Objects (GPOs) were applied, their precedence order, and any errors encountered during processing. GPRESULT is the command-line equivalent of the Resultant Set of Policy (RSOP) MMC snap-in.

GPRESULT is available in Windows XP Professional, Windows Server 2003, and all later Windows versions including Windows 10, Windows 11, and Windows Server 2022. It requires read access to the target user or computer; querying remote systems may require domain credentials. The command works in Command Prompt (CMD) and PowerShell.

GPRESULT Command Syntax

gpresult [/s computer] [/u domain\user /p password] [/scope {user|computer}]
         [/user targetusername] [/r | /v | /z] [/h filename] [/x filename] [/f]

Parameters and Switches

Parameter	Description
`/s computer`	Specifies remote computer name or IP
`/u domain\user`	Specifies user context for remote connection
`/p password`	Specifies password for /u (omit to prompt)
`/scope user`	Display user policy only
`/scope computer`	Display computer policy only
`/user targetusername`	Target specific user (for remote /s)
`/r`	Summary of policy (default scope: both)
`/v`	Verbose output
`/z`	Super verbose (all settings)
`/h filename`	Save report as HTML
`/x filename`	Save report as XML
`/f`	Overwrite existing file without prompt
`/?`	Display help information

Parameters in Detail

/r (Summary)

Displays a summary of applied Group Policy. Shows user and computer policy sections, last application time, and which GPOs were applied. Most commonly used for quick verification.

Example: gpresult /r provides a concise overview. Ideal for quick checks after gpupdate.

/v (Verbose)

Displays verbose output with detailed policy information. Includes more settings than /r. Use when /r doesn't provide enough detail.

Example: gpresult /v shows extended policy details. Useful for deeper troubleshooting.

/z (Super Verbose)

Displays all policy settings including those that weren't configured. Produces very long output. Use for comprehensive auditing or when you need to see every possible setting.

Example: gpresult /z outputs all settings. Redirect to file: gpresult /z > policy.txt.

/h (HTML Report)

Saves the report as an HTML file. Opens in browser for easy viewing. Best format for sharing, documentation, and compliance reports.

Example: gpresult /h C:\Reports\policy.html creates a navigable HTML report. Use /f to overwrite without prompt.

/scope user and /scope computer

Limits output to user or computer policy. Use when you only need to verify one or the other.

Example: gpresult /r /scope computer shows only computer policy. Useful when troubleshooting machine configuration.

Examples

Example 1: Summary of Current User and Computer Policy

Scenario: You've run gpupdate and want to verify policies were applied.

gpresult /r

Expected Output: Summary showing user and computer policy sections, last application time, and applied GPOs. Confirms policy refresh completed.

Example 2: Generate HTML Report for Documentation

Scenario: You need to document effective policy for a compliance audit.

gpresult /h C:\Reports\RSOP.html /f

Expected Output: HTML file created in C:\Reports. Open in browser for full report with expandable sections.

Example 3: Verbose Output for Troubleshooting

Scenario: A policy isn't applying; you need detailed information.

gpresult /v

Expected Output: Extended policy details including more settings. Helps identify why a specific policy failed or was overridden.

Example 4: Computer Policy Only

Scenario: You've applied computer-level GPOs and want to verify.

gpresult /r /scope computer

Expected Output: Only computer policy section. Faster than full report when only machine policy matters.

Example 5: User Policy for Specific User

Scenario: Query policy for a different user on the same computer (remote scenario).

gpresult /s SERVER01 /user DOMAIN\jdoe /r

Expected Output: RSOP for jdoe on SERVER01. Requires appropriate permissions.

Example 6: Super Verbose to File

Scenario: Generate complete policy dump for audit or analysis.

gpresult /z > C:\Reports\full_policy.txt

Expected Output: All policy settings written to file. Large output; use file for review.

Example 7: XML Report for Scripting

Scenario: Parse policy data programmatically.

gpresult /x C:\Reports\policy.xml /f

Expected Output: XML file with structured policy data. Use for automation or reporting scripts.

Example 8: Remote Computer with Credentials

Scenario: Query policy on a remote workstation.

gpresult /s WORKSTATION01 /u DOMAIN\admin /p password /h report.html

Expected Output: HTML report for WORKSTATION01. Omit /p to be prompted for password securely.

Common Use Cases

Verify policy after gpupdate – Run gpresult /r after gpupdate to confirm policies were applied correctly.
Troubleshoot "policy not applied" – Use gpresult /v or /h to see which GPOs were applied, precedence, and any errors.
Compliance auditing – Generate gpresult /h reports for workstations and servers to document effective configuration for auditors.
Document baseline configuration – Create HTML reports before and after major changes to track configuration drift.
Identify GPO precedence – When multiple GPOs conflict, gpresult shows which one prevailed and why.
Verify GPO link order – Confirm that GPOs are applied in the expected order from OU hierarchy.
Remote policy verification – Use /s and /u to query policy on remote computers without logging on.
Troubleshoot loopback processing – When loopback is enabled, gpresult shows which user policy (if any) replaced computer policy.
WMI filter verification – If a GPO isn't applied, gpresult can show whether WMI filter excluded the computer.
User policy for specific account – Use /user to see effective policy for a user without logging on as them.
Pre-deployment validation – Run gpresult on a reference machine before imaging to ensure policy baseline is correct.
Post-migration verification – After domain migration or OU move, verify policy application with gpresult.

Tips and Best Practices

Use /h for reports – HTML format is easiest to read and share. Use gpresult /h report.html /f for quick documentation.
Combine with gpupdate – Run gpupdate first, then gpresult to verify. Standard workflow for policy troubleshooting.
Use /scope for faster output – When only user or computer policy matters, use /scope to reduce output and processing time.
Redirect /z to file – Super verbose output is very long. Always redirect: gpresult /z > policy.txt.
Secure credentials – Omit /p when using /u to avoid password in command history. You'll be prompted when needed.
Check Event Viewer – Group Policy events in Event Viewer complement gpresult. Use both for full troubleshooting.
Document GPO names – Include GPO names in change documentation. gpresult shows GPO names; helps trace policy source.
Use /f with file output – /f overwrites without prompt. Essential for automated scripts.
Verify DC connectivity – If gpresult fails for remote computer, check network and firewall. Use nltest for DC connectivity.
Compare before/after – Generate gpresult reports before and after GPO changes to document impact.

Troubleshooting Common Issues

"Access is denied" When Running GPRESULT

Problem: GPRESULT fails with access denied.

Cause: Querying remote computer or different user requires appropriate permissions. Domain admin or local admin on target typically needed.

Solution: Run as Administrator. For remote: use domain admin account or ensure account has admin rights on target. Use /u with elevated account.

Prevention: Document required permissions for remote gpresult. Use service accounts with appropriate rights for automation.

GPRESULT Shows No Policies Applied

Problem: gpresult shows empty or minimal policy application.

Cause: Computer may not be domain-joined; user may not be domain user; DC unreachable; DNS issues; GPO not linked to correct OU.

Solution: Verify domain membership with systeminfo | find "Domain". Check DC connectivity. Run gpupdate /force. Verify GPO link in GPMC.

Prevention: Ensure reliable domain connectivity. Use GPMC to verify GPO links before troubleshooting.

HTML Report Won't Open or Is Corrupt

Problem: gpresult /h creates file but it won't open or shows errors.

Cause: Path may have invalid characters; insufficient disk space; antivirus blocking; file in use.

Solution: Use simple path without special characters: C:\Reports\policy.html. Ensure write permissions. Disable antivirus temporarily if needed. Close file if open elsewhere.

Prevention: Use standard paths. Run from directory with write access.

GPRESULT Shows Old Policy

Problem: gpresult shows policy that should have been changed.

Cause: gpupdate wasn't run; policy cached; GPO not yet replicated; wrong OU.

Solution: Run gpupdate /force. Wait for AD replication. Verify GPO link in GPMC. Check replication with repadmin.

Prevention: Always run gpupdate before gpresult when verifying new policy. Document replication schedule.

Remote Computer Query Fails

Problem: gpresult /s computer fails with RPC or timeout.

Cause: Firewall blocking WMI/RPC; computer off; network unreachable; invalid credentials.

Solution: Ensure Windows Firewall allows WMI on target. Verify computer is on and reachable (ping). Use correct credentials: domain\user format.

Prevention: Ensure firewall rules allow WMI for remote administration. Document remote query requirements.

Related Commands

gpupdate – Refresh Group Policy

gpupdate applies Group Policy. Use gpupdate before gpresult when verifying new policy. They work together: gpupdate applies, gpresult verifies.

When to use: Run gpupdate, then gpresult. See gpupdate command guide.

rsop.msc – Resultant Set of Policy (GUI)

rsop.msc is the graphical RSOP tool. Shows same information as gpresult in MMC format. Use for interactive review.

When to use: Prefer gpresult for scripting and reporting. Use rsop.msc for interactive troubleshooting.

gpmc.msc – Group Policy Management Console

gpmc.msc manages GPOs. Create and edit GPOs here; gpresult shows what was applied. Use Group Policy Modeling for "what if" analysis.

When to use: Edit policy with GPMC; verify with gpresult.

nltest – Domain and DC Diagnostics

nltest verifies domain connectivity. Use when gpresult fails due to DC unreachability.

When to use: nltest /dsgetdc:domainname to verify DC before gpresult.

Frequently Asked Questions

What does the gpresult command do?

GPRESULT displays the Resultant Set of Policy (RSOP)—which Group Policy settings were applied to a user or computer, from which GPOs, and in what order. Use it to verify policy application and troubleshoot "policy not applied" issues.

What is the difference between gpresult /r and /v?

/r shows a summary; /v shows verbose output with more settings. Use /r for quick checks; use /v when you need more detail for troubleshooting.

How do I save gpresult to a file?

Use gpresult /h filename.html for HTML (best for viewing) or gpresult /x filename.xml for XML (for scripting). Add /f to overwrite without prompt.

Can gpresult query a remote computer?

Yes. Use gpresult /s computername to query a remote computer. Add /u domain\user and /p password for credentials. Requires appropriate permissions on target.

How do I see only computer policy?

Use gpresult /r /scope computer for computer policy only. Use gpresult /r /scope user for user policy only.

What does "The processing of Group Policy failed" mean in gpresult?

It indicates a policy processing error. Check Event Viewer (Applications and Services Logs > Microsoft > Windows > GroupPolicy) for details. Common causes: DC unreachable, corrupted cache, DNS issues.

How do I verify a specific GPO was applied?

Run gpresult /r or gpresult /h report.html and search for the GPO name. The report lists all applied GPOs and their precedence order.

Can I run gpresult as a standard user?

Yes, for local policy. Standard users can run gpresult to see their own user policy. Querying computer policy or remote systems may require elevation.

What is the difference between gpresult and rsop.msc?

Both show RSOP. GPRESULT is command-line; rsop.msc is graphical. Use gpresult for scripting, automation, and reporting. Use rsop.msc for interactive review.

How do I get gpresult for a specific user?

Use gpresult /s computername /user domain\username /r to query policy for a specific user on a computer. Requires appropriate permissions.

Quick Reference Card

Command	Purpose	Example Use Case
`gpresult /r`	Summary of policy	Quick verification after gpupdate
`gpresult /v`	Verbose output	More detail for troubleshooting
`gpresult /z`	Super verbose	All settings (redirect to file)
`gpresult /h report.html`	HTML report	Documentation, compliance
`gpresult /r /scope computer`	Computer policy only	Verify machine GPOs
`gpresult /r /scope user`	User policy only	Verify user GPOs
`gpresult /s PC01 /user DOMAIN\jdoe /r`	Remote user policy	Query policy on remote PC

Try the GPRESULT Command in Our Simulator

Practice the gpresult command safely in our Windows Command Simulator. Explore gpupdate for refreshing policy, the Commands Reference for all Windows CMD utilities, and net view for network resource discovery.

Summary

The gpresult command displays the Resultant Set of Policy (RSOP) for users and computers in Windows. Use gpresult /r for a summary, gpresult /v for verbose output, and gpresult /h report.html for a detailed HTML report. Combine with gpresult to verify policy application after gpupdate. Use /scope to limit to user or computer policy, and /s with /u for remote queries. Follow best practices: use HTML for reports, redirect /z to file, and document GPO names for traceability. Master gpresult for effective Group Policy troubleshooting and compliance documentation.