Archiv Windows XP 25.916 Themen, 128.567 Beiträge

Fehlermeldung: start.exe hat ein Problem festgestellt ...

MBMBMB / 18 Antworten / Flachansicht Nickles

Hallo,

ich bekomme auf meinem PC (WINXP SP2) beim ausführen einer Installationsdatei immer die Fehlermeldung:

start.exe hat ein Problem festgestellt und muss beendet werden.

Auf meinem Laptop funktioniert diese jedoch einwandfrei - woran kann das liegen?

Danke

Wie genau? MBMBMB
Wie genau? shrek3
Ergebnis: MBMBMB
Ergebnis: MBMBMB
Antwort und Ergebnis MBMBMB
MBMBMB shrek3 „Ergänzung: Ich sehe gerade, dass du zwar schreibst, dass es auf dem Laptop...“
Optionen


Auf dem Laptop ist natürlich auch WIN XP Home SP2 drauf

...werde jetzt mal Deinen >Tipp von oben mit der Software probieren und habe unten mal den doch sehr langen Text von dem Link den ich anklicken sollte mit eingefügt vielleicht siehst Du da ja was?

Danke für die nette Hilfe!

* * * * * * * * *
der Text ist viel zulange kann ich Dir den evtl. so irgend wohin schicken, bzw. bringt Dir das überhaupt etwas? Hab jetzt mal den Text gekürzt!

Adrian Grigorof (Last update 2/28/2004):
If the application is iexplore.exe and you cannot do "New window" without crashing the browser, then see M316593 (there used to be another article, M272322 but it was removed from Microsoft's support site).

This may also occur if the application is not compatible with the operating system. For example, trying to run games designed for Windows 9x/ME on Windows 2000/XP.

Mihai Andrei (Last update 10/7/2007):
- Application: Rtvscan.exe, module: Rtvscan.exe - See the link to "Symantec Knowledge Base Document ID: 2005082415100448".
- Application: grovel.exe, module: grovel.exe - See M939383 for a hotfix applicable to Microsoft Windows Server 2003.
- Application: mcupdate.exe, module: kernel32.dll - See M935685 for a hotfix applicable to Windows Vista.
- Application: devenv.exe, module: ntdll.dll - See M935842 for a hotfix applicable to Microsoft Visual Studio 2005.
- Application: WinCal.exe, module: WinCal.exe - See M933942 for a hotfix applicable to Windows Vista.
- Application: msoobe.exe, module: urlmon.dll - See M932442.
- Application: lsass.exe, module: secur32.dll - See M897648 for a hotfix applicable to Microsoft Windows Server 2003 and Microsoft Windows XP, and M870997 for a hotfix applicable to Microsoft Windows 2000 and Microsoft Windows XP.
- Application: emsmta.exe, module: kernel32.dll - See M924835 for a hotfix applicable to Microsoft Exchange Server 2003.
- Application: setup.exe, module: wizardui.dll - See M842466.
- Application: spoolsv.exe, module: unknown - From a newsgroup post: "Disabling DEP (Data Execution Protection) solved the problem". See M875352 for a detailed description of the Data Execution Prevention (DEP) feature.
- Application: mmc.exe, module: hipobjects.dll - See M930285 for a hotfix applicable to Microsoft Host Integration Server 2006.
- Application: mmc.exe, module: aclui.dll - See M870995 for a hotfix applicable to Microsoft Windows Server 2003.
- Application: fs9.exe, module: mfc70.dll - See M555608.
- Application: w3wp.exe, module: rpcrt4.dll - See M917781.
- Application: w3wp.exe, module: exprox.dll - See M329067.
- Application: w3wp.exe, module: mscorwks.dll - See M913384 for a hotfix applicable to Microsoft .NET Framework 2.0.
- Application: w3proxy.exe, module: LinkTrans.dll - See M915411 for a hotfix applicable to Microsoft Internet Security and Acceleration Server 2000.
- Application: winlogon.exe, module: rpcrt4.dll - See M914048.
- Application: winlogon.exe, module: ntdll.dll - See M914048.
- Application: outlook.exe, module: rtfhtml.dll - See M318658.
- Application: tecadwins001.exe, module: msvcrt.dll - See "IBM Support Reference #21200995" and "IBM Support Reference #IY67231".
- Application: mapsvc.exe, module: mapper.dll - See M883520 for a hotfix applicable to Microsoft Windows Services for UNIX 3.5.
- Application: svchost.exe, module: qmgr.dll - See M939159 for a hotfix applicable to Windows Vista.
- Application: svchost.exe, module: ntdll.dll - See M910666.
- Application: svchost.exe, module: iassam.dll - See M894538 for a hotfix applicable to Microsoft Windows Server 2003.
- Application: svchost.exe, module: rpcss.dll - Microsoft article M326964 describes a similar situation. Also, several newsgroup posts suggest that installing M823980 solves the problem.
- Application: svchost.exe, module: msi.dll - See M927385 and M939273.
- Application: snalink.exe, module: snaipdlc.dll - See M898555 for a hotfix applicable to Microsoft Host Integration Server 2004.
- Application: msimn.exe, module: msoe.dll - See M898807.
- Application: mngcli.exe, module: snatrc.dll - See M883850.
- Application: store.exe, module: store.exe - See M833817 for a hotfix applicable to Microsoft Exchange Server 2003, and M933398 for additional information on this event.
- Application: store.exe, module: ntdll.dll - See M911703 for a hotfix applicable to Microsoft Exchange Server 2003.
- Application: store.exe, module: exoledb.dll - See M903935 for a hotfix applicable to Microsoft Exchange Server 2003.
- Application: store.exe, module: EXWIN32.DLL - See "JSI Tip 7103".
- Application: dllhost.exe, module: DasServer.dll - See M924394.
- Application: dllhost.exe, module: scrrun.dll - See M906092 for a hotfix applicable to Microsoft Windows Server 2003.
- Application: dllhost.exe, module: ntdll.dll - See M898921.
- Application: dllhost.exe, module: sqloledb.dll - See M838976 for a hotfix applicable to Microsoft Data Access Components.
- Application: explorer.exe, module: kernel32.dll - See M898051 for a hotfix applicable to Microsoft Windows Server 2003 and M322687 for additional information.
- Application: explorer.exe, module: shlwapi.dll - See "JSI Tip 7193".
- Application: explorer.exe, module: rkadmin.dll – See M900004 for information on this event.
- Application: explorer.exe, module: ntdll.dll - See M824136 for a hotfix applicable to Microsoft Windows XP and Microsoft Windows 2000.
- Application: wmiprvse.exe - See M914831 for a hotfix applicable to Microsoft Windows Server 2003.
- Application: wmiprvse.exe, module: HMonitor.dll - From a newsgroup post: "Adjusting configuration and security for WMI namespace, solved the problem. See M325353 for information on how to do this".
- Application: wmiprvse.exe, module: svrenumapi.dll - See M938911 for a hotfix applicable to Microsoft SQL Server 2005.
- Application: wmiprvse.exe, module: Fastprox.dll - See M835438 for a hotfix applicable to Microsoft Windows Server 2003.
- Application: wmiprsve.exe, module: mngbase.dll - See M916137 for a hotfix applicable to Microsoft Host Integration Server 2000 and 2004.
- Application: wmiprvse.exe - See the link to "Wmiprvse.exe file information" for details.
- Application: inetinfo.exe, module: unknown - See M930952 for a hotfix applicable to Microsoft Windows Server 2003.
- Application: inetinfo.exe - From a newsgroup post: "I got the hotfix (M827214) the other day and applied it. It did require a reboot of the box. I have not had any problems since I applied the hotfix".
- Application: java.exe, module: symcjit.dll - From a newsgroup post: "Please change the symcjit.dll file name to another name. (make a backup for that file). Run "Services.msc" on the SBS 2003 command line. Find the Oracle_POHTTPServer service, right-click on it to change its property to manual, stop the service and then click Apply and OK to save these changes. Change the name of the symcjit.dll file back the way it was. If the problem still exists, please contact Oracle for more support".
- Application: iexplore.exe, module: mshtml.dll - See M923996.
- Application: iexplore.exe, module: browseui.dll - See "JSI Tip 7193".
- Application: iexplore.exe, module: urlmon.dll - From a newsgroup post: "The problem was found by running the "Filemon utility" (see the link below). In the Filemon log, just as a file was downloaded and IE crashed, there was another program installed that also had a file called URLMON.DLL that was registered as well in the registry. When I renamed this file, everything worked as it should".
- Application: locator.exe, module: locator.exe - From a newsgroup post: "It seems to only happen when I am using the computer and it is not connected to the domain. As soon as I connect to the network where the DC resides, the error stops popping up. Removing NAI VirusScan 8i and going back to 7.1.0 fixed this problem".
- Application: Rtvscan.exe, module: PATCH32I.DLL - From a newsgroup post: "We just got off the phone with Symantec. A definition update caused the problem. According to them, our server was set up to aggressively receive updates once every few minutes, rather than the standard schedule, so we pulled an update that was not "fully tested" yet. Right now, about 30 servers and an unknown number of clients are infected. We have to run an executable that Symantec supplied and then manually start the SAV service on each affected box. We are going to patch and fix the servers manually and throw the client fix in a logon script".

If your computer is running Microsoft Windows Services for UNIX 3.5, and all Interix applications stop responding, see M914680 for a hotfix applicable to Microsoft Windows Services for UNIX 3.5.

Tony Mac (Last update 6/4/2007):
When you run ASP.NET 2.0 on a domain controller check permissions on the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ASP.NET_2.0.50727\Names .
When ASP.NET 2.0 is installed, the local group IIS_WPG is given special permissions on this key. When the server is a domain controller the IIS_WPG group becomes a domain group (there are no local groups on domain controllers) and the NETWORK SERVICE account cannot be a member of it as it is a BUILTIN account. What you will need to do is give the NETWORK SERVICE account specific permissions to that key. Start Regedit and navigate to that key. Right-click "Names" and select “Permissions” on the context menu. Click Add and enter NETWORK SERVICE, click "Check Names" and click "Ok". With NETWORK SERVICE highlighted in the "Groups or User Names" list, click "Advanced". On the "Advanced Security Settings for Names" dialogue highlight NETWORK SERVICE and click "Edit". In the "Permission entry for Names" dialogue check that the "Name" box is showing "NETWORK SERVICE" and put check marks against "Query Value", "Set Value", "Create Subkey", "Enumerate Subkeys", "Notify" and "Read Control". Click Ok on all the dialogues and close Regedit. Ensure your application pools are reconfigured to run as NETWORK SERVICE (or at least all the ones you want to be) and restart them.
After a restart, there should be no more errors.

Damian Arn (Last update 3/14/2007):
- Application: svchost.exe, module: msi.dll - See the link to "Tech Blender Blog" for a solution to this problem.

Kurt Raymond (Last update 1/22/2007):
- Application: spoolsv.exe, module: ntdll.dll - As similarly reported by someone else, uninstalling the Lexmark T640 series software in Add/Remove Programs solves the problem.

Anonymous (Last update 1/15/2007):
We were getting the error related to shell32.dll randomly with either Dr.Watson or the Explorer. We tried as many of the steps that applied here with no luck. One thing that was unique was it only happened on our Dual Core machines. It turns out that M896256 addresses issues with multi-core processing on XP SP2 machines. So far, this appears to have resolved our issue. It looks as though this also applies to Hyper-threading machines.

David Watson (Last update 12/24/2006):
- Application: iexplore.exe, module: ntdll.dll - This problem was caused by the Google toolbar after installing IE7. After I reinstalled the Google toolbar, the problem disappeared.

Anonymous (Last update 10/10/2006):
- Application: RPCServ.exe, module: Common.dll - See "McAfee Support Document ID: KB47356".

Paula H. (Last update 8/31/2006):
- Application: iexplore.exe, module: kernel32.dll - In my case, Iexplore crashed on WinXP Pro workstation when trying to open it and this event was logged. I changed the default home page to "Use Blank" and I unchecked the "Work Offline" option from the file menu. IE is back to normal and now I can set a default home page.

Anonymous (Last update 8/19/2006):
- Application: spoolsv.exe, module: ntdll.dll - Uninstalling the Lexmark software in add/remove programs solved the problem. After this, the printers work properly, and the spool service does not stop any more.

Anonymous (Last update 8/16/2006):
- Application: explorer.exe, module: unknown - I started to get random explorer restarts when scrolling through some directories, especially C:\Windows. I seem to have fixed it by disabling the "show hidden files and folders" option.

Anonymous (Last update 6/15/2006):
- Application: wmiprvse.exe, module: provDisk.dll - This is related to Intel Server Manager 8.x running on Windows 2003 server. There is a problem with the provided provdisk.dll. An explanation and replacement can be found at "Intel Support Solution ID: CS-022396".

Ionut Marin (Last update 5/23/2006):
If the application is Exchange 2000 and you are running Windows Server 2003, then the error occurs because Exchange 2000 is not supported on Windows Server 2003. You cannot run Exchange 2000 on a Windows Server 2003-based computer. See M822884 for more information about this error.

- Application: dns.exe, module: ntdll.dll - See M837088 for a hotfix.
- Application: lsass.exe, module: authz.dll - See M818080 for a hotfix.
- Application: lsass.exe, module: schannel.dll - See M875534 for a hotfix applicable to Microsoft Windows Server 2003.
- Application: lsass.exe, module: ntdsa.dll - See M886174 for a hotfix applicable to Microsoft Windows Server 2003.
- Application: tsadmin.exe, module: unknown - See M833890 for a hotfix applicable to Microsoft Windows Server 2003.
- Application: explorer.exe, module: comctl32.dll - From a newsgroup post: "Running “sfc /scannow” fixed the problem in my case".
- Application: explorer.exe, module: msvcrt.dll - This problem might be caused by M903234. Read Citrix Support Document ID: CTX108007 for details.
- Application: frontend.exe, module: conflt.dll - See "Network Associates Support Solution ID: nai25159".
- Application: miiserver.exe, module: miiserver.exe - See M884192 and M842531.
- Application: dbbackup.exe, module: mfc42u.dll - See the link to "Veritas Support Document ID: 272708".
- Application: icw.exe, module: unknown - See M888817.
- Application: bengine.exe, module: ntdll.dll - See the link to "Veritas Support Document ID: 238706"
- Application: w3wp.exe, module: mscsups.dll - See M828868 and M838466.
- Application: STORE.EXE, module: EXWIN32.DLL - See M810591.
- Application: ntbackup.exe - See M894390.
- Application: Iexplore.exe, module: Mshtml.dll - See M899102.
- Application: IWSSHTTPMain.exe, module: CerberianIFX.dll - See the link to "Trend Micro Support Solution ID: 23801".
- Application: msiexec.exe - See "Citrix Support Document ID: CTX106713".
- Application: cshadow.exe - See "Citrix Support Document ID: CTX106559".
- Application: wfshell.exe - See "Citrix Support Document ID: CTX109233" and "Citrix Support Document ID: CTX109245".
- Application: ofcservice.exe - See "Trend Micro Solution ID: 25294" and "Trend Micro Support Solution ID: 125294".
- Application: mmc.exe, module: crxf_xls.dll - Read McAfee solution kb43078. Go to the "McAfee Knowledge Search" page and search for the specified solution.
- Application: MMC.exe, module: mcvcr71.dll - read McAfee solution kb46794.
- Application: W3WP.exe - Read McAfee solution kb46835. Go to the "McAfee Knowledge Search" page and search for the specified solution.
- Application: dllhost.exe, module: SpamRouter.dll - Read McAfee solution kb46675.
- Application: outlook.exe, module: outllib.dll - Read McAfee solution kb46395.

As per Microsoft: "The indicated program stopped unexpectedly. The message contains details on which program and module stopped. A matching event with Event ID 1001 might also appear in the event log. This matching event displays information about the specific error that occurred". See MSW2KDB for more details.

If you are running Windows XP check M823772 for more information.

This issue can occur if you use keyboard commands to load the registry hive. In this case see M817448 for more details.


- Application: outlook.exe, module: fldpub.dll - From a newsgroup post: "This dll is a Netfolder component. M229962 article is a general troubleshooter for Netfolders. Also M266732 may help. Thirdly if you are not using Netfolders you may still have the add-in installed. It can be uninstalled by going to Tools > Options > Other > Advanced Options > Add-in Manager> if it is listed just uncheck".

- Application: wmplayer.exe, module: clvsd.ax - From a newsgroup post: "I was unable to play DVDs on my PC. I have been able to play them in the past. I have recently installed Windows Media Player 9. If I tried to play a DVD in Windows Media Player 9 or other DVD software player, the programs crash, reporting a fault in module “clvsd.ax”. I finally solved this by rolling back the NVIDIA driver to an earlier version".

- Application: rundll32.exe - From a newsgroup post: "Click Start ->Run. Type sfc /scannow. Select the OK button. Follow the prompts throughout the System File Checker process. Reboot the computer when System File Checker completes".

Leo (Last update 5/9/2006):
- Application: outlook.exe - - Application: outlook.exe - I had an issue with my MS Outlook 2000, which is installed on a Windows XP Service Pack 2 machine. If I composed a message and then tried to send it or if I closed Outlook, this error appeared in my event log.
The issue appeared to be a conflict with MS Outlook 2000 and the MSN Search Toolbar. Once I removed MSN Toolbar, the problem was resolved.

Thomas Blatti (Last update 5/4/2006):
- Application: svchost.exe, module: msi.dll - Looks like the msi.dll file became somehow damaged. I reinstalled Windows Installer 3.1 Redistributable (v2) from Microsoft and the problem was fixed. This problem happened after the last update from Microsoft.

Chris (Last update 2/14/2006):
- Application: TMproxy.exe - I have experienced various event ID 1000 Application Errors. Many of them have been related to TMproxy.exe or ccProxy.exe (Trend Micro/Symantec). It seems to happen only on two of our four machines. Both are HP hyper-threading machines. I searched on HP's, Microsoft’s, and Symantec’s sites, as well as many others (this has been an ongoing issue since December 2005). It turns out there are compatibility issues related to hyper-threading machines. I am waiting for Trend Micro to get back to me regarding a patch for hyper-threading machines. So far, the only other suggestion has been to disable hyper-threading (which defeats the purpose).

Mohammed Athif Khaleel (Last update 2/7/2006):
- Application: TNSLSNR.EXE, module: orantcp.dll - Orantcp9.dll is the dll file that interfaces Oracle and the TCP layer. Oracle Listener service fails to start and the listener process crashes with a Windows OS dialogue box saying: "TNSLSNR.EXE has encountered a problem and needs to close". This might be due to some malicious software. Run a spyware checker on your system. If that does not work, reset TCP WINSOCK. See M299357 for details on how to do that.

Chris McDowell (Last update 10/8/2005):
- Application: wmiprvse.exe, module: msvcrt.dll - I received this error on my Windows 2003 Server after installing SP1 and OpenManage 4.4. I found that the SNMP service was causing the problem. I reconfigured the SNMP communities on the server and allowed an XP workstation that had IT Assistant console version 7 (Dell software product for managing multiple servers running OpenManage) installed on it, to poll the server. Rebooted the server and the error ceased to occur.

Dave Murphy (Last update 8/11/2005):
- Application: tcpsvcs.exe, module: ntdll.dll - We have been receiving this error on our Windows 2003 domain controller, which happens to be both a DHCP and RIS server for a remote office. M842608 appears to clear up the issue.

PaulD (Last update 7/22/2005):
- Application name: dllhost.exe, module: ntdll.dll - See M896989 for a hotfix applicable to Microsoft Operations Manager (MOM) 2005, when used with Microsoft Windows Server 2003 Service Pack 1.
- Application: Rtvscan.exe, module: ScsComms.dll - See the link to "Symantec Support Document ID: 2005051516504748".