MS Office 2007 Service Packs, error 57e (1406)

[bbacle]

I have installed MS Office 2007 on my Win7 Ultimate 64-bit machine. Upon installation, it gives me 1406 errors saying that it cannot write to certain registry items. I click "Ignore" and it goes on and installs anyway and seems to work OK. When I attempt to update it to any SP (1, 2 or 3), it eventually tells me that the update installation has failed.
I have a dual boot computer with WinXP Pro on another hard drive, and I have been able to install MS Office 2007 and update it to SP3 with no difficulties at all.

I have tried every solution that Microsoft and others have offered, but so far nothing has worked:
1- I have clean booted the computer.
2- I have turned off all antivirus and all antispyware programs.
3- I have uninstalled MS Office 2007 numerous times using different methods each time and reinstalled MS Office 2007.
4- I have installed it using elevated privileges.

Does anyone have a solution for this problem?
All the other updates for MS Office 2007 install fine.
It's just the Service Packs that do NOT install.

 

[NoelDP]

When uninstalling, did you run the cleanup tool?
How to uninstall or remove Microsoft Office 2007 suites

This sounds like a registry permissions issue, but please run through the http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html and post the results.
It may either fix the problem, or give us a few pointers

 

[bbacle]

When uninstalling, did you run the cleanup tool?
How to uninstall or remove Microsoft Office 2007 suites

This sounds like a registry permissions issue, but please run through the http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html and post the results.
It may either fix the problem, or give us a few pointers

I uninstalled using the appwiz.cpl method described on the link for uninstalling Office 2007.
I did NOT see a cleanup tool...is there one?

I know it sounds like a registry permissions issue, so I gave the registry full control, and I still had the problem.

 

[NoelDP]

Methods 2, 3 and 4 in the article I linked to describe the various tools (including the one of last resort - a manual cleanup!)

 

[bbacle]

Methods 2, 3 and 4 in the article I linked to describe the various tools (including the one of last resort - a manual cleanup!)

OK...I used the 4th method (manual cleanup), and I did everything step by step.
It still will NOT install any Service Packs, and I have them all downloaded to my computer.

I don't know what else to do.
It is still giving me registry errors upon installation, but I just click "Ignore" and it installs anyway and works.
I just can't get the Service Packs installed.

All of the other Office 2007 updates update fine with no problems.

 

[bbacle]

When uninstalling, did you run the cleanup tool?
How to uninstall or remove Microsoft Office 2007 suites

This sounds like a registry permissions issue, but please run through the http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html and post the results.
It may either fix the problem, or give us a few pointers

I have run through all the possible solutions and cannot find anything that will fix this problem for me.
I canNOT install the SPs of Office 2007 - they all give me the 57e or 1406 error code.
I have given my registry full control permissions, but that has not solved the problem with either the installation nor the SP updates.

As I have said I have a dual boot machine with WinXP Pro on another hard drive, and I have been able to install Office 2007 and the SP3 update on it fine without any problems.
It is with Windows 7 that I cannot install SP1, or SP2, or SP3 on Office 2007.

Please help.

 

[NoelDP]

I can do nothing until you follow instructions.

 

[bbacle]

I can do nothing until you follow instructions.

Please tell me what I am to do.
I looked at the page in your link, but it had to do with submitting a log file for updating Windows, not for Office 2007.
I never saw any instructions for what I am to do with Office 2007.
Maybe I am dumb or something, but can you direct me?

I have run through the registry permissions link, but as I have mentioned, I had already done that, and it did not help at all.

 

[Layback Bear]

Windows Update Posting Instructions

 

[bbacle]

Windows Update Posting Instructions

OK...I have download the SURT file and run it.
I have run scannow.
I have got the log file zipped up.
I have attached the log file and a picture of the failed installation...no error codes were given.

 

[bbacle]

Windows Update Posting Instructions

