Windows 7: Windows update will not work properly

Linds6292 · 12 Jul 2012

Quote: Originally Posted by NoelDP

There is/was no problem with the WAT update in the report - that set of errors merely indicates that the update is not installed (not that there is any problem!)

Ok. cool. I have no idea (that's why I'm here)

Quote:

The poster may or may not choose to install it - but it's (almost certainly) irrelevant to the current situation in any case.

@Linds6292 - the report shows your system to be 32-bit (x86). I assume you've now installed the update OK? (not that it matters - hopefully your updates will now properly install)

I will try now.

Thanks

kegobeer · 12 Jul 2012

Quote: Originally Posted by NoelDP

There is/was no problem with the WAT update in the report - that set of errors merely indicates that the update is not installed (not that there is any problem!)

Sorry, I was pretty sure that

Quote:

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]

meant that the WAT update files didn't match, meaning that there was possible corruption.

Linds6292 · 12 Jul 2012

Ok,

So I ran update with no problems. I'm going to try and reinstall iTunes (that didn't install properly before), see how it goes.

Linds

Linds6292 · 12 Jul 2012

Quote: Originally Posted by kegobeer

Quote: Originally Posted by NoelDP

There is/was no problem with the WAT update in the report - that set of errors merely indicates that the update is not installed (not that there is any problem!)

Sorry, I was pretty sure that

Quote:

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]

meant that the WAT update files didn't match, meaning that there was possible corruption.

It did make a difference to windows update.

Linds6292 · 12 Jul 2012

iTunes installed properly, so did Quicktime.

Thank you Noel and Keg for your help.

Lindsay

kegobeer · 12 Jul 2012

Quote: Originally Posted by Linds6292

iTunes installed properly, so did Quicktime.

Thank you Noel and Keg for your help.

Lindsay

Glad you got things sorted and it turned out to be a fairly painless fix.

NoelDP · 13 Jul 2012

Quote: Originally Posted by Linds6292

It did make a difference to windows update.

Installing the update on its own does not make any difference to the functioning of Windows Update, although it may allow the system to see updates which weren't previously visible.

It's always possible that there was a minor registry error which was corrected by the install.

Whaever - you seem to have got it sorted now, so well done, and good luck!

Linds6292 · 13 Jul 2012

Quote: Originally Posted by NoelDP

Quote: Originally Posted by Linds6292

It did make a difference to windows update.

Installing the update on its own does not make any difference to the functioning of Windows Update, although it may allow the system to see updates which weren't previously visible.

I'd say that's definitely what happened. It was instant.

Quote:

It's always possible that there was a minor registry error which was corrected by the install.

Whaever - you seem to have got it sorted now, so well done, and good luck!

Lol. I didn't do anything except follow you two. Those test results may as well have been in Chinese.

I appreciate it.

I do have one more question. though it isn't really to do with this.

The system repair/reboot/factory reset partition would not work for my new (larger hdd). Is there a way that I could make this possible (to reset my system using this new HDD) in the future if need be?

Now I have my system working properly I am going to do another clone before I put any more data on the hdd. That way I ought have a bug free place to start next time.

Lindsay

NoelDP · 13 Jul 2012

Not really - the original disk probably had a custom MBR which reacted to the special commands from the ketstrokes required for a recovery boot.

Your best option would have been to have created the Recovery disks when you were supposed to (when you first got the computer) and kept them safe.

What you can do now is order a set of disks from the manufacturer for use in emergency.

Linds6292 · 13 Jul 2012

Quote: Originally Posted by NoelDP

Not really - the original disk probably had a custom MBR which reacted to the special commands from the ketstrokes required for a recovery boot.

Your best option would have been to have created the Recovery disks when you were supposed to (when you first got the computer) and kept them safe.

What you can do now is order a set of disks from the manufacturer for use in emergency.

Will that work for a different HDD though? Sorry, I really know squat about this stuff. If this stuff is important I wish manufacturers would inform you in manuals or at least provide the disks. But I suppose this is what they do with the recovery partition, (is it)?

Is taking a copy of my now working computer's hdd just as effective if something goes wrong?

Thanks

Lindsay

Windows 7: Windows update will not work properly

Windows update will not work properly problems?