Windows Script disappeared

Question

{ "shellProps": { "sessionId": "5e2e1d2139b941c982cc6f0cd14a0437", "extName": "Microsoft_Intune_DeviceSettings", "contentName": "ConfigureWMPolicyMenuBlade", "code": 404 }, "error": { "message": "Not found", "code": 404 }}

That's all what I have :)

Answer 1

I have the same issue. Platform scripts have disappeared with error 404 Not Found. Can't access them from graph API too.

Answer 2

The 404 error with extName": "Microsoft_Intune_DeviceSettings" and contentName": "ConfigureWMPolicyMenuBlade" indicates that the Intune portal blade or resource being requested no longer exists or cannot be found.

In similar cases, a 404 in a management or security portal typically means one of the following:

1. The feature or blade has been removed, renamed, or relocated in the admin UI.
2. The underlying resource (such as a script or policy object) was deleted.
3. The URL or navigation entry is stale and points to an old location.

For Intune PowerShell scripts and device configuration:

1. Verify the script or policy still exists
   • In the Intune admin center, go to Devices → Scripts (for PowerShell scripts) or the relevant configuration area.
   • Confirm the script/policy object is listed and not deleted.
2. Check script policies and assignments
   • Under PowerShell scripts, confirm the script policy is present and assigned.
   • Use Monitor → Device status or User status to ensure the script is still recognized and running as expected.
3. Recreate the script or policy if missing
   • If the script/policy is gone, recreate it:
     • Upload the PowerShell script again.
     • Configure properties such as runAsAccount, executionFrequency, and retryCount.
     • Assign it to the appropriate groups.
4. Confirm device-side behavior
   • If the concern is that the script “disappeared” from devices, validate via Intune Management Extension logs and, if needed, test locally using the documented method (for example, running the script under the System account using psexec -i -s) to ensure the script itself still works.

If the blade or feature has been retired or moved, use the main Intune navigation (Devices → Configuration, Scripts, or Endpoint security) instead of relying on old bookmarks or deep links, as those can produce 404 errors even when the feature is still available under a different path.

---

References:

• Use PowerShell Scripts on Windows Devices in Intune
• deviceShellScript resource type
• "HTTP 404 - File not found" error

AI-generated content may be incorrect. Read our transparency notes for more information.