[SOLVED] KB976932 (SP1) error 80004005 Win7 Home Prem (x64) - rolls back after 99% config

@jaHere It has been brought to my attention that you are being assisted on another forum by an untrained helper who has told you to go there seeking assistance.

While I do understand the urge to get this fixed as soon as possible, I do not appreciate you abandoning the thread and working with someone else, especially untrained, without making me aware of that.

That would have been fair after all the time I've invested into the thread.

Please let me know which of the the two threads you would like to continue and I will act accordingly.

Thank you.

softwaremaniac
 
It has been brought to my attention that you are being assisted on another forum by an untrained helper who has told you to go there seeking assistance.
Click to expand...

On Wednesday the guy said he had an idea based on the Mgadiag attachment here a couple of days ago. He noticed something strange about the laptop and I wanted to know what it was. So last night I posted the problem on his forum because he asked me to.

While I do understand the urge to get this fixed as soon as possible, I do not appreciate you abandoning the thread and working with someone else
Click to expand...

I'm not abandoning it. He has made a suggestion.

without making me aware of that.
Click to expand...

I was actually going to write to you about his suggestion to run it by you. It was the following [quoting Torchwood from seven forums]:

There is a slight problem with this, allthough your system reports as Activated, it also requires it to be registered, yours is missing the Event Time Stamp.
Standard fix is to (RE) install KB971033.
you only have 1 rearm remaining, can you read the COA sticker Key (battery compartment).

any reason why you have removed it before, (twice)
....
You get 3 rearms, I knew something was odd when i saw the FRST report you posted, it showed that the task performed quarterly by the KB had been removed.


I thought forums like these were an open exchange of information; and solving the problem, and letting the lessons be known generally so it might help others, is the most important thing. I also wrote in the seven forums that my "tutor" in the other forum has made an immense effort trying to help me, and I will remember this.
 
If you're developing an idea to see if it works then I'm happy to continue.
 
Of course, but once you start receiving help from one site, you're expected to stay there. I know this is frustrating because of the nature of the corruption and its extent, but this is the best way to solve this. I have been in the field for a while now and I know WU inside-out. We are currently stuck on the following error:

Code: 
2019-03-31 19:56:57, Error                 CSI    0000001c (F) STATUS_SXS_ASSEMBLY_NOT_FOUND #6257836# from CCSDirectTransaction::PerformChangeAnalysis(...)[gle=0xd0150004]
2019-03-31 19:56:57, Error                 CSI    0000001d@2019/3/31:10:56:57.085 (F) d:\win7sp1_gdr\base\wcp\componentstore\csd_winners.cpp(550): Error STATUS_SXS_ASSEMBLY_NOT_FOUND originated in function CCSDirectTransaction::PerformChangeAnalysis expression: m_Analysis->AllCompositionsWereFound()
[gle=0x80004005]
2019-03-31 19:56:57, Error                 CSI    0000001e (F) STATUS_SXS_ASSEMBLY_NOT_FOUND #6257835# from CCSDirectTransaction::PrepareForCommit(...)[gle=0xd0150004]
2019-03-31 19:56:57, Error                 CSI    0000001f (F) STATUS_SXS_ASSEMBLY_NOT_FOUND #6257834# from CCSDirectTransaction::ExamineTransaction(...)[gle=0xd0150004]
2019-03-31 19:56:57, Error                 CSI    00000020 (F) STATUS_SXS_ASSEMBLY_NOT_FOUND #6257833# from CCSDirectTransaction_IRtlTransaction::ExamineTransaction(...)[gle=0xd0150004]
2019-03-31 19:56:57, Info                  CSI    00000021 TLC operation Uninstall (1) incomplete for [Microsoft-Windows-StorageService-Deployment-LanguagePack, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral]), missing compositions
    Microsoft-Windows-StorageService.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2019-03-31 19:56:57, Error                 CSI    00000022 (F) STATUS_SXS_ASSEMBLY_NOT_FOUND #7963043# from CCSDirectTransaction::PerformChangeAnalysis(...)[gle=0xd0150004]
