Odd behaviour for this patch Tuesday (Oct.-09-12)

Joan Archer · 13 Oct 2012

I had 17 to do on all 3 machines here, 1 32 bit Ultimate, 1 64 bit Home Premium and 1 64 bit Home Premium Laptop. I did have to sign the new Eula for the Malicious Software Removal Tool before the download and install went ahead but then all 17 downloaded and installed without a glitch.

They all needed the reboot after but as I don't have anything else going on while I'm doing updates there was no problem with that.

Anak · 13 Oct 2012

After going over the information about my update errors I decided to run the Windows Update FixIt.

The results:
Attachment 236372

Even though it claims to resolve incorrect Windows Update data locations you can see in the highlighted red box, it did not.
How would they be repaired, a FixIt/Wizard or manually?

This lead me to thinking about running the System Update Readiness Tool, but there seems to be some caveats.

That page tells me that Windows Updates (WU) will offer me that tool if WU senses a problem with updates, so far it has not, and all during this last episode with patch Tuesday there were no red warnings, BSODs or error messages just erratic behaviour during the update process.

One was to export HKEY_LOCAL_MACHINE\Components, and delete certain keys, but I don't have HKEY_LOCAL_MACHINE\Components anywhere in my registry.

Another was to re-index Windows Server Update Services (WSUS) and cleanup, but I wasn't sure of doing that.
An update for Windows Server Update Services 3.0 Service Pack 2 is available

I do have WSUS 3.0, but not being in a server situation I'm thinking Windows Feels 3.0 is good enough for now and will offer the update when it feels it needs to.

This all leads me back to:

Anak said:

but I have been having trouble lately with FF15.0.1 not responding so I checked its settings and it was on Auto detect, but I had the option there to set it for No Proxies.
After I made the change, and restarted FF I haven't had any problems with it.

I think I failed to tell everyone that I was using FF15.0.1 when I went to apply this last patch Tuesday.

Some of my errors were related to connection inconsistencies, and that lead to the remaining errors.

I have since updated to FF16.0.1 and I notice an improvement in how FF is working without any changes to the proxy settings. So at this point I'm going to let sleeping dogs lie, and update this thread after the next patch Tuesday to let everyone know how it went.