Running Windows XP. The message 'exception unknown software exception 0xc000000d occurred in the application 0x00b849ad'showed up when I tried to use 'manage custom places' in CoPilot Live Laptop 10, a GPS program, by Alk Technologies. They are of no help since this is not their current program. How can I fix this?

• The exception unknown software exception (0xc000000d) occurred in the application at location 0x7813941a. Check the link below for more information.
• Very recently I will get a box showing up stating 'The exception unknown software exception (0xc06d007e) occurred in the application at location 0x7c812aeb' and I'm supposed to click OK or cancel.
• I just bought a new laptop yesterday with windows 10. Upon startup, before even logging in I get the following message: The exception unknown software exception (0xc06d007e) occurred in the application at location 0x0408B2.

I've built a .NET Windows Forms application in Visual Studio 2010. I also built a corresponding setup/install package via Visual Studio 2010. This is built as a 32-bit (x86) application. (We make use of third-party Windows Forms controls that are 32-bit only).

I am able to run the setup package and deploy successfully to other Windows 7 64-bit environments and 32 bit Windows XP boxes. The installed application runs fine on these.

Fix: Unknown Software Exception 0xe06d7363 Method 1: Running the app in Compatibility mode as Admin. Method 2: Installing the missing C redistributable packages. Method 3: Adding application folder to the exclusion list in AV. Method 4: Using Windows Repair (All in One) If the methods above. Microsoft Windows and software use exceptions, which allow Windows or other software to communicate in layers and communicate errors or exceptions. If a program is given an exception that is invalid or unknown, you'll encounter a fatal exception. Fatal exceptions are also commonly referred to as a Fatal 0E, or improperly as a Fatal OE.

However, when I attempt to run Windows Server 2008 R2 - 64 bit, the application crashes at startup. It installed successfully via the installer without any errors.

It appears to crash when loading the application. I put a message box as the first line in the application to see if it got past loading. The message box doesn't show up, so I assume that it occurs during loading/init of the application.

So far I haven't found much to go on. From the Details I see the following:

I've fished around/googled to see if there was anything obvious, but I saw nothing. I saw some references to a possible stack overflow in the CLR.

The Windows Forms application is built with the following references:

• DevExpress
• Infragistics Winforms controls
• ORACLE DataAccess DLL
• RabbitMQ

What is the issue?How do I approach figuring this out?How do I debug to get more useful information?

Peter MortensenJohnBJohnB

11 Answers

0xE0434352 is the exception code for all .NET exceptions so that won't tell you much. How did you got this exception code? The event log?

Your best bet is to use a debugger to get more information. If the Visual Studio debugger won't help you, then you might need to check out WinDbg with SOS. See here and here for an introduction. Let it break on the exception, and see if you can get more information on the why.

If you suspect it is an issue when loading assemblies you might want to check out the Fusion Log.

Peter Mortensen

How To Fix The Exception Unknown Software Exception 0xc06d007e

Lars TruijensLars Truijens

If you are getting that error from Event Viewer, you should see another error event (at least one) from the Source '.NET Runtime'. Look at that error message as it will contain the Exception info.

TergiverTergiver

It looks like this error 0xe0434352 applies to a number of different errors.

In case it helps anyone, I ran into this error when I was trying to install my application on a new Windows 10 installation. It worked on other machines, and looked like the app momentarily would start before dying. After much trial and error the problem turned out to be that the app required DirectX9. Though a later version of DirectX was present it had to have version 9. Hope that saves someone some frustration.

I was fighting with this a whole day asking my users to run debug versions of the software. Because it looked like it didn't run the first line. Just a crash without information.

Then I realized that the error was inside the form's InitializeComponent.

The way to get an exception was to remove this line (or comment it out):

Once you get rid of the line, you'll get a normal exception.

Peter Mortensen

I'm not sure if this will help anyone or not, but since it was my problem, I figure it's worth mentioning:

I was getting this error, and it turned out to be a problem with the platform for which the EXE was built. We had it building for x86, and it needed to be x64, because of an Oracle reference in the project. When we made that change, the problem went away. So, see if you have any similar conflicts.

I was getting this when the app deployed. In my case, I chose 'This is a full trust application' on the project security tab, and that fixed it.

Peter Mortensen

To fix the issue for me (as a number of applications started to throw this exception all of a sudden, for example, CorelDraw X6 being one), I uninstalled the .NET 4.5 runtime and installed the .NET 4 runtime. The two versions cannot be installed side by side, but they use the same version numbers in the GAC. This causes issues as some of the functions have been depreciated in 4.5.

DLL Hell has returned...

Peter Mortensen

So.. I had noticed in event viewer that this crash corresponded to a 'System.IO.FileNotFoundException' error.

So I fired ProcMon and noticed that one of the program dlls was failing to load vcruntime140. So I simply installed vs15 redist and it worked.

We got this error when the connection string to our database was incorrect. The key to figuring this out was running the dotnet blah.dll which provided a stacktrace showing us that the sql server instance specified could not be found. Hope this helps someone.

Jesse de Bruijne

How To Fix Exception Unknown Software 0x40000015

Issue:

.Net application code aborts before it starts its execution [Console application or Windows application]

Error received: Aborted with Error code 'E0434352'

