Results 1 to 9 of 9
  1. #1
    Lounger
    Join Date
    Nov 2010
    Location
    NJ
    Posts
    26
    Thanks
    2
    Thanked 1 Time in 1 Post

    Windows office updates throwing off msiInstaller warnings with every update

    After installing the latest November windows updates to my WIN7PRO64 machine, I got many warnings 1039 in the event viewer.


    All read like this "Product: Microsoft Office Single Image 2010. The application tried to modify a protected Windows registry key \Software\Classes\CLSID\{25336920-03F9-11CF-8FD0-00AA00686F13}\InprocServer32." Three quarters of the warnings mentioned "Office Single Image 2010", a quarter were similar but the product was "Visio." The warnings started in August of this year -- 32 warnings.
    Sample Details for Office Single Image warning:


    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
    <Provider Name="MsiInstaller" />

    <EventID Qualifiers="0">1039</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-11-28T21:19:51.000000000Z" />
    <EventRecordID>512719</EventRecordID>
    <Channel>Application</Channel>
    <Computer>MN-PC</Computer>
    <Security UserID="S-1-5-18" />
    </System>
    - <EventData>
    <Data>Microsoft Office Single Image 2010</Data>
    <Data>\Software\Classes\CLSID\{AE24FDAE-03C6-11D1-8B76-0080C744F389}\InprocServer32</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data />

    Details for Visio warning:

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
    <Provider Name="MsiInstaller" />
    <EventID Qualifiers="0">1039</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-11-28T21:19:21.000000000Z" />
    <EventRecordID>512688</EventRecordID>
    <Channel>Application</Channel>
    <Computer>MN-PC</Computer>
    <Security UserID="S-1-5-18" />
    </System>
    - <EventData>
    <Data>Microsoft Office Visio 2010</Data>
    <Data>\Software\Classes\Interface\{BEF6E003-A874-101A-8BBA-00AA00300CAB}\ProxyStubClsid</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data />

    I checked immediately to see if the updates had in fact been installed. They were, all listed as successful. I ran windows update again to see if some or all of the updates would reappear, and they do not. The computer seems to be running fine. Then I went back in time in the event viewer and found the same warnings for the last three or four times windows issued updates to Office products. Same warning message with each group of updates. Also several months ago I got one similar warning with a Quicktime update. All of the 1039 warnings started in October. All update appear to be successfully installed.Again, only Office updates generate the misInstaller 1039 warnings about not being able to open a protected registry key.


    I'm only guessing, but I think these messages started a few months ago when I installed the Calendar Printing Assistant Add-in in Outlook 2010. The add-in was developed for Outlook 2007, then modified to work with 2010. Trying to trouble shoot the msiInstalled 1039's, I read that the warnings might be caused when there are components on the same machine from two different versions of MSOffice. In my case that one component (even though modified to work with 2010) is still a version of the Outlook 2007 Calendar tool. I uninstalled the add-in (it was a regular install.) But PERHAPS THE UNINSTALL OF THE ADD-IN LEFT REGISTRY ENTRIES BEHIND THAT ARE KICKING OFF THE WARNINGS. Also, not long after I installed Office 2010 Pro years ago, I installed Visio separately.


    I've been advised to uninstall 2010, literally scrub it from my system with a manual uninstall, the reinstall the suite. That's at least a day's work, when you add the necessity of then shagging and installing all the updates that a fresh install will require, not to mention resetting all my preferences and giggling Outlook, as one always has to do, to get IMAP to work correctly.

    My question: is there a way to stop the msiInstaller 1039 warnings by modifying a registry key or another way to reconcile the 2010 suite with the 2007 component? Thanks for any thoughts.
    Last edited by mnorman; 2015-12-24 at 15:01.

  2. #2

  3. #3
    WS Lounge VIP
    Join Date
    Dec 2009
    Location
    Earth
    Posts
    8,191
    Thanks
    48
    Thanked 985 Times in 915 Posts
    Obviously "shagging" has a different meaning in the USA.

    cheers, Paul

  4. #4
    Administrator
    Join Date
    Mar 2001
    Location
    St Louis, Missouri, USA
    Posts
    23,592
    Thanks
    5
    Thanked 1,059 Times in 928 Posts
    The logging level is a command line option. I can't find anything that allows you to globally set options.

    Joe

  5. #5
    Lounger
    Join Date
    Nov 2010
    Location
    NJ
    Posts
    26
    Thanks
    2
    Thanked 1 Time in 1 Post
    A month later and I've discovered that the problem is not confined to MS Office products. I just updated Quicktime for the PC and and got this:

    Product: QuickTime 7. The application tried to modify a protected Windows registry key \Software\Classes\Component Categories\{7DD95801-9882-11CF-9FA9-00AA006C42C4}.

    Product: QuickTime 7. The application tried to modify a protected Windows registry key \Software\Classes\Component Categories\{7DD95802-9882-11CF-9FA9-00AA006C42C4}.

    So it appears to be an msiInstaller problem. Any ideas would be very helpful.

  6. #6
    WS Lounge VIP
    Join Date
    Dec 2009
    Location
    Earth
    Posts
    8,191
    Thanks
    48
    Thanked 985 Times in 915 Posts
    Check the system integrity.
    Start > Run, cmd, sfc /scannow

    cheers, Paul

  7. #7
    Super Moderator jwitalka's Avatar
    Join Date
    Dec 2009
    Location
    Minnesota
    Posts
    6,796
    Thanks
    117
    Thanked 799 Times in 720 Posts
    Quote Originally Posted by Paul T View Post
    Check the system integrity.
    Start > Run, cmd, sfc /scannow

    cheers, Paul
    I believe you have to open an administrative command window to run an SFC scan.

    Jerry

  8. #8
    Lounger
    Join Date
    Nov 2010
    Location
    NJ
    Posts
    26
    Thanks
    2
    Thanked 1 Time in 1 Post
    Thanks for the suggestion. I ran sfc /scannow this weekend and it turned up no errors. But I can certainly run it again.

  9. #9
    Lounger
    Join Date
    Nov 2010
    Location
    NJ
    Posts
    26
    Thanks
    2
    Thanked 1 Time in 1 Post
    Ran sfc /scannow again from the admin prompt and it reported no problems.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •