A Windows XP help forum. PCbanter

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.

Go Back   Home » PCbanter forum » Microsoft Windows 7 » Windows 7 Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Windows Component Store is Corrupt - Error 80073712



 
 
Thread Tools Rate Thread Display Modes
  #16  
Old December 21st 18, 08:07 PM posted to alt.windows7.general
Emrys Davies
external usenet poster
 
Posts: 310
Default Windows Component Store is Corrupt - Error 80073712


"Paul" wrote in message
news
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


It attempted to download 8 updates and was successful with three. The
others failed. Two of the successful ones were the regular two - KB3004375
and KB3031432. The other one was one of the two I uninstalled at your
request- KB2984976. I did not try the seven optional ones.

Ads
  #17  
Old December 21st 18, 08:35 PM posted to alt.windows7.general
Emrys Davies
external usenet poster
 
Posts: 310
Default Windows Component Store is Corrupt - Error 80073712


"Emrys Davies" wrote in message
...

"Paul" wrote in message
news
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


It attempted to download 8 updates and was successful with three. The
others failed. Two of the successful ones were the regular two -
KB3004375 and KB3031432. The other one was one of the two I uninstalled
at your request- KB2984976. I did not try the seven optional ones.


Incidentally, the 7 optional updates also failed. The code for those which
failed above was the usual 80073712.

  #18  
Old December 22nd 18, 01:11 AM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Windows Component Store is Corrupt - Error 80073712

Emrys Davies wrote:

"Emrys Davies" wrote in message
...

"Paul" wrote in message
news
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


It attempted to download 8 updates and was successful with three. The
others failed. Two of the successful ones were the regular two -
KB3004375 and KB3031432. The other one was one of the two I
uninstalled at your request- KB2984976. I did not try the seven
optional ones.


Incidentally, the 7 optional updates also failed. The code for those
which failed above was the usual 80073712.


There is guided help here. They only try the easy stuff, before
punting and suggesting a repair install or similar.

https://support.microsoft.com/en-us/...-update-errors

One of the suggested steps, should download the Windows Update Troubleshooter.
You would double-click this and run it. I doubt it will fix anything, but
again, it's a troubleshooter. It should be clearing SoftwareDistribution
as one of the steps.

http://download.microsoft.com/downlo...Update.diagcab

Paul
  #19  
Old December 22nd 18, 01:30 PM posted to alt.windows7.general
Emrys Davies
external usenet poster
 
Posts: 310
Default Windows Component Store is Corrupt - Error 80073712


"Paul" wrote in message
news
Emrys Davies wrote:

"Emrys Davies" wrote in message
...

"Paul" wrote in message
news 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

It attempted to download 8 updates and was successful with three. The
others failed. Two of the successful ones were the regular two -
KB3004375 and KB3031432. The other one was one of the two I
uninstalled at your request- KB2984976. I did not try the seven
optional ones.


Incidentally, the 7 optional updates also failed. The code for those
which failed above was the usual 80073712.


There is guided help here. They only try the easy stuff, before
punting and suggesting a repair install or similar.

https://support.microsoft.com/en-us/...-update-errors

One of the suggested steps, should download the Windows Update
Troubleshooter.
You would double-click this and run it. I doubt it will fix anything, but
again, it's a troubleshooter. It should be clearing SoftwareDistribution
as one of the steps.

http://download.microsoft.com/downlo...Update.diagcab

Paul


I had run these URLS on several occasions before our efforts began but with
a negative result, but did so again. They say: 1. Windows Update error Not
Fixed - error OX80073712, 2. Have fixed Service Registration, 3. Problems
installing recent updates Fixed, 4. Problems installing recent updates
Fixed.



  #20  
Old December 22nd 18, 07:02 PM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Windows Component Store is Corrupt - Error 80073712

Emrys Davies wrote:

"Paul" wrote in message
news
Emrys Davies wrote:

"Emrys Davies" wrote in message
...

