|
Reply
Re: VMware Server Console error: Application failure. hr = 0x80004003: (nul Jul 11, 2007 6:56 AM
Reply
30.
Re: VMware Server Console error: Application failure. hr = 0x80004003: (nul Jul 11, 2007 6:56 AM
You have got to be kidding me...
After many years of being a faithful user many are teling me that the fix is actually a registry hack posted by a user??? --no offense wislam but we should not have to muck up the registry due to poor coding. This is plain unacceptable from any company...let alone one owned by EMC. How did this issue ever pass QA? This frustration makes me almost want to consider a different product. KevinG, I think the community deserves a proper response. When will the patch or fix be released by VMware to resolve this issue? I am having the same issue with VMware Workstation 6 on Vista x64 -J |
|
Reply
Re: VMware Server Console error: Application failure. hr = 0x80004003: (nul Jul 11, 2007 8:14 PM
Reply
31.
Re: VMware Server Console error: Application failure. hr = 0x80004003: (nul Jul 11, 2007 8:14 PM
Add me to the list...
I get the same Application failure. hr = 0x80004003: (null) error. AMD (could that be the issue?) X2 3800+, 2GB RAM, 500GB HDD. Running Vista Business w/all patches. VMWare WS 6.0.0.45731. Tried running as Admin. Tried setting NTFS permissions on \VMWare to Everyone|Full Control. Tried the v6 registry hack. Same error every time. |
|
Reply
Re: VMware Server Console error: Application failure. hr = 0x80004003: (null) Jul 25, 2007 8:48 PM
|
|
Reply
Re: VMware Server Console error: Application failure. hr = 0x80004003: (null) Dec 6, 2007 12:23 PM
Reply
33.
Re: VMware Server Console error: Application failure. hr = 0x80004003: (null) Dec 6, 2007 12:23 PM
I had the same problem with VMWare Server 1.4 when running the Console. After reading through various posts came to the conclusion that i my case it was likely to be registry perms that were causing the problems. Using SysInternals (now Micro$oft) RegMon I could see ACCESS DENIED on a number of HKCR\vmappsdk* entries. Giving read access to the appropriate user account on each of these entries and any child entries cleared up these errors and allowed the console to run. The SysInternals tools are free and fantastic for tracking down the causes of problems like this: SysInternals Tools |
|
Hello / Bonjour, After searching for hours how to resolve the problem for myself, I succeeded ! I used the reg_fix.bat posted somewhere here on VmWare Communities, which I had to modify because I'm French, in order to avoid the error message "Structure d'ID de sécurité non valide" . All details are explained in a text file (in English and French) compressed in the RAR file archive following this link : http://rapidshare.com/files/86005455/vmware_6.0_0x80004003_reg_fix.rar.html In this archive, you will find the reg_fix.bat for both French and English users, for VmWare Workstation (also works with ACE) ver. 6.0 and 6.0.2, and another helpful tool. Just read the HOW_TO... I hope I was clear enough to help you with the explanations I wrote in this text file. Good luck ! |
|
Hi, I have tried the fix but it doesn't work! I have an administrator account but I apparently don't have the appropriate rights. Is there a fix for this. I have searched the forum but haven't found a solution to the problem. See the screenshot for what I get when I run the fix.
Attachments:
|
|
I have Windows vista home premium and Vmware 6.0.1 workstation I had the error hr = 0x80004003 and i solve this problem using vmware_0x80004003_reg_fix.zip. (attached in this post) you have to start the pc in safe mode and i run it, when it fihish start vmware. it worked for me and right now i'm instaling xp in a virtual machine
Attachments:
|
|
Reply
Re: VMware Server Console error: Application failure. hr = 0x80004003: (nul Oct 12, 2008 7:13 PM
Reply
44.
Re: VMware Server Console error: Application failure. hr = 0x80004003: (nul Oct 12, 2008 7:13 PM
After the same issue on XP professional I found that I did not have a FQDN and after adding mshome.net to my server name everything worked fine. Oh, I also ran the updated configuraiton script I hope this helps someone. |