Office File Validation patch leads to problems

Topic

New Reply

	PATCH WATCH Office File Validation patch leads to problems
	By Susan Bradley Microsoft’s Office File Validation update is not playing well with Excel, and the company knows it. So your top update priority is not the usual round of security patches, but it’s hiding and ignoring this problematic OFV update.

---

The full text of this column is posted at WindowsSecrets.com/patch-watch/office-file-validation-patch-leads-to-problems (opens in a new window/tab).

Columnists typically cannot reply to comments here, but do incorporate the best tips into future columns.[/td]

[/tr][/tbl]

Reply | Quote

Replies

Thanks as always for this information.
Could I invite you to consider listing patches in numeric order, rather than status, please? This would make it easier to find if you have included a particular patch.

Is there a consolidated list somewhere (eg on this lounge somewhere)? I have lots of patches being proposed that are not on your current list, so maybe I missed them some time.

Geoffrey

Reply | Quote

Hi Susan!

I read you Patch Watch Column religiously and find your advice very accurate and timely. My comment relates to the most recent set of patches pushed by Microsoft Update. It does appear to me that these are not ready for prime time. Of the 6 patches received, only two installed properly for me – Windows Malicious Software Removal Tool x64 – July 2011 (KB890830) and Definition Update for Windows Defender – KB915597 (Definition 1.107.1567.0). The other four did not – KB2507938, KB2532521, KB2555917 and KB2533623.

The install of these latter patches seemed to go well but on reboot, the installation aborts and then it recovers to pre-patch attempt state. I spent over two hours following the instructions to overcome the install error code 80070020 – update in safe mode and update in a Windows clean start (without boot-up third party software drivers). Neither worked. The first method overlooks the fact that Windows Update does not work in safe mode. The second method just does not result in the updates installing.

I’m sure that you will hear more about this from others. I will be interested in seeing your views on these matters.

Take care!

Lou Vaccarello

Reply | Quote

Of the 6 patches received, only two installed properly for me – Windows Malicious Software Removal Tool x64 – July 2011 (KB890830) and Definition Update for Windows Defender – KB915597 (Definition 1.107.1567.0). The other four did not – KB2507938, KB2532521, KB2555917 and KB2533623.

Lou, I was offered three of the four patches you noted as unsuccessful for my x64 Pro system. The only one I didn’t see was KB2532521, nor do I have any record of having previously installed it. The other three patches installed OK on the first try, which causes me to wonder if your problem lies with KB2532521.

According to Microsoft Security Bulletin MS11-053, KB2532521 relates to the Bluetooth Stack patch that Susan referenced in her latest Patch Watch article (KB2566220). I wonder why you were offered KB2532521 instead of KB2566220?

Also, the only other mention of a problem with this specific group of four patches was in a question on Microsoft Answers (which currently has no answers, of course). This person is a developer whose problem had to do with a specific code execution issue. Not the same as your problem, of course, but perhaps a clue to someone who is more knowledgeable than either of us.

@Susan: Perhaps you could look at that disparity of KB offerings?

Anyone else have either a successful install or problems installing KB2532521?

Reply | Quote

KB 2539520 (Office 2007 patch): The current chart recommends “Wait” on KB 2539581, an Office 2003 nonsecurity update, but doesn’t include a recommendation for KB 2539530, which looks like the same update for Office 2007. I’ve been offerred both updates, I assume because while I have Office 2003, I’ve also installed Office 2007 compatibility. Am I correct that the two patches should be treated the same and both are a “Wait?” Thanks.
MarciaG

Reply | Quote

Echo Geoffrey’s request. And his request for a consolidated list!

Reply | Quote

@Susan: In addition to the patches you discussed in listed in the 7/14 Patch Watch, I was also offered KB2532531 (Security Update for Windows 7 for x64-based Systems).

Please advise.

Reply | Quote

@Susan: In addition to the patches you discussed in listed in the 7/14 Patch Watch, I was also offered KB2532531 (Security Update for Windows 7 for x64-based Systems).

Please advise.

