Solved

Installer Service Broken after Fatal Error C0000034

Posted on 2011-03-11
13
1,258 Views
Last Modified: 2012-06-21
Windows 7 SP 1 appears to have failed on two of my 64-bit workstations with Fatal Error C0000034.  Fortunately I found a very detailed report over at Microsoft Forums that matched my scenario.  The solution is a manual system restore.  In short it tells us to revert to default files in Windows\System32\config.
http://answers.microsoft.com/en-us/windows/forum/windows_7-system/fatal-error-c0000034-on-boot-after-service-pack-1/5f7127e8-9887-4f01-aaa5-9729b69544b7

You may recognize this as a Vista manual system restore:
http://social.technet.microsoft.com/Forums/en-US/itprovistasp/thread/4491fe25-be44-430e-a384-fb58c5da5ad0/#862434ba-a802-474e-8c54-83ad9721effa

I was finally able boot Windows 7, but now the Windows Installer 5.0 is broken.  "The Windows Installer Service could not be accessed.  This can occur if the Windows Installer is not correctly installed.  Contact your support personnel for assistance."  This is true with any MSI file including Windows Updates.

I looked for a redistributable of Installer 5.0 with no luck.
 
In Windows Update history Win 7 SP 1 (KB976932) appears as installed, but when I check for updates it's still on-deck.  This is a problem.  I tried to reinstall it but the job hangs.

I downloaded the SP 1 iso file from the Microsoft Download Center; the package knows instantly that Windows Installer is broken.

I tried some Windows XP fixes.  Does these still apply to Windows 7?

msiexec /regserver
ren msihnd.dll msihnd.old
Source:  http://support.microsoft.com/kb/324516

I have no permissions to access msi.dll.  I didn't have time to play with ownership before I got called to look at something else.

I hope that Microsoft is playing catch-up on this one.  I'd really appreciate some advice.  Thanks.

0
Comment
Question by:kengreg
13 Comments
 
LVL 9

Expert Comment

by:Timothy McCartney
Comment Utility
Do you have any restore points available?
0
 
LVL 30

Expert Comment

by:IanTh
Comment Utility
I tried some Windows XP fixes.  Does these still apply to Windows 7?


absolutely not
0
 
LVL 9

Expert Comment

by:Timothy McCartney
Comment Utility
Have you checked the Windows Installer service to see if it's running?

Start > Run > Type "Services.msc" and click OK > Browse to Windows Installer service and verify it's running
0
 
LVL 9

Expert Comment

by:Timothy McCartney
Comment Utility
If there are no restore points available, you could try either of the two following:

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html - Run System File Checker

http://www.sevenforums.com/tutorials/3413-repair-install.html - Repair Windows 7 Installation **This one should definitely correct your issue**
0
 

Author Comment

by:kengreg
Comment Utility
Unfortunately, no, there were no system restore points on these two workstations prior to the fatal error.  The owners and end users had a laundry list of requests during deployment and not much interest in other things.

Yes, the Windows Installer is running.  It will run as automatic or manual.  I left it on automatic.  I stopped and started a couple of times.  I restarted the machine a couple of times.  I checked for dependences like RPC.
0
 

Author Comment

by:kengreg
Comment Utility
Yes, the repair install looks about right.  I won't have access to this location for a couple of weeks.
0
Better Security Awareness With Threat Intelligence

See how one of the leading financial services organizations uses Recorded Future as part of a holistic threat intelligence program to promote security awareness and proactively and efficiently identify threats.

 
LVL 47

Expert Comment

by:dstewartjr
Comment Utility
Have you come across ?

http://blogs.webguild.com/gary/archive/2011/02/23/fatal-error-c0000034-installing-windows-7-sp1.aspx


Or

Your computer may freeze or restart to a black screen that has a "0xc0000034" error message after you install Windows 7 Service Pack 1 or a Windows Vista service pack

http://support.microsoft.com/kb/975484/en-us
0
 

Author Comment

by:kengreg
Comment Utility
Rant...

This site is generally helpful but seriously; some guy spends thirty seconds in a search engine and pastes a link, then I'm supposed to feel pressured to award points.  That's not exactly how I operate.  I reward hard work and experience.  Isn't that my role as the questioner.  This site has prompted me to close this question many times and I won't budge.  Abandoned?

This is not an abandoned question.  This business is simply operating two compromised PCs indefinitely.  The PCs are still being used to generate business.  If the PCs truly go down they will call me in.

