This is a service that I decided to disable.
For some reason, it will not stay disabled.
It reverts back to the Startup Type of Manual (Trigger Start).
I've never had this type of problem with any service that I have disabled. Could someone tell me why this happens and what I can do to keep it disabled? Thanks...
It's the usual thing. Microsoft uses a malware technique,
just like tag team wrestlers in a ring. You try to disable
a service, a "boss process" comes up behind you and hits
you over the head with a chair. Classy.
On 8/25/2023 11:43 AM, AllanH wrote:
This is a service that I decided to disable.
For some reason, it will not stay disabled.
It reverts back to the Startup Type of Manual (Trigger Start).
I've never had this type of problem with any service that I have disabled. >> Could someone tell me why this happens and what I can do to keep it disabled?
Thanks...
Claimed to be Win10 only, and should be manual.
https://batcmd.com/windows/10/services/dmwappushservice/
It's the usual thing. Microsoft uses a malware technique,
just like tag team wrestlers in a ring. You try to disable
a service, a "boss process" comes up behind you and hits
you over the head with a chair. Classy.
https://www.tweakhound.com/2021/03/18/oo-shutup10-issue/
"I check the Error Log and find:
Error Event ID 406 Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider
MDM PushRouter: Pushrouter failed to start because the dmwappushservice service is disabled.
"
This is related to Mobile Device Management (MDM) and InTune. Maybe the automation you see, is in Win10 Pro ? They were presumably testing
this Enterprise feature, in end-user PCs. Pushing out policies via it,
is similar to GPEDIT (a Pro feature, for IT Enterprise control of end-users).
There is no structure in Enrollments, that matches a description here.
https://answers.microsoft.com/en-us/windows/forum/all/event-2545-microsoft-windows-devicemanagement/a7e0f8e9-685f-44d8-be69-58fd1f8a716e?page=6
Go to HKLM\Software\Microsoft\Enrollments
Delete the key referencing the MDM.
Delete the key referencing WMI_Bridge_SCCM_Server
gpupdate /force
But that could be on an Enterprise machine. The Enrollments on my VM
are just GUIDs. And none of them is "special looking". What would
happen if you killed every entry in the Enrollments ? Hmmm.
Could we stop the service, disable it, then
sc delete servicename
I suppose that would last until Patch Tuesday. Or... less.
Maybe there would be a "permissions issue", a need to elevate
as TrustedInstaller. Which is not an insurmountable problem.
Windows TagTeamWrestlers do not normally re-run installers,
so we have that working for us. A DISM restorehealth might
repair damage from a user-hammering.
Paul
On 8/25/2023 11:43 AM, AllanH wrote:
This is a service that I decided to disable.
For some reason, it will not stay disabled.
It reverts back to the Startup Type of Manual (Trigger Start).
I've never had this type of problem with any service that I have disabled. >> Could someone tell me why this happens and what I can do to keep it disabled?
Thanks...
Claimed to be Win10 only, and should be manual.
https://batcmd.com/windows/10/services/dmwappushservice/
It's the usual thing. Microsoft uses a malware technique,
just like tag team wrestlers in a ring. You try to disable
a service, a "boss process" comes up behind you and hits
you over the head with a chair. Classy.
https://www.tweakhound.com/2021/03/18/oo-shutup10-issue/
"I check the Error Log and find:
Error Event ID 406 Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider
MDM PushRouter: Pushrouter failed to start because the dmwappushservice service is disabled.
"
This is related to Mobile Device Management (MDM) and InTune. Maybe the automation you see, is in Win10 Pro ? They were presumably testing
this Enterprise feature, in end-user PCs. Pushing out policies via it,
is similar to GPEDIT (a Pro feature, for IT Enterprise control of end-users).
There is no structure in Enrollments, that matches a description here.
https://answers.microsoft.com/en-us/windows/forum/all/event-2545-microsoft-windows-devicemanagement/a7e0f8e9-685f-44d8-be69-58fd1f8a716e?page=6
Go to HKLM\Software\Microsoft\Enrollments
Delete the key referencing the MDM.
Delete the key referencing WMI_Bridge_SCCM_Server
gpupdate /force
But that could be on an Enterprise machine. The Enrollments on my VM
are just GUIDs. And none of them is "special looking". What would
happen if you killed every entry in the Enrollments ? Hmmm.
Could we stop the service, disable it, then
sc delete servicename
I suppose that would last until Patch Tuesday. Or... less.
Maybe there would be a "permissions issue", a need to elevate
as TrustedInstaller. Which is not an insurmountable problem.
Windows TagTeamWrestlers do not normally re-run installers,
so we have that working for us. A DISM restorehealth might
repair damage from a user-hammering.
Paul
On 8/25/2023 11:43 AM, AllanH wrote:
This is a service that I decided to disable.
For some reason, it will not stay disabled.
It reverts back to the Startup Type of Manual (Trigger Start).
I've never had this type of problem with any service that I have disabled. >> Could someone tell me why this happens and what I can do to keep it disabled?
Thanks...
Claimed to be Win10 only, and should be manual.
https://batcmd.com/windows/10/services/dmwappushservice/
It's the usual thing. Microsoft uses a malware technique,
just like tag team wrestlers in a ring. You try to disable
a service, a "boss process" comes up behind you and hits
you over the head with a chair. Classy.
https://www.tweakhound.com/2021/03/18/oo-shutup10-issue/
"I check the Error Log and find:
Error Event ID 406 Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider
MDM PushRouter: Pushrouter failed to start because the dmwappushservice service is disabled.
"
This is related to Mobile Device Management (MDM) and InTune. Maybe the automation you see, is in Win10 Pro ? They were presumably testing
this Enterprise feature, in end-user PCs. Pushing out policies via it,
is similar to GPEDIT (a Pro feature, for IT Enterprise control of end-users).
There is no structure in Enrollments, that matches a description here.
https://answers.microsoft.com/en-us/windows/forum/all/event-2545-microsoft-windows-devicemanagement/a7e0f8e9-685f-44d8-be69-58fd1f8a716e?page=6
Go to HKLM\Software\Microsoft\Enrollments
Delete the key referencing the MDM.
Delete the key referencing WMI_Bridge_SCCM_Server
gpupdate /force
But that could be on an Enterprise machine. The Enrollments on my VM
are just GUIDs. And none of them is "special looking". What would
happen if you killed every entry in the Enrollments ? Hmmm.
Could we stop the service, disable it, then
sc delete servicename
I suppose that would last until Patch Tuesday. Or... less.
Maybe there would be a "permissions issue", a need to elevate
as TrustedInstaller. Which is not an insurmountable problem.
Windows TagTeamWrestlers do not normally re-run installers,
so we have that working for us. A DISM restorehealth might
repair damage from a user-hammering.
Paul
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 297 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 04:57:23 |
| Calls: | 6,666 |
| Files: | 12,213 |
| Messages: | 5,335,947 |