OK...I have download the SURT file and run it.
I have run scannow.
I have got the log file zipped up.
I have attached the log file and a picture of the failed installation...no error codes were given.

Thanks for taking the time to solve this problem.
Any word yet on the outcome?

 

[NoelDP]

Sorry - it's been a busy few days!
The only significant error I can find in the recent logs is this

2013-03-07 11:07:32, Info                  SXS    Submitting install transaction
2013-03-07 11:07:32, Info                  CSI    000000c7 Performing 1 operations; 1 are not lock/unlock and follow:
  Install (5): flags: 0 tlc: [policy.8.0.Microsoft.VC80.MFC, Version = 8.0.50727.762, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12}]"win32-policy", TypeName neutral, PublicKey neutral]) ref: ( flgs: 00000000 guid: {27dec61e-b43c-4ac8-88db-e209a8242d90} name: [l:0]"" ncdata: [l:62{31}]"C:\Windows\system32\msiexec.exe") thumbprint: [l:128{64}]"d5ecf2ab9387e082648bbcccd6eceb9d67b096939150833d0ae3066b3a1a676e"
2013-03-07 11:07:32, Info                  CSI    000000c8 Component change list: 
2013-03-07 11:07:32, Info                  CSI    000000c9 Couldn't find the hash of component: policy.8.0.Microsoft.VC80.MFC, Version = 8.0.50727.762, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12}]"win32-policy", TypeName neutral, PublicKey neutral in the catalog [l:192{96}]"\SystemRoot\WinSxS\Catalogs\d5ecf2ab9387e082648bbcccd6eceb9d67b096939150833d0ae3066b3a1a676e.cat".
2013-03-07 11:07:32, Error                 CSI    [EMAIL="000000ca@2013/3/7:16:07:32.201"]000000ca@2013/3/7:16:07:32.201[/EMAIL] (F) d:\win7sp1_gdr\base\wcp\componentstore\csd_winners.cpp(1302): Error 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] originated in function CCSDirectTransaction::AddImplicationsToCatalogsAndVerifyComponentHashes expression: (null)
[gle=0x80004005]
2013-03-07 11:07:35, Error                 CSI    000000cb (F) 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] #41874# from CCSDirectTransaction::PrepareForCommit(...)[gle=0x90092004]
2013-03-07 11:07:35, Error                 CSI    000000cc (F) 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] #41873# from CCSDirectTransaction::ExamineTransaction(...)[gle=0x90092004]
2013-03-07 11:07:35, Error                 CSI    000000cd (F) 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] #41872# from CCSDirectTransaction_IRtlTransaction::ExamineTransaction(...)[gle=0x90092004]
2013-03-07 11:07:35, Error                 CSI    000000ce (F) CRYPT_E_NOT_FOUND #41729# from Windows::COM::CPendingTransaction::IStorePendingTransaction_Analyze(...)[gle=0x80092004]
2013-03-07 11:07:35, Error                 SXS    Analyze Transaction failed with 0x80092004
2013-03-07 11:17:39, Info                  CBS    Reboot mark refs incremented to: 1
2013-03-07 11:17:39, Info                  CBS    Scavenge: Starts
2013-03-07 11:17:39, Info                  CSI    [EMAIL="000000cf@2013/3/7:16:17:39.746"]000000cf@2013/3/7:16:17:39.746[/EMAIL] CSI Transaction @0x193bac0 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id [10]"TI6.0_0:0/"

It appears to be an error in the registry regarding the Visual C++ 2005 install

It hasn't reappeared since that time, so doesn't seem to be associated with your Office problems.

I'm not familiar enough with Office updating to be able to get further into it - both your CBS and CheckSUR logs are otherwise clear.

I would suggest trying the Office Community forums for assistance....
Office - Microsoft Community
where people with immense knowledge of Office problems hang out

 

[bbacle]

Sorry - it's been a busy few days!
The only significant error I can find in the recent logs is this

