[SOLVED] [Win7SP1 x64] KB4025341 causes error 0x8007371b

H

HeatSurge

Member
Joined
Jul 12, 2017
Posts
7
Hi,

New here. I'm hoping for help since you guys seem to have the knowledge.

I'm having problems with KB4025341, and I'm pretty sure somewhere around here is the issue:

2017-07-12 03:00:38, Info CSI -3082_neutral_LDR" ncdata: [l:0]"") thumbprint: (null)
2017-07-12 03:00:40, Info CSI 00000013 Changelist shadowed missing its manifest - Microsoft-Windows-MSInfo32-Exe, Version = 6.1.7601.0, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2017-07-12 03:00:40, Error CSI 00000014@2017/7/12:09:00:40.871 (F) d:\w7rtm\base\wcp\componentstore\csd_winners.cpp(935): Error STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE originated in function OriginateManifestsMissingError expression: (null)
[gle=0x80004005]
2017-07-12 03:00:40, Error CSI 00000015 (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #1155548# from CCSDirectTransaction::PerformChangeAnalysis(...)[gle=0xd0150024]
2017-07-12 03:00:40, Error CSI 00000016 (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #1155547# from CCSDirectTransaction::PrepareForCommit(...)[gle=0xd0150024]
2017-07-12 03:00:40, Error CSI 00000017 (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #1155546# from CCSDirectTransaction::ExamineTransaction(...)[gle=0xd0150024]
2017-07-12 03:00:40, Error CSI 00000018 (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #1155545# from CCSDirectTransaction_IRtlTransaction::ExamineTransaction(...)[gle=0xd0150024]
2017-07-12 03:00:41, Info CSI 00000019 Changelist shadowed missing its manifest - Microsoft-Windows-MSInfo32-Exe, Version = 6.1.7601.0, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2017-07-12 03:00:41, Error CSI 0000001a@2017/7/12:09:00:41.135 (F) d:\w7rtm\base\wcp\componentstore\csd_winners.cpp(935): Error STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE originated in function OriginateManifestsMissingError expression: (null)
[gle=0x80004005]
2017-07-12 03:00:41, Error CSI 0000001b (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #1603747# from CCSDirectTransaction::PerformChangeAnalysis(...)[gle=0xd0150024]
2017-07-12 03:00:41, Error CSI 0000001c (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #1603746# from CCSDirectTransaction::PrepareForCommit(...)[gle=0xd0150024]
2017-07-12 03:00:41, Error CSI 0000001d (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #1603745# from CCSDirectTransaction::GenerateComponentChangeList(...)[gle=0xd0150024]
2017-07-12 03:00:41, Error CSI 0000001e (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #1603744# from Windows::COM::CPendingTransaction::ExtractInformationFromRtlTransaction(...)[gle=0xd0150024]
2017-07-12 03:00:41, Error CSI 0000001f (F) HRESULT_FROM_WIN32(ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE) #1031678# from Windows::COM::CPendingTransaction::IStorePendingTransaction_Analyze(...)[gle=0x8007371b]
2017-07-12 03:00:41, Error CSI 00000020 (F) HRESULT_FROM_WIN32(ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE) #1008204# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_Commit(Flags = 47 (0x0000002f), pSink = NULL, disp = 0, coldpatching = FALSE)[gle=0x8007371b]
2017-07-12 03:00:41, Error CSI 00000021 (F) HRESULT_FROM_WIN32(ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE) #1008203# 2859486 us from Windows::ServicingAPI::CCSITransaction_ICSITransaction::Commit(flags = 0x0000002f, pSink = NULL, disp = 0)
[gle=0x8007371b]
2017-07-12 03:00:41, Info CBS Setting ExecuteState key to: ExecuteStateNone
2017-07-12 03:00:41, Info CBS Setting RollbackFailed flag to 0
2017-07-12 03:00:41, Info CBS Clearing HangDetect value
2017-07-12 03:00:41, Info CBS Saved last global progress. Current: 0, Limit: 1, ExecuteState: ExecuteStateNone
2017-07-12 03:00:41, Info CBS Exec: Restoring driver operations because of a CSI commit failure.
2017-07-12 03:00:41, Error CBS Exec: Failed to pend CSI transaction because transactions cannot be merged: 0. [HRESULT = 0x8007371b - ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE]
2017-07-12 03:00:41, Info CSI 00000022@2017/7/12:09:00:41.165 CSI Transaction @0xce5150 destroyed
2017-07-12 03:00:41, Info CBS Perf: InstallUninstallChain complete.
2017-07-12 03:00:41, Info CBS Failed to execute execution chain. [HRESULT = 0x8007371b - ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE]
2017-07-12 03:00:41, Error CBS Failed to process single phase execution. [HRESULT = 0x8007371b - ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE]
2017-07-12 03:00:41, Info CBS WER: Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.23862.1.6, status: 0x8007371b, failure source: Execute, start state: Staged, target state: Installed, client id: WindowsUpdateAgent
2017-07-12 03:00:41, Info CBS Failed to query DisableWerReporting flag. Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2017-07-12 03:00:41, Info CBS Failed to add %windir%\winsxs\pending.xml to WER report because it is missing. Continuing without it...
2017-07-12 03:00:41, Info CBS Failed to add %windir%\winsxs\pending.xml.bad to WER report because it is missing. Continuing without it...
2017-07-12 03:00:41, Info CBS Failed to add %windir%\inf\setupapi.dev.log to WER report because it is missing. Continuing without it...
2017-07-12 03:00:41, Info CBS Reboot mark refs: 0

However, I lack the knowledge to fix this particular one. I've fixed issues by looking at the CBS log before myself, but this has got me stumped.

A bit of history: I had a registry corruption issue. I think it was caused by a bad reboot, but it was a long time ago and I can't remember the circumstances. Once in a while, an update will fail and I'll find out what the issue is - I remember a nasty one where a few keys were corrupt so I had to export/import hives of adjacent keys which luckily didn't have any unique information underneath (it's related to the SxS "Winners" branch IIRC, but it's been a LONG time ago - probably 2 years or more, so I don't remember) so I'm not surprised at this, and this might be somehow related.

Anyway, I'll be attaching my log, and you guys let me know what to do please. I already ran SFCfix and it didn't find any errors to fix automatically...

I've also run sfc /scannow which does finish successfully and says we're all good.

Sorry my log is really gigantic... there are other errors as well, but I'd like just the critical one fixed to make the update go through, unless the others are easy to fix. If they're not easy, please just ignore them.

Edit: Looks like the log is too large, so I'm putting it as a link. Let me know if there are any issues: http://gangov.com/ugh/CBS.zip
 
I've been looking around, and this thread seems the closest related issue - except in that one the guy had like 10 of these issues and I have just one...

It looks like I might need some registry entries to fill in the "missing manifest."

I've been trying to search for msinfo32 6.1.7160.0 but I keep finding things that don't give me ideas.

Still hope for someone to help.

Thanks
 
I've tried to do a lot of troubleshooting myself over the last couple of days.

I found out this after running SFCFix:

WARNING: Failed to backup registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-msmpeg2vdec_31bf3856ad364e35_0.0.0.0_none_10efd5f6b889b531.
CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-msmpeg2vdec_31bf3856ad364e35_0.0.0.0_none_10efd5f6b889b531) on component watchlist.

Also Checksur says this after running the SURT for Win7x64:

Checking Component Watchlist
(f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-msmpeg2vdec_31bf3856ad364e35_0.0.0.0_none_10efd5f6b889b531 Package_56_for_KB3033929~31bf3856ad364e35~amd64~~6.1.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-msmpeg2vdec_31bf3856ad364e35_0.0.0.0_none_10efd5f6b889b531 Package_56_for_KB3033929~31bf3856ad364e35~amd64~~6.1.1.1 Package registry presence failed, possibly an orphaned package on package watchlist

As a result of the Checksur log I (maybe stupidly) decided to uninstall KB3033929 to see if it would "magically fix it."

It wouldn't uninstall from the GUI, so after running wusa /uninstall /kb:3033929 (and it was successful), now I can't reinstall it because it says it's already been installed.

The funny thing is if I run wusa /uninstall /kb:3033929 again, it says it's already been uninstalled -_- . Kind of a joke I guess. So the update is not installed, but it's also already installed.

Can you help me with this first if it's easier? Maybe it's related to what I'm looking for...

Help...

By the way, aside from the "update breaking" error, the SURT fixed a lot of the other missing and broken errors I think. There's only a few left now - 13 in all supposedly.

Thanks
 
I was able to force-reinstall KB3033929 using some instructions I found (extract the package, and then dism force-install the .cab). It worked, and now it shows in the updates again.

Indeed, it fixed that KB3033929-related error, so that's pretty awesome.

However, the show-stopping error in the original post remains.

I am slowly starting to lose hope.
 
I have been through a LOT of different forums in the last few days and I am still hoping that someone will help me through this.

I streamlined the CBS log to a much smaller size without the bloat, by Disk Cleanup (Windows Update superseded packages removal), and just copying it before it gets bloated by the scan and error being copied over and over.

It shows the same thing as above, really.

Still hoping someone will help.

Here you go:

View attachment CBS - Copy.zip
 
I must have spent 20+ hours on this in the last week.

In short, yesterday I finally got another older laptop I have up to date so I can have a 1:1 comparison looking around the registry (also running Windows 7 x64). Here's what I found out which is probably very valuable to people so they don't waste time:
- sfc /scannow and dism /online /cleanup-image /scanhealth (only /scanhealth is supported on windows 7) are VERY useful commands. However, they were coming up "clean" so they didn't fix my problem.
- windows update reset (the MS fixit) acknowledged the problem, but fixed nothing
- sfcfix did not acknowledge a problem whatsoever (same as sfc /scannow)
- SURT (system update readiness tool) installed without issues as well (SURT seems to give the exact same results as dism /online /cleanup-image /scanhealth including generating checksur.log... why is it even recommended to download it? just run the command instead??)
- I must have read 50 different forum posts on various errors. None of them fixed anything, and a few pointed me towards the components registry branch... which was also the wrong way to go in my case.
- I tried to do a bunch of other generic troubleshooting (regdelnull, .net cleanup tools, reset pending updates, tweak.net troubleshooter scripts, windows reset troubleshoot scripts). Ultimately, all the generic stuff was a waste of time entirely.
- I also tried to check and make sure I'm not missing anything related to Microsoft-Windows-MSInfo32-Exe in the SxS and the manifest folder: C:\Windows\WinSxS\Manifests . This was ultimately close to the problem, but I was thinking about it backwards - see below.

So what finally fixed it?

Well, I kept coming back to the error log. As it turned out, obviously what it says there is EXACTLY what was wrong.

These two lines should've been all I ever needed:
2017-07-12 03:00:40, Info CSI 00000013 Changelist shadowed missing its manifest - Microsoft-Windows-MSInfo32-Exe, Version = 6.1.7601.0, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2017-07-12 03:00:40, Error CSI 00000014@2017/7/12:09:00:40.871 (F) d:\w7rtm\base\wcp\componentstore\csd_winners.cpp(935): Error STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE originated in function OriginateManifestsMissingError expression: (null)

The first one is that something is wrong with "Microsoft-Windows-MSInfo32-Exe" and the second, that there's something wrong with the SXS "winners" branch.

So what the process for fixing it was searching literally for Microsoft-Windows-MSInfo32-Exe in regedit on my "good" laptop which didn't have a problem, and my "broken" desktop with the issue, and then making each key the exact same on the "bad" registry.

What I found out:
There was some EXTRA stuff on the "broken" machine on the HKLM\COMPONENTS branch related to Microsoft-Windows-MSInfo32-Exe values. Like !f256 entries and whatever... I don't remember. I actually erased some of the values underneath the keys to make it like the "good" machine. Ultimately, nothing on HKLM\COMPONENTS fixed anything - for me anyway. I'm sure the problem for someone else might be there, but not mine.

The real issue was in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners keys.

In particular, I believe what actually fixed it was, again, no surprises, as it says in the log above, in the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-msinfo32-exe_31bf3856ad364e35_none_83878e77044b56e3\6.1, the (Default) value was something like 6.1.9600.1741< instead of 6.1.9600.17415 (yes, a f'n "<" instead of a digit), thereby probably causing ALL my issues. There were a few other values to be updated/fixed, but I really think this was the corrupt one.

So, instead of a "missing manifest" which was the message from the error, it turns out the manifest was really there all along. What was wrong was the registry entry, which made windows look for the "wrong" manifest (the version of it anyway), which was, unsurprisingly, "missing."

What needed fixing was ultimately the registry entry pointing to the manifest.

Funnily enough, after making all the changes in the registry to make the "broken" machine "look like" the "good" machine - in terms of all references to Microsoft-Windows-MSInfo32-Exe, sfc /scannow actually showed a "corruption detected and repaired successfully" - or something to that effect. Checking the cbs.log referenced a few hashes and things related to msinfo32.exe, and windows update worked afterwards. So when you think you've fixed your registry (or added your manifests if in your case they are missing), make sure you rerun sfc /scannow - even if it said it "detected no problems" previously.

Hope that helps anyone or gives you ideas.

The history behind sxs\winners for my computer was that there was existing corruption in a few other keys (my best guess caused by a bad restart in the middle of an update a few years ago), so I'm not surprised I had this problem. It was just amazing how difficult it was to find the registry corruption in this case, which was a single digit corrupted to a < ...

Anyway. Have fun.

P.S. By the way, looking at cbs.log (non-critical errors related to "not found" packages) and comparing registries also made me realize that HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing is missing a few references to packages I had in C:\Windows\servicing\Packages (again, not the "packages" were missing, but the references to them were missing), so I copied a few of the registry branches containing missing package references from my "good" laptop. They seem to have worked out. Packages seem to be better checked with dism /online /cleanup-image /scanhealth, so if you have "packages" issues - run that and check checksur.log afterwards and see if you might have issues after fixing your registry - e.g. registry references to package files you're missing (which you'll have to acquire from a friend, a working machine at the same windows version and update state, or the win7 x64 DVD)...

Hopefully I'm "good" now for a while - or if something else pops up I now have the experience to fix it -_- .
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top