"Paul" wrote in message
news 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

It attempted to download 8 updates and was successful with three.
The others failed. Two of the successful ones were the regular two
- KB3004375 and KB3031432. The other one was one of the two I
uninstalled at your request- KB2984976. I did not try the seven
optional ones.

Incidentally, the 7 optional updates also failed. The code for
those which failed above was the usual 80073712.


There is guided help here. They only try the easy stuff, before
punting and suggesting a repair install or similar.

https://support.microsoft.com/en-us/...-update-errors

One of the suggested steps, should download the Windows Update
Troubleshooter.
You would double-click this and run it. I doubt it will fix anything, but
again, it's a troubleshooter. It should be clearing SoftwareDistribution
as one of the steps.

http://download.microsoft.com/downlo...Update.diagcab


Paul


I had run these URLS on several occasions before our efforts began but
with a negative result, but did so again. They say: 1. Windows Update
error Not Fixed - error OX80073712, 2. Have fixed Service Registration,
3. Problems installing recent updates Fixed, 4. Problems installing
recent updates Fixed.


Potential Windows Update Database error detected – Not fixed
0x80073712 (a file needed by Windows Update is damaged or missing)

I'm still not getting the solid technical information I
need. Just a lot of "hail mary" repair procedures (the
ones you've already tried.

The summary from this article, is none too good, in that
the next step is to repair install Windows 7 to get
Windows Update working again. I'm going to wait
a bit before recommending that. As it's a lot of work.

https://www.winhelp.us/reinstall-windows-update.html

surcheck
windows update troubleshooter
repair install of Windows 7 Sp1

*******

Since the complaint is about the "database", well,
lets try and find a database. It could be this
one, and mine is huge. Space on the database is
added in "blocks", so we expect the file to be
a multiple of 65536 bytes in size. They add an
empty "chunk" to the file, like a scratchpad,
then write to that chunk until the chunk is
used up. As a result, the database never has
any "odd" sizes

C:\Windows\SoftwareDistribution\DataStore\
DataStore.edb 1,551,958,016 (multiple of 65536 or 262144
Logs\ journal for .edb, would delete
if .edb deleted

This command checks the integrity of the database
used by Windows Update. The .edb should be a
Jet Blue database. The fact that the test I
did passed, kinda proves it is a Jet Blue.

esentutl /g DataStore.edb

Generally databases are "open" when you want to do stuff,
so you can't just type the command "any old time". On my test
system, now I have to dream up a way to test it. To make this
easy, I "freeze" a copy of the OS by doing a Macrium
Reflect backup of C: .

1) Macrium Reflect, make a backup .mrimg
2) The .mrimg can be viewed (mounted) as if it was
a disk drive, including disabling permissions.
3) Now, make a copy of the (frozen) DataStore.edb
and run the command against it.

cd /d I:\ # where the file will be staged when I get it
esentutl /g DataStore.edb # see what it says

Here is a sample run. I made a backup first, then right-clicked the .mrimg
from my Macrium backup. This gives me a nice accessible copy of C:
where none of the files are busy, and the files have been
made easy to copy.

https://i.postimg.cc/43R1p2BD/exposi...busy-files.gif

Here, I've copied the file I wanted to a separate (scratch)
workplace. Then changed directory (partition I), and
ran the command. My DataStore with my Windows Updates
is "good". The tool cannot tell that Windows Update
is going to work though. The tool only knows it's
a good database file, and nothing else.

https://i.postimg.cc/HnFMdjNq/database-is-OK.gif

If that file (and the Logs directory) were to
get deleted, Windows can rebuild the information.
The worst case damage is a lost of the Windows Update
history display. The OS still actually knows what
packages are installed and what ones aren't. All you
can lose when fooling around, is the history list
which is there for human consumption.

If the damn "Windows Update Troubleshooter" would do
its job, we could have more than a structural test,
and could have a functional test instead. But beggars
can't be choosers.

