Question and Answers

Eulalaucher.exe corrupt file error, can someone help me? - Ok so here's the deal guys. I have a Dell Inspiron E1525 running Windows Vista.Upon start up I'm getting these error messages: EULALauncher.exe-Configuration parser error Error parsing C:\Windows\Microsoft.NET\framework\v2.0.50727\config\machine.config Parser returned error 0x80070570 CLI.EXE-Configuration parser error Error parsing C:\Windows\Microsoft.NET\framework\v2.0.50727\config\machine.config Parser returned error 0x80070570. In the tool bar this error message comes up: EULALauncher.exe-Corrupt File The file or directory\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG is corrupt and unreadable.please run Chkdsk utlilty. CLI.exe-Corrupt File thefile or directory\Windows\Microsoft.NET\framework\v2.0.50727\CONFIG is corrupt and inreadable. please run the Chkdsk utility. so when I close these messages it then says: EULALauncher has stopped working A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available. CLIApplication(Command Line Interface) has stopped working A problem caused the program to stop working properly. windows will close the program and notify you if a solution is available. Window Media center Store Update Manager stopped working and was closed. A problem caused the program to stop working properly. Windows will notify you if a solution is available. Ok. So microft notified me that that the last error message (media center data store) was caused by the update process (Mcupdate.exe) not being able to access the windows media center data store probably because of damage to that file. Directed me to delete this file:%SYSTEMDRIVE%\ProgramData\Microsoft\eHome\mediaCenterDatastore.db It then said to run media center and all would be ok. I did this( however my file DID NOT have .db in the title) and recieved this message ehshell.exe-Configuration parser error C:\Windows\Microsoft.NET\Framework\v2.0.50727\config\machine.config Parser returned error 0x80070570 Now guys I have tried to simply restore my system to a date before all these infuriatingly irritating error messages started popping up and was not allowed to. whenever I try I get this message: System Restore The disk OS (C: ) Windows has detected file system corruption on OS ( C: ) You must check the disk for errors before it can be restored. But of course when I try to check the disk for error it informs me that it cannot check while the dsk is running at which point I schedule it to check upon startup. But when I startup it doesn't seem to check for anything only more error messages!!! I have attempted to access this file I can only get this far: C:\Windows\Microsoft.NET\framework\v2.0.50727\ It will not allow me to open the CONFIG folder because it says it is corrupt or unreadable. However when I open the properties of CONFIG it says that it is empty.0 Bytes. 0 Folders. How can these files be corrupt and noexistant? Or is it that the file were delted somehow and that's why is saying corrupt because it's looking but can't find it?

Best Answer: ruanchored, Sorry bro. But being a technician won't help much when you're dealing with raw error. Joana, the applications that you explained are none-other than the Dell-system stock software that often clashes with drivers or simply gets divided by the system upon shutdown. Both CLI Application and EULALauncher.exe are applications that need to be removed from startup. If you can, uninstall the Dell software and try to locate these applications to make sure they are all removed. Also, you can troubleshoot using: http://support.microsoft.com/kb/929135 You'll be instructed to go down a pretty good list of operation to help find the main source of your problems but it will definitely help get you back on the right path. As for what ruanchored said... NTFS is the Secure/Stable one bro... FAT32 doesn't support clusters that are 64kb or larger... it's also the most unstable and any hard drives that support 40+ gigs of space may not even calculate the correct disk space when using FAT32.... I won't even go into discussion about FAT16, sorry but I cant laugh without breathing and type... it's much too difficult. But yea -- no drive issues. Just a crappy Dell startup item that needs to be removed. Do what you can to remove those applications from startup. Going into Start->Run and typing in msconfig will also help with disabling those startup items or services. If you have any questions feel free to E-mail me at Hex@xpence.net - Hex - Hex

Hi,Joana There are 3 step to repair eulalaucher.exe error If you got eulalaucher.exe error then there is a 94% chance that your computer has registry problems. To repair eulalaucher.exe error you need to follow the steps below: * Step 1 - Download a Perfect Optimizer,install this error repair tool. * Step 2 - Click the Repair All Button.It will scan you pc for Free. * Step 3 - Then click the Repair All Button again and your done! It is very easy to repair eulalaucher.exe error. Here are the url of Perfect Optimizer:http://www.fixerrorinstantly.com/tidpp-eulalaucher.exe_error-zz0001 - Bill

Hard to diagnose long distance this way, but there are a few things I can suggest. re: System Restore. I would avoid using this. System Restore is a silly joke. It can't/doesn't restore everything properly. It can sometimes get you running again quickly, but it's likely to mess up as much as it fixes. I generally turn the stupid feature off of all my drives to avoid the extra overhead of a failed idea. And yes, especially if your file system is corrupt, you don't want to be using stuff like this, not that it will let you. "How can these files be corrupt and nonexistant?" If the file system really is corrupt - it'll tell you anything - doesn't bother telling you the truth of what it does and doesn't know. So your first priority is to get that volume checked out. I'm not sure why it's not re-checking it as scheduled to on restart. But here's the problem: NTFS is a very unstable file system. You could lose important documents of your own just by "fixing" the file system. I lost loads of data on an NTFS drive from only a very small drive error, and I've never again stored critical info on single NTFS volume. The other problem is that you don't know yet if you're having only minor file system corruption, or if the physical hard drive itself is failing. If you have information/documents/files on that computer that you value, I would suggest contacting a local paid professional instead of trying to get your answers on Yahoo. It might be a simple fix that only requires running the volume scanner (chkdsk), but until you CAREFULLY check out some other things, you're liable to lose data. If you still want to do it yourself and you have a fair idea of what you're doing, I'd say to start by checking the disk (both file and physical sectors). If the currently installed OS won't let you do it, either with restarts, command prompt safe-mode, etc., do it with a bootable disk, like an installation CD or any of many other bootable CDs designed for stuff like this. Even from within regular windows, you should be able to run a complete disk scan - you just won't be able to fix the problems. Hope this helps. - ruanchored

Report Abuse

Best Answers are selected by the person who asked the question or other Yahoo! users. Find out more at Yahoo! Answers.