CBS.log oddities

I have problems getting the WinUpdate packages installed
I always get a 'rollback' of the changes during a boot. So
tried to study my logs. Thinking the cbs.log could give me
a good reason why Wupdate failed, I used the trick to set the
env-var:
WINDOWS_TRACING_FLAGS=10000

in the System-environment to get more verbose logging
in my c:\Windows\Logs\CBS\CBS.log. It has now grown to
15 MByte and has many of these lines:

Skipping package [Microsoft-Windows-LanguageFeatures-Basic-nb-no-Package~
31bf3856ad364e35~amd64~~10.0.10240.16384] since it has a release-type
[OnDemand Pack] that makes it not superseded

In fact there are 30 of those;
cat c:\Windows\Logs\CBS\CBS.log| grep -I 'superseded'| wc -l
30

Seems my Pending update files are severely hosed. Is there a good
tutorial as to get my WinUpdate back into a fresh state?

ElChino wrote:
I have problems getting the WinUpdate packages installed
I always get a 'rollback' of the changes during a boot. So
tried to study my logs. Thinking the cbs.log could give me
a good reason why Wupdate failed, I used the trick to set the
env-var:
WINDOWS_TRACING_FLAGS=10000

in the System-environment to get more verbose logging
in my c:\Windows\Logs\CBS\CBS.log. It has now grown to
15 MByte and has many of these lines:

Skipping package [Microsoft-Windows-LanguageFeatures-Basic-nb-no-Package~
31bf3856ad364e35~amd64~~10.0.10240.16384] since it has a release-type
[OnDemand Pack] that makes it not superseded

In fact there are 30 of those;
cat c:\Windows\Logs\CBS\CBS.log| grep -I 'superseded'| wc -l
30

Seems my Pending update files are severely hosed. Is there a good
tutorial as to get my WinUpdate back into a fresh state?

Try the .bat file here ?

Some of these batch files are overkill, as you probably
don't need to re-register all the DLLs.

http://www.tenforums.com/tutorials/2...dows-10-a.html

Or, look for Troubleshooting in Control Panels
and with that open, use the Search box in the
upper right and enter descriptive terms like
"Update" and see if a troubleshooter is present
in the list.

When I do the search here in 11082, I get one
result which is a Windows Update troubleshooter.

I find the search better, as the itemized list is
deceptive.

Paul

Paul wrote:

ElChino wrote:
....
In fact there are 30 of those;
cat c:\Windows\Logs\CBS\CBS.log| grep -I 'superseded'| wc -l
30

Seems my Pending update files are severely hosed. Is there a good
tutorial as to get my WinUpdate back into a fresh state?

Try the .bat file here ?

Some of these batch files are overkill, as you probably
don't need to re-register all the DLLs.

http://www.tenforums.com/tutorials/2...dows-10-a.html

I tried that .bat, but it failed to delete the pending.xml
files. I tried manually and also failed (Duh!). Even after
stopping the important services in the .bat and *successfully*
taking ownership using "takeown /f pend*". I still have these
present he
C:\Windows\WinSxS dir pend*

9.12.2015 13.10 3.535.052 pending.xml.01d1327a6bc8b5cb
9.12.2015 13.10 3.535.052 pending.xml.01d1327a567603f8
9.12.2015 13.16 3.535.059 pending.xml.01d1327b1f7958cf
9.12.2015 13.16 3.535.059 pending.xml.01d1327b4c2cf03b
9.12.2015 13.30 3.535.063 pending.xml.01d1327d3aa40e3d
...
24.12.2015 3.01 3.538.222 pending.xml.01d13deedf1e8efa
24.12.2015 3.01 3.538.222 pending.xml.01d13deef387c2f9
28.12.2015 3.46 3.538.230 pending.xml.01d14119cb9bc6ba
28.12.2015 3.46 3.538.230 pending.xml.01d14119e00e26ff
28.12.2015 22.14 3.538.238 pending.xml.01d141b4a9dbf7cf
28.12.2015 22.14 3.538.238 pending.xml.01d141b491b78891

And there are still those worrying lines in my cbs.log:

----------------------
WER: Generating failure report for package: Package_for_KB3116869~
31bf3856ad364e35~amd64~~10.0.1.2, status: 0x80070011, failure source:
POQ, start state: Staged, target state: Installed, client id: WindowsUpdateAgent

Reporting package change completion for package: Package_for_KB3116869~
31bf3856ad364e35~amd64~~10.0.1.2, current: Staged, original: Staged,
target: Installed, status: 0x80070011, failure source: POQ, failure
details: "(null)", client id: WindowsUpdateAgent, initiated offline:
False, execution sequence: 124, first merged sequence: 124, pending
decision: PackagePended_Smart, primitive execution context:
PSRL Flight: False

Startup: Package: Package_for_KB3116869~31bf3856ad364e35~amd64~~10.0 .1.2
completed startup processing, new state: Staged, original: Staged,
targeted: Installed. hr = 0x80070011

Startup: Processing complete. [HRESULT = 0x80070011 - ERROR_NOT_SAME_DEVICE] !!

Startup processing completed. [HRESULT = 0x80070011]

Failed during startup processing, continuing with Trusted
Installer execution [HRESULT = 0x80070011]
----------------------

"0x80070011" seems to come from poqexec. Which AFAICS is the low-level
worker doing the update during a boot.

Pretty serious if you ask me. Any hint for this situation?

BTW. the last entry in my c:\Windows\WinSxS\poqexec.log is:

1d14280d8aad328: 8bd, c00000d4, 191, 0, HardLinkFile ;
\SystemRoot\WinSxS\amd64_presentationcore_31bf3856 ad364e35_10.0.1
0240.16603_none_b43539262a9e15f6\PresentationCore. dll,
\??\f:\ProgramFiler\Reference Assemblies\Microsoft\Framework\v3.0\PresentationCo re.dll

Seem copying across partitions failed!?
\SystemRoot = c:\Windows - f:\ProgramFiler

Why should that be so hard?

ElChino wrote:
Paul wrote:

ElChino wrote:
...
In fact there are 30 of those;
cat c:\Windows\Logs\CBS\CBS.log| grep -I 'superseded'| wc -l
30

Seems my Pending update files are severely hosed. Is there a good
tutorial as to get my WinUpdate back into a fresh state?
Try the .bat file here ?

Some of these batch files are overkill, as you probably
don't need to re-register all the DLLs.

http://www.tenforums.com/tutorials/2...dows-10-a.html

I tried that .bat, but it failed to delete the pending.xml
files. I tried manually and also failed (Duh!). Even after
stopping the important services in the .bat and *successfully*
taking ownership using "takeown /f pend*". I still have these
present he
C:\Windows\WinSxS dir pend*

9.12.2015 13.10 3.535.052 pending.xml.01d1327a6bc8b5cb
9.12.2015 13.10 3.535.052 pending.xml.01d1327a567603f8
9.12.2015 13.16 3.535.059 pending.xml.01d1327b1f7958cf
9.12.2015 13.16 3.535.059 pending.xml.01d1327b4c2cf03b
9.12.2015 13.30 3.535.063 pending.xml.01d1327d3aa40e3d
...
24.12.2015 3.01 3.538.222 pending.xml.01d13deedf1e8efa
24.12.2015 3.01 3.538.222 pending.xml.01d13deef387c2f9
28.12.2015 3.46 3.538.230 pending.xml.01d14119cb9bc6ba
28.12.2015 3.46 3.538.230 pending.xml.01d14119e00e26ff
28.12.2015 22.14 3.538.238 pending.xml.01d141b4a9dbf7cf
28.12.2015 22.14 3.538.238 pending.xml.01d141b491b78891

And there are still those worrying lines in my cbs.log:

----------------------
WER: Generating failure report for package: Package_for_KB3116869~
31bf3856ad364e35~amd64~~10.0.1.2, status: 0x80070011, failure source:
POQ, start state: Staged, target state: Installed, client id: WindowsUpdateAgent

Reporting package change completion for package: Package_for_KB3116869~
31bf3856ad364e35~amd64~~10.0.1.2, current: Staged, original: Staged,
target: Installed, status: 0x80070011, failure source: POQ, failure
details: "(null)", client id: WindowsUpdateAgent, initiated offline:
False, execution sequence: 124, first merged sequence: 124, pending
decision: PackagePended_Smart, primitive execution context:
PSRL Flight: False

Startup: Package: Package_for_KB3116869~31bf3856ad364e35~amd64~~10.0 .1.2
completed startup processing, new state: Staged, original: Staged,
targeted: Installed. hr = 0x80070011

Startup: Processing complete. [HRESULT = 0x80070011 - ERROR_NOT_SAME_DEVICE] !!

Startup processing completed. [HRESULT = 0x80070011]

Failed during startup processing, continuing with Trusted
Installer execution [HRESULT = 0x80070011]
----------------------

"0x80070011" seems to come from poqexec. Which AFAICS is the low-level
worker doing the update during a boot.

Pretty serious if you ask me. Any hint for this situation?

BTW. the last entry in my c:\Windows\WinSxS\poqexec.log is:

1d14280d8aad328: 8bd, c00000d4, 191, 0, HardLinkFile ;
\SystemRoot\WinSxS\amd64_presentationcore_31bf3856 ad364e35_10.0.1
0240.16603_none_b43539262a9e15f6\PresentationCore. dll,
\??\f:\ProgramFiler\Reference Assemblies\Microsoft\Framework\v3.0\PresentationCo re.dll

Seem copying across partitions failed!?
\SystemRoot = c:\Windows - f:\ProgramFiler

Why should that be so hard?

Perhaps the XML files are only considered, during the
interval of either applying the Windows Update, or
having it fail and backing out. Maybe those are
orphans now, and no longer matter.

For WinSXS health, there are the three DISM commands
(to be run as administrator, from an administrator
Command Prompt window).

http://www.tenforums.com/tutorials/7...-10-image.html

Dism /Online /Cleanup-Image /CheckHealth

Dism /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /RestoreHealth

I would not expect RestoreHealth to be even remotely
interested in those XML files, because they're not
a package as such.

In this example, the quoted log seems to have DISM
"look at" the pending.xml files but not do anything
to them.

http://www.tenforums.com/tutorials/7...-image-16.html

And I hesitate to suggest using cleanmgr.exe (Disk Cleanup)
at a time like this, as that might only make matters worse.

If you know a problem is present, you don't want to
"test" how the OS handles a new problem... The DISM
runs above though, should be pretty safe.

You could check and make sure System Restore is
turned on first, if you were concerned about
being able to undo changes. There were reports
the OS did not have it turned on by default,
after an Upgrade install. It's your choice
whether you use System Restore points and
rely on them, or use full OS backups for
safety purposes. I like backups if I have
doubts about how one of my "experiments" will
turn out. I've rescued two OSes that way now :-)

Paul