Paul
  #21  
Old December 23rd 18, 01:27 AM posted to alt.windows7.general
Emrys Davies
external usenet poster
 
Posts: 310
Default Windows Component Store is Corrupt - Error 80073712


"Paul" wrote in message
news
Emrys Davies wrote:

"Paul" wrote in message
news
Emrys Davies wrote:

"Emrys Davies" wrote in message
...

"Paul" wrote in message
news 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

It attempted to download 8 updates and was successful with three. The
others failed. Two of the successful ones were the regular two -
KB3004375 and KB3031432. The other one was one of the two I
uninstalled at your request- KB2984976. I did not try the seven
optional ones.

Incidentally, the 7 optional updates also failed. The code for those
which failed above was the usual 80073712.

There is guided help here. They only try the easy stuff, before
punting and suggesting a repair install or similar.

https://support.microsoft.com/en-us/...-update-errors

One of the suggested steps, should download the Windows Update
Troubleshooter.
You would double-click this and run it. I doubt it will fix anything,
but
again, it's a troubleshooter. It should be clearing SoftwareDistribution
as one of the steps.

http://download.microsoft.com/downlo...Update.diagcab

Paul


I had run these URLS on several occasions before our efforts began but
with a negative result, but did so again. They say: 1. Windows Update
error Not Fixed - error OX80073712, 2. Have fixed Service Registration,
3. Problems installing recent updates Fixed, 4. Problems installing
recent updates Fixed.


Potential Windows Update Database error detected – Not fixed
0x80073712 (a file needed by Windows Update is damaged or missing)

I'm still not getting the solid technical information I
need. Just a lot of "hail mary" repair procedures (the
ones you've already tried.

The summary from this article, is none too good, in that
the next step is to repair install Windows 7 to get
Windows Update working again. I'm going to wait
a bit before recommending that. As it's a lot of work.

https://www.winhelp.us/reinstall-windows-update.html

surcheck
windows update troubleshooter
repair install of Windows 7 Sp1

*******

Since the complaint is about the "database", well,
lets try and find a database. It could be this
one, and mine is huge. Space on the database is
added in "blocks", so we expect the file to be
a multiple of 65536 bytes in size. They add an
empty "chunk" to the file, like a scratchpad,
then write to that chunk until the chunk is
used up. As a result, the database never has
any "odd" sizes

C:\Windows\SoftwareDistribution\DataStore\
DataStore.edb 1,551,958,016 (multiple of 65536 or
262144
Logs\ journal for .edb, would
delete
if .edb deleted

This command checks the integrity of the database
used by Windows Update. The .edb should be a
Jet Blue database. The fact that the test I
did passed, kinda proves it is a Jet Blue.

esentutl /g DataStore.edb

Generally databases are "open" when you want to do stuff,
so you can't just type the command "any old time". On my test
system, now I have to dream up a way to test it. To make this
easy, I "freeze" a copy of the OS by doing a Macrium
Reflect backup of C: .

1) Macrium Reflect, make a backup .mrimg
2) The .mrimg can be viewed (mounted) as if it was
a disk drive, including disabling permissions.
3) Now, make a copy of the (frozen) DataStore.edb
and run the command against it.

cd /d I:\ # where the file will be staged when I get
it
esentutl /g DataStore.edb # see what it says

Here is a sample run. I made a backup first, then right-clicked the .mrimg
from my Macrium backup. This gives me a nice accessible copy of C:
where none of the files are busy, and the files have been
made easy to copy.

https://i.postimg.cc/43R1p2BD/exposi...busy-files.gif

Here, I've copied the file I wanted to a separate (scratch)
workplace. Then changed directory (partition I), and
ran the command. My DataStore with my Windows Updates
is "good". The tool cannot tell that Windows Update
is going to work though. The tool only knows it's
a good database file, and nothing else.

https://i.postimg.cc/HnFMdjNq/database-is-OK.gif