2019-03-31 19:56:57, Error                 CSI    00000023@2019/3/31:10:56:57.506 (F) d:\win7sp1_gdr\base\wcp\componentstore\csd_winners.cpp(550): Error STATUS_SXS_ASSEMBLY_NOT_FOUND originated in function CCSDirectTransaction::PerformChangeAnalysis expression: m_Analysis->AllCompositionsWereFound()
[gle=0x80004005]
2019-03-31 19:56:57, Error                 CSI    00000024 (F) STATUS_SXS_ASSEMBLY_NOT_FOUND #7963042# from CCSDirectTransaction::PrepareForCommit(...)[gle=0xd0150004]
2019-03-31 19:56:57, Error                 CSI    00000025 (F) STATUS_SXS_ASSEMBLY_NOT_FOUND #7963041# from CCSDirectTransaction::GenerateComponentChangeList(...)[gle=0xd0150004]
2019-03-31 19:56:57, Error                 CSI    00000026 (F) STATUS_SXS_ASSEMBLY_NOT_FOUND #7963040# from Windows::COM::CPendingTransaction::ExtractInformationFromRtlTransaction(...)[gle=0xd0150004]
2019-03-31 19:56:57, Error                 CSI    00000027 (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_NOT_FOUND) #6064907# from Windows::COM::CPendingTransaction::IStorePendingTransaction_Analyze(...)[gle=0x800736b3]
2019-03-31 19:56:57, Error                 CSI    00000028 (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_NOT_FOUND) #6050152# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_Commit(Flags = 102 (0x00000066), pSink = NULL, disp = 0, coldpatching = FALSE)[gle=0x800736b3]
2019-03-31 19:56:57, Error                 CSI    00000029 (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_NOT_FOUND) #6050151# 49082214 us from Windows::ServicingAPI::CCSITransaction_ICSITransaction::Commit(flags = 0x00000066, pSink = NULL, disp = 0)
[gle=0x800736b3]
2019-03-31 19:56:57, Info                  CBS    Setting ExecuteState key to: ExecuteStateNone
2019-03-31 19:56:57, Info                  CBS    Setting RollbackFailed flag to 0
2019-03-31 19:56:57, Info                  CBS    Clearing HangDetect value
2019-03-31 19:56:57, Info                  CBS    Saved last global progress. Current: 0, Limit: 1, ExecuteState: ExecuteStateNone
2019-03-31 19:56:57, Error                 CBS    Exec: Failed to commit CSI transaction to execute changes. [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2019-03-31 19:56:57, Info                  CSI    0000002a@2019/3/31:10:56:57.724 CSI Transaction @0x2b3f630 destroyed
2019-03-31 19:56:57, Info                  CBS    Perf: InstallUninstallChain complete.
2019-03-31 19:56:57, Info                  CBS    Failed to execute execution chain. [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2019-03-31 19:56:57, Error                 CBS    Failed to process Multi-phase execution. [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]

This means there is an error with the StorageService Deployment. It could be missing or incomplete to some extent.

Let's start by having you re-run a scan from this post. That will help me compare the results and hopefully get us going.

Also, while I am providing assistance, I expect to be fully apprised of any suggestions you receive there prior to following them, but my recommendation would be to choose one site and stick to it.
 
softwaremaniac said:
Also, while I am providing assistance, I expect to be fully apprised of any suggestions you receive there prior to following them,
Click to expand...

I'd have thought this was obvious as some external suggestions could disturb your workflow.

Anyhow, here's the SearchReg.txt file.
 

Attachments

Please take a screenshot of your enabled features in Turn Windows Features on or off. I believe I have asked you to do this in the past, but just in case, I would like to see that again. Thank you.
 
Here's the screenshot.

After that I also ran FRST according to your previous instructions and have attached the SearchReg file -- just in case anything has changed: had a BSOD today, possibly due to overheating. It has happened a few times in the past, but not for 9 months or so.
 

Attachments

Which dump? CBS file?

I posted the Windows features screenshot last Sunday. And the Searchreg output file.
 
just in case anything has changed: had a BSOD today, possibly due to overheating. It has happened a few times in the past, but not for 9 months or so.
Click to expand...

The minidump file that should have been created after the crash. If there is an underlying hardware issue, we need to prioritize that over Windows Update.

Please navigate to C:\Windows\Minidump, copy it to your Desktop, zip it up and upload it somewhere for my review.
 
Thanks:

GSmartControl
Follow the instructions below to check your SMART status with GSmartControl:


  • Download the portable version of GSmartControl and save it on your Desktop;
  • Extract the zip file to your Desktop. Open the folder gsmartcontrol-1.1.3-win64 which should be located on your Desktop and double-click gsmartcontrol.exe to launch the program.
  • Identify your drive in the list (if recognized by the tool), and hover your mouse over it.
  • You should see something called: SMART status. It will either read: Enabled, in which case you should do the following:
  • Double-click on it to bring up its window (usually you'll find your drive by its size or its brand name);
  • Go to the Self-Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete);
  • Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your next reply or take a screenshot;
  • Also, go in the Attributes tab and if you have any entries highlighted in red or pink, take a screenshot of the GSmartControl window and attach it in your next reply;
  • Please note: If the SMART Status reads: Unsupported, stop and let me know.
    info_failing.png
 
Sadly, we have discovered the root cause of your issues.

Please backup your data and replace the hard drive. Due to the extent of the damage that is present, I recommend a fresh install of Windows onto a new drive rather than a clone.

Sorry to reach such an abrupt ending to this :(
 
Solving a problem isn't a sad thing. Knowing a clear way forward is actually a good feeling.

As long as I can save the data.

Thanks for your patient help since last October.

I should have checked the hardware first... lesson for next time.
 
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