2013-03-07 11:07:32, Info                  SXS    Submitting install transaction
2013-03-07 11:07:32, Info                  CSI    000000c7 Performing 1 operations; 1 are not lock/unlock and follow:
  Install (5): flags: 0 tlc: [policy.8.0.Microsoft.VC80.MFC, Version = 8.0.50727.762, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12}]"win32-policy", TypeName neutral, PublicKey neutral]) ref: ( flgs: 00000000 guid: {27dec61e-b43c-4ac8-88db-e209a8242d90} name: [l:0]"" ncdata: [l:62{31}]"C:\Windows\system32\msiexec.exe") thumbprint: [l:128{64}]"d5ecf2ab9387e082648bbcccd6eceb9d67b096939150833d0ae3066b3a1a676e"
2013-03-07 11:07:32, Info                  CSI    000000c8 Component change list: 
2013-03-07 11:07:32, Info                  CSI    000000c9 Couldn't find the hash of component: policy.8.0.Microsoft.VC80.MFC, Version = 8.0.50727.762, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12}]"win32-policy", TypeName neutral, PublicKey neutral in the catalog [l:192{96}]"\SystemRoot\WinSxS\Catalogs\d5ecf2ab9387e082648bbcccd6eceb9d67b096939150833d0ae3066b3a1a676e.cat".
2013-03-07 11:07:32, Error                 CSI    000000ca@2013/3/7:16:07:32.201 (F) d:\win7sp1_gdr\base\wcp\componentstore\csd_winners.cpp(1302): Error 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] originated in function CCSDirectTransaction::AddImplicationsToCatalogsAndVerifyComponentHashes expression: (null)
[gle=0x80004005]
2013-03-07 11:07:35, Error                 CSI    000000cb (F) 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] #41874# from CCSDirectTransaction::PrepareForCommit(...)[gle=0x90092004]
2013-03-07 11:07:35, Error                 CSI    000000cc (F) 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] #41873# from CCSDirectTransaction::ExamineTransaction(...)[gle=0x90092004]
2013-03-07 11:07:35, Error                 CSI    000000cd (F) 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] #41872# from CCSDirectTransaction_IRtlTransaction::ExamineTransaction(...)[gle=0x90092004]
2013-03-07 11:07:35, Error                 CSI    000000ce (F) CRYPT_E_NOT_FOUND #41729# from Windows::COM::CPendingTransaction::IStorePendingTransaction_Analyze(...)[gle=0x80092004]
2013-03-07 11:07:35, Error                 SXS    Analyze Transaction failed with 0x80092004
2013-03-07 11:17:39, Info                  CBS    Reboot mark refs incremented to: 1
2013-03-07 11:17:39, Info                  CBS    Scavenge: Starts
2013-03-07 11:17:39, Info                  CSI    000000cf@2013/3/7:16:17:39.746 CSI Transaction @0x193bac0 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id [10]"TI6.0_0:0/"

It appears to be an error in the registry regarding the Visual C++ 2005 install

It hasn't reappeared since that time, so doesn't seem to be associated with your Office problems.

I'm not familiar enough with Office updating to be able to get further into it - both your CBS and CheckSUR logs are otherwise clear.

I would suggest trying the Office Community forums for assistance....
Office - Microsoft Community
where people with immense knowledge of Office problems hang out

Thanks for trying...I was wondering if it had something to do with some other installation.
Maybe the Visual C++ 2005 could be the problem.
I know that on my WinXP SP3 Pro, I had no problem at all, and I am running a dual boot machine, so the specs for the machine would be exactly the same for both OS's.

 

[bbacle]

Sorry - it's been a busy few days!
The only significant error I can find in the recent logs is this