If that file (and the Logs directory) were to
get deleted, Windows can rebuild the information.
The worst case damage is a lost of the Windows Update
history display. The OS still actually knows what
packages are installed and what ones aren't. All you
can lose when fooling around, is the history list
which is there for human consumption.

If the damn "Windows Update Troubleshooter" would do
its job, we could have more than a structural test,
and could have a functional test instead. But beggars
can't be choosers.

Paul


Nearly all of what you have just said is totally beyond me and you cannot
blame me for thinking why has he waffled to such an extent when you must
know by now that only simple steps where I understand the logic of what I am
doing will suffice. Otherwise it causes an uncomfortable feeling and I am
left thinking why don't I leave well alone rather that being subjected to
stressful situations at my age, when everyone says 'Enjoy Yourself'. Unless
you can take short steps without the technical explanations, which mean
nothing to me, it is best that we call it a day.

  #22  
Old December 23rd 18, 04:49 AM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Windows Component Store is Corrupt - Error 80073712

Emrys Davies wrote:


Nearly all of what you have just said is totally beyond me and you
cannot blame me for thinking why has he waffled to such an extent when
you must know by now that only simple steps where I understand the logic
of what I am doing will suffice. Otherwise it causes an uncomfortable
feeling and I am left thinking why don't I leave well alone rather that
being subjected to stressful situations at my age, when everyone says
'Enjoy Yourself'. Unless you can take short steps without the technical
explanations, which mean nothing to me, it is best that we call it a day.


I hate not leaving people with *some* choices.

I'm not able to find any good suggestions for where
to look next.

Even the sites where the author of the site has
the technical skill to make further suggestions,
they offer "Windows Update Troubleshooter" as
their solution. That is not a solution, because
it's success rate is so low.

*******

The next step for you is Repair Install.

There are no other options on the chart now.

That's it.

*******

Repair Install is a tradeoff between "it would be nice if I
could get Windows Update to work, for the security
patches", versus all the side-effects of doing
a Repair Install.

A repair install is relatively easy. You will need
a Windows 7 SP1 DVD to match the machine setup you
currently have. You can use the "winver" command
as one way to get version information. You can
use the "System" control panel to determine the
bit-ness of the current OS installation. The DVD will
be 32 bit or 64 bit, to match the 32 bit or 64 bit
OS install. You start by collecting "winver" and
"System" control panel information first, then
reviewing your DVD collection for a match.

If you purchased Windows 7 and installed the OS yourself,
then you could use the media (DVD disc) you got. While
Windows 7 is running, you run "Setup.exe" off the DVD
when it is inserted in the DVD drive. And it will
re-install the OS, keeping your programs and user
data files.

When such an installation is finished, you will still
need to do ~200 updates or whatever Windows Update
throws at you. It would be nice to think that
a Windows Update run would be "flawless" on an
out-of-the-box install, but this is seldom
the case, and I won't bore you with the details.

The WSUSOffline patch installer, it actually knows
how to "bandaid" a freshly Repair Installed Windows 7
machine, for best results. In fact, that's where
we "steal the recipe" for tipping a new install
properly upright. The WSUSOffline patcher installs
the latest version of Windows Update first, plus
it manually installs five other patches that "work
the best" with todays Windows Update.

http://download.wsusoffline.net/

You run the tool in "collection mode" first, and
collect around 2GB of patches. Once the Repair Install
is finished, you use the USB stick with your
"collection" on it, and run the stick in Install Mode.
And it will finish the Windows Update steps for you.

*******

Since this is bound to upset you, take the machine
to Geek Squad. For $200, they will do a Repair Install
and patch Windows Update to the very latest patch.

If you use Geek Squad, *back up the hard drive* first.
Never ever ever go to a mom-and-pop or a Geek Squad
repair depot, without making the backup first. The
backup can be stored on an external hard drive. You
keep the external hard drive at home, where they
can't muck it up :-)