Similar issue here except this patch, KB2532531, was successfully installed on my Windows 7 computer last week and it showed up again this week. MS says that this might happen in relation to another patch, KB2552343. I don’t know if that patch has ever been installed on my computer. And since MS doesn’t offer any reasonable way to determine whether or not a patch has been installed previously – other than reading down through the list of installed patches, which is now dozens of pages long here – I am not certain if I need to install this again or if it is just one of those rogue patches that forever wants to be reinstalled.

I really HATE Microsoft’s patch system!

Jim

Reply | Quote

. And since MS doesn’t offer any reasonable way to determine whether or not a patch has been installed previously – other than reading down through the list of installed patches,Jim

You don’t have to read down through that list. Go to Control Panel/uninstall programs/view installed updates and type the KB number in the search box. BINGO. It will tell you yes or no in a skinny minute.

BJ

Reply | Quote

Thanks BJ – I hadn’t noticed that; I mainly use Revo Uninstaller rather than the one provided in Windows. Plus I guess I am remembering back when Microsoft did not list the individual KB #’s in the Remove Programs dialog.

Thanks again!

Jim

PS – BTW it was never installed; never offered to me for that matter. And I saw a note on the MS page for KB2532531 saying that there is a problem for many where that patch keeps being offered even after its successful installation. I’ll just keep ignoring it.

Reply | Quote

In view of Bob’s comment #10 above, it seems likely that KB2552343 might have to be installed prior to KB532531 to avoid the latter being offered repeatedly. I’m going to try that right after lunch, so will check back and report my results.

Thanks to all for all the info

Gary

Reply | Quote

That is recommended by Microsoft Gary, but then again Susan has KB2552343 rated as “Wait” in her patch watch table. I’m going to hold off on it until that is cleared.

Jim

Reply | Quote

JMac001 – in the version of the patch table that I see, it says install for 2552343. Maybe that’s a recent change, but I printed my version on 7/19/11. Checked again just now to be sure. Guess I’ll go ahead and try 2532342 > 2532531.

All: To avoid any possible confusion, KB2532531 referred to by bethel95 in an earlier post, got typo’d to KB2532521 for a few posts.

Thanks, Gary

Reply | Quote

Susan,

Could you please write a booklet or make available to us even if for $$$$$, that starts from the beginning of Win7 and lists the dos and do nots of updates. A timeline, and maybe update numbers would be helpful. I was so afraid of bad updates, that a recent purchase of a custom I5 desk top, caused me to tell the techs NOT to auto update anything. I have Win7 with sp1. The machine was picked up about 2 weeks ago and I am lost as to what to add and what not to add, because I do not know where to start.

I am willing to purchase such a manual and I am sure a lot of us would. If there is something in place OTHER than researching a year or two of the newsletter, I would like to know about it.

Thanks in advance,
Rufus Barker

Reply | Quote

Susan,

Could you please write a booklet or make available to us even if for $$$$$, that starts from the beginning of Win7 and lists the dos and do nots of updates. A timeline, and maybe update numbers would be helpful. I was so afraid of bad updates, that a recent purchase of a custom I5 desk top, caused me to tell the techs NOT to auto update anything. I have Win7 with sp1. The machine was picked up about 2 weeks ago and I am lost as to what to add and what not to add, because I do not know where to start.

I am willing to purchase such a manual and I am sure a lot of us would. If there is something in place OTHER than researching a year or two of the newsletter, I would like to know about it.

Thanks in advance,
Rufus Barker

A brand new box is the BEST time to to update. You aren’t in a ‘crusty’ state. If I were in your shoes I’d run Microsoft update on a brand new box until you don’t get offered any more updates.

Reply | Quote

KB 2518864 (MS11-044): I am being offerred two patches that both relate to .NET Framework 2.0 SP3 and 3.5 SP1. The current Patch Chart refers only to the .NET Framework patches in MS11-039, but does not included recommended action for the .NET Framework patches in MS11-044 which Susan discussed in her June 29th column. Is KB 2518864 also a “Skip and hide?”

