Microsoft Update - Language Pack Error 800706BE

Page 1 of 2 12 LastLast

  1. Posts : 18
    Windows 7 Ultimate 64bit
       #1

    Microsoft Update - Language Pack Error 800706BE


    Hi I've been trying to install Japanese for the last few hour when Update gave me this code 800706BE and whenever I'd install it, it give a message box saying

    Microsoft Visual C++ Runtime Library

    This application has requested the Runtime to terminate it in an unsual way.
    Please contact the application's support team for more information

    Incidentally whenever I would go to "Install display languages" then "Browse computer or network" it would give the same exact message box then another saying "Language Pack Installer has stop working"

    I think I have the option of re-installing the OS but incidentally I just did that 16 hours ago when I installed a new MOBO teehee...so I really don't want to go back there installing language usually being the last thing I do when prepping up, I would have to redo everything from the start again, any ideas?
      My Computer


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

    Please follow the Windows Update Posting Instructions and post the requested data
      My Computer


  3. Posts : 18
    Windows 7 Ultimate 64bit
    Thread Starter
       #3

    Hmm Okay the Code being:

    Code 800706BE
    Attachment 256830

    Weird Message Box just to be safe:

    Attachment 256829

    CBR files:

    Attachment 256828

    Code:
    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    
    Validation Code: 0
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-H4D9J-J2B4P-8DK9D
    Windows Product Key Hash: 1wB42v50x0uXdijeaGuGDrOZrA8=
    Windows Product ID: 00426-OEM-9154367-79481
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.1.7601.2.00010100.1.0.001
    ID: {29FFCD6B-A8A4-402C-9C4E-4ADF7DD70192}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Ultimate
    Architecture: 0x00000009
    Build lab: 7601.win7sp1_gdr.130104-1431
    TTS Error: 
    Validation Diagnostic: 
    Resolution Status: N/A
    
    Vista WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    
    Windows XP Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    File Exists: No
    Version: N/A, hr = 0x80070002
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002
    
    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002
    
    OGA Data-->
    Office Status: 100 Genuine
    Microsoft Office Enterprise 2007 - 100 Genuine
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005
    
    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files (x86)\Mozilla Firefox\firefox.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed
    
    File Scan Data-->
    File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[Hr = 0x80070003]
    File Mismatch: C:\Windows\system32\wat\npwatweb.dll[Hr = 0x80070003]
    File Mismatch: C:\Windows\system32\wat\watux.exe[Hr = 0x80070003]
    File Mismatch: C:\Windows\system32\wat\watweb.dll[Hr = 0x80070003]
    
    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{29FFCD6B-A8A4-402C-9C4E-4ADF7DD70192}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-8DK9D</PKey><PID>00426-OEM-9154367-79481</PID><PIDType>3</PIDType><SID>S-1-5-21-2794972190-1625447856-1390950012</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>3302</Version><SMBIOSVersion major="2" minor="7"/><Date>20121122000000.000000+000</Date></BIOS><HWID>C96B3A07018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Pacific Standard Time(GMT-08:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90120000-0030-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>C075330C9ED4D86</Val><Hash>k5+vI7tzg9Aw6zMRc9OhkO1wV0I=</Hash><Pid>89388-707-5803104-65309</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="12" Result="100"/><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="19" Version="12" Result="100"/><App Id="1A" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="44" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/><App Id="BA" Version="12" Result="100"/></Applications></Office></Software></GenuineResults>  
    
    Spsys.log Content: 0x80070002
    
    Licensing Data-->
    Software licensing service version: 6.1.7601.17514
    
    Name: Windows(R) 7, Ultimate edition
    Description: Windows Operating System - Windows(R) 7, OEM_COA_NSLP channel
    Activation ID: cfb3e52c-d707-4861-af51-11b27ee6169c
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00426-00182-543-679481-02-1033-7601.0000-0542013
    Installation ID: 018426732862239576485956050543552805789993572102898080
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
    Partial Product Key: 8DK9D
    License Status: Licensed
    Remaining Windows rearm count: 3
    Trusted time: 2/25/2013 2:38:12 AM
    
    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: N/A
    HealthStatus: 0x0000000000000000
    Event Time Stamp: N/A
    ActiveX: Not Registered - 0x80040154
    Admin Service: Not Registered - 0x80040154
    HealthStatus Bitmask Output:
    
    
    HWID Data-->
    HWID Hash Current: NgAAAAEAAwABAAEAAQADAAAAAgABAAEAHKJKYTzodMQKU2THgm0yGjC6oIPkroE/9KLIrC5z
    
    OEM Activation 1.0 Data-->
    N/A
    
    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information: 
      ACPI Table Name    OEMID Value    OEMTableID Value
      APIC            ALASKA        A M I
      FACP            ALASKA        A M I
      HPET            ALASKA        A M I
      MCFG            ALASKA        A M I
      FPDT            ALASKA        A M I
      SSDT            SataRe        SataTabl
      SSDT            SataRe        SataTabl
      SSDT            SataRe        SataTabl
      BGRT            ALASKA        A M I
      DMAR            INTEL         SNB
      My Computer


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

    I don't see any results from the CheckSUR tool??
      My Computer


  5. Posts : 18
    Windows 7 Ultimate 64bit
    Thread Starter
       #5

    Ahh about that it's was kind of 2am in the morning had to sleep just woke up, will be posting it a little late, sorry

    Um SURT said it successfully installed...what now? Can't find any new entries in the Start Menu

    Tried installing the Jap Language pack again...still no change

    Oh this might help though I made the mistake of installing Norton Symantics as it was bundled with my new Mobo's extra applications, then I tried installing the Language Pack and got the error, then found out that sometimes Apps like Norton interfere with the firewall so I decided to remove it using the Control Panel but not completely, It gave me the option keeping my settings if ever I wanted to install it again, now I look at my Win Firewall and it is no longer is managed by Norton but maybe it still might have left settings in my system although I doubt this, also even though I couldn't install the Language pack I could install other Updates except for a few others but with either different Codes errors attached to them or unimportant all-together
    Last edited by diemeow23; 24 Feb 2013 at 20:40. Reason: Update after installing SURT Win 7 64bit
      My Computer


  6. Posts : 18
    Windows 7 Ultimate 64bit
    Thread Starter
       #6

    Bumping Thread!
      My Computer


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

    You're not the only one who has to sleep occasionally :)
    Please post the C:\Windows\Logs\CBS\CheckSUR.log file
      My Computer


  8. Posts : 18
    Windows 7 Ultimate 64bit
    Thread Starter
       #8

    Hahaha Sorry about that

    Attachment 256913

    Anyway Here's the CheckSUR.log file along with a few of the files updated
      My Computer


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

    There's an awful lot of missing files - from KB2790655, KB2790113, KB2786400, KB2732059.

    It may take me a while, but I'll post back with a fix protocol later.

    For reference, the files are....
    Code:
     winsxs\manifests\x86_microsoft-windows-usp_31bf3856ad364e35_6.1.7601.18009_none_af119411b6b203d9.manifest
     winsxs\manifests\amd64_microsoft-windows-usp_31bf3856ad364e35_6.1.7601.18009_none_0b302f956f0f750f.manifest
     winsxs\manifests\amd64_microsoft-windows-consolehost_31bf3856ad364e35_6.1.7601.17965_none_d24cc50618e0e99c.manifest
     winsxs\manifests\amd64_microsoft-windows-kernel32_31bf3856ad364e35_6.1.7601.17965_none_f1aee2f66d12ac97.manifest
     winsxs\manifests\amd64_microsoft-windows-kernelbase_31bf3856ad364e35_6.1.7601.17965_none_84f37608cb5b3483.manifest
     winsxs\manifests\amd64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.17965_none_c616c5beee1655b2.manifest
     winsxs\manifests\msil_oxpsconverter.resources_31bf3856ad364e35_6.1.7601.17932_en-us_43cf59dda1e8ca92.manifest
     winsxs\manifests\amd64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.22209_none_c6e51d4206ffe39b.manifest
     winsxs\manifests\amd64_microsoft-windows-consolehost_31bf3856ad364e35_6.1.7601.22209_none_d31b1c8931ca7785.manifest
     winsxs\manifests\amd64_microsoft-windows-kernel32_31bf3856ad364e35_6.1.7601.22209_none_f27d3a7985fc3a80.manifest
     winsxs\manifests\amd64_microsoft-windows-winsrv_31bf3856ad364e35_6.1.7601.22209_none_153debdacc05e77d.manifest
     winsxs\manifests\amd64_microsoft-windows-kernelbase_31bf3856ad364e35_6.1.7601.22209_none_85c1cd8be444c26c.manifest
     winsxs\manifests\x86_microsoft-windows-usp_31bf3856ad364e35_6.1.7601.22171_none_af477f18d00f9c82.manifest
     winsxs\manifests\wow64_microsoft-windows-netio-infrastructure_31bf3856ad364e35_6.1.7601.22209_none_bfaf6c60195efb2c.manifest
     winsxs\manifests\amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17965_none_68a2edab92971725.manifest
     winsxs\manifests\x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17965_none_0c845227da39a5ef.manifest
     winsxs\manifests\msil_oxpsconverter.resources_31bf3856ad364e35_6.1.7601.22091_en-us_4416ed12bb382ec6.manifest
     winsxs\manifests\wow64_microsoft-windows-winsrv_31bf3856ad364e35_6.1.7601.22209_none_1f92962d0066a978.manifest
     winsxs\manifests\wow64_microsoft-windows-kernelbase_31bf3856ad364e35_6.1.7601.22209_none_901677de18a58467.manifest
     winsxs\manifests\wow64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.22209_none_d139c7943b60a596.manifest
     winsxs\manifests\wow64_microsoft-windows-kernel32_31bf3856ad364e35_6.1.7601.22209_none_fcd1e4cbba5cfc7b.manifest
     winsxs\manifests\amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.22209_none_6971452eab80a50e.manifest
     winsxs\manifests\x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.22209_none_0d52a9aaf32333d8.manifest
     winsxs\manifests\amd64_microsoft-windows-usp_31bf3856ad364e35_6.1.7601.22171_none_0b661a9c886d0db8.manifest
     winsxs\manifests\wow64_microsoft-windows-kernel32_31bf3856ad364e35_6.1.7601.17965_none_fc038d48a1736e92.manifest
     winsxs\manifests\wow64_microsoft-windows-winsrv_31bf3856ad364e35_6.1.7601.18043_none_1ed7b60fe76ee441.manifest
     winsxs\manifests\wow64_microsoft-windows-kernelbase_31bf3856ad364e35_6.1.7601.17965_none_8f48205affbbf67e.manifest
     winsxs\manifests\amd64_oxpsconverter_31bf3856ad364e35_6.1.7601.17933_none_0804e1f7c5c64bf1.manifest
     winsxs\manifests\wow64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.18043_none_d07ee7772268e05f.manifest
     winsxs\manifests\amd64_microsoft-windows-winsrv_31bf3856ad364e35_6.1.7601.18043_none_14830bbdb30e2246.manifest
     winsxs\manifests\amd64_oxpsconverter_31bf3856ad364e35_6.1.7601.22091_none_084b74e2df1696ce.manifest
     winsxs\manifests\amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.22209_none_11dd678a9616f2c8.manifest
     winsxs\manifests\amd64_microsoft-windows-netio-infrastructure_31bf3856ad364e35_6.1.7601.22209_none_b55ac20de4fe3931.manifest
     winsxs\manifests\amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.18042_none_112187237d20143a.manifest
     servicing\packages\Package_2_for_KB2786400~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_2_for_KB2786400~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_2_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_2_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_2_for_KB2790655~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_2_for_KB2790655~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_36_for_KB2732059~31bf3856ad364e35~amd64~~6.1.5.1.mum
     servicing\packages\Package_36_for_KB2732059~31bf3856ad364e35~amd64~~6.1.5.1.mum
     servicing\packages\Package_3_for_KB2786400~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_3_for_KB2786400~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_3_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_3_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_3_for_KB2790655~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_3_for_KB2790655~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_4_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_4_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_7_for_KB2732059~31bf3856ad364e35~amd64~~6.1.5.1.mum
     servicing\packages\Package_7_for_KB2732059~31bf3856ad364e35~amd64~~6.1.5.1.mum
     servicing\packages\Package_for_KB2732059_SP1~31bf3856ad364e35~amd64~~6.1.5.1.mum
     servicing\packages\Package_for_KB2732059_SP1~31bf3856ad364e35~amd64~~6.1.5.1.mum
     servicing\packages\Package_for_KB2732059~31bf3856ad364e35~amd64~~6.1.5.1.mum
     servicing\packages\Package_for_KB2732059~31bf3856ad364e35~amd64~~6.1.5.1.mum
     servicing\packages\Package_for_KB2786400_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2786400_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2786400~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2786400~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2790113_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_for_KB2790113_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_for_KB2790655_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2790655_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2790655~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2790655~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_2_for_KB2786400~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_2_for_KB2786400~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_2_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.cat
     servicing\packages\Package_2_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.cat
     servicing\packages\Package_2_for_KB2790655~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_2_for_KB2790655~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_36_for_KB2732059~31bf3856ad364e35~amd64~~6.1.5.1.cat
     servicing\packages\Package_36_for_KB2732059~31bf3856ad364e35~amd64~~6.1.5.1.cat
     servicing\packages\Package_3_for_KB2786400~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_3_for_KB2786400~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_3_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.cat
     servicing\packages\Package_3_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.cat
     servicing\packages\Package_3_for_KB2790655~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_3_for_KB2790655~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_4_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.cat
     servicing\packages\Package_4_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.cat
     servicing\packages\Package_7_for_KB2732059~31bf3856ad364e35~amd64~~6.1.5.1.cat
     servicing\packages\Package_7_for_KB2732059~31bf3856ad364e35~amd64~~6.1.5.1.cat
     servicing\packages\Package_for_KB2732059_SP1~31bf3856ad364e35~amd64~~6.1.5.1.cat
     servicing\packages\Package_for_KB2732059_SP1~31bf3856ad364e35~amd64~~6.1.5.1.cat
     servicing\packages\Package_for_KB2732059~31bf3856ad364e35~amd64~~6.1.5.1.cat
     servicing\packages\Package_for_KB2732059~31bf3856ad364e35~amd64~~6.1.5.1.cat
     servicing\packages\Package_for_KB2786400_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2786400_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2786400~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2786400~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2790113_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
     servicing\packages\Package_for_KB2790113_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
     servicing\packages\Package_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.cat
     servicing\packages\Package_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.cat
     servicing\packages\Package_for_KB2790655_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2790655_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2790655~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2790655~31bf3856ad364e35~amd64~~6.1.1.0.cat
      My Computer


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

    I've uploaded a file - dmwaa.zip - to my SkyDrive at Noel's SkyDrive
    Please download and save it.
    Right-click on the downloaded file, and select Extract all…
    Extract to the default location - which will create a new folder dmwaa in the same place.
    Open this folder - there should be two folders inside it (Manifests, and Packages)

    Copy the content of the Packages folder to the folder
    C:\Windows\Temp\CheckSur\Servicing\Packages

    And the content of the manifests folder (.manifest files) into this folder:

    C:\Windows\Temp\CheckSur\Winsxs\Manifests

    Now run the CheckSUR tool again (it may take a while)

    Post the new CheckSUR.log file, and the CheckSUR.persist.log file.
      My Computer


 
Page 1 of 2 12 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 12:17.
Find Us