Trouble installing some updates

Page 3 of 5 FirstFirst 12345 LastLast

  1. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #21

    There are actually no errors in that CBS.log
    I'll ask a BSOD specialist to come in and take a look - meanwhile, here's the errors from the CheckSUR..
    Code:
    (f) CSI Payload File Missing 0x00000000 SOS.dll amd64_netfx-sos_dll_b03f5f7f11d50a3a_6.1.7601.17559_none_a0a2734da2fcd3e0 
    (f) CSI Payload File Missing 0x00000000 mscorlib.dll x86_mscorlib_b77a5c561934e089_6.1.7601.21660_none_854a972197a1432d
    ...which is as expected.
    I don't think these are likely to be related to your BSOD's.

    Please follow the Blue Screen of Death (BSOD) Posting Instructions and post the zip file created in this thread so we can keep things together.
    I'll post a fix protocol for those two files in a few minutes.
      My Computer


  2. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #22

    I've uploaded a file - hkrac.zip - to my OneDrive at Noel's OneDrive
    Please download and save it.

    Right-click on the saved file and select Extract all...
    Change the target to C:\ and click on Extract
    Close all windows (it would be a good idea to print these instructions!)

    Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
    Pick that
    You'll have to log in with your username and password.

    Pick the option to use a Command Prompt
    At the prompt type
    DIR C:\hkrac
    hit the enter key - if you get a 'Not Found' error try
    DIR D:\hkrac
    or
    DIR E:\hkrac

    The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...

    XCOPY <drive>:\hkrac <drive>:\windows\winsxs /y /i /s /v /h

    (e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



    run the command (it should take almost no time) and when the prompt returns, type
    EXIT
    and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

    Now run SFC /SCANNOW in an Elevated Command Prompt
    then reboot and upload the new CBS.log file to your reply

    Also run CheckSUR again, and post the new CheckSUR.log file
      My Computer


  3. Posts : 19
    Windows 7 Ultimate x64
    Thread Starter
       #23

    I’ve copied the two files you provided me in the Repair console and then booted in normal mode en ran sfc /scannow again and it said:

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    Again the Cbs.log is included. I am no expert in these things, but I noticed a section (at the top) in the Cbs.log file that was first logged (when I booted up the pc) before I started to run sfc /scannow. I mean this section:

    Code:
     2014-10-25 12:00:58, Info                  CBS    Starting TrustedInstaller initialization.
      2014-10-25 12:00:58, Info                  CBS    Loaded Servicing Stack v6.1.7601.17592 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\cbscore.dll
      2014-10-25 12:00:59, Info                  CSI    00000001@2014/10/25:10:00:59.221 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fef9f7f0ad @0x7fefa519849 @0x7fefa4e34e3 @0xffbce97c @0xffbcd799 @0xffbcdb2f)
      2014-10-25 12:00:59, Info                  CSI    00000002@2014/10/25:10:00:59.221 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fef9f7f0ad @0x7fefa566816 @0x7fefa532aac @0x7fefa4e35b9 @0xffbce97c @0xffbcd799)
      2014-10-25 12:00:59, Info                  CSI    00000003@2014/10/25:10:00:59.221 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fef9f7f0ad @0x7fefa808738 @0x7fefa808866 @0xffbce474 @0xffbcd7de @0xffbcdb2f)
      2014-10-25 12:00:59, Info                  CBS    Ending TrustedInstaller initialization.
      2014-10-25 12:00:59, Info                  CBS    Starting the TrustedInstaller main loop.
      2014-10-25 12:00:59, Info                  CBS    TrustedInstaller service starts successfully.
      2014-10-25 12:00:59, Info                  CBS    SQM: Initializing online with Windows opt-in: False
      2014-10-25 12:00:59, Info                  CBS    SQM: Cleaning up report files older than 10 days.
      2014-10-25 12:00:59, Info                  CBS    SQM: Requesting upload of all unsent reports.
      2014-10-25 12:00:59, Info                  CBS    SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
      2014-10-25 12:00:59, Info                  CBS    SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
      2014-10-25 12:00:59, Info                  CBS    SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
      2014-10-25 12:00:59, Info                  CBS    SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]
      2014-10-25 12:00:59, Info                  CBS    No startup processing required, TrustedInstaller service was not set as autostart, or else a reboot is still pending.
      2014-10-25 12:00:59, Info                  CBS    NonStart: Checking to ensure startup processing was not required.
      2014-10-25 12:00:59, Info                  CSI    00000004 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x9bf950
      2014-10-25 12:00:59, Info                  CSI    00000005 Creating NT transaction (seq 1), objectname [6]"(null)"
      2014-10-25 12:00:59, Info                  CSI    00000006 Created NT transaction (seq 1) result 0x00000000, handle @0x1ec
      2014-10-25 12:00:59, Info                  CSI    00000007@2014/10/25:10:00:59.284 CSI perf trace:
      CSIPERF:TXCOMMIT;550
      2014-10-25 12:00:59, Info                  CBS    NonStart: Success, startup processing not required as expected.
      2014-10-25 12:00:59, Info                  CBS    Startup processing thread terminated normally
      2014-10-25 12:00:59, Info                  CSI    00000008 CSI Store 3928464 (0x00000000003bf190) initialized
      2014-10-25 12:00:59, Info                  CBS    Session: 30404666_2477194668 initialized by client WindowsUpdateAgent.
      2014-10-25 12:01:04, Info                  CBS    Trusted Installer signaled for shutdown, going to exit.
      2014-10-25 12:01:04, Info                  CBS    Ending the TrustedInstaller main loop.
      2014-10-25 12:01:04, Info                  CBS    Starting TrustedInstaller finalization.
      2014-10-25 12:01:06, Info                  CBS    Ending TrustedInstaller finalization.
    I see the word "failed" a couple of times and I don’t know if this means something or not?

    I again ran Checksur and it didn’t give any error’s anymore thank god or should I say thank Tom.

    Concerning the BSOD, I didn’t get them anymore and for some strange reason it never made a dump file (in my case a mini dump file). This means I can’t upload anything really. Normally I would use a program called “BlueScreenView” that would give me insight right away which file crashed and caused the BSOD. By the way in case you didn’t hear of this wonderful tool it is downloadable here: Blue screen of death (STOP error) information in dump files.

    However, I hope everything is now ok and you don’t have to put in your time and afford for any extra files that I am missing. If everything is ok then I will restore the latest backup and then copy all of the files you gave me at onces and also the SFCFix script files you gave me. And then run SFC /scannow and Checksur and everything should be repaired at ones and not in sections like now. Then I will move the CBS.log and CheckSUR.log to another location and run them again and have a look if everything is fully repaired and ok.

    Then I will make a Full backup of my systemdrive and hope no BSOD’s will occur.
      My Computer


  4. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #24

    Those failure codes at the top are present in almost every CBS log, and can be ignored.

    CheckSUR is now clear.
    I can't see any significant errors in the CBS logs - so I reckon you're good to go.

    Feel free to post the data produced by the tool anyhow - our guys can generally work wonders even with that minimal data. (One or two have already subscribed to the thread and are waiting with bated breath... )
      My Computer


  5. Posts : 19
    Windows 7 Ultimate x64
    Thread Starter
       #25

    Dear Tom,

    From the bottom of my heart I would like to thank you for taking the time and afford to assist me in this (I thought) impossible repair. I really appreciate it and I will add to your reputation (wherever I can). I have my Windows 7 installation for almost 4 years now and with the help of Acronis I can repair/restore/inspect/reproduce most of my PC problems. However, during those years it appears that a lot of important files have corrupted/deleted and you can only fix that with the steps you took me through.

    I will let you know as soon as I restored my backup and done all the necessary repairs again (copy everything for one big SFC/CheckSUR fix. After that I will make my Full backup with Acronis 2010 (still the best version IMO).

    Then after that if I would get any BSOD's, I will surely post them here! :) The link that I posted to that tool to diagnose BSOD's (in my previous reply), did you already know the utility?

    I think I have the flue or something and thus I think my answer will have to wait a couple of days before I post again with my results.
      My Computer


  6. Posts : 2,663
    Windows 8.1 Pro x64
       #26

    Hulkster said:
    Dear Tom,
    Noel has done most of the hard work here, but you're welcome nonetheless :)
      My Computer


  7. Posts : 19
    Windows 7 Ultimate x64
    Thread Starter
       #27

    Wow, my flue must have totally clouded my mind because I was under the impression that was helped by 1 person (Tom). Consumed by my PC problems and still having the flue, I honestly didn’t read who was responding. That is why I mentioned the name Tom (it was his threat where I started posting). I know this sounds very stupid (and it is) but I have to be honest and apologize for this totally stupid assumption of mine. I don’t want to sound ungrateful NoelDP because I am very grateful to you guys. I apologies for this strange mix-up on my part. You must have thought, why in the hell does he call me Tom.

    So hereby NoelDP, from the bottom of my heart I would like to thank you for taking the time and afford to assist me in this (I thought) impossible repair. And also Tom who redirected my post(s) into a separate topic and making a great start! Normally, when I post these MS error's on other forums people say "just install your PC all over again" or "I am having the same problem but I can't fix it".

    I will post back when my health is better and I done my restore and fixes and full backup. If any other problems arise I will surely keep in touch. Wow, this is the best forum I come across ever!
      My Computer


  8. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #28

    Not a problem

    Good luck, and good health!
      My Computer


  9. Posts : 2,663
    Windows 8.1 Pro x64
       #29

    Hulkster said:
    Wow, my flue must have totally clouded my mind because I was under the impression that was helped by 1 person (Tom). Consumed by my PC problems and still having the flue, I honestly didn’t read who was responding. That is why I mentioned the name Tom (it was his threat where I started posting). I know this sounds very stupid (and it is) but I have to be honest and apologize for this totally stupid assumption of mine. I don’t want to sound ungrateful NoelDP because I am very grateful to you guys. I apologies for this strange mix-up on my part. You must have thought, why in the hell does he call me Tom.

    So hereby NoelDP, from the bottom of my heart I would like to thank you for taking the time and afford to assist me in this (I thought) impossible repair. And also Tom who redirected my post(s) into a separate topic and making a great start! Normally, when I post these MS error's on other forums people say "just install your PC all over again" or "I am having the same problem but I can't fix it".

    I will post back when my health is better and I done my restore and fixes and full backup. If any other problems arise I will surely keep in touch. Wow, this is the best forum I come across ever!
    No need to apologise, it's a simple mistake to make. Yeah, me and Noel are two of a handful of people who will attempt to fix these rather than go straight to reinstalling Windows so it's easy to confuse us, lol.

    Hope you're feeling better soon :)
      My Computer


  10. Posts : 25,847
    Windows 10 Pro. 64/ version 1709 Windows 7 Pro/64
       #30

    Noel and Tom do tag team well together.

    As always I'm lurking in the background watching them work.
      My Computer


 
Page 3 of 5 FirstFirst 12345 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:44.
Find Us