If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Windows Component Store is Corrupt - Error 80073712
I have Internet Explorer 11, 32 bit and Windows 7 Home Premium, bit 64.
Windows Update will not download and install updates except the very very odd one. So far there are thirty updates missing. The main error number is 80073712. Can anyone solve this for me please. |
Ads |
#2
|
|||
|
|||
Windows Component Store is Corrupt - Error 80073712
Emrys Davies wrote:
I have Internet Explorer 11, 32 bit and Windows 7 Home Premium, bit 64. Windows Update will not download and install updates except the very very odd one. So far there are thirty updates missing. The main error number is 80073712. Can anyone solve this for me please. For Windows 7, you use a CheckSUR download from the bottom of the page. Try to select a matching download, for your system setup. https://support.microsoft.com/en-ca/...date-readiness They're also available from Catalog. https://www.catalog.update.microsoft....aspx?q=947821 The files should be updated for those, as time passes. Download a fresh one, before using it. One a year old isn't much good to you. ******* On Windows 10, it's easier. Dism /Online /Cleanup-Image /CheckHealth Dism /Online /Cleanup-Image /ScanHealth Dism /Online /Cleanup-Image /RestoreHealth ******* The CheckSUR should be similar to a RestoreHealth. Paul |
#3
|
|||
|
|||
Windows Component Store is Corrupt - Error 80073712
"Paul" wrote in message news Emrys Davies wrote: I have Internet Explorer 11, 32 bit and Windows 7 Home Premium, bit 64. Windows Update will not download and install updates except the very very odd one. So far there are thirty updates missing. The main error number is 80073712. Can anyone solve this for me please. For Windows 7, you use a CheckSUR download from the bottom of the page. Try to select a matching download, for your system setup. https://support.microsoft.com/en-ca/...date-readiness They're also available from Catalog. https://www.catalog.update.microsoft....aspx?q=947821 The files should be updated for those, as time passes. Download a fresh one, before using it. One a year old isn't much good to you. ******* On Windows 10, it's easier. Dism /Online /Cleanup-Image /CheckHealth Dism /Online /Cleanup-Image /ScanHealth Dism /Online /Cleanup-Image /RestoreHealth ******* The CheckSUR should be similar to a RestoreHealth. Paul I am trying to fix the corrupted component store. Does what you have suggested help that endeavour. If it does, it is quite a way beyond me unless you walk me through it gently. |
#4
|
|||
|
|||
Windows Component Store is Corrupt - Error 80073712
Emrys Davies wrote:
I am trying to fix the corrupted component store. Does what you have suggested help that endeavour. If it does, it is quite a way beyond me unless you walk me through it gently. The theory is, you should be able to run a CheckSUR even on a C: that doesn't need it. It's supposed to repair/verify the WinSXS folder. Steps: 1) Click the download for your OS, either the 32 bit one or the 64 bit one. Your System control panel contains a text string identifying the OS. System == System Type: 32-bit Operating system 32-bit W7SP1 https://www.microsoft.com/download/details.aspx?id=3132 64-bit W7SP1 https://www.microsoft.com/download/d....aspx?id=20858 2) The file that is downloaded, is a .msu, an executable file. You double click it. Windows6.1-KB947821-v34-x86.msu 239,126,136 bytes Windows6.1-KB947821-v34-x64.msu 564,744,309 bytes 3) It will take at least ten minutes for the running MSU installer to complete. 4) When it finished, the details (that I can see here) are in: C:\Windows\Logs\CheckSUR.log Here is a picture of my step (4). https://i.postimg.cc/ZqrDjCVr/check-...tput-files.gif I found that file by searching in Explorer for "CBS" which stands for Component Based Servicing. The WinSXS folder is the "trove" that CBS uses for maintaining your OS and keeping copies of necessary things. If something was corrected, it should be in the log. I ran that demo on a virtual machine. I made a backup. Now, I'll be doing a restore to a previous point in time, just to reduce bloat... CheckSUR has "versions", which is why the version 26 I installed today, if I downloaded and ran two months from now, it could be version 27, and it would install like version 26 did. Version 27 would "Supercede" version 26, which is why Version 27 would install. You only need to run that, when other parts of the system provide feedback something is wrong with your WinSXS store. Sometimes the errors in WinSXS are "false positives". You'll know this when CheckSUR says it "couldn't fix something" and there might be mention the file was an HTML file. An HTML file is not normally a part of the store and could be ignored. The store would have DLLs and some sort of catalog files, which you can examine at your leisure to see what's in there. If your store is corrupted, it will likely be repairing more important items. Paul |
#5
|
|||
|
|||
Windows Component Store is Corrupt - Error 80073712
Emrys Davies wrote:
"Paul" wrote in message news After getting to the folder, you can have a look around, such as cd /d C:\Windows\Logs\ dir notepad CheckSUR.log This was shown with masses of log details , but I could not see anything of interest, but then that was me trying to be a 'Master' when I was totally out of my depth. What you're looking for, is "cannot fix" type messages, where CheckSUR didn't finish its job. If it seems to have repaired everything, then your Windows Update should be working again and so on. Paul |
#6
|
|||
|
|||
Windows Component Store is Corrupt - Error 80073712
"Paul" wrote in message news Emrys Davies wrote: "Paul" wrote in message news After getting to the folder, you can have a look around, such as cd /d C:\Windows\Logs\ dir notepad CheckSUR.log This was shown with masses of log details , but I could not see anything of interest, but then that was me trying to be a 'Master' when I was totally out of my depth. What you're looking for, is "cannot fix" type messages, where CheckSUR didn't finish its job. If it seems to have repaired everything, then your Windows Update should be working again and so on. Paul Nothing has changed. The Windows Update continues to fail except for three which continue to install, over and over again, regardless. The others continue to fail over and over again. All were acting like that before we intervened. I know what is wrong it is me trying to put into action what you have requested with me being totally out of my depth and I thank you sincerely for being so persistent and patient. |
#7
|
|||
|
|||
Windows Component Store is Corrupt - Error 80073712
Emrys Davies wrote:
Nothing has changed. The Windows Update continues to fail except for three which continue to install, over and over again, regardless. The others continue to fail over and over again. All were acting like that before we intervened. I know what is wrong it is me trying to put into action what you have requested with me being totally out of my depth and I thank you sincerely for being so persistent and patient. We're not out of options yet. One question I have, before suggesting new things to try, is did "Windows Component Store is Corrupt - Error 80073712" go away ? Or is that still happening ? If you're still getting that error, then it's possible other operations will not run or work right. It's important to fix that. ******* Write down the failed (looping) KB numbers. They are likely queued up behind the thing that is really jammed. Look in Windows Update "history" tab, for the first one that failed, that never got fixed by a later attempt to install it. Let's say KB12345678 is missing. Go to https://www.catalog.update.microsoft.com/Home.aspx and type in the failed KB number as "KBxxxxxxx" or so. The search will return candidates. Make sure you grab the 64 bit one for a 64-bit OS. Click the Download button. If you see a "Delta" one in the list, ignore. What you really want to download, is one ending in .msu. You can double-click the file once it downloads. I find that SoftwareDistribution problems can sometimes be bypassed, by manually doing the .msu based installs instead. Once you fix the one that is actually jamming up the works, the others sometimes then install with no further fuss. ******* You can clean out SoftwareDistribution. There are scripts for this. https://www.sevenforums.com/tutorial...ate-reset.html You can instead, also look in Control Panels for Troubleshooter, and use the Windows Update one for fun. This is safer, because Microsoft is doing it :-/ https://i.postimg.cc/Hj1gJMGS/troubleshooter.gif Paul |
#8
|
|||
|
|||
Windows Component Store is Corrupt - Error 80073712
"Paul" wrote in message news Emrys Davies wrote: Nothing has changed. The Windows Update continues to fail except for three which continue to install, over and over again, regardless. The others continue to fail over and over again. All were acting like that before we intervened. I know what is wrong it is me trying to put into action what you have requested with me being totally out of my depth and I thank you sincerely for being so persistent and patient. We're not out of options yet. One question I have, before suggesting new things to try, is did "Windows Component Store is Corrupt - Error 80073712" go away ? Or is that still happening ? That error is still ever present If you're still getting that error, then it's possible other operations will not run or work right. It's important to fix that. ******* Write down the failed (looping) KB numbers. They are likely queued up behind the thing that is really jammed. Look in Windows Update "history" tab, for the first one that failed, that never got fixed by a later attempt to install it. Let's say KB12345678 is missing. Go to https://www.catalog.update.microsoft.com/Home.aspx and type in the failed KB number as "KBxxxxxxx" or so. The prominent looping number is KB3071756 The search will return candidates. Make sure you grab the 64 bit one for a 64-bit OS. Click the Download button. If you see a "Delta" one in the list, ignore. What you really want to download, is one ending in .msu. You can double-click the file once it downloads. I find that SoftwareDistribution problems can sometimes be bypassed, by manually doing the .msu based installs instead. Once you fix the one that is actually jamming up the works, the others sometimes then install with no further fuss. I found one likely search result for KB3071756 out of 17 suggestions and it made an effort to install it after initializing but it failed saying 'The following updates were not installed (KB3071756) You can clean out SoftwareDistribution. There are scripts for this. https://www.sevenforums.com/tutorial...ate-reset.html You can instead, also look in Control Panels for Troubleshooter, and use the Windows Update one for fun. This is safer, because Microsoft is doing it :-/ https://i.postimg.cc/Hj1gJMGS/troubleshooter.gif Paul Done the latter many time and very recently, but without success. One point of interest: These two updates repeatedly download successfully and they mostly head the failed ones. They are KB3004375 and KB3031432. Microsoft Security Essentials KB2310138, which I installed quite recently, has always been successful but repeated itself several times, but not of late. |
#9
|
|||
|
|||
Windows Component Store is Corrupt - Error 80073712
Emrys Davies wrote:
"Paul" wrote in message news Emrys Davies wrote: Nothing has changed. The Windows Update continues to fail except for three which continue to install, over and over again, regardless. The others continue to fail over and over again. All were acting like that before we intervened. I know what is wrong it is me trying to put into action what you have requested with me being totally out of my depth and I thank you sincerely for being so persistent and patient. We're not out of options yet. One question I have, before suggesting new things to try, is did "Windows Component Store is Corrupt - Error 80073712" go away ? Or is that still happening ? That error is still ever present If you're still getting that error, then it's possible other operations will not run or work right. It's important to fix that. ******* Write down the failed (looping) KB numbers. They are likely queued up behind the thing that is really jammed. Look in Windows Update "history" tab, for the first one that failed, that never got fixed by a later attempt to install it. Let's say KB12345678 is missing. Go to https://www.catalog.update.microsoft.com/Home.aspx and type in the failed KB number as "KBxxxxxxx" or so. The prominent looping number is KB3071756 The search will return candidates. Make sure you grab the 64 bit one for a 64-bit OS. Click the Download button. If you see a "Delta" one in the list, ignore. What you really want to download, is one ending in .msu. You can double-click the file once it downloads. I find that SoftwareDistribution problems can sometimes be bypassed, by manually doing the .msu based installs instead. Once you fix the one that is actually jamming up the works, the others sometimes then install with no further fuss. I found one likely search result for KB3071756 out of 17 suggestions and it made an effort to install it after initializing but it failed saying 'The following updates were not installed (KB3071756) You can clean out SoftwareDistribution. There are scripts for this. https://www.sevenforums.com/tutorial...ate-reset.html You can instead, also look in Control Panels for Troubleshooter, and use the Windows Update one for fun. This is safer, because Microsoft is doing it :-/ https://i.postimg.cc/Hj1gJMGS/troubleshooter.gif Paul Done the latter many time and very recently, but without success. One point of interest: These two updates repeatedly download successfully and they mostly head the failed ones. They are KB3004375 and KB3031432. Microsoft Security Essentials KB2310138, which I installed quite recently, has always been successful but repeated itself several times, but not of late. It suggests here, the damage was done in the year 2015. https://answers.microsoft.com/en-us/...0-2f0e99612b53 You've probably gone past my pay scale right there. My skill set is limited to relatively simple things, like jamming in a pesky .msu manually and hoping for the best. ******* A question from me would be, "does the broken component store prevent KB removals?". I don't know that. And that's how computer maintenance works. There are several possibilities 0) update in-flight stuck - not likely in this case because the machine still boots. An update will resolve as "failed" or "succeeded" upon boot, and can't be in-flight then. 1) updating blocked in the forward direction (install .msu is typical solution) 2) update and corrective removal blocked at the same time, preventing forward or backward movement without fixing one of them. Might have to fix removal problem first. 3) Deadly embrace. Forward and backward movement "share" something, such that any attempt to do either, results in failure. I've experienced this on Gentoo Linux, for example. I managed to fix one of these once, with guided help. And a couple other times, not. I was at my limits on "thinking" and "playing chess" on those. I'm *hoping* in your case, it's (1) and the corrupted component store is a red herring. And that removal of those suggested KBs might have some positive effect. But that's a long shot. CheckSUR should normally be able to repair the WinSXS component store. And that's why, examining the checksur log was important, to see if there are any comments that might suggest your situation is a (2). As far as I know, Windows doesn't have (3), and that's just a Gentoo thing - on Gentoo it happens because the OS changes entire software subsystems on the fly, something Windows doesn't do. Before doing anything rash, do a system backup capturing C: and System Reserved (if you have one). That's in case you break something while working on it. ******* You can prepare a patch collection with this for Windows 7. http://download.wsusoffline.net/ That's a tool which prepares a complete patch set for a virgin OS. Once the DVD or USB stick is prepared, the idea is, you can plug the media into any Windows 7 machine and patch it up-to-date to todays date. How it works, is the tool downloads wsusscn2.cab (250MB from Microsoft) and works out a patch list. The tool has folders with "exceptions" and patches it does not plan on installing. The tool currently has a nuance, in that you can select "Security Only" patches and (perhaps) avoid adding CEIP (Customer Experience Improvement Program, a kind of program performance spyware) support to your OS. Just ticking the right tick boxes for shortest preparation time, is an art with that tool. It will take you a few tries before you become comfortable with preparing one. If you tick too many boxes, you will get several 800MB Service Pack files for example. The only penalty for ticking too many boxes, is an extremely long download time. An "economical" preparation still has to download 250 files or so. The files don't have to be stored any place magical. There's no benefit to putting the files on an ISO or a USB stick. The reason for putting the files on media, is for easy sharing or bulk deployment (in your IT kit bag). As long as you can get at the folder with the "file collection" in it, that's what counts the most. You could, for example, access the files via file sharing or something. But the tool does have tick boxes which make it seem like "output media" is the only option. You can simply have the files collected right next to the tool itself, and deal with loading the files onto a USB stick later. The tool has a "collector" to collect the patch, and a "client installer". You run the "client installer" when you take the USB stick to some machine. Nothing prevents you from running the "client installer" on the same machine as you did the collecting with. In the client subfolder, is where you run the installer and have it figure out what to install. The *files* being downloaded, come from Microsoft, *not* from wsusoffline. All that wsusoffline does in this case, is craft the update list and fetch the files. The files are still straight from Microsoft. Microsoft would send out its legal team, if any attempt was made to serve the files directly from a wsusoffline server. The only way wsusoffline would improve the current situation, is if some supersedence in it allowed removal of the pesky patches automatically. But that tool is another way to patch up a Windows system. If you do a "Repair Install" of your OS, you can use wsusoffline stick to security patch it up-to-date. One magical thing the wsusoffline has, is it has a short list of patches (around five or so) that are critical to getting Windows Update to stop looping on a virgin system. Once the five patches are installed, the "delay" before Windows does anything with the patches, is reduced. Your current system already has the critical patches in place (since Windows Update is nominally working now to fetch updates). ******* All I've got to offer you, is the above answers.microsoft.com thread. I couldn't find anything on askwoody.com that seemed applicable. You're probably three years behind on patching. Not that this is important in any way. It's just for perspective I'm pointing this out. Being jammed is good, in the sense that if you can locate the two named patches in the thread, removing those patches might still help - even though it's three years later. Paul |
#10
|
|||
|
|||
Windows Component Store is Corrupt - Error 80073712
"Paul" wrote in message news Emrys Davies wrote: "Paul" wrote in message news Emrys Davies wrote: Nothing has changed. The Windows Update continues to fail except for three which continue to install, over and over again, regardless. The others continue to fail over and over again. All were acting like that before we intervened. I know what is wrong it is me trying to put into action what you have requested with me being totally out of my depth and I thank you sincerely for being so persistent and patient. We're not out of options yet. One question I have, before suggesting new things to try, is did "Windows Component Store is Corrupt - Error 80073712" go away ? Or is that still happening ? That error is still ever present If you're still getting that error, then it's possible other operations will not run or work right. It's important to fix that. ******* Write down the failed (looping) KB numbers. They are likely queued up behind the thing that is really jammed. Look in Windows Update "history" tab, for the first one that failed, that never got fixed by a later attempt to install it. Let's say KB12345678 is missing. Go to https://www.catalog.update.microsoft.com/Home.aspx and type in the failed KB number as "KBxxxxxxx" or so. The prominent looping number is KB3071756 The search will return candidates. Make sure you grab the 64 bit one for a 64-bit OS. Click the Download button. If you see a "Delta" one in the list, ignore. What you really want to download, is one ending in .msu. You can double-click the file once it downloads. I find that SoftwareDistribution problems can sometimes be bypassed, by manually doing the .msu based installs instead. Once you fix the one that is actually jamming up the works, the others sometimes then install with no further fuss. I found one likely search result for KB3071756 out of 17 suggestions and it made an effort to install it after initializing but it failed saying 'The following updates were not installed (KB3071756) You can clean out SoftwareDistribution. There are scripts for this. https://www.sevenforums.com/tutorial...ate-reset.html You can instead, also look in Control Panels for Troubleshooter, and use the Windows Update one for fun. This is safer, because Microsoft is doing it :-/ https://i.postimg.cc/Hj1gJMGS/troubleshooter.gif Paul Done the latter many time and very recently, but without success. One point of interest: These two updates repeatedly download successfully and they mostly head the failed ones. They are KB3004375 and KB3031432. Microsoft Security Essentials KB2310138, which I installed quite recently, has always been successful but repeated itself several times, but not of late. It suggests here, the damage was done in the year 2015. https://answers.microsoft.com/en-us/...0-2f0e99612b53 You've probably gone past my pay scale right there. My skill set is limited to relatively simple things, like jamming in a pesky .msu manually and hoping for the best. ******* A question from me would be, "does the broken component store prevent KB removals?". I don't know that. And that's how computer maintenance works. There are several possibilities 0) update in-flight stuck - not likely in this case because the machine still boots. An update will resolve as "failed" or "succeeded" upon boot, and can't be in-flight then. 1) updating blocked in the forward direction (install .msu is typical solution) 2) update and corrective removal blocked at the same time, preventing forward or backward movement without fixing one of them. Might have to fix removal problem first. 3) Deadly embrace. Forward and backward movement "share" something, such that any attempt to do either, results in failure. I've experienced this on Gentoo Linux, for example. I managed to fix one of these once, with guided help. And a couple other times, not. I was at my limits on "thinking" and "playing chess" on those. I'm *hoping* in your case, it's (1) and the corrupted component store is a red herring. And that removal of those suggested KBs might have some positive effect. But that's a long shot. CheckSUR should normally be able to repair the WinSXS component store. And that's why, examining the checksur log was important, to see if there are any comments that might suggest your situation is a (2). As far as I know, Windows doesn't have (3), and that's just a Gentoo thing - on Gentoo it happens because the OS changes entire software subsystems on the fly, something Windows doesn't do. Before doing anything rash, do a system backup capturing C: and System Reserved (if you have one). That's in case you break something while working on it. I backed up my contacts, WLM and hard drive to my external hard drive last week and it appeared to be successful. You can prepare a patch collection with this for Windows 7. http://download.wsusoffline.net/ That's a tool which prepares a complete patch set for a virgin OS. Once the DVD or USB stick is prepared, the idea is, you can plug the media into any Windows 7 machine and patch it up-to-date to todays date. How it works, is the tool downloads wsusscn2.cab (250MB from Microsoft) and works out a patch list. The tool has folders with "exceptions" and patches it does not plan on installing. The tool currently has a nuance, in that you can select "Security Only" patches and (perhaps) avoid adding CEIP (Customer Experience Improvement Program, a kind of program performance spyware) support to your OS. Just ticking the right tick boxes for shortest preparation time, is an art with that tool. It will take you a few tries before you become comfortable with preparing one. If you tick too many boxes, you will get several 800MB Service Pack files for example. The only penalty for ticking too many boxes, is an extremely long download time. An "economical" preparation still has to download 250 files or so. The files don't have to be stored any place magical. There's no benefit to putting the files on an ISO or a USB stick. The reason for putting the files on media, is for easy sharing or bulk deployment (in your IT kit bag). As long as you can get at the folder with the "file collection" in it, that's what counts the most. You could, for example, access the files via file sharing or something. But the tool does have tick boxes which make it seem like "output media" is the only option. You can simply have the files collected right next to the tool itself, and deal with loading the files onto a USB stick later. The tool has a "collector" to collect the patch, and a "client installer". You run the "client installer" when you take the USB stick to some machine. Nothing prevents you from running the "client installer" on the same machine as you did the collecting with. In the client subfolder, is where you run the installer and have it figure out what to install. The *files* being downloaded, come from Microsoft, *not* from wsusoffline. All that wsusoffline does in this case, is craft the update list and fetch the files. The files are still straight from Microsoft. Microsoft would send out its legal team, if any attempt was made to serve the files directly from a wsusoffline server. The only way wsusoffline would improve the current situation, is if some supersedence in it allowed removal of the pesky patches automatically. But that tool is another way to patch up a Windows system. If you do a "Repair Install" of your OS, you can use wsusoffline stick to security patch it up-to-date. One magical thing the wsusoffline has, is it has a short list of patches (around five or so) that are critical to getting Windows Update to stop looping on a virgin system. Once the five patches are installed, the "delay" before Windows does anything with the patches, is reduced. Your current system already has the critical patches in place (since Windows Update is nominally working now to fetch updates). ******* All I've got to offer you, is the above answers.microsoft.com thread. I couldn't find anything on askwoody.com that seemed applicable. You're probably three years behind on patching. Not that this is important in any way. It's just for perspective I'm pointing this out. Being jammed is good, in the sense that if you can locate the two named patches in the thread, removing those patches might still help - even though it's three years later. Paul The remainder of what you have said is totally beyond me but I am able, I think, to do things in simple steps. My computer is working well regardless of the fact that the updates have not worked properly since 2015. Error 80073712 is the baddie and that occurs when the windows component store in corrupt. |
#11
|
|||
|
|||
Windows Component Store is Corrupt - Error 80073712
Emrys Davies wrote:
"Paul" wrote in message It suggests here, the damage was done in the year 2015. https://answers.microsoft.com/en-us/...0-2f0e99612b53 The remainder of what you have said is totally beyond me but I am able, I think, to do things in simple steps. My computer is working well regardless of the fact that the updates have not worked properly since 2015. Error 80073712 is the baddie and that occurs when the windows component store in corrupt. From the thread "I uninstalled both KB2922229 and KB2984976, rebooted and checked for updates again." "It said the same two updates were available, KB3071756 and KB3060716. I went ahead with the installation and they installed successfully." I patched up my system, in 2016. I did a giant patch run that took hours of work. Since I did it in 2016, the KB2922229 and KB2984976 weren't offered and are not in my install list. They were already superseded. The following picture shows the KB3071756 and KB3060716 pair, and how a right-click on an item offers an uninstall item. Removing the items (if you can find them) should be easy. https://i.postimg.cc/zGZ2bsRq/window...76-removal.gif If they're not actually present, then we're without a solution! So you can start by checking for them, like in the picture and see if they're there or not. I don't have KB2922229 and KB2984976 because I started my patch run in 2016, after the patches had been removed from the list of candidates by Microsoft. This article shows how to manually set a restore point. https://www.sevenforums.com/tutorial...nt-create.html Doing a system backup is a more complicated step, and perhaps you already have backup software installed and know how to do this. You should always have a backup to a second drive, as protection against hardware (disk) failures. The purpose of a system backup, is to have an "easy way" to restore the computer to a working state, if one of your experiments goes wrong. One time, I absolutely destroyed my C: drive (NTFS - unrecoverable), and I'd made a backup on a lark only two hours earlier, *never suspecting* I would need it that day. And that's the system used to make that picture, still alive and kickin. Paul |
#12
|
|||
|
|||
Windows Component Store is Corrupt - Error 80073712
"Paul" wrote in message news Emrys Davies wrote: "Paul" wrote in message It suggests here, the damage was done in the year 2015. https://answers.microsoft.com/en-us/...0-2f0e99612b53 The remainder of what you have said is totally beyond me but I am able, I think, to do things in simple steps. My computer is working well regardless of the fact that the updates have not worked properly since 2015. Error 80073712 is the baddie and that occurs when the windows component store in corrupt. From the thread "I uninstalled both KB2922229 and KB2984976, rebooted and checked for updates again." "It said the same two updates were available, KB3071756 and KB3060716. I went ahead with the installation and they installed successfully." I patched up my system, in 2016. I did a giant patch run that took hours of work. Since I did it in 2016, the KB2922229 and KB2984976 weren't offered and are not in my install list. They were already superseded. The following picture shows the KB3071756 and KB3060716 pair, and how a right-click on an item offers an uninstall item. Removing the items (if you can find them) should be easy. https://i.postimg.cc/zGZ2bsRq/window...76-removal.gif If they're not actually present, then we're without a solution! So you can start by checking for them, like in the picture and see if they're there or not. I don't have KB2922229 and KB2984976 because I started my patch run in 2016, after the patches had been removed from the list of candidates by Microsoft. This article shows how to manually set a restore point. https://www.sevenforums.com/tutorial...nt-create.html Doing a system backup is a more complicated step, and perhaps you already have backup software installed and know how to do this. You should always have a backup to a second drive, as protection against hardware (disk) failures. The purpose of a system backup, is to have an "easy way" to restore the computer to a working state, if one of your experiments goes wrong. One time, I absolutely destroyed my C: drive (NTFS - unrecoverable), and I'd made a backup on a lark only two hours earlier, *never suspecting* I would need it that day. And that's the system used to make that picture, still alive and kickin. Paul KB3060716 and KB3071756 are not present in Uninstall and Update and that is understandable as they are failed 'loopers', but they are in abundance in Review of Update History because of their being failed. You are able to get them into Uninstall and Update because you system did not fail them. Interestingly, I fail to see two of the repeating successful updates, namely KB3004375 and KB3031432, in Uninstall and Update, probably because they have not been as successful as indicated. |
#13
|
|||
|
|||
Windows Component Store is Corrupt - Error 80073712
Emrys Davies wrote:
KB3060716 and KB3071756 are not present in Uninstall and Update and that is understandable as they are failed 'loopers', but they are in abundance in Review of Update History because of their being failed. You are able to get them into Uninstall and Update because you system did not fail them. Interestingly, I fail to see two of the repeating successful updates, namely KB3004375 and KB3031432, in Uninstall and Update, probably because they have not been as successful as indicated. The idea is to see if you have KB2922229 and KB2984976. And remove them if you do. Paul |
#14
|
|||
|
|||
Windows Component Store is Corrupt - Error 80073712
"Paul" wrote in message news Emrys Davies wrote: KB3060716 and KB3071756 are not present in Uninstall and Update and that is understandable as they are failed 'loopers', but they are in abundance in Review of Update History because of their being failed. You are able to get them into Uninstall and Update because you system did not fail them. Interestingly, I fail to see two of the repeating successful updates, namely KB3004375 and KB3031432, in Uninstall and Update, probably because they have not been as successful as indicated. The idea is to see if you have KB2922229 and KB2984976. And remove them if you do. Paul Found KB2922229 - Installed on 9/04/2014 - and KB2984976 - Installed on 15/10/2014. Both removed. |
#15
|
|||
|
|||
Windows Component Store is Corrupt - Error 80073712
Emrys Davies wrote:
"Paul" wrote in message news Emrys Davies wrote: KB3060716 and KB3071756 are not present in Uninstall and Update and that is understandable as they are failed 'loopers', but they are in abundance in Review of Update History because of their being failed. You are able to get them into Uninstall and Update because you system did not fail them. Interestingly, I fail to see two of the repeating successful updates, namely KB3004375 and KB3031432, in Uninstall and Update, probably because they have not been as successful as indicated. The idea is to see if you have KB2922229 and KB2984976. And remove them if you do. Paul Found KB2922229 - Installed on 9/04/2014 - and KB2984976 - Installed on 15/10/2014. Both removed. Reboot. OK, now run Windows Update. What are the new symptoms. Paul |
|
Thread Tools | |
Display Modes | Rate This Thread |
|
|