2013-03-07 11:07:32, Info                  SXS    Submitting install transaction
2013-03-07 11:07:32, Info                  CSI    000000c7 Performing 1 operations; 1 are not lock/unlock and follow:
  Install (5): flags: 0 tlc: [policy.8.0.Microsoft.VC80.MFC, Version = 8.0.50727.762, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12}]"win32-policy", TypeName neutral, PublicKey neutral]) ref: ( flgs: 00000000 guid: {27dec61e-b43c-4ac8-88db-e209a8242d90} name: [l:0]"" ncdata: [l:62{31}]"C:\Windows\system32\msiexec.exe") thumbprint: [l:128{64}]"d5ecf2ab9387e082648bbcccd6eceb9d67b096939150833d0ae3066b3a1a676e"
2013-03-07 11:07:32, Info                  CSI    000000c8 Component change list: 
2013-03-07 11:07:32, Info                  CSI    000000c9 Couldn't find the hash of component: policy.8.0.Microsoft.VC80.MFC, Version = 8.0.50727.762, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12}]"win32-policy", TypeName neutral, PublicKey neutral in the catalog [l:192{96}]"\SystemRoot\WinSxS\Catalogs\d5ecf2ab9387e082648bbcccd6eceb9d67b096939150833d0ae3066b3a1a676e.cat".
2013-03-07 11:07:32, Error                 CSI    000000ca@2013/3/7:16:07:32.201 (F) d:\win7sp1_gdr\base\wcp\componentstore\csd_winners.cpp(1302): Error 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] originated in function CCSDirectTransaction::AddImplicationsToCatalogsAndVerifyComponentHashes expression: (null)
[gle=0x80004005]
2013-03-07 11:07:35, Error                 CSI    000000cb (F) 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] #41874# from CCSDirectTransaction::PrepareForCommit(...)[gle=0x90092004]
2013-03-07 11:07:35, Error                 CSI    000000cc (F) 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] #41873# from CCSDirectTransaction::ExamineTransaction(...)[gle=0x90092004]
2013-03-07 11:07:35, Error                 CSI    000000cd (F) 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] #41872# from CCSDirectTransaction_IRtlTransaction::ExamineTransaction(...)[gle=0x90092004]
2013-03-07 11:07:35, Error                 CSI    000000ce (F) CRYPT_E_NOT_FOUND #41729# from Windows::COM::CPendingTransaction::IStorePendingTransaction_Analyze(...)[gle=0x80092004]
2013-03-07 11:07:35, Error                 SXS    Analyze Transaction failed with 0x80092004
2013-03-07 11:17:39, Info                  CBS    Reboot mark refs incremented to: 1
2013-03-07 11:17:39, Info                  CBS    Scavenge: Starts
2013-03-07 11:17:39, Info                  CSI    000000cf@2013/3/7:16:17:39.746 CSI Transaction @0x193bac0 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id [10]"TI6.0_0:0/"

It appears to be an error in the registry regarding the Visual C++ 2005 install

It hasn't reappeared since that time, so doesn't seem to be associated with your Office problems.

I'm not familiar enough with Office updating to be able to get further into it - both your CBS and CheckSUR logs are otherwise clear.

I would suggest trying the Office Community forums for assistance....
Office - Microsoft Community
where people with immense knowledge of Office problems hang out

Thanks for trying...I was wondering if it had something to do with some other installation.
Maybe the Visual C++ 2005 could be the problem.
I know that on my WinXP SP3 Pro, I had no problem at all, and I am running a dual boot machine, so the specs for the machine would be exactly the same for both OS's.

Thanks again for trying. I went to the link you gave me to try their solutions - no joy.
Seems like a lot of people (and I mean a lot) are having the same issues and still Microsoft does NOT have a viable solution.
Did you know this has been happening since Office 2000???
And Microsoft still has not fixed the problem.
I'm beginning to think it is NOT going to be fixed either.

 

[NoelDP]

