Win7 SP1 Update not installing - mismatched Mail file. 0x80004005

Page 3 of 6 FirstFirst 12345 ... LastLast

  1. Posts : 37
    Windows 7 Pro x64
    Thread Starter
       #21

    Am I reading correctly that the system32 version of the slwga.dll is not the latest x64 version contained in winsxs, it looks like the original x86 version. Should I copy over with the latest version or is this an update that the failing SP1 has downloaded but not yet applied?
      My Computer


  2. Posts : 37
    Windows 7 Pro x64
    Thread Starter
       #22

    @ NoelDP - I googled and found the Windows Validation page and ran it. No issues reported.

    Good to learn from these tests that my W7 installation is not showing corruption and potantial issues are being eliminated. In doing so, it seems we have wandered away from the initial issue and error message.

    Any further thoughts on how to either "reinstall" so that SP1 can uninstall or, in the alternative, convince SP1 that the feature it wants to uninstall is already uninstalled? I would think there is a registry entry that is driving all this attention toward an obsolete mail system. Does this trigger any ideas?


    Further update - Running the Fix-It MicrosoftFixit.wu.LB.132265375617751032.4.1 repeatedly, an error is always identified and reported as fixed so it makes me wonder whether the fix is sticking. Unfortunately there is scant reporting or log detail to identify the issue. Per the Fix-It's manual method, I renamed the SoftwareDistribution folder to see if a fresh scan might uncover an unapplied update required by SP1. Unfortunately, no joy! Some security updates were successfully applied, but SP1 errored out again - same error & issue.
    Last edited by DukeS; 10 Jul 2012 at 16:21. Reason: Listing one more tactic that was tried.
      My Computer


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

    Windows is (presumably) happy that the file is OK - let's see what the CheckSUR tool has to say for itself now.
    Download a fresh copy of the tool and run it Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, for Windows 7, and for Windows Server 2008 R2 - then post the CheckSUR.log file
      My Computer


  4. Posts : 37
    Windows 7 Pro x64
    Thread Starter
       #24

    Latest CheckSUR log says:

    Code:
    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7601.21645
    Package Version 15.0
    2012-07-10 15:47
    
    Checking Windows Servicing Packages
    
    Checking Package Manifests and Catalogs
    
    Checking Package Watchlist
    
    Checking Component Watchlist
    
    Checking Packages
    
    Checking Component Store
    
    Summary:
    Seconds executed: 1631
     No errors detected
    (w)    Unable to open Event Log    0x000006B5    Application        OpenEventLog failed: 0x000006B5 - The interface is unknown.
    .
    (w)    Unable to open Event Log    0x000006B5    System        OpenEventLog failed: 0x000006B5 - The interface is unknown.
    .
    In view of the Event log issue, ran SC QC EVENTLOG and got:
    Code:
    C:\Windows\system32>SC QC EVENTLOG
    [SC] QueryServiceConfig SUCCESS
    
    SERVICE_NAME: EVENTLOG
            TYPE               : 20  WIN32_SHARE_PROCESS
            START_TYPE         : 2   AUTO_START
            ERROR_CONTROL      : 1   NORMAL
            BINARY_PATH_NAME   : C:\Windows\System32\svchost.exe -k LocalServiceNetworkRestricted
            LOAD_ORDER_GROUP   : Event Log
            TAG                : 0
            DISPLAY_NAME       : Windows Event Log
            DEPENDENCIES       :
            SERVICE_START_NAME : NT AUTHORITY\LocalService
    The CBS log, attached, has a whole lot of "Failed to open package". Is this because I renamed the SoftwareDistribution folder?

    While I was in the CBS folder, I noticed that I had saved a log file from the last time I tried to solve this issue. This Log is also attached. What caught my attention was near the end:

    Code:
    POQ 128 starts:
     
    POQ 128 ends.
    2011-11-03 12:22:42, Info                  CSI    00000304 [SR] Verify complete
    2011-11-03 12:22:42, Info                  CSI    00000305 [SR] Repairing 1 components
    2011-11-03 12:22:42, Info                  CSI    00000306 [SR] Beginning Verify and Repair transaction
    2011-11-03 12:22:43, Info                  CSI    00000307 Hashes for file member \??\C:\Program Files\Windows Mail\msoe.dll do not match actual file [l:16{8}]"msoe.dll" :
      Found: {l:32 b:PZ9ks7Qp7NKxY6VvxmvhatJtz7c3N66FbCpPp1MLRxI=} Expected: {l:32 b:ejT8LNy4JLgkGRQ8Ycnx3nQzJL6Dd5w/1NrqDQGHQRw=}
    2011-11-03 12:22:43, Info                  CSI    00000308 [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Program Files\Windows Mail"\[l:16{8}]"msoe.dll" from store
    2011-11-03 12:22:43, Info                  CSI    00000309 Repair results created:
    POQ 129 starts:
         0: Move File: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\3f54e693559acc014839000060140806._0000000000000000.cdf-ms", Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"
        1: Move File: Source = [l:218{109}]"\SystemRoot\WinSxS\Temp\PendingRenames\a0b5e893559acc014939000060140806.program_files_ffd0cbfc813cc4f1.cdf-ms", Destination = [l:130{65}]"\SystemRoot\WinSxS\FileMaps\program_files_ffd0cbfc813cc4f1.cdf-ms"
        2: Move File: Source = [l:244{122}]"\SystemRoot\WinSxS\Temp\PendingRenames\0017eb93559acc014a39000060140806.program_files_windows_mail_e07902f329fe05e9.cdf-ms", Destination = [l:156{78}]"\SystemRoot\WinSxS\FileMaps\program_files_windows_mail_e07902f329fe05e9.cdf-ms"
        3: Hard Link File: Source = [l:238{119}]"\SystemRoot\WinSxS\amd64_microsoft-windows-mail-core-dll_31bf3856ad364e35_6.1.7600.16543_none_b49cf6153edc812f\msoe.dll", Destination = [l:84{42}]"\??\C:\Program Files\Windows Mail\msoe.dll"
    
    POQ 129 ends.
    2011-11-03 12:22:43, Info                  CSI    0000030a [SR] Repair complete
    2011-11-03 12:22:43, Info                  CSI    0000030b [SR] Committing transaction
    2011-11-03 12:22:43, Info                  CSI    0000030c Creating NT transaction (seq 2), objectname [6]"(null)"
    2011-11-03 12:22:43, Info                  CSI    0000030d Created NT transaction (seq 2) result 0x00000000, handle @0x1ac4
    2011-11-03 12:22:43, Info                  CSI    0000030e@2011/11/3:18:22:43.301 CSI perf trace:
    CSIPERF:TXCOMMIT;31680
    2011-11-03 12:22:43, Info                  CSI    0000030f [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired
    Perhaps this repair explains how the msoe.dll file got either matched or from SP1's perspective mismatched in the first place. If I recall correctly, the file at that time was the Vista msoe.dll and the repair killed the Vista-version Windows Mail that had been running up until then.
      My Computer


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

    I'm back with no head ache but no smarter. Validation code zero (0) means the operating system has not been validated by Microsoft and needs to be validated.
      My Computer


  6. Posts : 37
    Windows 7 Pro x64
    Thread Starter
       #26

    Hi Bear -

    I went to the validation page earlier when Noel pointed this out and ran the validator. No issues reported. No change in SP1. But results don't seem to stick anywhere.

    Other ideas? Especially with that repair log entry for the suspect file? Would it have left droppings behind?
    Last edited by DukeS; 10 Jul 2012 at 18:20. Reason: Finish note
      My Computer


  7. Posts : 37
    Windows 7 Pro x64
    Thread Starter
       #27

    Hey Noel - I couldn't find which pub you were hiding in so I bought you (or one of your kin) a virtual beer. I just can't tell you guys apart! And, so many welsh brands, I didn't know which you would like. At least this one says it's beer!

    Anyway, hope you enjoy it while coming up the next idea to try.

    Duke
    Attached Thumbnails Attached Thumbnails Win7 SP1 Update not installing - mismatched Mail file. 0x80004005-noeldp.jpg  
      My Computer


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

    Layback Bear said:
    I'm back with no head ache but no smarter. Validation code zero (0) means the operating system has not been validated by Microsoft and needs to be validated.
    No it doesn't :)
    In an MGADiag report, 0x0 implies 'no error'.

    In fact the clue comes later - where the line
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    appears - the AcitveX control hasn't been installed (or has been removed)
      My Computer


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

    DukeS said:
    Hey Noel - I couldn't find which pub you were hiding in so I bought you (or one of your kin) a virtual beer. I just can't tell you guys apart! And, so many welsh brands, I didn't know which you would like. At least this one says it's beer!

    Anyway, hope you enjoy it while coming up the next idea to try.

    Duke
    My pub....
    www.royaloakgreenfield.co.uk
    It's right next to what used to be the town brewery.
      My Computer


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

    There are a couple of causes for concern in the new CBS log....
    Failed to unload the COMPONENTS hive. [HRESULT = 0x80070005 - E_ACCESSDENIED]
    is the one that catches my eye.
    Problem is I have no real idea what it means :)

    What happens if you open Event Viewer??
      My Computer


 
Page 3 of 6 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:06.
Find Us