KB 2512827: The current chart does not include a recommended action for the Silverlight patch addressing a combined vulnerability in Silverlight and .NET, which in Susan’s June 16th column was a “Wait.” What is the recommended action for KB 2512827?

Thanks.
MarciaG

Reply | Quote

KB 2518864 (MS11-044): I am being offerred two patches that both relate to .NET Framework 2.0 SP3 and 3.5 SP1. The current Patch Chart refers only to the .NET Framework patches in MS11-039, but does not included recommended action for the .NET Framework patches in MS11-044 which Susan discussed in her June 29th column. Is KB 2518864 also a “Skip and hide?”

KB 2512827: The current chart does not include a recommended action for the Silverlight patch addressing a combined vulnerability in Silverlight and .NET, which in Susan’s June 16th column was a “Wait.” What is the recommended action for KB 2512827?

Thanks.
MarciaG

As noted repeatedly in Susan’s columns, .NET patches can go by a number of apparently different KB Numbers. The MS Numbers are the only reliable way to tell which patch the KB Articles are really referring to.

Along the same lines, I’d be willing to bet that the KB2532521 article is merely an update of the KB2532520 article Susan mentioned in her column. Again, it is the MS Number which counts, not the KB Number.

I’ll let Susan explain the .NET-Silverlight security connection. That one is beyond my current knowledge.

-- rc primak

Reply | Quote

As noted repeatedly in Susan’s columns, .NET patches can go by a number of apparently different KB Numbers. The MS Numbers are the only reliable way to tell which patch the KB Articles are really referring to.

Along the same lines, I’d be willing to bet that the KB2532521 article is merely an update of the KB2532520 article Susan mentioned in her column. Again, it is the MS Number which counts, not the KB Number.

I’ll let Susan explain the .NET-Silverlight security connection. That one is beyond my current knowledge.

Thanks Bob. I do understand that it’s the MS Number that counts. When my KB Number isn’t in Susan’s column I do always attempt to get to the MS Bulletin and then search for that in Susan’s column.

So, to rephrase my question re the .NET patches: What is the recommendation re MS11-044 .NET patches? In her June 29th column Susan discussed waiting on the MS11-044 patches, which she lists by KB number, along with the MS11-039’s, but the July 14th list has a recommendation only for the patches in MS11-039, but no recommendation for those in MS11-044.

RE the Office 2007 patch: I meant to ask what the recommendation is for KB 2539530 (not KB 2539520). The KB 2539530 patch appears to be the same nonsecurity update for Office 2007 as KB 2539581 is for Office 2003. I cannot find an MS Number for either — the link in each patch explanation goes to an article with an ID number that is the same as the KB number.

MarciaG

Reply | Quote

Susan,
Thanks for all you do in trying to keep us safe despite Micros – – t’s worst efforts!

Please add my vote to Geoffrey’s and Auggie’s regarding your “Regularly updated problem-patch chart”. This is perhaps the most useful maintainer’s tool available, but it could become a true must-have if you could post a consolidated version sorted by number — or even better sortable via column heading.

Thanks again, and God bless!
Jack O’Sullivan

Reply | Quote

Thanks Gary. However I haven’t seen any table from 7/19. The table I used was the last one posted in the Windows Secrets Newsletter, which was dated 7/12. Notice I first posted about this at 1:30 am on 7/19 and I am fairly certain that the 7/12 table was the latest at that time. I still haven’t seen a later table.

Thank you.
Jim

Reply | Quote

Wow. Nonsense in my previous post. That should say 2552343 > 2532531. Sorry – looked at too many similar numbers in the last few days .

Anyway – when I installed 2552343 and searched for updates again, neither 2532531 nor 2566220 were offered, whereas 2532531 was offered previously. Does this seem strange or expected?

Thanks,
Gary

Reply | Quote

Wow. Nonsense in my previous post. That should say 2552343 > 2532531. Sorry – looked at too many similar numbers in the last few days .

Anyway – when I installed 2552343 and searched for updates again, neither 2532531 nor 2566220 were offered, whereas 2532531 was offered previously. Does this seem strange or expected?

Thanks,
Gary

