Since 'fix', laptop no longer installs important updates

Page 2 of 5 FirstFirst 1234 ... LastLast

  1. Posts : 22
    Windows 7 Home Premium 64bit
    Thread Starter
       #11

    NoelDP said:
    The file size, date, permissions, and other obvious data appears to be correct for an RTM install.

    That being the case, please read the 'Answer' posted in this thread, and follow its instructions....
    Windows Update fails to install with error code 8e5e03fb - Microsoft Community
    Not sure why but the link is unavailable. I googled the page's title, but I couldn't get on it there either. Could you C+P the content here please?

    EDIT: Never mind, got on it.
      My Computer


  2. Posts : 22
    Windows 7 Home Premium 64bit
    Thread Starter
       #12

    Okay, so I followed those instructions and it was all going smoothly until I got to this part:

    III) Reregister DLL files that are associated with Cryptographic Services

    To register .dll files that are associated with Cryptographic Services, follow these steps:
    Click Start, type cmd in the Start Search box, right-click cmd.exe, and then click Run as administrator.

    At the command prompt, type the following commands, and press ENTER after each command:
    regsvr32 /u softpub.dll
    regsvr32 /u wintrust.dll
    regsvr32 /u initpki.dll
    regsvr32 /u dssenh.dll
    regsvr32 /u rsaenh.dll
    regsvr32 /u gpkcsp.dll
    regsvr32 /u sccbase.dll
    regsvr32 /u slbcsp.dll

    regsvr32 /u mssip32.dll
    regsvr32 /u cryptdlg.dll


    regsvr32 softpub.dll
    regsvr32 wintrust.dll
    regsvr32 initpki.dll
    regsvr32 dssenh.dll
    regsvr32 rsaenh.dll
    regsvr32 gpkcsp.dll
    regsvr32 sccbase.dll
    regsvr32 slbcsp.dll

    regsvr32 mssip32.dll
    regsvr32 cryptdlg.dll
    exit
    Note: Click OK if you are prompted.

    Restart the computer.
    Most of them came out okay, but some of them (in bold), did not. I continued onto the next step to see if it mattered.

    IV) Empty the software distribution folder
    Click Start, type services.msc in the Start Search box, right-click services.msc, and then click Run as administrator.
    In the Services (Local) pane, right-click Automatic Updates, and then click Stop.
    Minimize the Services (local) window.
    Select all the contents of the Windows distribution folder, and then delete them.

    Note By default, the Windows distribution folder is located in the drive:\Windows\SoftwareDistribution folder. In this location, drive is a placeholder for the drive where Windows is installed.
    Make sure that the Windows distribution folder is empty, and then maximize the Services (local) window.
    In the Services (Local) pane, right-click Automatic Updates, and then click Start.
    Restart the computer, and then run Windows Update again.
    The problem was 'Automatic Updates' was nowhere to be found. The closest thing to it was "Windows Updates" which was set to automatic, so I stopped that. Then I looked for the Windows Distribution folder, but the 'drive is a placeholder...' lost me. There was no 'drive'

    Anyway, I reset that to how it was before, with Windows Updates back on, and tried doing the updates. Same problem; 0%.

    Then I ran the sfc /scannow, and instead of stopping at 34% as it had previously, it completed. It said there were corrupt(?) files, but it couldn't fix them. It also said it stored them in the CBS folder. So I thought I'd reupload that, to see if anything different is in there.
      My Computer


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

    The list of dll's is all-embracing (for XP through to Win7) so some don't exist :)
    Good - at least the SFC completes now.

    The problem files from the CBS log are....
    Code:
     Line 20040: 2013-01-27 20:20:22, Info                  CSI    0000033d [SR] Beginning Verify and Repair transaction
     Line 20041: 2013-01-27 20:20:22, Info                  CSI    0000033e [SR] Cannot repair member file [l:64{32}]"BabyBoyMainToNotesBackground.wmv" of Microsoft-Windows-OpticalMediaDisc-Style-BabyBoy, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
     Line 20042: 2013-01-27 20:20:22, Info                  CSI    0000033f [SR] Cannot repair member file [l:72{36}]"BabyBoyMainToNotesBackground_PAL.wmv" of Microsoft-Windows-OpticalMediaDisc-Style-BabyBoy, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
     Line 20043: 2013-01-27 20:20:22, Info                  CSI    00000340 [SR] Cannot repair member file [l:66{33}]"BabyBoyMainToScenesBackground.wmv" of Microsoft-Windows-OpticalMediaDisc-Style-BabyBoy, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
     Line 20044: 2013-01-27 20:20:22, Info                  CSI    00000341 [SR] Cannot repair member file [l:74{37}]"BabyBoyMainToScenesBackground_PAL.wmv" of Microsoft-Windows-OpticalMediaDisc-Style-BabyBoy, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
     Line 20047: 2013-01-27 20:20:22, Info                  CSI    00000343 [SR] Cannot repair member file [l:20{10}]"vssapi.dll" of Microsoft-Windows-VssApi, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 20050: 2013-01-27 20:20:22, Info                  CSI    00000345 [SR] Cannot repair member file [l:22{11}]"chtbrkr.dll" of Microsoft-Windows-WordbreakerStemmer-ChineseTraditional, Version = 7.0.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    Interestingly, the vssapi.dll file is still flagged, so I wasn't too far off :)

    I'll post back a bit later with a fix protocol for these problems.
    Please run another CheckSUR scan/install, and post the new CheckSUR.log - assuming it completes.
      My Computer


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

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

    Right-click on the saved file and select Extract all...
    Change the target to C:\ and click on Extract
    This should create a folder C:\li147a

    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:\li147a
    hit the enter key - if you get a 'Not Found' error try
    DIR D:\li147a
    or
    DIR E:\li147a


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

    XCOPY <drive>:\li147a <drive>:\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 SkyDrive Public folder, and post a new link

    Also run a new MGADiag report, and post the result.

      My Computer


  5. Posts : 22
    Windows 7 Home Premium 64bit
    Thread Starter
       #15

    Well, believe it or not, instead of seven updates, three came up, so I tried installing them. Seemed to all go well, but one (Windows Service Pack I think) didn't install. The error was 0x800f0816.

    Anyway, I'll run the CheckSUR scan. Assuming that fails I'll follow the instructions from your next post.
      My Computer


  6. Posts : 22
    Windows 7 Home Premium 64bit
    Thread Starter
       #16

    Tried to run the SUR scan again...

    Initializing installation... done! >>> Didn't get this before
    Installing Hotfix for Windows (KB947821) (update 1 of 1)...

    Got to the next part, and didn't do anything. The installation bar never moved, so I'm going to do a reboot as above.
      My Computer


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

    The installation bar usually sticks for a while - that's normal.
    I have seen it not move for an hour or more, before zipping along to the end.
    It all depends how much work it's having to do at what point in the process.
      My Computer


  8. Posts : 22
    Windows 7 Home Premium 64bit
    Thread Starter
       #18

    You've seen it go over an hour without even starting? If it moved at all I'd be more reassured. I'll run it again now. By the way, I ran the sfc scan, the log wouldn't go in my folder so I'll put it in here. It says it found and repaired the corrupt files this time.
      My Computer


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

    Ah- not starting is unusual - it normally tends to stick at around 30% and 70%.....
    Have you checked for disk activity at that time? - or CPU usage (in Task Manager or Resource Monitor?)

    It did actually start - it discovered the same errors as the SFC....
    Code:
    2013-01-27 21:25
    Checking Windows Servicing Packages
    Checking Package Manifests and Catalogs
    Checking Package Watchlist
    Checking Component Watchlist
    Checking Packages
    Checking Component Store
    (f) CSI Payload File Missing 0x00000000 BabyBoyMainToNotesBackground.wmv amd64_microsoft-windows-o..adisc-style-babyboy_31bf3856ad364e35_6.1.7600.16385_none_f13596916b261f67 
    (f) CSI Payload File Missing 0x00000000 BabyBoyMainToNotesBackground_PAL.wmv amd64_microsoft-windows-o..adisc-style-babyboy_31bf3856ad364e35_6.1.7600.16385_none_f13596916b261f67 
    (f) CSI Payload File Missing 0x00000000 BabyBoyMainToScenesBackground.wmv amd64_microsoft-windows-o..adisc-style-babyboy_31bf3856ad364e35_6.1.7600.16385_none_f13596916b261f67 
    (f) CSI Payload File Missing 0x00000000 BabyBoyMainToScenesBackground_PAL.wmv amd64_microsoft-windows-o..adisc-style-babyboy_31bf3856ad364e35_6.1.7600.16385_none_f13596916b261f67
    but never got to the registry checks.
      My Computer


  10. Posts : 22
    Windows 7 Home Premium 64bit
    Thread Starter
       #20

    Well like I say, this time it sort of started, but the bar didn't fill at all, so it looked like it'd just frozen. I might leave it on for a while to see if it moves at all.

    I've not really got anything else running. I've been using my phone primarily today, to let this try sort itself out, so CPU usage isn't a problem. Only at 18% now.
      My Computer


 
Page 2 of 5 FirstFirst 1234 ... 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 04:55.
Find Us