VCS vSphere – Check new notifications stuck on Queued – VMware vCenter Update Manager Check Notification
So if you have a bunch of queued items in your VMware vSphere Client Recent Tasks that say “Check new notifications” initiated by “VMware vCenter Update Manager Check Notification“, there is an easy fix. Here’s what it looks like:
To fix, all you have to do is restart the VMware vCenter Update Manager Service on your VCS server. See below:
You can also do a “net stop vmware-ufad-vci” then a “net start vmware-ufad-vci” as well. Let me know if this works out for you! 
Thanks for the tip! Restarting that service cleared it up.
I hit this one too. Thanks for the post!
Don’t forget to use PowerCLI to cancel all of the open tasks:
get-task -status queued | stop-task
Moi aussi. Although when I attempted to restart the service, I got an error 1067. I rebooted the vCenter server and all was well. (this coincided with a need for Windows Activation and an admin password change – been a while since I was using the lab!)
Thanks! This solved my problem as well, they all cleared up after this.
That worked great without a reboot. I like no reboot!!!
So how long after restarting the service have people noticed the queued messages go away?
Thanks — it worked for me, too! I appreciate the tip! I didn’t check it for a little while (maybe a half hour or so), but they were all gone by then!
Thanks worked for me too!
Yeah it works also for me
Bloggers rulez the planet 
Likely you can combine the two commands like so: “net stop vmware-ufad-vci && net start vmware-ufad-vci” to do it in one shot.
So many sites listed this as a fix. Just wanted to state that I was able to track this down to our vCenter server IP address changing. Long story short I tracked it down due to some other errors I was seeing. I added the old address so that the vCenter Server had both the new and former addresses (both on the same subnet) and this task finally completed.
I suspect it had something to do with an SSL cert but I’m still trying to untangle that. vCenter works without that nagging error and we’ll go back and find out what went wrong when we changed the IP.
Worked like a charm. We created a new vCenter and imported the old data but had changed the IP address so this might be a valid reason.