I've had a few reports of people heading off to
the computer store, and some yutz there deletes
the entire drive and does a "Clean Install" and
all the files are gone. And the dude who does
this will say "Oops! Too bad and so sad", meaning,
if you had a backup, you would not be screwed by
his incompetence. Computer shop people *never ever*
do backups before they start a procedure. They
take no prisoners. If what they've done fails,
you're on the hook for the files, not them.

It's because they line the machines up, like in
a production line. All the "Clean Install" machines
go into a pile. It's easy for a PC to be put in the
wrong pile, they do a "Clean Install", and right
after that... the idiot reads the customer problem
description and finds out he wasn't supposed to do
that. That's how clueless they are. It's a factory,
not "personal service" model. Shops can do good
work, better than I could do, but they have to be
in a good mood before it happens. If the success
rate of shop repairs was better, I would not have
to give this warning to people.

*******

Since this is a Windows Update problem, you should
be able to phone up Microsoft Support, and *without*
a credit card, they can try and fix it. You might
need to be elevated to next-level support to
actually get it fixed. The entry level support
will be trying the "Windows Update Troubleshooter",
just like you did :-/ If you're not a rich guy,
that's the route I would take next. Only certain
issues on Windows machines receive free support.

https://support.microsoft.com/en-us/...-phone-numbers

I can't necessarily get the US number as they use
geolocation to give me the Canadian support number,
which would not work for you.

https://www.microsoft.com/en-us/contact.aspx

https://www.microsoft.com/en-us/about/officelocator

They'll do just about anything to avoid giving
a phone number... easily. But it's still worth
a try. If you had a Microsoft Store in town, you
could contact them and see if you could do a
"walk in" with the computer case. And have them
fix the Windows Update they broke.

And all you need to tell them is (substitute your version):

Windows 7 Home Premium, Windows Update 0x80073712
Windows Troubleshooter cannot fix.

HTH,
Paul
  #23  
Old December 24th 18, 11:41 PM posted to alt.windows7.general
Emrys Davies
external usenet poster
 
Posts: 310
Default Windows Component Store is Corrupt - Error 80073712


"Paul" wrote in message
news
Emrys Davies wrote:


Nearly all of what you have just said is totally beyond me and you cannot
blame me for thinking why has he waffled to such an extent when you must
know by now that only simple steps where I understand the logic of what I
am doing will suffice. Otherwise it causes an uncomfortable feeling and
I am left thinking why don't I leave well alone rather that being
subjected to stressful situations at my age, when everyone says 'Enjoy
Yourself'. Unless you can take short steps without the technical
explanations, which mean nothing to me, it is best that we call it a day.


I hate not leaving people with *some* choices.

I'm not able to find any good suggestions for where
to look next.

Even the sites where the author of the site has
the technical skill to make further suggestions,
they offer "Windows Update Troubleshooter" as
their solution. That is not a solution, because
it's success rate is so low.

*******

The next step for you is Repair Install.

There are no other options on the chart now.

That's it.

*******

Repair Install is a tradeoff between "it would be nice if I
could get Windows Update to work, for the security
patches", versus all the side-effects of doing
a Repair Install.

A repair install is relatively easy. You will need
a Windows 7 SP1 DVD to match the machine setup you
currently have. You can use the "winver" command
as one way to get version information. You can
use the "System" control panel to determine the
bit-ness of the current OS installation. The DVD will
be 32 bit or 64 bit, to match the 32 bit or 64 bit
OS install. You start by collecting "winver" and
"System" control panel information first, then
reviewing your DVD collection for a match.

If you purchased Windows 7 and installed the OS yourself,
then you could use the media (DVD disc) you got. While
Windows 7 is running, you run "Setup.exe" off the DVD
when it is inserted in the DVD drive. And it will
re-install the OS, keeping your programs and user
data files.

When such an installation is finished, you will still
need to do ~200 updates or whatever Windows Update
throws at you. It would be nice to think that
a Windows Update run would be "flawless" on an
out-of-the-box install, but this is seldom
the case, and I won't bore you with the details.

