Does anyone know how to disable UpdateNotificationMgr.exe UNP Task?

I've stumbled across this today for the first time. https://www.askvg.com/what-are-updat...in-windows-10/

The problem is that when I try to disable UNP \Microsoft\Windows\UNP I get The user account you are operating under does not have permission to disable this task.

Neither PSTools is working. When I try to execute PSTools using CMD as Admin I get Error establishing communication with PsExec service on.......:
The network path was not found.

In the past PSTools was working for me, but not any more. I do have Windows 10 Update Blocker. So I have the rest disabled. UNP was the first time I have spotted it running in the background briefly.

I'm pretty sure Windows 10 Updates will not be affected even if this task schedule was disabled. I've had Windows 10 updates disabled for the last 9 months since disabling them using an Update Blocker. But this is the first time I've stumbled across the UNP task schedule.

I tried SFC /Scannow now and get Windows Resource Protection did not find any integrity violations.

Windows 10 has never allowed me to delete or disable a Task Schedule normally without using PSTools! If someone knows how to overcome this I'll be very grateful!

My Windows 10 version is 1903 (OS Build 18362.720).

- - - Updated - - -

Problem solved! Just found a solution to disable the Universal Notification Pipeline schedule.

First of all, you need to download the Windows Update Blocker tool. Windows Update Blocker v1.6
In the Wub folder open Wub.ini file, open this with notepad and then add UNP=1 in [TaskScheduler_List] and then RunUpdateNotificationMgr=2,4 in the [Service_List]

After that you simply Open Windows Update Blocker tool and press the Apply Now button to reconfirm this change.

Then return back to your Task Scheduler and disable the task normally and like Magic the Task Schedule for UNP is now disabled!

It turns out this is much simpler than one could imagine. Without this tool it is impossible to manually disable the task scheduler yourself even with Administrator account. Windows is programmed to not let you, unless you use PSTools or the Windows Update Blocker tool.

If you want Windows Update again, no problem. Simply open Wub again and press Enable Updates and Windows update will work again. And after you're done updating Windows 10 you can disable it using the blocker tool again and you're good to go.

Paul Black said:

Hello @BLaZiNgSPEED,

I looked at this yesterday and did some investigating for you and found the link below, but I haven't been able to post it until now. BUT, I have just seen that you have found a solution. Anyway, here is the link that might help others visiting this thread that have the same problem and are looking for an answer . . .

> What are UpdateNotificationMgr.exe, UNPUXLauncher.exe, UNPUXHost.exe Files and UNP Folder in Windows 10?

I hope this helps someone.

Yes, I posted that same link in my topic. In fact, I even posted the solution to AskVG comment section. But seems like my posts haven't been approved there yet.

Btw, I am wrong to include RunUpdateNotificationMgr=2,4 in the [Service_List]

As this is not a service, but more of a Task Schedule. You only need to include UNP=1 in [TaskScheduler_List]

But if you enable Windows Update again, I believe UNP will need to be temporarily re-enabled. I'm not sure if Windows will update successfully with this task schedule disabled.

I spotted this running 2 days when when my Waterfox Web Browser was not closing properly after closing the browser. Basically I was clicking on a shortcut web icon and Waterfox was saying that it was already running, so it didn't close. As soon as I opened Task Manager, I spotted UpdateNotificationMgr.exe running in the background! That gave me clues that it was this causing my Waterfox web browser to be slow. When it finishing the task then the browser closed normally without me having to end it.

And this is when I found out in Task Scheduler that this was running at exactly 7:44pm on the 11th December 2 days ago. It is an every day brief task that happens by schedule. Most people will not notice it, just as I didn't all these months, but it is unnecessary for it to be scanning, just like with the Windows Update scanning, it will search for updates even when Windows 10 is up to date.

I know this is an old thread. But I'm posting a warning to this. That when I tried to do this, it didn't work. And also it caused a BSOD upon windows start up than it would reset itself and then go to a BSOD. Basically an infinite boot loop. Luckily I had a restore point 2 hours before this happened.


I added the line

UNP=1

To the Wub.ini file under
[TaskScheduler_List]


Like this:

[TaskScheduler_List]
; 0=Without Action
; 1=Enable Task
; 2=Disable Task
Microsoft\Windows\WindowsUpdate\*=1,2
Microsoft\Windows\UpdateOrchestrator\Schedule Maintenance Work=0,2
Microsoft\Windows\UpdateOrchestrator\Schedule Wake To Work=0,2
Microsoft\Windows\UpdateOrchestrator\Schedule Work=0,2
Microsoft\Windows\UpdateOrchestrator\*=1,2
Microsoft\Windows\WaaSMedic\PerformRemediation=1,2
UNP=1


I selected
Disabled Updates (by the way for some reason my windows updater according to this program is running even though I
disabled it through the registry a while back)

Protect services settings. And I clicked apply now.
It didn't really notify me of the changes I put in the Wub.ini
So I just clicked apply now.


okay so now I go into the Task Scheduler
I go to the Windows folder then I find UNP.
I click on the folder and to the right I click
on "RunUpdateNotificationMgr"
I try to disable and it says you can't do this under this account.

So I figure It would try

RunUpdateNotificationMgr=2,4 in the [Service_List]


I Run the Windows Update Blocker and click apply the changes. There was no notifications to appear ever about changing lines in the ini file.

So I go to to task scheduler I find the UNP folder. I try to disable it and it doesn't let me. So I look around the internet for some more advice. It says you can delete it. So I delete it. So I want to do a restart to make sure the changes do the same. The end result is I encounter a BSOD before I can even make it to login. I get CRITICAL_PROCESS_DIED. And it just restarts and loops infinitely until you get to recovery page. Which lucky for me, the computer had made a restore point for me 2 hours before this happened.

This is what I get according to Windows Debugger tool.

FAILURE_ID_HASH_STRING: km:0xef_services.exe_bugcheck_critical_process_5f9f0700_nt!pspcatchcriticalbreak

I think its related to Windows Update Blocker v1.7. Although I don't know if it was because I was adding the codes to the Wub.INI file or disabling updates was the trigger itself. Anyways, the result it didn't work and it caused a BSOD for me, so becareful.