Windows 10: Weird MDM Error after installing KB4598291

So I've never seen this error in Event Viewer before, and it just started happing after installing KB4598291 on Windows 10 20H2 version 19042.789:

Log name: Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin

Source: DeviceManagement-Enterprise-Diagnostics-Provider

Event ID: 406

Error: MDM PushRouter: Pushrouter failed to start because the dmwappushservice service is disabled.

Okay... this is on my home PC running Windows 10 Pro, so I'm not joined to a domain, nor do I use MDM or even the Phone app in Settings - let alone any other software for mobile devices and managing them. Also, the dmwappushservice is NOT disabled, but is set to Manual (trigger start).

I've ran gpedit.msc and disabled the MDM options there and it still randomly pops up. Also, I've done a search in the Registry for MDM PushRouter and Pushrouter but couldn't find anything meaningful.

Of course, googling this event ID and specific error isn't showing jack squat, so I'm not sure what's going on other than it's a new bug with this KB.

Anyone else getting this and/or have seen this before?

:)

 

Getting this error on everything

I'd suggest installing the latest directX.

Other than that, weird errors like that would make me want to format too.

 

Linux Noob - Ubuntu fails on install GRUB error 2

Did you burn the image on the slowest setting possible? Pop your disc in and try checking the disc for errors (booting from the disc). If it has an error on it then you have a bad install.

I just googled your motherboard and ubuntu... This thread is on the list. XD

If it's a bad install I'd suggest a different version of Ubuntu or to try Fedora instead. I had nothing but trouble with 8.04.

Also, try your connections. Sounds stupid but maybe the CD sent it and the hard drive couldn't get it or some weird thing like that. (Talking out my rear end now, but it's worth a shot)

Sorry I couldn't help more. *Frown

 

MDM on Windows 10: Office 365 installation unenlightened

MDM Enrollment

We are deploying MDM. All users have the same license assigned.

New equipment with Windows 10 Enterprise

Some Devices simply refuse to enroll in MDM and enroll in MAM instead

Devices are Hybrid AD joined. Some of these machines work beautifully and all our apps become enlightened

Every time a work file is opened in Outlook, regardless of type this is received





Exclusion policies make no difference, checking Enterprise context simply lists Personal. On the machines, where the MDM enrollment works the same apps (same version etc.) are listed as enlightened.

Event Viewer is of no help, some of the machines enroll and never list into Endpoint Device Management

...