Security update issue

What is a POQ and what is its significance? I tried to do a search and Yahoo changed the POQ to POS. I hate Yahoo's search engine. I have Win7 Ultimate, if that makes a difference.

How do I fix these background errors?

PS - sorry if I've given you indigestion. :)

The Primitive Operation Queue (POQ) in SFC is a batch of up to 100 file tests which the system executes at a very low level to check the system integrity - roughly speaking, each test refers to one system file.
It checks a number of parameters for every file involved - such as the security settings and the SHA256 hash value - against what should be present according to the system manifests and catalogs. If there's a mismatch, then it will try to correct it before passing to the next operation.

Most x86 machines start out with around 68 POQs in an SFC scan - x64 machines with around 120. This does build up over time, as updates are installed, and can reach 200+, but I don't recall ever seeing one over 1000 before.

This is above my head, but Gandalf, have you run the newish Disk Cleanup for superseded updates?

Update is available that enables you to delete outdated Windows update

A Guy

Even a fully loaded system like mine only has (from memory) around 260 POQs - and that's with every update known to man installed, and the disk cleanup not run :)

I did what A Guy suggested. Here is a new log report.
I cleared the CBS log then rebooted to get a fresh log.

the sfc results are the same :)

Code:

POQ 2236 ends.
2014-03-21 00:11:55, Info                  CSI    00002790 [SR] Verify complete
2014-03-21 00:14:30, Info                  CBS    Session: 30360789_872627103 initialized by client WindowsUpdateAgent.
2014-03-21 00:14:30, Info                  CBS    Read out cached package applicability for package: WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256, ApplicableState: 112, CurrentState:112
2014-03-21 00:14:30, Info                  CBS    Session: 30360789_872783103 initialized by client WindowsUpdateAgent.

I've asked elsewhere what could be causing this, as I have no idea.

Don't run away!

Thanks. I'll be here. A Guy has me nailed to my chair.

That sounds like Bill! :)

Noel - have you given up on me?

Nope - I have requests for assistance going out across the world :)

Unfortunately, it's one of those questions that touches on an undocumented (so far as I can tell) area of the Windows OS - which means that I need to happen across one of the ten people who may be interested as well as knowledgeable

At the moment, all I can think of is a repair install - which I never willingly advise.