Tag Archives: WSUS

Config Manager client scan error

Yup, I’ve been a bit quiet of late.

Out of the blue, my Windows 10 device suddenly stopped patching. I checked the WUAHANDLER.log and found something new. Which is always nice. Here is the log:

Cheers Microsoft.

Continue reading

WSUS Boot-Strapper Error

Following a client upgrade, I did notice a niggle with one of Config Manager’s Components:

So fustrating at times... the error doesn't really tell what the real issue is.

So frustrating at times… the error doesn’t really tell what the real issue is.

A constant stream of:

WSUS Configuration Manager failed to publish client boot-strapper package

So basically something is wrong, but there were no details to give me a definitive direction. I delved into the logs, and headed straight for the WSUS logs. I opened the WCM.log, and although nothing was flagged in red, I did find some interesting text:

Continue reading

KB3114409 – Joy to the world

It’s that most wonderful time of the month again, when Microsoft release the monthly Outlook show stopper. In November, we had fun and games with bad updates for Outlook 2010 and Outlook 2013.

Microsoft appear to have outdone themselves again, by releasing KB3114409. This December 2015 update causes havoc for Outlook 2010 users. thankfully this time round my beta testers actually told me about it. A quick Google of “Outlook 2010, reading pane, December updates”, and I was awash with unhappy punters.

Continue reading

Office 2013 and KB3101488

This is a bit of a retrospective post rant.

In November we were well into the swing of a migration from Office 2010 to Office 2013. The vast majority of the update alpha test group were running Office 2010. The vast majority of the beta test group were Office 2013.

As part of the November 2015 monthly release, I deployed KB3101488. It went through the alpha testing and no issues were recorded… but as noted above, we were light on the ground for Office 2013 :-/

Worryingly, it sailed through beta testing.

Continue reading

Windows Update Agent woe Part II

Following on from my blog here, I applied the server-side WSUS update, KB2938066. I then ran the server clean up wizard and was quite surprised at the numbers:



It does make me wonder if the server clean up wizard alone is enough. it’s something I need to look into… I would not have considered there to be so many deletions for a database that is cleaned up once a month. However I digress.

Continue reading

Windows Update Agent woe

I’ve come across an issue with my Windows 7 PCs during this month’s alpha testing. Some PCs would pick up updates, and consume gigabytes of memory. Others would just refuse to do anything. Upon further digging, I found that my x86 PCs were reporting no errors Config Manager wise, but the WindowsUpdateAgent.log kept throwing up this error code:

2015-06-11    13:16:23:757    5340    17bc    COMAPI    WARNING: ISusInternal::GetUpdateMetadata2 failed, hr=8007000E

There's always something!

There’s always something!

Continue reading

SCUP and a PKI Certificate – SCUP Headache NUmber 2!

Following on from the WSUS/SUP rebuild I blogged about here, I noticed that all SCUP updates in Config Manager were flagged up with a grey cross. All except the most recent Adobe reader/ acrobat/flash which were in the monthly test cycle.

I downloaded all the updates and everything seemed to be fine.

However reports started to float in for reader/acrobat/flash failing to install, with error code  0x80091007. The failures were only limited to the very latest updates, which were now live. The older SCUP updates installed fine.

Uh oh… too much of a coincidence here.

I tried removing the affected updates from the SUGs and deleting them from the package; I published and resigned the updates but this had no affect. I then deleted the updates from SCUP and removed the catalogue; next I imported the library from Adobe but interestingly the updates were now marked as expired. I duplicated them and tagged as MKII. and published into the WSUS catalogue.

This now worked… the affected updates, or rather the MKII versions, now installed without any errors. Strangely the original updates are flagged as not expired but if I attempted to publish them, it would error stating they are expired.



The root cause? I’m not sure but I am going to suggest that having them in multiple SUGs as part of the monthly testing and rollout ended up with them being stuck in our WSUS catalogue signed with the old self-signed certificate. It is very odd how it only affected these three… Maybe I missed the initial clear out but it’s strange that from the word go they had a green icon instead of the grey cross like other SCUP updates.

Anyway, prodigious use of duplicate and “MKII” saved the day 😛