Update pending verification

Question

_{Tuesday, December 1, 2015 10:56 AM}

Hello guys,

I am facing an issue where I am installing Windows updates on servers through a Task Sequence which run during a Maintenance Window. One particular update (always the same so far) remains in "Pending Verification" and therefore doesn't give back the hand to the Task Sequence to go further. This process works fine on some other servers.

Here is what I see in Software Center :

Here is the status for that paricular update within "Windows Update" on the server :

So the update seems installed, and same story within the WUAHandler.log :

1. Update (Missing): Security Update for Microsoft .NET Framework 4.5, 4.5.1 and 4.5.2 on Windows 7, Vista, Server 2008, Server 2008 R2 x64 (KB3097996) (103a0bdd-e71c-4f33-8cf1-7b68198ad536, 205)    WUAHandler  12/1/2015 02:14:51  9532 (0x253C)

...

Update 1 (103a0bdd-e71c-4f33-8cf1-7b68198ad536) finished installing (0x00000000), Reboot Required? No   WUAHandler  12/1/2015 02:16:35  6380 (0x18EC)

This issue already occured few times, does someone have a solution for this ? What is the "Pending Verification" process doing ? I can't find anything useful on the web ...

All replies (8)

_{Monday, December 7, 2015 8:40 AM}

A little up since last week.

Thank you

_{Saturday, December 12, 2015 5:25 PM}

Is the issue solved or not?

-- Adam

_{Monday, December 14, 2015 10:33 AM}

Absolutely not ! So far I removed the update from the deployment package.

_{Monday, December 14, 2015 10:45 AM}

It's officially not supported to use task sequences outside OSD. Have you already tried to deploy that update using a software update group (removing the deployment of the TS) for testing purposes? What do the updates log tell (esp. scanagent.log and wuahandler.log)?

Torsten Meringer | http://www.mssccmfaq.de

_{Wednesday, December 16, 2015 3:13 AM}

I do not use a task sequence and I have seen it happen occasionally, it always ended up installing. I try to pre cache the updates in advance so they have enough time to download and exist in the SCCM cache.

-- Adam

_{Monday, December 28, 2015 7:36 PM}

Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?

Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

_{Saturday, January 9, 2016 5:58 PM}

Since no one has answer this post, I recommend opening  a support case with Microsoft Customer Support Services (CSS) as they can work with you to solve this problem.

Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

_{Friday, April 15, 2016 8:52 AM}

Actually I removed the update from the package so far, sooner or later a superseding KB will appear, I hope the issue won't happen again.