I already posted this in the latest Patch Watch thread but thought I should answer this post also: KB2552343 was showing – and still is in the latest chart – twice: once as “Wait” and then again as “Install”. So I am just leaving it alone till something is clarified on this – if it ever is!

Thank you.

Jim

Reply | Quote

I’ve check this thread and cannot find any reference to the following Security Updates: Office 2007 System – 2553074, 2553089. 2553090, 2584063 and Excel 2553073. I also can’t seem to find them in Susan Bradley’s Patch Watch list. I’m trying to determine if they are OK to install. Can anyone help me determine if these are OK to install?

Thanks,
Wayne Anthony

Reply | Quote

Well, confusing anyway!

Jim

Reply | Quote

Still looking for a recommendation on KB 2512827 patch for combined Silverlight and .NET vulnerability.

Susan’s 6/16 column said “wait.” Not discussed with other .NET patches in 6/29 column and not on 7/12 list. Not one of the MS11-039 or MS11-044 patches.

MarciaG

Reply | Quote

So I read this thread (a lot of times, cannot completely wrap my head around it, going to try though), but this is what I got out of this

KB2507938, KB2555917, KB2533623 – for Lou, install went bad. bethel95 says install was ok. No other comments after 7-16-2011 (Pending)
KB2532521 – Might be an update to KB2532520? KB2532521 was installed and after a week shows up again. Microsoft confirms this. (Pending)
KB2518864 – Skip? Reading Susan’s column on 6-30-2011 this is; if installed and no issues, good. If not installed, skip. (Pending)
KB2512827 – Requesting an action. (Pending)

Gary said it correctly “looked at too many similar numbers in the last few days”. So just attempting to look at this from a broad view, there are a lot of KB numbers thrown in here and I am just attempting to try to clean it up for us. I put (Pending) just so we know that there was no definitive answer. Just trying to clear the air

The first three I mentioned just needs more of peoples input. Any other bad or good results from installing these 3?

Looks like the KB2532531 that reappears after installing should be something to look out for. Anyone else having this install and then having the issue?

KB2518864 is dependent on if you installed or not. If not, where are we with this one?

KB2512827 is at a “Wait” status, where are we on this one as well?

Again, just trying to help us all out here. My input, I have not installed any of these except the last two KB’s and with those last 2 KB’s I have no issues.

Reply | Quote

@swatbat2142 — A reoffered Microsoft Update (such as the KB2532531 item listed in your post) can be a symptom of a deeper underlying issue in the Windows installation. Could you keep us posted on whether that one keeps being reoffered?

-- rc primak

Reply | Quote

Sorry, I did not mean that these issues were happening with myself. I was just reiterating what was said in this post and where it was left off. I personally am not having this KB2532531 show up on any of my systems, I was just trying to help out Jmac and others who are having this issue. In this thread there were only two people who brought this KB2532531 up, then there were no responses. Just looking to see if anyone else will answer to this KB2532531.

Sorry if my thread was not that clear BP.

Reply | Quote

Sorry, I did not mean that these issues were happening with myself. I was just reiterating what was said in this post and where it was left off. I personally am not having this KB2532531 show up on any of my systems, I was just trying to help out Jmac and others who are having this issue. In this thread there were only two people who brought this KB2532531 up, then there were no responses. Just looking to see if anyone else will answer to this KB2532531.

Sorry if my thread was not that clear BP.

Let’s leave the note up anyway about reoffered MS Updates. I think this point is often overlooked, as it is more convenient to hide reoffered updates than to find out why they are being reoffered. In my own case, there were driver issues on one of my laptops. So this can be an indicator of deeper issues which could prevent important future updates from installing. No one was meant to be singled out. Sorry about that mixup.

As to the issue of applying one update or a group of updates, and then previously offered updates are no longer being offered: This usually means that the previous updates were superseded by newer updates, and when the newer updates were installed, some of the older updates were no longer relevant. Hence, they disappear. This has happened to me sometimes if I skip or hold off on troublesome patches, and then apply more recent patches.

-- rc primak

Reply | Quote