Windows Update Error Code 80073712 (kb976932) SP 1

Page 1 of 3 123 LastLast

  1. Posts : 14
    windows 7 professional 32bit
       #1

    Windows Update Error Code 80073712 (kb976932) SP 1


    As the title says I have problem installing/updating this.
    I've googled this problem and did the hotfix or windows readiness but still no problems were found or were to be fixed

    I also did the SFC scan yet still no good.

    I've included a screenshot of the error on the attachments and so with my CBS folder

    There's really not much to say but that I have no clue what has happened with this update failure since all other updates have been successful. I also even tried the command on stopping the windows service and restarting it yet still no luck. This is my first time to post and actually I was going over the other threads with the same problem but then I found the posting instructions. So please please please help!

    Oh yeah, the main reason is that, I want the free upgrade update on windows 10

    Thank you!
    Wy.
    Attached Thumbnails Attached Thumbnails Windows Update Error Code 80073712 (kb976932) SP 1-failedupdate.png  
      My Computer


  2. Posts : 14
    windows 7 professional 32bit
    Thread Starter
       #2

    I don't know if bumping is allowed but, bump pls :)
      My Computer


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

    Odd - CheckSUR is complaining of errors in the registry, but what I can see in the report looks perfectly OK to me.

    Code:
    Checking Component Store
    (f)	CSI Corrupt Component Keyform	0x00000000	identity	x86_microsoft-windows-r..ilityanalysisengine_31bf3856ad364e35_6.1.7601.17514_none_8a744e94f47f8489	identity and keyform do not match; keyform is wrong.
    (f)	CSI Corrupt Component Keyform	0x00000000	identity	x86_microsoft-windows-usp_31bf3856ad364e35_6.1.7601.17514_none_af01e2f9b6be7939	identity and keyform do not match; keyform is wrong.
    (f)	CSI Corrupt Component Keyform	0x00000000	identity	x86_microsoft-windows-i..l-keyboard-00000450_31bf3856ad364e35_6.1.7601.17514_none_e8d79520c2c34e33	identity and keyform do not match; keyform is wrong.
    (f)	CSI Corrupt Component Keyform	0x00000000	identity	x86_microsoft-windows-b..tiondata-com-server_31bf3856ad364e35_6.1.7601.17514_none_e1aac5cdc2fe634f	identity and keyform do not match; keyform is wrong.
    (f)	CSI Corrupt Component Keyform	0x00000000	identity	x86_microsoft-windows-erratamanager_31bf3856ad364e35_6.1.7601.17514_none_702de18eca1beb23	identity and keyform do not match; keyform is wrong.
    (f)	CSI Corrupt Component Keyform	0x00000000	identity	x86_microsoft-windows-raschap_31bf3856ad364e35_6.1.7601.17514_none_14c66cf0d58e8ff1	identity and keyform do not match; keyform is wrong.
    (f)	CSI Corrupt Component Keyform	0x00000000	identity	x86_microsoft-windows-tcpip_31bf3856ad364e35_6.1.7601.17514_none_638cffc7ed9bc3c3	identity and keyform do not match; keyform is wrong.
    (f)	CSI Corrupt Component Keyform	0x00000000	identity	x86_microsoft-windows-twext_31bf3856ad364e35_6.1.7601.17514_none_5e0c3b81f1369b05	identity and keyform do not match; keyform is wrong.
    (f)	CSI Payload File Missing	0x00000000	KBDBASH.DLL	x86_microsoft-windows-i..l-keyboard-0000046d_31bf3856ad364e35_6.1.7601.17514_none_ffe6f3b0b3f05340	
    (f)	CSI Payload File Missing	0x00000000	prevhost.exe	x86_microsoft-windows-shell-previewhost_31bf3856ad364e35_6.1.7601.17514_none_4544cf0e5f20beea	
    (f)	CSI Payload File Missing	0x00000000	KBDCZ1.DLL	x86_microsoft-windows-i..l-keyboard-00010405_31bf3856ad364e35_6.1.7601.17514_none_8e2deef7b3e701ea	
    (f)	CSI Payload File Missing	0x00000000	schannel.dll	x86_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.17514_none_241db4f9b384efcc	
    (f)	CSI Payload File Missing	0x00000000	net1.exe	x86_microsoft-windows-net1-command-line-tool_31bf3856ad364e35_6.1.7601.17514_none_88e35d5cb2d54359	
    (f)	CSI Payload File Missing	0x00000000	termsrv.dll	x86_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.1.7601.17514_none_90a6abb3b286306d	
    (f)	CSI Payload File Missing	0x00000000	dot3ui.dll	x86_microsoft-windows-dot3ui_31bf3856ad364e35_6.1.7601.17514_none_2ae95267b383c867	
    (f)	CSI Payload File Missing	0x00000000	odbccp32.dll	x86_microsoft-windows-m..-odbc-installer-dll_31bf3856ad364e35_6.1.7601.17514_none_8f326e5fb376d9c0	
    (f)	CSI Payload File Missing	0x00000000	stobject.dll	x86_microsoft-windows-stobject_31bf3856ad364e35_6.1.7601.17514_none_4c2a5fb4b3be1db1	
    (f)	CSI Payload File Missing	0x00000000	accessibilitycpl.dll	x86_microsoft-windows-accessibilitycpl_31bf3856ad364e35_6.1.7601.17514_none_5b652abeb21da986	
    (f)	CSI Payload File Missing	0x00000000	kernel32.dll	x86_microsoft-windows-kernel32_31bf3856ad364e35_6.1.7601.17514_none_95c54f2cb48da1b9	
    (f)	CSI Payload File Missing	0x00000000	mfc40u.dll	x86_microsoft-windows-mfc40u_31bf3856ad364e35_6.1.7601.17514_none_f51a7bf0b3d25294	
    (f)	CSI Payload File Missing	0x00000000	KBDINMAR.DLL	x86_microsoft-windows-i..l-keyboard-0000044e_31bf3856ad364e35_6.1.7601.17514_none_0058a86eb3a72485	
    (f)	CSI Payload File Missing	0x00000000	KBDINKAN.DLL	x86_microsoft-windows-i..l-keyboard-0000044b_31bf3856ad364e35_6.1.7601.17514_none_ff0412e4b48216f0	
    (f)	CSI Payload File Missing	0x00000000	winmm.dll	x86_microsoft-windows-audio-mmecore-base_31bf3856ad364e35_6.1.7601.17514_none_b7e72625aff23492	
    (f)	CSI Payload File Missing	0x00000000	rdpdd.dll	x86_microsoft-windows-t..s-rdp-displaydriver_31bf3856ad364e35_6.1.7601.17514_none_e6933edeb33b09b7	
    (f)	CSI Payload File Missing	0x00000000	KBDTUQ.DLL	x86_microsoft-windows-i..l-keyboard-0000041f_31bf3856ad364e35_6.1.7601.17514_none_00ca73f4b35ddc29	
    (f)	CSI Payload File Missing	0x00000000	uxlib.dll	x86_microsoft-windows-s..on-wizard-framework_31bf3856ad364e35_6.1.7601.17514_none_b85a4f21afbb528a	
    (f)	CSI Payload File Missing	0x00000000	KBDLT1.DLL	x86_microsoft-windows-i..l-keyboard-00010427_31bf3856ad364e35_6.1.7601.17514_none_8f10cfc3b3553e3a	
    (f)	CSI Payload File Missing	0x00000000	netcfg.exe	x86_microsoft-windows-netcfg_31bf3856ad364e35_6.1.7601.17514_none_123645a3afbba020	
    (f)	CSI Payload File Missing	0x00000000	logoncli.dll	x86_microsoft-windows-s..ity-netlogon-netapi_31bf3856ad364e35_6.1.7601.17514_none_d53d54cbb43c056c	
    (f)	CSI Payload File Missing	0x00000000	mprapi.dll	x86_microsoft-windows-mprapi_31bf3856ad364e35_6.1.7601.17514_none_1613eed7b146b444	
    (f)	CSI Payload File Missing	0x00000000	KBDGR1.DLL	x86_microsoft-windows-i..l-keyboard-00010407_31bf3856ad364e35_6.1.7601.17514_none_8f10fd53b3550af8	
    (f)	CSI Payload File Missing	0x00000000	KBDINHIN.DLL	x86_microsoft-windows-i..l-keyboard-00010439_31bf3856ad364e35_6.1.7601.17514_none_8ff3c757b2c360e9	
    
    Summary:
    Seconds executed: 677
     Found 32 errors
      CSI Corrupt Component Keyform Total count: 8
      CSI Payload File Missing Total count: 24
    It's possible that the missing payload files are causing part of this problem, so this is one of the rare cases where we need to attack the SFC results before the CheckSUR ones...
    Looking at the CBS.log, there is an error involving a Manifest file there which should have been picked up by CheckSUR...
    Code:
    2015-08-19 21:19:29, Error                 CSI    0000000d (F) Unable to load manifest for component [ml:280{140},l:158{79}]"x86_microsoft-windows-usp_31bf3856ad364e35_6.1.7601.17514_none_af01e2f9b6be7939"[gle=0x80004005]
    2015-08-19 21:19:29, Error                 CSI    0000000e@2015/8/19:13:19:29.744 (F) d:\win7sp1_gdr\base\wcp\componentstore\storelayout.cpp(2714): Store corruption detected in function ComponentStore::CRawStoreLayout::FetchManifestContent expression: 0
      FileHashMismatch on resource [106]"\winsxs\manifests\x86_microsoft-windows-usp_31bf3856ad364e35_6.1.7601.17514_none_af01e2f9b6be7939.manifest"[gle=0x80004005]
    2015-08-19 21:19:32, Error                 CSI    0000000f (F) HRESULT_FROM_WIN32(14098) #3023# from Windows::ServicingAPI::CCSITransactionAnalysis_ICSIInventory::GetDeploymentInformation(flags = 0, class = ICSIINVENTORY_GET_DEPLOYMENT_INFORMATION_CLASS_CLOSURE (1), information = {dwFlags=00000000})
    [gle=0x80073712]
    Going back through the CBSPersist logs, I find other errors which I would have expected CheckSUR to pick up on as well.

    The SFC scan itself was clear.
    While I try to get the fix protocol together for the missing files, I need to have a look at your COMPONENTS registry hive

    Please copy the C:\Windows\System32\config\COMPONENTS file (no extension) to your desktop and then compress it - upload the compressed file to your favoured fileshare site (preferably Dropbox or OneDrive) and post a link.
      My Computer


  4. Posts : 14
    windows 7 professional 32bit
    Thread Starter
       #4

    Actually I don't really know the results when I run SUR since after it installs it just says finish. I tried launching the application by typing the software name on the start button but it won't show anything. Sorry if I caused confusion about it.

    And about the SFC Scan, it just automatically closes after performing the command so I really don't know what happened.

    So when I looked at the posting instructions, the only thing I was able to do was to upload the CBS log and that's why I'm here now desperately trying to find help.

    Thank you for the response! I have included in the attachments the required file in zip.

    Wy.
      My Computer


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

    Sorry - I obviously wasn't clear at the start of my post - that first code box is the relevant output from the CheckSUR scan :)


    I've had a look at the registry hive - and it doesn't look pretty
    I suspect that there are a lot more errors hidden in there, and probably elsewhere in the registry - and I'm not sure it's going to be possible to repair them manually. There are a number of values present which appear to have come from other areas of updates - and it's this type of thing which is making both CheckSUR and SFC unreliable at best.

    I rather think your best option is a repair install of the OS, if you have the media available.
      My Computer


  6. Posts : 14
    windows 7 professional 32bit
    Thread Starter
       #6

    So the only option left is to reformat my pc or to reinstall my os?
      My Computer


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

    A Repair install is just that - it repairs the current install without deleting data or installed programs (usually!)
    See here for instructions... Repair Install
      My Computer


  8. Posts : 14
    windows 7 professional 32bit
    Thread Starter
       #8

    Oh thank yo so much! Sorry for my ignorance on such things :) I'll be gladly doing the reinstall now

    Thank you! I will post ASAP what happens to my computer after the reinstall :)
      My Computer


  9. Posts : 14
    windows 7 professional 32bit
    Thread Starter
       #9

    If I'm correct, what I need to follow is step 6? Since I do not have the SP1 update yet? But it seems that the download links are down and I'm having trouble searching for the ISO file without the SP1


    my question is, will it still work with the iso file with SP1?
      My Computer


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

    I've had mixed reports about that - My experience is that it does work - but that was a few years ago now, and more recent statements by others say that you cannot use an SP1 disk for a repair install of RTM Windows
      My Computer


 
Page 1 of 3 123 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:46.
Find Us