Woody Leonhard's no-bull news, tips and help for Windows and Office
Home icon Home icon Home icon Email icon RSS icon
  • Ms Defcon 2 – unknown Office patches on the horizon

    Posted on January 4th, 2017 at 07:43 woody 63 comments

    Apologies for this very abbreviated note. I’m on the road and working from my phone.

    Microsoft just pushed a bunch of non security Office patches. I suggest you avoid them until we have a chance to scope them out.

    Accordingly, I’m switching to Ms Defcon 2. Unless you have a pressing need to install a specific patch, don’t do it

    If that helped, take a second to support AskWoody on Patreon

    63 Responses to “Ms Defcon 2 – unknown Office patches on the horizon”

    1. JNP says:


      The Office patches didn’t pop for me yet, but our old friend, INTEL – System – 10/3/2016 12:00:00 AM –, which I had hidden did, this time with a new release date of 1/1/17. The size of the file remains the same, 58kb, suggesting it is identical. Perhaps, if he wants, Ch100 will be able to dig in deeper to confirm.

      • ch100 says:

        Yes, that’s interesting. Please give me few days and I will investigate if my hardware matches what you have seen.

        On a different subject, but still at Driver Updates, I was offered on a few years old Acer machine, an update for an Intel NIC card, Intel – LAN, LAN (Server) – Intel(R) 82579LM Gigabit Network Connection.
        Searching the Catalog, I found related updates, but among the 6 available, none was the “good” one. It was the same driver I would say, but without the correct descriptor in the .inf file. Remember that I said that the Microsoft Drivers match the Hardware ID correctly, otherwise they are offered rarely or maybe never (without matching the Hardware ID) and only when there is no other option – no functional driver installed on the machine.
        This is the reason why I prefer Windows Update drivers if they are newer than the computer manufacturer’s drivers compared to the generic ones which and if they do not match the Hardware ID (sometimes and this is mostly the case for Intel generic drivers, they do and this is the best option then).
        Using the WUMT with the option to copy the URL for the update, I was able to download the correct one from the Windows Update servers.
        I have no idea though why I could not find the correct driver and its download by searching the Catalog, it was either not published there at all or the search criteria are messed up, thanks to the great search engine which is Bing.

        • JNP says:


          Thanks. A few observations. First, while I understand your progression in preference for drivers we all should understand that most people, even many in the industry, are not going to be as careful as you are. So, because the only thing most people see is the WU notification, MS has to get these right the vast majority of the time.

          Second, is 58 Kb large enough to actually and directly install a driver on probably millions of machines, from different companies, or is this update merely a portal to second level of installation, about which somebody like you can’t really see the actual file and actual driver, that is going to be installed on the machine?

          Third, I am somewhat suspicious as to why MS is so invested in pushing this driver which, for many, is a driver that means their machine will be OK for easier upgrading to Win10, from Win7 for instance, especially when we are past when the free give away has ended and the numbers of new upgrades, at least for now, are down. Where’s the fire!

          • woody says:

            I wonder if this isn’t the start of a new Get Windows 10 push. Hopefully kinder and gentler this time. Will write about the signs in InfoWorld later this week or early next week.

              • woody says:

                Ed’s experience matches mine. But you gotta ask yourself, how many people with 7 ( or even 8.1) really want 10?

                • messager7777777 says:

                  @ woody & JNP ……. With M$ actively “degrading” Win 7/8.1 updating n restoring/reinstalling experience, a few Win 7/8.1 users may just give up resisting M$ n “submit” = take the still-free Win 10 upgrade ala Ed Bott. Hence, M$ hv been making themselves ready to embrace them as new Win 10 users/borgs.
                  “Resistance is futile” – Star Trek’s Borg

            • Lizzytish says:

              I’m butting in here as when reading the comments a thought came to mind about why MS are pushing these drivers and talk about it being easier to upgrade to Win10.

              When MS were doing their big GWX push last year….. those that did upgrade be it unwittingly or otherwise…. among some of them when their machine came back to life with Win10 after the installation, they found that they were lacking the correct drivers and so some aspects didn’t work. So they had to do a mad scramble and find the appropriate drivers quickly……. I know Nvidia was one of them that got
              triggered! So maybe that is what MS are trying to avoid happening. But of course they also may be planning another onslaught! Just my 2 bits! LT

              Blessed are the cracked, for they will let in the light.

              • ch100 says:

                I said the same earlier, based on the two scenarios which you have just mentioned.
                Something must be true 🙂

                • Lizzytish says:

                  Thanks ch100…… it would be nice if MS actually came out and stated that (if that’s the case)………. rather than being so vague about it all.

                  I’ve come to realise and understand that when speaking to people, and this becomes especially evident when asking for something you want done … one needs to be v. precise about it all. Some/most things are never interpreted as you intended!

                  Guess that’s why all the books for Dummies are out there!!! LT

                  “It is seldom at the frontier that discoveries are made but more often in the dustbin.”
                  Alan Bennett

                  • ch100 says:

                    @LT I think that what happens in fact is only a coincidence because we have Intel Chipsets and some components on our motherboards are the same with what is on the Intel NUC kits which have been released more recently. Intel NUC kits are in fact very small factor computers and who is interested can find their pictures on the Intel site and in may other places.
                    So the newer drivers are not released for us, but for the other devices and what matches can be used by us as an option – I am not recommending them unless there is no other functional driver installed previously and Microsoft actually says the same thing based on the classification – Optional for upgrade but Recommended for systems with missing drivers.
                    Sure enough this could be documented, but in fact there was never any documentation for drivers pushed via Windows Update, except for a generic page to the Microsoft site dedicated to driver development for Windows.
                    The best that we can do is to go to the Intel web site and try to identify the equivalent or even identical drivers there and read whatever is documented there. It is close enough and relevant in this situation and in general when it is about Intel drivers.

                    • Lizzytish says:

                      Many thanks for your explanation, ch100….. guess it’s never something straight forward and simple…… with so many scenarios to match up with. I can understand that completely…….. but it would be nice all the same if they could innumerate their objectives and motives…. and not just blandly say that it’s to provide a better experience of updating to Win10. Just thinking aloud! LT

                      “We are what we repeatedly do. Excellence then, is not an act, but a habit.” – Aristotle

          • ch100 says:

            “First, while I understand your progression in preference for drivers we all should understand that most people, even many in the industry, are not going to be as careful as you are.”

            I know this very well, but this is why we spend time here, to be better than them. 🙂

            I don’t know why Microsoft is now pushing for those drivers, it may be part of the effort for consolidation of the updates in only a few, or… you know what else.

        • JNP says:


 also present on WU for my notebook, Lenovo V570, the above was for the desktop, Dell Inspiron 660. Intel scan is giving me the same results as last week: the Dell could use the Intel driver the Lenovo doesn’t need a driver. Of course, the Dell doesn’t need any driver as I have an Nvidia video card in the slot.

          • ch100 says:


            Your notebook probably uses one of the supported Intel Chipsets, it is not possible to be offered the driver otherwise.

            To be clear and this is very important, there is nothing actually installed.
            This driver as we know, only updates the description of Intel components from Microsoft generic to Intel specific.
            The other functionality is to create a placeholder “driver” where Microsoft thinks there is a need for a driver and warns the user accordingly, while Intel knows better because it is their hardware and removes the warning correctly.

            What I found is that the Chipset Driver version, including the one downloaded directly from Intel, does not cover the USB Controller description for some chipsets at least – I noticed this on Series 7 Chipsets, while older Chipset Drivers do. In that case, the USB Controller would stay at the old version, generally speaking 9.x.x, if installed. The other components would get upgraded to
            The only reason of which I can think is that is actually meant to cover the Intel NUC kits and there are 2 other versions of this Chipset Driver, but it only happens that parts of the NUC kits are the same with what we have on our motherboards and only those overlapping parts are actually offered the newer driver.

            There is absolutely no need to install this driver in most cases and in particular if it is offered as Optional, as this indicates a previous version is already installed.
            If it is offered as Recommended, then it may be installed, but because it is incomplete in some situations, it is still better to get the driver from the computer manufacturer or from Intel, but a previous version which is suitable, suggesting here or for older motherboards

            We covered all this before though, just providing few more details and recommendations with specific version numbers here.

            • JNP says:


              Thanks for clarifying, distilling and adding. with Woody’s belief that MS wants to reboot Win10 for free, all this makes sense from a MS point of view. It does not make sense to install, from a consumer’s point of view, especially as this is a placeholder and not the real thing.

              Again, thanks.

          • ch100 says:

            NVidia graphics has nothing to do with the Chipset descriptor.
            This is for some of the components found under System Devices in Device Manager, while the Intel Graphics card has a separate proper driver, like NVidia card, not only a placeholder.
            I found the Intel utility misleading and while it is still useful, it may give the wrong information or none at all for older versions of Intel hardware. As such, I think the results provided should be double-checked very much in the same way like we normally do with Windows Update patches. Useful and for most part correctly issued, but still a certain dose of caution is even better.

    2. Megan Ryan says:

      I’m fine 🙂 I turned off my windows update on monday after I did my december updates on Sunday the 2nd.

    3. DaveE says:

      If these were Office patches, it’s got me puzzled. I had some updates come thru, I thought it was KB3207752 for Win7, which I was avoiding, trying to stay in GroupB. Last night, did the shutdown, and was puzzled to see it was installing updates, I thought perhaps I had hit the “yes’ button for the update. Switched the rig back-on today, and installing again, took it’s time, did it’s own clean-up, and when it was functional, there was no record of what it was, being installed, and the KB still had not been selected at all. I’m using Office2010.
      I have also a slower WinX rig. and it likes to download +180Mb of something, quite often, when it says updates are ‘up to date’, although looking thru recent used files, it seems to point largely to Cortana, that sweet talking data collector.
      What gets me about MS, is all they give you is a still-born OS, until your personalization brings it to life. it will just sit there until you make it something, I think their eula is very over-baked.

    4. srasuarez says:

      Hi Woody, (here I am ones again; one of the dummy with Win7 and in group B) I’m a bit delayed with my December updates. I’m with it now and after cleaning all stuff I don’t want I’m left with 6 Office security patches that I suppose I can download and KB3205402. I have just one question; can I download this Security and Quality Rollup for .NET Framework?
      It was so confusing this last month and it has been difficult to understand all your discussions so I just want to know if it’s dangerous? I mean can my machine crash down or something!!

      I list here the Office updates just in case one of them belongs to the new group you have switch to defcon2: KB2883033, 3128020, 3128022, 3128024, 3128019, 3128025

      By the way, sorry to bother you with these stupid things. I’m aware this place isn’t for this. I really try hard to just read, learn, shut up and make my own decisions. Thanks for your help

      • ch100 says:

        ¡Hola! srasuarez

        Woody is away and seems to have difficulties with a crashed computer at the moment – yes, it happens to everyone, but I think in this situation it is about hardware failure.
        The updates for December 2016 can all be installed safely, but according to the preference – Group B or Group A. This applies to the main update for Windows.
        For the .NET Framework, the recommended update is the one coming on Windows Update and there is no need to download separately from the Catalog.
        The Office Updates for January should be postponed and I believe that they are flagged as Important, but not ticked by default. In general, the updates which are not ticked by default, should not be installed as they will likely change later when Microsoft considers so. Otherwise, they should be treated as Optional, regardless of the category under which they are presented.

    5. Dianne says:

      I have installed the office updates that were dated 13 Dec 2016 as you said we could yesterday.

      After checking there were no new ones for today that you suggested we wait for.
      But of the 2 Win7Pro 64-bit laptops both running Office 2010, only one had an old Definition Update for Office 2010 KB3115475 32 bit edition checked and showing up today.

      I checked back and in Sept when you gave the go ahead this KB was NOT checked so I did not install it on one laptop. BUT it WAS checked on the other laptop, so I installed it.

      Therefore, on the previously unchecked laptop this KB is now showing up this month and only on that computer. So do I now go ahead and install it, since it is now showing checked?
      Thanks Woody and Happy New Year!

    6. jmwoods says:

      Shouldn’t that be MS-DEFCON 2 for Office patches only?

      Someone who still has outstanding security updates they have not applied may interpret that as “all patches”…

      • ch100 says:

        Yes, it should be obvious that it is for the Office patches for January 2017.
        However, because there is no pressing need and for simplicity, I think Woody prefers to recommend waiting for all updates until the end of the month just to avoid end-user confusion. Some of the new updates will make the current updates obsolete (superseded).
        But if there is enough care taken in selecting the updates, you are right, MS-DEFCON 2 should apply only for the Office January 2017 updates.

    7. ch100 says:

      KB3213552 was released for Windows 2016 in the Catalog. This update which is a hotfix (although cumulative) for the public regular update KB3206632 was previously released for Windows 10 1607 only.
      Either of KB3213552 or KB3206632 should be installed on Windows 10 1607 or Windows 2016 to clear the December 2016 and end of year patches for those Operating Systems.

      Please be aware that in some configurations the WU/WSUS type of updating may fail and the only known reliable method to install in such conditions is to download from the Catalog and install manually.

    8. Rafael Castro says:

      So far so goo. Installed and I was able to login after reboot 🙂

    9. K says:

      Dear Woody or anyone reading who knows,

      Did Microsoft Office 2007 have any updates issued today for Windows 10?

      I still cannot get the December updates installed at all, and when I did a search for Microsoft updates this afternoon EST to find the Office updates Woody mentions here, I found nothing.

      I did a restore point back before I installed the troublesome Malwarebytes 3.0 and I am still not getting updates installed for Windows 10 version 1511 0x800705b4 for all updates.

      Considering the problems I am having, I thought I would do the December updates and then install the anniversary updates but I can’t get the December updates installed.

      I don’t want to work on installations of December updates until I know if there are January Microsoft Office 2007 updates out there that I should not install, and thus that I need to continue to wait and search to hide them.

      Windows 10 update trouble shooter found no problems.

      The system restore did restore MBAE (Anti-Exploit) and a non-working version of MBAM. I thought I would uninstall the nonworking MBAM, but have not proceeded yet due to not knowing if I simply have not yet found todays Office updates.

      Malwarebytes support has been on and off with the problem since December 16th with no responses and days of nothing due to the holidays and then just more silence–I do have the paid version–so I seem to be making no headway with them what-so-ever. Their techs are usually right on the money and quick, but not this time. It has been 20 days since the faulty MBAM 3.0 was downloaded–many people were having a similar problem.

      I don’t want to have a bunch of updates out there that need to be installed.

      If I find any MS Office updates for 2007 that were released today and then get them hidden, I will try to install the December updates again after removing the non-working Malwarebytes 2.versioin x. If it fails again, I guess I will have to assume it is Trend Micro causing the problem.

      I really don’t want to turn my anti malware off for the many, many hours it takes for MS to search for and find and download the updates, especially since I have not been successful the 6 or 7 times I have tried.

      The error code I get is supposedly related to MS defender, but it is turned off currently due to my 3rd part malware support.

      Any help would be appreciated.

      I am thankful I finally threw up my hands regarding MS and bought a MacBook Pro this December, but I have a lot to learn before I begin the process of transferring documents from decades back over to the Apple OS. I will be stuck with Windows 10 for a long time I fear as I make the transition.

      • jmwoods says:

        A key phrase on the Office support site states..

        “After the December 2014 Cumulative Update (CU), all updates will be included in the Public Update (PU). CUs will no longer be released.”

        I was able to see the updates on Microsoft Catalog.

        There were none for Office 2007 and 2010.

        Office 2016 – 16 updates

        Office 2013 – 2 updates

        Click on the Last Updated column to sort newest to oldest.

        • ch100 says:


          What is your understanding of:
          “After the December 2014 Cumulative Update (CU), all updates will be included in the Public Update (PU). CUs will no longer be released.”

          Does this mean that separate updates outside of MU will not be released any longer and that the PUs will replace the previous CUs?
          Or does that mean that there will no longer be CUs for Office in general, public or released via other channels.
          I think what we see now is combination of those 2 methods, in the sense that Security Updates (for Office) seem to be cumulative, while the non-security updates are not.

        • abbodi86 says:

          It’s the first guess 🙂
          separate updates outside of MU will not be released any longer

          those “separate updates” were released as requestable hotfixes eavery two months

          all Office updates are cumulative since day 1
          they are cumulative to the same component that is represented by file name, i.e.
          mso2013-kb3141474 include all fixes from previous mso2013-kbxxxxxxx updates

          the update classification does not matter, security supersede all previous non-security, and non-security supersede all security

          • ch100 says:

            Thank you 🙂
            It is not clear though by looking at the documented supersedence in WSUS (or Catalog). Some are cumulative, some appear not to be.
            On an Office 2016 Pro installation patched to date including the patches released this week, I see 78 patches in total. 6 of them are Security and the difference are Update and 1 Definition (Junk Mail filter for Outlook). What complicates things is that Project and Visio although they have their own lists of updates, some of them are in the main Office list.
            From the numbers it would appear that only the Security updates are true cumulative while the others are not which is not the case. I would like to see only less than 10 updates for each product if the updates are cumulative in reality.
            Office uses the msi mechanism with msp increments and backs up older versions on disk. Disk Cleanup does not operate on Office Updates which would be very useful if it worked on Office.
            I think the Office Update mechanism for updating is closer to the XP mechanism than to that of the newer versions of Windows.

          • abbodi86 says:

            Like i said, Office patches are cumulative for the specific component
            but ther are not rolled up, only a very very few hotfixes have patches for multiple components

            yes, MSI/MSP mechanism is old and not differential which cause the patches to be large-sized

            Office 2010 patches are a little less in sized because the rarely-updated multilingual components are separated from the regulary-updated neutral components
            i.e. the current neutral update for word is
            while the latest multilingual update for Word is

            Office 2013 patches pre-SP1 were the same

            but with Office 2013 post-SP1 and Office 2016, all patches became multilingual
            the multilingual components are included with every update, even if there is nothing fixed or updated in these files
            that’s why we are presented with nearly 1GB of office updates each month

            this list details Office 2013 updates, you can install latest security or latest non-security for each patch

      • ch100 says:

        “Did Microsoft Office 2007 have any updates issued today for Windows 10?”

        The answer is no.
        Office 2007 is close to the end of support and probably is stable enough by now that it does not require so much (quality) updating. The current round of updates are non-security.
        Office 2007 updates (and any Office updates) are not specific for a version of Windows though, they are stand-alone for the product they represent.

      • ch100 says:

        Use Windows update MiniTool for updating Windows 10 and you will be able to select everything that you need.

      • TonyS says:

        @K and regarding MWB v3 upgrade, have you looked at the forum
        especially known issues and FAQ’s? It’s possible to revert to v2 if you are having ongoing problems – personally I’m waiting until the dust settles before I upgrade.

    10. K says:


      This number, 0x800705b4, I threw into the end of the 3rd paragraph is the error code I get when the attempt at download of the December update fails.

      I am still learning the Delete button on the MacBook. It only deletes going backward and I think I deleted some important works by mistake assuming it was working like a MS keyboard. Sorry.

      Thank you for the help!

      • Günter Born says:

        0x800705b4 stands for ERROR_TIMEOUT – something prevent your machine from downloading the update. Maybe an installed third party antivirus system?

        Try to dig into that direction.

        BTW: Office 2007 is out of support – so no more updates yet.

        • Jim4 says:

          Microsoft Office Suite 2007 Service Pack 3
          Extended Support End Date: 10/10/2017


          • ch100 says:

            I think you have the correct date. Support for Office 2007 was extended for other 6 months and I had the old date.

        • ch100 says:

          Sorry Gunther, this is not accurate. Office 2007 still receives security updates. The Extended Support for Office 2007 ends April 11, 2017.

          This is useful too


          • Günter Born says:

            @Jim4, @oh100: You are right! I misinterpreted things – my reading was related to non security updates (for Office patchday, 1st thuesday in month) – I overlocked the monthly security updates – which are still addressing Office 2007 until Oct 2017. Sry

            • ch100 says:

              Not a problem Günther.
              It is important though for those who still use Office 2007 to feel that they use a supported product even if they do not keep updating regularly.

        • K says:

          @ch100 and Gunter Born, Tony and others,

          Thank you for the help. I still am in limbo. I have read the articles suggested.

          MBAM representative told me to use MBAM-clean and MBAE clean to completely remove the Malwarebytes products that had been there. I did that. He also e told me to install Malwarebytes 3.0. I tried, but I got a runtime error. He asked me to do that yesterday and and he did not respond to my questions. So today with the day moving forward I did the removals and attempted download of 3.0.

          After that I decided it was time to do a Windows 10 update Trouble Shooter again and it found a lot of issues. It fixed all but one. That was: Potential Windows Update Database error detected-Not fixed
          and under that it listed: Repair Windows Update Database Corruption- Not run.

          There were a lot of issues. One had to do with the BITS service—it said the requested service was started and where to get more help—>NET HELPMSG 2182. I did a search for that on the web but could not understand it. I don’t really understand what any of the errors were. . .

          I am in the many hour process of unhiding the December cumulative update for Windows 10 version 1511 again, and the Adobe Flash Win 10 version 1511 updates.

          I will see if can succeed at updating the computer. Next Tuesday is looming close and I will be out of town most of that day-ugh and Monday. I hope I can resolve this before then.

          I do have a system image from after the last update, before trying to install these updates, and one from before then, so system images before the installation of December and November updates. The December one might have MBAM 3.0 on it, and I don’t know at what point of trying to remove it, but I think I had tried.

          I have never restored from a system image, but that may end up being a last resort if this does not work. Not being computer knowledgeable, I am concerned about doing a system image restore correctly if necessary.

          If I manage to get these updates downloaded (i.e., no system image use) I will try Version 1607. I hope that may “clean up” my system if I do not have to use the system images.

          . . . .any suggestions?

          • jmwoods says:

            The current version of Malwarebytes Anti-Malware is now at 3.0.5

            Malwarebytes Anti-Exploit is no longer a stand-alone, free tool.

            It is now included (as is Malwarebytes Anti-Ransomware) in the paid version of Malwarebytes Premium.

            • TonyS says:

              MWB is certainly at v3.0.5 and does include MWB-AE, but you can still go back to MWB v2 and run MWB-AE beta as a standalone extra.

          • K says:

            Following the trouble shooting tool changes and after unhiding the windows 10 December Cumulative update version 1511, the Adobe Flash Update and the MSRT tool, I got the same error message. I tried what I had tried many iterations before, prior to my last system restore, when it worked by going to the updates Advanced link on the Update settings page and unchecking the choice to not download non-update related products, like the MS office updates, although I had none “out there” to install. Again, they downloaded.

            I stopped at this point.

            Will making a system image of version 1511 help me if the 1607 download creates lots of issues?

            I ask because I know the roll back time is very limited once you upgrade to 1607.

            If a system image of version 1511 could possibly help me, I will make it and then update to 1607 and hope the MS Office 2007 updates from December will update with the 1607 version successfully.

            • ch100 says:

              It is always useful to have an image to rollback and this is even more important if you have concerns about the quality of the upgrade.
              Re upgrade, I would download a full image and perform the upgrade manually instead of trusting Windows Update for this purpose. There are known unresolved issues with Windows Update and Windows 10 1607.

              • K says:

                @ch100 Do you recommend the Media Creation Tool, which I have never used, and just read about yesterday, or the Update Catalog? MS warns that only system admins should use the catalog.

                Thank you for your help. I am very appreciative of it!

                I finally got MBAM straightened out after 22 days. The last tech I was working with using email gave me a courtesy phone call after I asked for one. It was very productive.

                One issue was that no matter what we did MB Anti-Exploit would not uninstall even though we used the tool twice. We finally got rid of it and installed the newest version.

                The newest version still has a weird glitch. When first installed it says not all shields are working, but if you go to the main page it either shows they all are working, or you can turn on the anti-exploit shield and then all is well. They are working on this glitch. All seems to be fine with it now.

                My system image is being made now, and I will await the answer to where I should get the Anniversary Update for the manual download.

                Thanks again!

                • K says:

                  I ended up using WSUS because I read the Media Creation tool would wipe out temporary files rather than upgrade in place and the MS Catalog says only System Admins should use it.

                  I just used an ethernet connection rather than the WiFi. I think it all went okay and it didn’t take too long.

                  I am wondering if it is still safe to turn off or disable the Connected User Experiences and Telemetry service. In 2015, articles were saying one should do this for privacy. I did originally. I see it is running on my new version 1607. Having a Home Windows 10, I do not have gpedit capabilities.

                  MBAM 3.0 is running fine now.

                  I want to thank everyone for their help!

    11. Günter Born says:

      Microsoft’s office engineering team was this time late to document the details for Office updates. Updates was only for Office 2013/2017 and the Viewers (Office Viewers will be discontinued in Nov 2017 (as I mentioned in my blog post http://borncity.com/win/2017/01/05/office-patchday-updates-january-3-2017/=

      Microsoft’s office engineering team finally delivered details here:


      It’s all optional updates related to several bug fixes. No need to install these updates, if you are not affected by those bugs.

    12. Clueless says:

      Re: Günter Born “http://borncity.com/win/2017/01/05/office-patchday-updates-january-3-2017/=”

      Throws ‘Page not Found’.

    13. Clueless says:

      Re: last post.

      Remove last “=” from G. Born’s link & it works

    14. ch100 says:

      This is quite unbelievable! Microsoft releasing patches for Office 2003 (Word Viewer 2003) in November 2016 (13 years after the release of the product) and failing by breaking functionality, which is fixed in January 2017!
      Read for yourself.

      Improvements and fixes
      Fixes the following issue:
      You experience formatting issues (font loss and table corruption prompt) in RTF files. This issue occurs after you install MS16-133: Description of the security update for Word Viewer: November 8, 2016.

      This is the latest incarnation of the January 3, 2017, update for Word Viewer (KB3141490)


      To apply this update, you must have Service Pack 3 for Microsoft Word Viewer 2003 installed.

      Applies to
      Microsoft Office Word Viewer 2003 Service Pack 3

    Leave a Reply