Welcome to the business world.  It's not a technical panacea.

There are similar machines on the premises that did not experience the problem.  We will deliberately and manually install SP 1 on one such machine to see if it works.  That will happen when business is slow.  The business will not consider the schedule of Experts Exchange.

Thanks for your understanding.
0
 

Author Comment

by:kengreg
Comment Utility
Points will go to the next expert who tells me to call Microsoft at on of the following numbers:

866 PC SAFETY
800 642 7676
800 936 5700
0
 

Accepted Solution

by:
kengreg earned 0 total points
Comment Utility
I called MIcrosoft to open a case
866 PC SAFETY
800 642 7676
800 936 5700

Then I corresponded with a support representative over email.  I was asked to stop, reset, and restart Windows Update.  

The update issue can occur if one of the following factors is true:

1. Corrupted Windows Update temporary folder.
2. A Windows Update component is not working.
3. A system file is not working.

We can refer to the following steps to test our issue.

Suggestion 1: Rename the Windows Update temporary folders:
====================================
1. Click "Start", in "Start Search" item, type: "notepad" (without quotes) and press Enter.
2. Copy the following commands and then paste them into the opened Notepad window:

net stop wuauserv
net stop CryptSvc
ren %windir%\system32\catroot2 catroot2.old
ren %windir%\SoftwareDistribution sold.old
net start CryptSvc
net start wuauserv
pause
3. After pasting the above commands, please close the Notepad window. Choose "Save" when you are prompted to save the file. Type "rename.bat" as the file name and save it to the Desktop.
4. Return to the Desktop, right click the rename.bat file and choose "Run as administrator".
5. You will see a DOS-like window processing.

Now try Windows Update to see if the issue has been resolved.The update issue can occur if one of the following factors is true:

1. Corrupted Windows Update temporary folder.
2. A Windows Update component is not working.
3. A system file is not working.

We can refer to the following steps to test our issue.

Suggestion 1: Rename the Windows Update temporary folders:
====================================
1. Click "Start", in "Start Search" item, type: "notepad" (without quotes) and press Enter.
2. Copy the following commands and then paste them into the opened Notepad window:

net stop wuauserv
net stop CryptSvc
ren %windir%\system32\catroot2 catroot2.old
ren %windir%\SoftwareDistribution sold.old
net start CryptSvc
net start wuauserv
pause
3. After pasting the above commands, please close the Notepad window. Choose "Save" when you are prompted to save the file. Type "rename.bat" as the file name and save it to the Desktop.
4. Return to the Desktop, right click the rename.bat file and choose "Run as administrator".
5. You will see a DOS-like window processing.
Now try Windows Update to see if the issue has been resolved.

That did not help with the actually Windows Installer problem, so I was asked to reregister the ms installer service:

1. Restart the computer. Keep pressing the F8 key until the Windows Startup menu appears.
2. Choose Safe Mode, and press Enter.
3. Click Start, click "All programs", and click "Accessories".
4. Right-click "Command Prompt", and click "Run as administrator".
5. In the black command line window, type in the following command and press Enter:
MSIexec  /unregister

This did not help so the two machines were set aside.  We will reinstall Windows 7 at a later date.

Thanks
0
 

Author Comment

by:kengreg
Comment Utility
I'd rather document what happened than abandon it.
0
 

Author Closing Comment

by:kengreg
Comment Utility
This entire thread has good information.
0

Featured Post

Enabling OSINT in Activity Based Intelligence

Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

Join & Write a Comment

So many times I have seen the words written in a question "if only I could show you" or " I know how hard it is for you since you can't see it" in any zone. That has inspired me to write about this tool in windows 7 called "Problem Steps Recorder…
Possible fixes for Windows 7 and Windows Server 2008 updating problem. Solutions mentioned are from Microsoft themselves. I started a case with them from our Microsoft Silver Partner option to open a case and get direct support from Microsoft. If s…
In this Micro Tutorial viewers will learn how to use Boot Corrector from Paragon Rescue Kit Free to identify and fix the boot problems of Windows 7/8/2012R2 etc. As an example is used Windows 2012R2 which lost its active partition flag (often happen…
This Micro Tutorial will teach you how to the overview of Microsoft Security Essentials. This is a free anti-virus software that guards your PC against viruses, spyware, worms, and other malicious software. This will be demonstrated using Windows…

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now