Security update issue

Thanks, Noel. I've always been able to come up with aspects of Windows that people say wait for the next SP upgrade.
I've never been very good with patience, but I'll try.

Here's an 'official' response to my query - Maybe you can make more sense out of it than I can..

When component is changed (modify, install, uninstall), file and registry changes are primitive operations during this process, system would use primitive installer to take the component change list to generate the list of primitive operations, all primitive operations from all primitive installers together form the POQ (Primitive Operation Queue).
If POQ cannot be executed immediately, system pends the transaction and records the operations in pending.xml file.
SFC /scannow would verify the integrity of system, in my understanding, it would check the all POQ nodes occurred in system, and this is related to the system change times.

To my mind, that is a 'nothing' response, and doesn't answer the question anyhow
SFC has ridiculously high nuber of POQ sections...

Does anyone have ANY idea what could cause there to be 2236 PQOs in an SFC, where the usual number is 120-200??

I did notice your original post read PQO vice POQ. OOPS.

Is the responder an engineer or a lawyer? I know I'm new at this, but the response makes no sense to me either. Is the POQ a list of operations the computer is meant to perform and if so, when is the list meant to be performed? Could I be keeping the computer to busy to perform these operations with my BOINC crunching. That doesn't make sense to me, but then what do I know.

If this was easy, I won't need you!

EDIT: I did move the C drive when my motherboard died to a different PC. I had to go though a phone call with MS to get it Re-Activated. Could this have anything to do with the high POQ?

FYI - The C drive is also a SSD vice a HDD.

In normal operations, POQ's would be processed at shutdown or startup (via the pending.xml) if they couldn't be processed immediately.
In SFC, POQ's are I think constructed on-the-fly by reading registry data (something in the COMPONENTS hive, I would hope), and processed immediately - it shouldn't matter about BOINC.

Let's see if that's anywhere near right...


I need to have a look at your COMPONENTS registry hive

Please copy the C:\Windows\System32\config\COMPONENTS file (no extension) to your desktop and then compress it - upload the compressed file to your favoured fileshare site (preferably Dropbox or OneDrive) and post a link.

I'm new at sharing files, so I hope I got it right...
https://jumpshare.com/v/KM8x1pqw2qdO...YiPvzKULcxEPgS

WOW! 57MB, compressed! and 237MB uncompressed.
No wonder it's a huge SFC. The more normal size is around 6-10MB compressed (about 40MB uncompressed)

How many of the Windows Language Packs do you have installed? - a quick look shows that it may be these that are causing the effect. (there are over 10,000 entry for the it-IT mui alone compared to 900 on my machine)

How would I remove those? When you set the Windows Update to automatic, MS will send you all kinds of things.

This may have been part of the SDK when I was trying to set up for DUMP analysis.

You can uninstall the language packs from the Installed Updates listing - the general recommendation is to only have 3-5 installed (not 35 :)) since it does make updating a lot more onerous as all the relevant files have to be updated.

Having large number of Language Packs installed is known to prevent the proper installation of SP1 - so it may well prevent other updates as well.

When I noticed the language pack being installed, I uninstall them from the Programs and Features.
However, as with so many programs, there are leftover folders like the c:\Windows folder it-IT remaining. Should I manually delete these folders? Should I manually run through the Registry to delete these language file entries? Is there something else I should do to minimize the POQ?

I did a Registry compression and here is the resulting sfc run...