Microsoft Intune / Windows Update
Windows Update GPO Conflicts
Detect and remove a limited set of legacy WSUS and update-blocking policy values on approved Windows Update for Business devices. For Windows Pro devices managed with Business Premium alone, use the standalone Platform script. For users with eligible Enterprise, Education, or VDA licensing, the scheduled Remediations option is also available.
The ZIP includes detect.ps1, the standalone cleanup script remediate.ps1, the full deployment guide, and mocked test fixtures. Choose one deployment method below; do not assign both to the same devices. The test file is for local testing only and must not be uploaded to Intune.
Platform script (Windows Pro / Business Premium) · Remediations (eligible Enterprise / Education / VDA licensing)
Before you extract the download
Windows may mark internet downloads with Mark of the Web (MOTW), which can cause PowerShell to block scripts. First inspect the package and confirm that you trust it. If Windows blocks it, right-click the ZIP, choose Properties, select Unblock on the General tab, then select Apply before extracting. Alternatively, run Unblock-File -LiteralPath '.\Windows Update GPO Conflicts.zip' in PowerShell from the download folder. Unblocking removes a Windows security mark; do so only for a reviewed, trusted package and in accordance with your organization's policy.
Deployment at a glance
- Use only on devices approved for Intune/Windows Update for Business updates, not devices intentionally using WSUS or Configuration Manager software updates.
- Resolve or unassign the source GPO or management setting first; otherwise it may reapply the values.
- Configure the scripts to run as SYSTEM in 64-bit Windows PowerShell, and pilot with an approved device group.
- The remediation changes only its allowlisted registry values. A clean result confirms registry cleanup, not Windows Update health.
Option 1: Platform script (Windows Pro / Business Premium)
This is the recommended option for supported Windows Pro devices managed with Microsoft 365 Business Premium alone. Business Premium includes Intune Plan 1 and Windows Business rights for qualifying Windows Pro devices, not Windows Enterprise E3/E5 licensing. It does not by itself meet the additional licensing requirements for Remediations. Devices need the Intune management extension and 64-bit Windows PowerShell. Platform scripts are not exclusive to Windows Pro; they can also be used on supported Enterprise or Education devices.
Download the standalone Platform script (remediate.ps1). This is the same cleanup script used by the Remediations option: it checks, removes only targeted values, and verifies the result in one run. No detection script, companion files, or deployment parameters are required.
- In the Microsoft Intune admin center, go to Devices > Scripts and remediations > Platform scripts > Add > Windows 10 and later. Some portal layouts include Manage devices under Devices.
- Under Basics, enter a name such as Windows Update GPO Conflicts - one-time cleanup.
- Configure the following Script settings.
| Setting | Value |
|---|---|
| Script location | remediate.ps1, not the detection script or ZIP |
| Run this script using the logged on credentials | No (SYSTEM) |
| Enforce script signature check | No for the supplied unsigned script. Choose Yes only after signing through your approved process and establishing publisher trust. |
| Run script in 64-bit PowerShell host | Yes (required) |
- Set your organization's Scope tags, if required.
- Under Assignments, include a dedicated Microsoft Entra device security group of approved 64-bit pilot devices. Exclude intentional WSUS/Configuration Manager devices.
- Select Review + add > Add. Expand to production only after validating the pilot.
- Open the script and check Monitor > Device status (and User status where applicable). Exit 0 means verified clean or no targeted values found; exit 1 means cleanup or verification failed and needs investigation.
No daily schedule: Platform scripts do not provide recurring detection and remediation. Intune normally reruns them only after a script or policy change; Microsoft also documents runs for new users signing in on device-targeted policies. Failures are retried at the next three consecutive management extension check-ins, then retries stop. Remove the source policy first; do not rely on this script to continuously remove settings. If another cleanup is required, investigate the cause and redeploy a reviewed script/policy change.
Do not upload detect.ps1 here: it reports conflicts but does not clean them up. For a local preview only, use .\remediate.ps1 -WhatIf in elevated 64-bit Windows PowerShell after reviewing and unblocking the script.
Option 2: Remediations (additional licensing)
Business Premium alone does not license Remediations. Eligible user licenses include Windows Enterprise E3/E5, Windows Education A3/A5, or Windows VDA per user. Verify the current Microsoft requirements and confirm licensing in Intune before using this option.
Windows edition and license entitlement are separate: Microsoft lists Windows Professional, Enterprise, and Education as supported editions for Intune-enrolled Remediations devices. Remediations are therefore not technically Enterprise-only: Windows Pro can qualify when the user has an eligible license and the device meets the other prerequisites. Conversely, an Enterprise installation alone does not establish licensing entitlement. For Windows Pro with Business Premium alone, choose the Platform script above.
Go to Devices > Scripts and remediations > Remediations > Create script package (some layouts include Manage devices). Enter a name, then configure:
| Setting | Value |
|---|---|
| Detection script | detect.ps1 |
| Remediation script | remediate.ps1 |
| Run this script using the logged-on credentials | No (SYSTEM) |
| Enforce script signature check | No for the supplied unsigned scripts; otherwise use your approved signing and trust process. |
| Run script in 64-bit PowerShell | Yes |
| Assignments | Dedicated approved device security group, pilot first; exclude intentional WSUS/Configuration Manager devices. |
| Schedule | Daily at a suitable time for your approved devices. |
Apply scope tags as needed and select Review + create. Monitor the package's Device status and detection/remediation output. Detection exit 1 triggers cleanup; exit 0 means no targeted values; exit 2 reports an inspection failure and must not trigger cleanup. Use UTF-8 scripts without BOM for either deployment option.