Forum Discussion
Error 65000 with Settings Catalog
Hello Community!
This is my first posting looking for answers. I'm pretty new to Intune and Endpoint Manager. In doing some testing, I have created a configuration profile using the settings catalog. I'm trying to disable the News and Interests from the taskbar. I have applied this to my testing group. Below is a screenshot of the settings I used.
After the policy pushes to the device, it errors out. I get the following Error details for this device. I've tried looking for information on this error with no luck.
Any help would be appreciated!
Duncan
52 Replies
For me, the following setting worked to remove the feature from the taskbar in Windows 11:
Settings Catalog > Windows 11 > Widgets > Allow Widgets = Not allowed
This setting effectively removes the Widgets button (including news feed) from the taskbar.
Look into the event logs under Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostic-Provider > Admin. This can provide more specific details about the error
- having the same with "Daily Recurrent" reboot option.... issue with updated w10 22h2 business so maybe again something that works on pro but not bus
cmendes Check on the target machine in Task Scheduler and see if it did it anyways. I also used the Reboot CSP via Intune and every machine threw a 65000 type 2 error. Every machine was updated to latest build, every machine was missing the feeds file and every machine stilll installed the Reboot policy and rebooted.
I think it throws the error due to the admx (reboot in this case) being missing on initial attempt, then it installs the admx, then it works but the error came first *shrug*
- KentMitchell
Microsoft
If anyone reading this is looking for step-by-step guidance on how to manage organization-owned or bring-your-own-device (BYOD) mobile devices and applications, be sure to review the Intune setup guide in the Microsoft 365 admin center. The setup guide is used to set rules and configure policies needed to protect access to data and networks. This integration improves the effectiveness of device management for devices enrolled and managed through Intune.
Additionally, if you wish to co-manage between Intune and Configuration Manager, visit the Comanage setup guide.
Note: If you don't have Microsoft 365 admin permissions, open the guide in a test or POC tenant to get instructions.
- ???
Why bother to post it in this thread?
Just tested the same setting.. On a windows 10 enterprise device no problems on a windows 11 enterprise device the same 65000 error... I will take a look on whats happening
UPDATE:
You must have installed the April 2021 Cumulative Update Preview (or May 2021 quality update), You can check if the required Feeds.admx. exist by navigating to C:\Windows\PolicyDefinitions and locating the file. If it does not exist... that's your problem
- Hi @rudy, appreciate your suggestion please.
We are also facing multiple errors like 65000 in many settings catalogs especially the browsers settings and browser lock down settings, we see the feed. Admx is present, it's windows 22h2 (22621.307) win 11 enterprise and Purely AAD INTUNE manged devices through user driven autopilot.Sai_Krishna2311 I am in the exact same boat as you. 100% intune managed EntraID, user-enrolled corporate devices running W11 Enterprise (E5 licensing ftw) and seeing this specifically on disabling the News & Interests function too. Same typ2 error, 65000.
Rudy_Ooms_MVP I checked for Feeds.amdx and it does exist on the target machine. I should have specified it is a Windows 10 devices on version 20H2. I did see a log from the error. I attached the full log below. It stated the policy was rejected by licensing. We have M365 Business Premium.
- AHhh... so no enterprise... I am searching the official ms documentation... but it's only working with enterprise when configuring it... what happens when you manually configure the registry keys?
- Hi
I don't know the error code but could you maybe
-CHeck if maybe the policy has applied successfully (so maybe the reporting part failed)
-Checking the intunemgtextension log and the deviceenterprise event log to find if they could give some more information
