Error Code: 0x80070643
-
Saturday, August 05, 2006 1:55 PM
I have tried to install Windows and Office updates utilizing the Automatic installation tool; but, the initialization takes place and none of the updates are intalled.

I ran WinDoctor and I am told that I am missing file "ORUN32.exe" and it cannot access "learn32.dll" and "pctree32.dll". I have searched my computer and found the orun32 and pctree32 files but not the learn32 file.
I don't know how it got deleted and not sure how to get it back in place to use the automatic update.
What do I do to get my Automatic updates to run again?

Please help me!
All Replies
-
Tuesday, October 17, 2006 11:49 AM
In the toolbar Icons on the left you should have a small yellow sheild with an exclaimation mark in the middle. Jusk click on sheild icon in the bar to try to run the installer again.
However, it may still give you problems. This is also a problem that doesn't have much documentation. It is hard to know what is going on.
-
Monday, November 13, 2006 6:15 AMI have the same installation failure error. Has anyone found a solution?
-
Wednesday, November 15, 2006 6:59 PM
This worked for me:
Microsoft has published Knowledge Base article 903772 to describe the issue, and suggested a few possible resolutions and solutions to the problem. Basically, the issue centered around Ose.exe which is Microsoft Office Source Engine, and the troubleshooting and resolving steps involve checking Ose.exe status or replacing the corrupted Ose.exe.
Determine the status of the Office Source Engine service by using the following steps:
Click Start, click Run, type services.msc, and then click OK.
In the list of services, double-click Office Source Engine.
View the Startup type list.
If the startup type is set to Disabled, change the startup type to Manual. To do this, click Manual in the Startup type list, and then click OK.
Try to install the Office update again.
If Automatic Updates has continously prompted you to install critical updates related to Microsoft Office 2003, this step is most likely meaningless. -
Saturday, November 18, 2006 10:23 AM
Office Source Engine bull *** solution does not work...no matter how many times you restart this service.
This problem was most likely created by a registry cleaner that has removed important link in the registry that belong to office source engine. If the path for the original installation files had been deleted, you will have to create a new one, the following article does not appear to be related to the error 0x80070643, it refers to installation failure for SP or updates in general but you will find it closely related to your problem. Follow the steps exactly, not that difficult (When you get to the part where you modify the "Path" value, type D:\), here is the article:
http://support.microsoft.com/?id=884298 (Full article)
or u can follow this instructions (Copied from article above):
RESOLUTION
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To resolve this issue, you must identify the product code globally unique identifiers (GUID) for your Office 2003 products. Then, you must re-create the path of the original installation source in the registry.
Step 1: Identify the product code GUID for your Office 2003 product
To determine the product code GUID for your Office 2003 product, see the following article in the Microsoft Knowledge Base:
832672 (http://support.microsoft.com/kb/832672/) Description of numbering scheme for product code GUIDs in Office 2003
Make a note of all the product code GUIDs for your Office 2003 products that you have installed on your computer. One missing entry may prevent all your Office 2003 products from being updated.
Step 2: Re-create the path of the original installation source in the registry
To do this, follow these steps:1. Click Start, click Run, type regedit, and then click OK. 2. Locate and then click to select the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Delivery\SourceEngine\Downloads\download_code
The download_code subkey is a series of numbers and letters in a format that may look similar to the following:
90000409-6000-11D3-8CFE-0150048383C9
Note There may be multiple download code subkeys that have a similar format of numbers and letters separated by dashes.3. With the download code subkey selected, click to select the Sources subkey.
In the Sources subkey, you will find the product code GUID values for your Office 2003 product that you previously identified.
Note There may be multiple product code GUID values.4. With the product code GUID value for your Office 2003 product selected, point to New on the Edit menu, and then click String Value. 5. Type Path, and then press ENTER. 6. With Path selected, click Modify on the Edit menu. 7. In the Value data text box, type the full path of the original installation source for your Office 2003 program, and then click OK.
For example, type D:\ if the CDROM drive used for installation is the D: drive.8. Repeat steps 4 through 8 for each product code GUID value that corresponds to an Office 2003 product that is installed on your computer. 9. Repeat steps 3 through 9 for each download code subkey if you determined in step 3 that you have multiple download code subkeys. 10. When you have completed all steps, click Exit on the File menu Good luck and report back!
-
Saturday, November 18, 2006 10:24 AM
Office Source Engine bull *** solution does not work...no matter how many times you restart this service.
This problem was most likely created by a registry cleaner that has removed important link in the registry that belong to office source engine. If the path for the original installation files had been deleted, you will have to create a new one, the following article does not appear to be related to the error 0x80070643, it refers to installation failure for SP or updates in general but you will find it closely related to your problem. Follow the steps exactly, not that difficult (When you get to the part where you modify the "Path" value, type D:\), here is the article:
http://support.microsoft.com/?id=884298 (Full article)
or u can follow this instructions (Copied from article above):
RESOLUTION
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To resolve this issue, you must identify the product code globally unique identifiers (GUID) for your Office 2003 products. Then, you must re-create the path of the original installation source in the registry.
Step 1: Identify the product code GUID for your Office 2003 product
To determine the product code GUID for your Office 2003 product, see the following article in the Microsoft Knowledge Base:
832672 (http://support.microsoft.com/kb/832672/) Description of numbering scheme for product code GUIDs in Office 2003
Make a note of all the product code GUIDs for your Office 2003 products that you have installed on your computer. One missing entry may prevent all your Office 2003 products from being updated.
Step 2: Re-create the path of the original installation source in the registry
To do this, follow these steps:1. Click Start, click Run, type regedit, and then click OK. 2. Locate and then click to select the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Delivery\SourceEngine\Downloads\download_code
The download_code subkey is a series of numbers and letters in a format that may look similar to the following:
90000409-6000-11D3-8CFE-0150048383C9
Note There may be multiple download code subkeys that have a similar format of numbers and letters separated by dashes.3. With the download code subkey selected, click to select the Sources subkey.
In the Sources subkey, you will find the product code GUID values for your Office 2003 product that you previously identified.
Note There may be multiple product code GUID values.4. With the product code GUID value for your Office 2003 product selected, point to New on the Edit menu, and then click String Value. 5. Type Path, and then press ENTER. 6. With Path selected, click Modify on the Edit menu. 7. In the Value data text box, type the full path of the original installation source for your Office 2003 program, and then click OK.
For example, type D:\ if the CDROM drive used for installation is the D: drive.8. Repeat steps 4 through 8 for each product code GUID value that corresponds to an Office 2003 product that is installed on your computer. 9. Repeat steps 3 through 9 for each download code subkey if you determined in step 3 that you have multiple download code subkeys. 10. When you have completed all steps, click Exit on the File menu Good luck and report back!
-
Saturday, November 18, 2006 10:25 AM
Office Source Engine bull *** solution does not work...no matter how many times you restart this service.
This problem was most likely created by a registry cleaner that has removed important link in the registry that belong to office source engine. If the path for the original installation files had been deleted, you will have to create a new one, the following article does not appear to be related to the error 0x80070643, it refers to installation failure for SP or updates in general but you will find it closely related to your problem. Follow the steps exactly, not that difficult (When you get to the part where you modify the "Path" value, type D:\), here is the article:
http://support.microsoft.com/?id=884298 (Full article)
or u can follow this instructions (Copied from article above):
RESOLUTION
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To resolve this issue, you must identify the product code globally unique identifiers (GUID) for your Office 2003 products. Then, you must re-create the path of the original installation source in the registry.
Step 1: Identify the product code GUID for your Office 2003 product
To determine the product code GUID for your Office 2003 product, see the following article in the Microsoft Knowledge Base:
832672 (http://support.microsoft.com/kb/832672/) Description of numbering scheme for product code GUIDs in Office 2003
Make a note of all the product code GUIDs for your Office 2003 products that you have installed on your computer. One missing entry may prevent all your Office 2003 products from being updated.
Step 2: Re-create the path of the original installation source in the registry
To do this, follow these steps:1. Click Start, click Run, type regedit, and then click OK. 2. Locate and then click to select the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Delivery\SourceEngine\Downloads\download_code
The download_code subkey is a series of numbers and letters in a format that may look similar to the following:
90000409-6000-11D3-8CFE-0150048383C9
Note There may be multiple download code subkeys that have a similar format of numbers and letters separated by dashes.3. With the download code subkey selected, click to select the Sources subkey.
In the Sources subkey, you will find the product code GUID values for your Office 2003 product that you previously identified.
Note There may be multiple product code GUID values.4. With the product code GUID value for your Office 2003 product selected, point to New on the Edit menu, and then click String Value. 5. Type Path, and then press ENTER. 6. With Path selected, click Modify on the Edit menu. 7. In the Value data text box, type the full path of the original installation source for your Office 2003 program, and then click OK.
For example, type D:\ if the CDROM drive used for installation is the D: drive.8. Repeat steps 4 through 8 for each product code GUID value that corresponds to an Office 2003 product that is installed on your computer. 9. Repeat steps 3 through 9 for each download code subkey if you determined in step 3 that you have multiple download code subkeys. 10. When you have completed all steps, click Exit on the File menu Good luck and report back!
-
Sunday, November 19, 2006 2:36 AMThanks DCKline that worked for me i've been trying for days to get it to download and your advice did the trick thanks again.
-
Sunday, November 19, 2006 3:39 PM
Thanks for the tip, the first solution did nothing for me as the service was all ready set to manual. But by adding the path key in the registry for one of the product keys I was able to complete the update to Office 2003 with no other issues!
Scott
-
Tuesday, November 21, 2006 6:36 AMit works for me! Thanks.
-
Tuesday, November 28, 2006 12:05 PMThis worked for me - 1,000 thanks. The trouble was caused by a 'clean up' using a RegEdit software package combined with my lack of knowledge around Office 2003 identifiers and Source Engine links. Where as a little knowledge can be dangerous, no knowledge can be disasterous. Thanks again. I have contacted my RegEdit supplier and asked them what, if anything, they can/propose to do for the future - e.g. warn users or maybe include the M'Soft source engine identifiers in a ready-made 'ignore' list.

-
Tuesday, November 28, 2006 3:26 PMMicrosoft support told me to use my Office 2003 installation disk to do a "repair". That fixed the update error problem and all updates installed following repair with no further problems.
-
Wednesday, December 06, 2006 2:18 PMawesome dude. it worked. this things been bugging me for long time. you are a lifesaver
-
Friday, December 15, 2006 11:03 PM
I have attempted every 'fix' written about this problem, and all my parameters meet the specs. I cannot install the Junk Mail Filter to MS Office 2003 and most other MS Office updates.
They all download, but they do not wish to install. I have a history of error numbers and have attempted each solution finding nothing to help. Is there really a fix for this disgusting problem besides deleting and reinstalling? If even that would work? Pardon my cynicism.
Thanks for any and all help, thoughts, ideas and karma.

-
Tuesday, January 09, 2007 6:47 PM
Reporting back to say that this most arcane procedure worked perfectly. But why? Why would one download fail because it couldn't discover how Office 2003 was originally installed [from the D:\ drive]- especially when several other Office updates have installed without difficulty? And the variety of fixes for this one failure code suggests that 0x80070643 means nothing more than: "Haven't a clue - all I know is it didn't work! From here on in you're on your own, son." But many many thanks to you!
rossmac1
-
Tuesday, January 16, 2007 10:09 PMSO nice thanks. I love all nerds and the nerd in my self heheh. keep up the good work
-
Wednesday, January 24, 2007 11:37 AMThis was it, been trying to fix a customers system and was almost to the point of reinstalling all the software. Thanks Armen2003
-
Thursday, February 22, 2007 3:37 PM
Thank you DCKline.
That's all it took to get mine to work.

-
Thursday, February 22, 2007 4:13 PM
armen2003 wrote: Office Source Engine bull *** solution does not work...no matter how many times you restart this service.
Hello armen2003
DCKline's fix may not have worked for you, but the solution
posted by DCKline worked on mine and apparently on several other users systems also.
My recommendation, for whatever it's worth, is for users with this problem is to try the easiest option first and then move on to the more hard core options
if the 1st one doesn't work. You shouldn't call anyones solution that has worked for others "Bull **". I think everyones input is appreciated even if it doesn't work for some people.
By the way, it did NOT say to "restart" the service. I'm sure if you read it again you'll notice that DCKline said if the service is set to disabled then you need to set it to MANUAL.
Perhaps it didn't work for you if you were starting the service instead of letting Microsoft Update start and stop the service as needed.
Thanks for posting a 2nd option for those who weren't able to get their updates installed by setting the service to manual.
Tuesday, February 27, 2007 10:31 PMThanks DCKline! The short fix you suggested worked great.Saturday, March 10, 2007 3:46 AMI followed your directions but I still can't get the updates to install. Any other suggestions?Tuesday, March 13, 2007 3:18 PMDear OhioMom,
I call this the SKU011.cab problem. We are getting this from both WSUS, or by AutoUpdate setting.
The problem is related to a set of Office 2003 Updates (such as Kb924885 Junk E-mail filter and about 6 others, listed at the end) that won't install due to missing original Office install files, specifically SKU011.cab, either because you did not "Run All from My Computer, chose the "Delete Installation (cache) files" option after the install, or the update can't find the original install path (such as installing from a CD on a server (orphaned path), or the outside chance that the original Office CD had some bad files (or bootleg source). We have fixed dozens of our networked PCs using the solution below.
The fix is, let the updates that won't install, sit in the System Tray (yellow shield). Then, from Control Panel, Add/Remove Programs, Office 2003 entry, select Change, Add or Remove Features, must check the box for "Choose Advanced Customization of Applications", Update button, on top MS Office level, must choose dropdown arrow for Run All From My Computer, Update button, see Install progress, caching cab files messages (including SKU011.cab), then the Install will stop and ask for the original CD source, change the path to the local CD drive (ex. D:\ ), load the Office CD, click Ok, and let it continue until Finish ("successful install"). Then, from the system tray, open the awaiting Updates, choose Custom option, Install, then see the updates install successfully. If no updates in the tray, then manually run Windows Updates, wait for it to find the problem updates, then install them. They should succeed.
The ultimate solution when installing Office, is to copy the entire Office CD contents (use Edit, Select All) to a folder you make on the hard drive C:\ root (ex. zOffice2003), and then install Office from the hard drive folder, Custom option, Run All From My PC, do not delete the cached install files files, and in the future all updates will subsequently install without ever asking for the CD again, because all the source files are now referenced from the hard drive.
Current Office updates that won't install due to this error are: 928013, 929064, 929057, 929058, 925251, 929060, 924885.
Tuesday, March 20, 2007 8:30 PMTo Cline Thank you for your valuable tip. I spent many hours searching for a solution and I was not able to solve the problem. I did what you sugested and windows is working now full updated.Tuesday, March 20, 2007 10:04 PMThanks, this worked for me. I might have caused the problem by using a program to clean the registry called, RegistryFix.Monday, March 26, 2007 12:32 AMHey Armen2003,
You really know your stuff! It was the reg cleaner that created the problem. Luckily, I had the back ups and was able reverse the damage. Everything works perfectly now. You are great and again THANK YOU THANK YOU THANK YOU!
Thursday, April 19, 2007 11:11 PMThe ultimate solution when installing Office, is to copy the entire Office CD contents (use Edit, Select All) to a folder you make on the hard drive C:\ root (ex. zOffice2003), and then install Office from the hard drive folder, Custom option, Run All From My PC, do not delete the cached install files files, and in the future all updates will subsequently install without ever asking for the CD again, because all the source files are now referenced from the hard drive.
I lost my original Office CD and had to purchase a copy from Microsoft so essentially I am starting over.
Should I uninstall my current version of Office 2003 before copying all contents to a file on hard drive?
Am a newbie at this, will there be an option NOT to delte the cached install files offered during the installation?
Thanks in advance for your time.
hawkhock
Friday, May 11, 2007 7:21 PMThanks DCKline, this worked for me to.Tuesday, May 15, 2007 11:43 PMThanks, armen. This also worked for me!Monday, May 21, 2007 10:27 PMYou are totally right about those update numbers being the ones that won't install. However, it didn't work for me. It's a pity as I was hoping it would.
Now I'll have to try the registry option. Come to think of it, my problems seemed to come along after using a registry cleaner recommended by PC Utilities magazine. And yes, as a fairly experienced computer user, I should have backed up my registry before starting! :-(
Saturday, June 16, 2007 4:49 PMFunkkw wrote: I have the same installation failure error. Has anyone found a solution? Saturday, June 16, 2007 4:49 PMFunkkw wrote: I have the same installation failure error. Has anyone found a solution? Tuesday, June 19, 2007 9:56 PMThanks Armen
Your advice really did the trick. I was reluctant to 'play' with the registry so I kept putting it off but in the end I read your advice and followed the instructions very carefully - and those 3 updates installed just as easily as the rest of them had done!! BRILLIANT!! THANKS!!
Brianpals
Thursday, July 05, 2007 4:58 PMI have tried to install Windows and Office updates using Automatic Updates. The program intialization function occurs but the install fails What can I do to get my Automatic Updates to be Automatic again?Saturday, July 07, 2007 6:51 PMThis is interesting and plausible. I went through the whole process including eventually re-installing Office. Updates started working after several months of failures until the dreaded Junk email etc.
Does MS want me to buy Office 2007?
Sunday, July 29, 2007 12:26 AM
This helped so much thank you for the info about how to fix this problem!!!!Wednesday, August 22, 2007 12:15 PMHi guys,
Sorry but i didn't really understand the Downloads_Code fix
In : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Delivery\SourceEngine\Downloads
I only have :
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Delivery\SourceEngine\Downloads\microsoft.watson.alrtintl.data
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Delivery\SourceEngine\Downloads\microsoft.watson.watsonrc.data
So i create a :
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Delivery\SourceEngine\Downloads\90110409-6000-11D3-8CFE-0150048383C9
and
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Delivery\SourceEngine\Downloads\90110409-6000-11D3-8CFE-0150048383C9\Sources with a Path reg_sz
Can you confirm it's correct or wrong, or give me an exemple of how you create your new keys ?
Thank's a lot
Regards
Harold
Friday, August 24, 2007 5:09 AMMy service was already set to manual. I tried starting it, but that didn't work. What did work was re-enabling a harddrive that I had pulled out. That F: drive is where the MSOCache (i.e. Microsoft Office Install File cache) file had been written and the absense of that drive/folder seemed to throw Windows Update off. I figured this out when I tried to use the install disk for Office 2003 to do a "Repair" option and it errored out and complained about the invalid path to F:\MSOCache.
Glad I hadn't wiped that drive clean yet.
:-)
BTW, there is at least one MS KB article on deleting the MSOCache folder.So if you deleted your MSOCache folder, and you've tried DCKline's, Armeen's, and the guy with the "repair with install disk" suggestions to no avail, see that article for ideas on how to get around this (possible problem). Good luck.
Friday, August 24, 2007 5:10 AMI had the registry entry in as described so no need to build a "path" value.
What did work was re-enabling a harddrive that I had pulled out. That F: drive is where the MSOCache (i.e. Microsoft Office Install File cache) file had been written and the absense of that drive/folder seemed to throw Windows Update off. I figured this out when I tried to use the install disk for Office 2003 to do a "Repair" option and it errored out and complained about the invalid path to F:\MSOCache.
Glad I hadn't wiped that drive clean yet.
:-)
BTW, there is at least one MS KB article on deleting the MSOCache folder.So if you deleted your MSOCache folder, and you've tried DCKline's, Armen2003's, and the guy with the "repair with install disk" suggestions to no avail, see that article for ideas on how to get around this (possible problem). Good luck.
Thursday, August 30, 2007 3:37 AMArmen2003 says: "Office Source Engine bull *** solution does not work...no matter how many times you restart this service."
Well, your wrong buddy. It worked first try for me. Maybe we need to chill on the flames of other folks suggestions.
Thursday, August 30, 2007 3:41 AMarmen2003 says:"Office Source Engine bull *** solution does not work...no matter how many times you restart this service."
Well buddy, it worked for me the first try. Maybe you should worry about your own solutions, instead of flaming someone elses.
Thursday, September 06, 2007 10:14 PMI tried the long soluition first by editing the registry and it was not successful. I then enabled the Office Source Engine service and the update worked!! This is not bull pucky as another user suggested. It worked perfectly for me. Thanks much.
Friday, September 21, 2007 3:51 AMThanks DCKline. This sure worked well for me. It seems I have to do this each time the new Outlook 2003 Junk Filters are released. I sure would like to find out what keeps changing that setting to disabled.Friday, September 21, 2007 5:00 PM
dckline, thanks! It worked for me also.Thursday, December 06, 2007 2:44 AMThank you for your concise offer with help. However I cannot find Office Source Engine - I cannot update Defender. Have used the online-tool, and the result was that the error massage changed from one 0x80072EE2 to another 0x80070643.
I wonder if your well-developed knowledge (IMO) has an answer, please?
Thank you in anticipation
Thula
Saturday, February 16, 2008 5:18 PMit works, u r wonderfulWednesday, February 20, 2008 4:13 PMI had the same error and the solution DCKline suggests worked perfectly. Thanks for the posting.
Saturday, March 01, 2008 4:16 PMThanks a lot. After months of tinker around with other items, this post did the trick.
Friday, March 14, 2008 5:00 PMarmen 2003:
Did All of the above and it worked for me. Thanks.
Monday, April 14, 2008 4:41 AMCheck to see if the Office Source Engine is disabled in Control Panel/Administrative Tools/Computer Management/Services and Applications/Services.
Thursday, May 08, 2008 10:56 PMThank you Armen2003. The registry changes for Path allowed the updates to complete. I do use registry cleaner software. Maybe it was the culprit.Sunday, July 27, 2008 11:21 AMcan some one plz tell me what to do aswell? m getting sick and tired of this error..0x80070643 fatal error
Sunday, July 27, 2008 1:58 PMThe forum lists several answers. You may have to read and try a few... If nothing else works the bad news is backup, reinstall windows, reinstall office turn on Microsoft update and let the system recover. Of the several shortcuts here none worked for me. The reinstall did. Note, I had used a registry cleaner tool and I did not reinstall it in the new copy of the system. No problems so far.Saturday, August 16, 2008 1:15 AMDCKline wrote: This worked for me:
Microsoft has published Knowledge Base article 903772 to describe the issue, and suggested a few possible resolutions and solutions to the problem. Basically, the issue centered around Ose.exe which is Microsoft Office Source Engine, and the troubleshooting and resolving steps involve checking Ose.exe status or replacing the corrupted Ose.exe.
Determine the status of the Office Source Engine service by using the following steps:
Click Start, click Run, type services.msc, and then click OK.
In the list of services, double-click Office Source Engine.
View the Startup type list.
If the startup type is set to Disabled, change the startup type to Manual. To do this, click Manual in the Startup type list, and then click OK.
Try to install the Office update again.
If Automatic Updates has continously prompted you to install critical updates related to Microsoft Office 2003, this step is most likely meaningless.I just wanted you to know your fix (in bold blue for emphasis) eliminated Error Code: 0x80070643, thereby fixing a long standing failure of Microsoft security updates (while running Windows Update for my Windows XP machine) to install.
Another poster gave advice on changing the Windows Registry. Even though the following Registry entry (using Run > regedit) was obsolete:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Delivery\SourceEngine\Downloads\90000409-6000-11D3-8CFE-0150048383C9\Sources\########-####-####-####-############\Path:\\netdrive\common\apps\OFFICE11\
(reason: the path containing the original install no longer existed on the network) your above fix worked like a charm!
NOTE: I used # symbols to replace the serial number because I wasn't sure if this number is unique to each licensed user.
Thanks for helping me to get rid of Error Code: 0x80070643!
Sunday, August 17, 2008 11:43 PMI cannot believe the simplicity of the fix... just by identifying the path of the original Office Source. Now if I only could figure out who/what changed the registry in the first place.
What I find more incredable is that these simple answers for specific error codes don't simply pop up on a search of the Microsoft Knowledgebase. Maybe Microsoft should hire Oracle to help with the database management - Nah, that would make matters worse!
Saturday, September 06, 2008 8:02 AMHey Armen2003, It worked for me. Since I did used a registry cleaner recently, accidentaly I might have cleaned up some registries that I need. This has been bugging me. So, I can sleep well tonight.
Thanks for your post. Take care, SGK Wednesday, September 10, 2008 6:38 PMthank you DCKline this did the trick my updates worked straight away after trying your tip thanks again
Monday, September 15, 2008 6:40 AMJust used the Reg Edit trick and it has installed all three updates for office without a hitch
Thanks for the advice on this, I also think it was due to Ccleaner registry cleaning program
At least we know for next timeSaturday, September 27, 2008 6:19 PMIts a miracle!
It worked. All I had to do was follow your instructions. Apparently, the registry did not know where the path was to the Office CD.
Thanks again
Sunday, October 05, 2008 10:59 AMHello armen2003,
It worked! Thanks.
atlpinheiro (Portugal)
Saturday, October 18, 2008 8:51 AMThanks DCKline.... simple instructions... and they work!Friday, October 24, 2008 2:23 AMIt has been almost a year since I was able to download updates. Also, at least once every two weeks I have called the support center and they had not been able to solve the problem. So each time a new solution was posted online I try it. I was looking into buy a new computer just to get rid of this problem.
HAPPY DAYS ARE HERE AGAIN!! this worked for me.
Thank you so much!
Wednesday, August 26, 2009 5:21 PMThis fix still works. Fast and Easy, just the way I like her. Just follow the instuctions.Monday, July 12, 2010 6:14 AMI tried your Ideal writen in blue but it didn't help me one bit. I still have the same problem.
Corlis TindelFriday, May 27, 2011 2:09 AM@armen2003 You rock!!! The only MS Office components on my machine are Word & Excel Viewers. I entered the path to the MSUpdate subdirectory of my Download directory and all but two updates installed without a hitch. (I'm guessing the two that failed are only necessary for a system with the entire Office suite installed.) Thanks so much...Sunday, July 24, 2011 6:12 PMarmen2003 you are the man (I think?). I have been plagued with this problem for months. Read the post, thought, no too simple; but have tried numerous other 'fixes', so I gave it a shot.
IT WORKED!!!
Thank you!!!


Microsoft is conducting an online survey to understand your opinion of the Msdn Web site. If you choose to participate, the online survey will be presented to you when you leave the Msdn Web site.
Would you like to participate?