The WSUSOffline patch installer, it actually knows
how to "bandaid" a freshly Repair Installed Windows 7
machine, for best results. In fact, that's where
we "steal the recipe" for tipping a new install
properly upright. The WSUSOffline patcher installs
the latest version of Windows Update first, plus
it manually installs five other patches that "work
the best" with todays Windows Update.

http://download.wsusoffline.net/

You run the tool in "collection mode" first, and
collect around 2GB of patches. Once the Repair Install
is finished, you use the USB stick with your
"collection" on it, and run the stick in Install Mode.
And it will finish the Windows Update steps for you.

*******

Since this is bound to upset you, take the machine
to Geek Squad. For $200, they will do a Repair Install
and patch Windows Update to the very latest patch.

If you use Geek Squad, *back up the hard drive* first.
Never ever ever go to a mom-and-pop or a Geek Squad
repair depot, without making the backup first. The
backup can be stored on an external hard drive. You
keep the external hard drive at home, where they
can't muck it up :-)

I've had a few reports of people heading off to
the computer store, and some yutz there deletes
the entire drive and does a "Clean Install" and
all the files are gone. And the dude who does
this will say "Oops! Too bad and so sad", meaning,
if you had a backup, you would not be screwed by
his incompetence. Computer shop people *never ever*
do backups before they start a procedure. They
take no prisoners. If what they've done fails,
you're on the hook for the files, not them.

It's because they line the machines up, like in
a production line. All the "Clean Install" machines
go into a pile. It's easy for a PC to be put in the
wrong pile, they do a "Clean Install", and right
after that... the idiot reads the customer problem
description and finds out he wasn't supposed to do
that. That's how clueless they are. It's a factory,
not "personal service" model. Shops can do good
work, better than I could do, but they have to be
in a good mood before it happens. If the success
rate of shop repairs was better, I would not have
to give this warning to people.

*******

Since this is a Windows Update problem, you should
be able to phone up Microsoft Support, and *without*
a credit card, they can try and fix it. You might
need to be elevated to next-level support to
actually get it fixed. The entry level support
will be trying the "Windows Update Troubleshooter",
just like you did :-/ If you're not a rich guy,
that's the route I would take next. Only certain
issues on Windows machines receive free support.

https://support.microsoft.com/en-us/...-phone-numbers

I can't necessarily get the US number as they use
geolocation to give me the Canadian support number,
which would not work for you.

https://www.microsoft.com/en-us/contact.aspx

https://www.microsoft.com/en-us/about/officelocator

They'll do just about anything to avoid giving
a phone number... easily. But it's still worth
a try. If you had a Microsoft Store in town, you
could contact them and see if you could do a
"walk in" with the computer case. And have them
fix the Windows Update they broke.

And all you need to tell them is (substitute your version):

Windows 7 Home Premium, Windows Update 0x80073712
Windows Troubleshooter cannot fix.

HTH,
Paul


Paul,

My first thought is to leave well alone because my computer is serving me
well without hassle. It is relatively old and will diminish gradually as
Windows fail to support it. Eventually I might decide to buy a new one
which will do the job. In the meantime I will fiddle about and try to solve
this problem. Today I ran sfc/scannow and it looked very promising until I
checked Windows Updates. It said: 'Windows Resource Protection found
corrupt files but was unable to fix some of them' a familiar story. Details
are included in the CBS.Log windir\Logs\CBS.log.

My very sincere greetings for the festive season.

  #24  
Old December 25th 18, 01:26 AM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Windows Component Store is Corrupt - Error 80073712

Emrys Davies wrote:


Paul,