I've had installs of every Office version from OXP to Office 2013 on Win7 with no problems at all, so it has to be a peculiarity of the affected machines - and possibly not the same cause for all of them!
If I install it on a new machine, it typically goes in as soon as I have the AV up and running (which happens after I've updated) - so I may just be getting it in before the system is modified sufficiently to breakthe installer.
Have you EVER run the AVG registry 'cleaner', or any other such trash? DON'T!! If you have, try undoing anything it's done, (and uninstalling it) and then running the Office install again.

 

[bbacle]

I've had installs of every Office version from OXP to Office 2013 on Win7 with no problems at all, so it has to be a peculiarity of the affected machines - and possibly not the same cause for all of them!
If I install it on a new machine, it typically goes in as soon as I have the AV up and running (which happens after I've updated) - so I may just be getting it in before the system is modified sufficiently to breakthe installer.
Have you EVER run the AVG registry 'cleaner', or any other such trash? DON'T!! If you have, try undoing anything it's done, (and uninstalling it) and then running the Office install again.

No...I have NEVER run the AVG registry cleaner, but I have run the Advanced System Care registry cleaner numerous times. Maybe it has caused some problems...I couldn't undo it as I have run it so many times since I have had the machine.
Maybe I need to reinstall Win7 fresh and start over...that would take a long time since I have so many programs installed, but it might just work.

 

[NoelDP]

ASC is known to cause multiple problems - I suggest that you try resetting everything it's 'optimised' back to default, and then uninstall it.
A repair install is a much quicker option.



Download the SP1 Refresh for your language and edition from the links on these pages...

Heidoc - Microsoft DR Download links

The links are for downloads from the Digital River servers run for MS, so are about as safe as you can get

Once you have it downloaded, you then need to burn the DVD from it - use either the Windows Disk Image Burner, or (better still) your favourite burning application at the slowest speed possible.

Note that you do NOT 'drag and drop' the file to the disk, you must use the 'burn an image' option from your app - or you'll end up with a useless coaster

Once you have the disk burnt, check that it boots the (or any other) system OK - but do NOT start the repair from there - you must start the repair from within a normal Windows boot.

Follow the instructions in this tutorial - http://www.sevenforums.com/tutorials/3413-repair-install.html
- and they should help you get through it (it's not as difficult as it looks!)

Always ask questions first if you're unsure

Good luck with it!

 

[bbacle]

ASC is known to cause multiple problems - I suggest that you try resetting everything it's 'optimised' back to default, and then uninstall it.
A repair install is a much quicker option.



Download the SP1 Refresh for your language and edition from the links on these pages...

Heidoc - Microsoft DR Download links

The links are for downloads from the Digital River servers run for MS, so are about as safe as you can get

Once you have it downloaded, you then need to burn the DVD from it - use either the Windows Disk Image Burner, or (better still) your favourite burning application at the slowest speed possible.

Note that you do NOT 'drag and drop' the file to the disk, you must use the 'burn an image' option from your app - or you'll end up with a useless coaster

Once you have the disk burnt, check that it boots the (or any other) system OK - but do NOT start the repair from there - you must start the repair from within a normal Windows boot.

Follow the instructions in this tutorial - http://www.sevenforums.com/tutorials/3413-repair-install.html
- and they should help you get through it (it's not as difficult as it looks!)

Always ask questions first if you're unsure

Good luck with it!

WOW!!! After reading about this, it seems a bit extreme.
A lot of things will no longer work and you have to update your drivers.
I would be very hesitant using this technique, as it sounds like it could wreck some programs and other things on my computer.
I think I will just stay with Office 2007 the way it is until such time as I want to reinstall Windows 7 fresh and then I will install Office fresh on it.
I may even think about upgrading to Office 2010 or Office 2013 and maybe they will work correctly.

Thanks for the info though, and I do appreciate your taking the time to help me.

 

[NoelDP]

A repair install actually breaks very little - much less than in previous incarnations. It does force you to do some housekeeping, though - which you should be doing anyhow.

 

[torchwood]

registry changes

Trouble is TOO MANY people run the registry cleaner option without reading instructions.
Bbacle there is a rescue function built-in for this purpose, try that.

Roy