Results 1 to 2 of 2

Thread: Error 8007066F after running Microsoft Office Update

  1. #1
    Join Date
    Oct 2004
    Posts
    76

    Error 8007066F after running Microsoft Office Update

    I am facing a bit complex issue here. I am getting Error 8007066F after office update. I thought this would be fixed by performing the update back but still the same error persist. I cannot find any relative fix for that also. I am have installed both Microsoft Office 2003 and Microsoft Office 2007 on my system. Office 2007 was a trial. Later on I directly upgraded to Office 2007. Then I also upgraded my OS from XP to Vista and such error appeared. How can I fix them.

  2. #2
    Join Date
    Oct 2005
    Posts
    54

    Re: Error 8007066F after running Microsoft Office Update

    The error which you had mentioned appeared when you install or download the update. I will recommend you to follow the manual way of updating your system. That would help you. Also download the updates which are really needed and ignore other one. Once there is a proper fix available this kind of issues can be avoided. For more information just check the below link.

    Error code when you use the Windows Update Web site or the Microsoft Update Web site to install updates: "0x8007064C"

Similar Threads

  1. Microsoft Office Updates for Mac Office Update Service
    By @nkit Trivedi in forum Office Update Service
    Replies: 2
    Last Post: 20-04-2012, 02:14 PM
  2. Replies: 5
    Last Post: 12-09-2011, 11:01 PM
  3. Replies: 5
    Last Post: 19-08-2010, 02:22 PM
  4. Error 57E while running Office Update
    By destroyer in forum Office Update Service
    Replies: 5
    Last Post: 14-01-2010, 12:07 AM
  5. Microsoft Office 2007 SP2 Update failed
    By Daisyel in forum Office Setup
    Replies: 1
    Last Post: 04-05-2009, 05:02 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,711,665,491.75535 seconds with 17 queries