My first thought is to leave well alone because my computer is serving
me well without hassle. It is relatively old and will diminish
gradually as Windows fail to support it. Eventually I might decide to
buy a new one which will do the job. In the meantime I will fiddle
about and try to solve this problem. Today I ran sfc/scannow and it
looked very promising until I checked Windows Updates. It said:
'Windows Resource Protection found corrupt files but was unable to fix
some of them' a familiar story. Details are included in the CBS.Log
windir\Logs\CBS.log.

My very sincere greetings for the festive season.


The problem likely starts with something in WinSXS, rather than
in System32 say.

The CheckSUR run was supposed to do the equivalent of a
DISM /restorehealth run and fix up WinSXS. Or at least
identify what needs to be fixed in there. That's why checking
the associated logfile would be important.

You don't have to read the entire article here, just note the
path of where the output went.

https://support.microsoft.com/en-us/...e-checksur-log

%WinDir%\Logs\CBS\CheckSUR.log == C:\Windows\Logs\CBS\CheckSUR.log

echo %WinDir% # that's how you check an environment variable

notepad C:\Windows\Logs\CBS\CheckSUR.log # may be permissions problems...

Once WinSXS is healthy, then it would likely be safe to
run SFC /scannow and verify the files the OS is actually
using at the moment.

Paul
  #25  
Old December 25th 18, 12:11 PM posted to alt.windows7.general
Emrys Davies
external usenet poster
 
Posts: 310
Default Windows Component Store is Corrupt - Error 80073712


"Paul" wrote in message
news
Emrys Davies wrote:


Paul,

My first thought is to leave well alone because my computer is serving me
well without hassle. It is relatively old and will diminish gradually as
Windows fail to support it. Eventually I might decide to buy a new one
which will do the job. In the meantime I will fiddle about and try to
solve this problem. Today I ran sfc/scannow and it looked very promising
until I checked Windows Updates. It said: 'Windows Resource Protection
found corrupt files but was unable to fix some of them' a familiar story.
Details are included in the CBS.Log windir\Logs\CBS.log.

My very sincere greetings for the festive season.


The problem likely starts with something in WinSXS, rather than
in System32 say.

The CheckSUR run was supposed to do the equivalent of a
DISM /restorehealth run and fix up WinSXS. Or at least
identify what needs to be fixed in there. That's why checking
the associated logfile would be important.

You don't have to read the entire article here, just note the
path of where the output went.

https://support.microsoft.com/en-us/...e-checksur-log

%WinDir%\Logs\CBS\CheckSUR.log == C:\Windows\Logs\CBS\CheckSUR.log

echo %WinDir% # that's how you check an environment
variable

notepad C:\Windows\Logs\CBS\CheckSUR.log # may be permissions
problems...

Once WinSXS is healthy, then it would likely be safe to
run SFC /scannow and verify the files the OS is actually
using at the moment.

Paul


Again I am totally lost and I think that I will just toddle along with what
I have got, which does the job for me. Many thanks for your considerable
trouble and patience.



  #26  
Old December 25th 18, 12:26 PM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Windows Component Store is Corrupt - Error 80073712

Emrys Davies wrote:

Again I am totally lost and I think that I will just toddle along with
what I have got, which does the job for me. Many thanks for your
considerable trouble and patience.


Updating the OS after reinstalling, is a degree of work
and takes time. Avoiding that if you have no interest,
is a good idea. The absolute worst OS to be installing
today is Vista, and Windows 7 is only slightly less
annoying. It's almost impossible to get Windows Update
to work on Vista SP2, out-of-the-box. The best recipe
for Windows 7, is to use wsusoffline and build an update
collection that way. They've automated the repair of
Windows 7 in the out-of-the-box state.

I would recommend doing backups though, of any personal
data (like email database), so if the OS does tip over,
you're ready to rescue the things that are important to
you. If you don't do email on the machine and do not
care to preserved browser bookmarks, it's also possible
there is nothing at all on the machine worth preserving,
in which case you would not need a backup. Just nuke and pave
if the OS crashes, or if the internal hard drive needs
replacement with an empty new one.

Paul

 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 09:19 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.