Exception: Unknown exception

Scenario 1:

When an application is already executed, which have used some of the dependent resources and those resources are still in use with the application executed, when another application or the same exe is triggered from some other source then one of the app throws the error

Scenario 2:

When an application is triggered by scheduler or automatic jobs, it may be in execution state at background, meanwhile when you try to trigger the same application again, the error may be triggered.

Solution:

Create an application, when & where the application release all its resources as soon as completedKill all the background process once the application is closedCheck and avoid executing the application from multiple sources like Batch Process, Task Scheduler and external tools at same time.Check for the Application and resource dependencies and clean up the code if needed.

BHUVANESH MOHANKUMARBHUVANESH MOHANKUMAR

I know this is a somewhat old thread, but I had this problem too with a c#/WPF app I was creating. The app worked fine on the development machine, but would not start on the test machine. The Application Log in the Event Viewer gave a somewhat nebulous .NET Runtime error of System.IO.DirectoryNotFoundException.

I tried using some debugging software but the app would not stay running long enough to attach the debugger to the process. After banging my head against my desk for a day and looking at many web pages like this one, what I wound up doing to troubleshoot this was to install VS2019 on my test machine. I then dragged the .exe file from its folder (it was deep in the Users[user]AppDataApps2.0... folder) to the open VS2019 instance and went to start it from there. Immediately, it came up with a dialog box giving the exception and the cause.

In my case, when I added an icon to one of the forms, the complete path to the icon was placed into the XAML instead of just the icon name. I had copied the icon file into the project folder, but since the project folder does not exist on the test machine, this was the root cause of the error. I then removed the path from the XAML, leaving just the icon name one, rebuilt the solution and re-published it, and it ran just fine on the test machine now. Of course there are many causes besides what gave me the error, but this method of troubleshooting should hopefully identify the root cause of the error, since the Windows Event Viewer gives a somewhat vague answer.

To summarize, use Visual Studio on the test machine as a debugger of sorts. But, to get it to work right, I had to drag the .exe file into the IDE and Start (run) it from there. I believe this will also work with VS2017 as well as VS2019. Hopefully this helps someone who is still having this issue.

Not the answer you're looking for? Browse other questions tagged c#.netwinformsvisual-studio-2010 or ask your own question.

0xC06D007E Error is a problem that involves the Citrix Multi-monitor configuration settings and reference. The error notification typically appears on your screen when you try to use programs that access the Citrix Multi-monitor registry settings and are having problems reading the settings. The error messages usually appear after you have performed software updates that leave registry values for the old program. You need to resolve the error to do away with the annoying error messages. This tutorial will enable you to fix the 0xC06D007E errors in your PC easily.

What Causes The 0xC06D007E Error?

The Windows error with 0xC06D007E code is primarily caused by incorrect set of settings for the program that you are trying to use. Most of the time, a software update leads to the error message appearing on your screen. The problem can also be caused by serious problems inside the registry. You need to identify the source of the problem to be able to fix the error – which can be done using the steps outlined below:

How To Fix Error 0xC06D007E

How To Fix Exception Unknown Software 0xc0000409

Step 1 – Re-Install The Software Causing The Errors

The first thing that you need to do to fix the error is re-install the program that leads to the errors. Remove the program first before you can re-install the program which you can do by doing this:

Click Start> Run and type “appwiz.cpl” and then press “Enter.”

Select the program from the list and then click the “Remove” (for XP) or “Uninstall” (for Vista and Win7) button.

It is important that you restart your computer after completing the removal process. Once you are logged back in to Windows, ensure that all parts of the program have been completely removed by locating the directory in which it was installed and delete folders and files that you find. To re-install the program, insert the CD/DVD installer onto your optical drive or run the file installer from your hard drive.

Step 2 – Set Up Another “DWORD Setting” for The Broken Software

To be able to resolve issues with the troublesome software, you can manually provide another “DWORD” setting by entering the registry. Here’s how you can do this:

Click Start> Run and type “regedit” in the box that appears, and then click OK or press ENTER.

Inside the left pane of the registry, navigate to “HKEY_LOCAL_MACHINESOFTWARECitrixCtxHook

AppInit_DllsMultiple Monitor Hook.”

Right-click in the open space in the right pane and click New> Dword Value.

For the name of the Dword value you have just added, put the executable name of the broken software. For example, if the program you are trying to fix is Dreamweaver, give the Dword value a “dreamweaver.exe” name.

Enter a value of “0” for the Dword and close the registry.

Restart your PC for the changes to take effect.

Exception Unknown Software Application Error

Step 3 – Clean Out The Registry

The Exception Unknown Software 0xc06d007e

The “registry” is part of Windows that contains the settings and options for all files and programs. It is a vital Windows component that is needed for your system to run smoothly. However, it is also a big source of errors including the 0xC06D007E errors and other critical problems that can slow down your system and produce error notifications. The errors inside the registry are caused by damaged registry keys and must be repaired. You can clean out errors inside the registry by using a “registry cleaner” that can effectively scan your system and repair detected errors.

We highly recommend that you use this tool which works by efficiently removing 99% of system errors and stopping viruses from infecting your system enabling your computer to run fast again and without errors.

Exception Unknown Software Exception