The “An unhandled win32 exception occurred in *application_name*‘ error typically occurs when the user tries to launch an application that was built in Visual Studio. Most reported instances of this error are associated with Uplay, Internet Explorer and several Legacy games initially built for older Windows versions.
Note: Here’s how to fix a Runtime Library related to Visual C++.
What Causes the “Unhandled Exception has Occurred in your Application” Error on Windows?
There are several simple causes of this problem and the problem can be effectively tackled if you are able to recognize your scenario simply based on identifying the correct cause. Check out the list below:
- Your antivirus may be the culprit – Some antivirus tools such as Panda Antivirus are known to have caused this issue so make sure you replace them.
- Certain programs or malware may be running – If an installed program or malware is running on your computer, you might want to get rid of it. Make sure you boot into clean boot to see if that is the correct cause.
- Microsoft .NET Framework installation is corrupt – If its core files are corrupt, you can either try repairing its installation, installing a newer version, or performing an SFC scan.
- Script debugging is enabled via Registry – As it turns out, a particular registry key can contribute to the apparition of this issue. To take care of it, you’ll need to disable Script Debugging Via Registry Keys.
- Access violation in Msvcr92.dll – An exceeding source buffer or an improper final byte are also potential causes of this issue. To address them, you will need to install every pending Windows update.
- Deleting the Ubisoft launcher registry key – If you see this error while trying to launch Uplay.exe, it’s due to a bug with the Ubisoft Game Launcher. This issue can also be resolved via registry by deleting the value belonging to this launcher.
- System file corruption – A system file inconsistency can also create this issue. Light corruption can be resolved by simple DISM and SFC scans. In more severe circumstances, a clean install or repair install should help you in resolving the issue.
Solution 1: Install every pending Windows Update
One of the most common causes that will end up causing the “An unhandled win32 exception occurred‘ error is an application that was built for the x64 platform using the MSVCR90.DLL that ends up calling the strncpy function.
In this case, an access violation triggered in Msvcr92.DLL file will most likely cause the application to stop responding in the strncpy function. An exceeding source buffer or an improper final byte are the most likely causes of this issue.
Fortunately, Microsoft is already aware of this issue and has released a hotfix for this issue that will automatically resolve it. To take advantage of it, all you need to do is update your OS version to the latest version available.
Note: This hotfix was pushed within a revision of Visual Studio 2008, which Windows automatically updates, so the steps below are universal and should work regardless of your OS version.
Here’s a quick guide on updating your Windows build to the latest version in order to install the hotfix for Visual Studio 2008 and resolve the issue:
- Press Windows key + R to open up a Run dialog box. Next, type ‘ms-settings:windowsupdate’ and press Enter to open up the Windows update tab of the Settings app.
Note: In case you encounter this issue on Windows 7 or Windows 8.1. use the ‘wuapp’ command instead.
- After you manage to arrive inside the Windows Update screen, start by clicking on Check for updates. Then, start following the on-screen prompts to complete the installation of every Windows Update that is currently waiting to be installed.
Note: Keep in mind that it’s crucial that you install every update, not just the critical ones. Since the hotfix is included in a revision of Visual Studio, you might find the update in question under Optional, so make sure to install all of them.
- In the event that you’re prompted to restart before you get the chance to install every available update, do so. But make sure to return to this same screen after the next startup is complete in order to complete the installation of the rest of the updates.
- Once every pending update is installed, restart your computer one final time and then repeat the action that was previously causing the error message to see if the problem is fixed.
In case you’re still encountering the “An unhandled win32 exception occurred‘ error, move down to the next method below.
Solution 2: Replace Your Antivirus
Free antivirus tools can be quite helpful and they can do their job protecting your computer but sometimes they just don’t get along well with other things on your computer. Consider replacing your antivirus if it causes this problem while it’s turned on!
- Click on the Start menu and open Control Panel by searching for it. Alternatively, you can click on the gear icon in order to open settings if you are using Windows 10.
- In Control Panel, select to View as – Category at the top right corner and click on Uninstall a Program under the Programs section.
- If you are using the Settings app, clicking on Apps should immediately open a list of all installed programs on your PC.
- Locate your antivirus tool in Control Panel or Settings and click on Uninstall.
- Its uninstall wizard should open so follow the instructions to uninstall it.
- Click Finish when the uninstaller completes the process and restart your computer to see whether errors will still appear. Make sure you choose a better antivirus option.
Solution 3: Deleting the Launcher Registry value (if applicable)
If you’re encountering the “An unhandled win32 exception occurred‘ error when trying to launch Uplay.exe or a different application belonging to Ubisoft, it’s most likely due to a bug with their Ubisoft Game Launcher.
As it turns out, this seems to be a widespread issue on Windows 10, especially among users that have both Steam and Uplay installed at the same time.
Several affected users that we’re struggling to resolve this issue have managed to get it fixed by using the Registry Editor to find the string registry value belonging to the launcher and deleting it. This supposedly eliminates the conflict, allowing both applications to function properly under the same machine.
Here’s a quick guide on deleting the Registry value associated with the Uplay launcher:
- Press Windows key + R to open up a Run dialog box. Inside the text box, type ‘regedit’ and press Enter to open up the Registry Editor. When you are prompted by the UAC (User Account Control) prompt, type Yes to grant administrative privileges.
- Once you’re inside the Registry Editor, use the left-hand side section of the window to navigate to the following location:
Note: You can either navigate there manually or you can paste the location directly into the navigation bar at the top and press Enter to get there instantly.
- After you manage to land in the correct location, move down to the right-hand section of the screen, right-click on Launcher and choose to Delete to get rid of it.
Note: In case you can delete the key, here’s how to take ownership of registry keys.
Note: After you delete it, the launcher will be forced to create a new Launcher string value with fresh data, which should resolve the issue.
- Once the key has been deleted, close Registry Editor and restart your computer.
- At the next computer startup, repeat the action that was previously causing the “An unhandled win32 exception occurred‘ error and see if the problem is resolved.
In case the same issue is persisting, move down to the next potential fix below.
Solution 4: Reset Internet Explorer (if applicable)
Another potential instance with the potential of creating this issue is a series of corrupted Internet Explorer (IE). If you’re encountering the “An unhandled win32 exception occurred in iexplore.exe’ error chances are it appears after a failing script.
To fix this issue, you should reset your Internet Explorer settings via the Internet Options menu. This operation was confirmed to be successful by a lot of users that were dealing with this error.
Here’s a quick guide on resetting Internet Explorer in order to resolve the “An unhandled win32 exception occurred‘ error:
- Ensure that Internet Explorer, Edge or any other associated instance is turned off and no background process is running.
- Press Windows key + R to open up a Run dialog box. Inside the text box, type ‘inetcpl.cpl’ and press Enter to open up the Internet Options menu.
Note: If you are prompted by the UAC (User Account Control), click Yes to grant administrative privileges.
- After you manage to get inside the Internet Properties screen, select the Advanced tab from the horizontal menu at the top. Next, go to the Reset Internet Explorer settings and click on the Reset button.
- Once you see the confirmation screen, ensure that the box associated with Delete personal settings is checked, then click on the Reset button.
- Wait until the operation is complete, then restart your machine and see if the issue is resolved at the next computer startup.
In case the same “An unhandled win32 exception occurred in iexplore.exe’ error is still occurring, move down to the next method below.
Solution 5: Disable Script Debugging and associated Registry Keys (if applicable)
If you’re encountering the issue with Internet Explorer on a machine that has VS installed on it, the issue can also occur due when Script Debugging is enabled and the registry entries end up containing corrupted data.
Several affected users that encountered this issue have confirmed that the issue was resolved after they accessed the Internet Options menu to disable Script Debugging and then deleted the associated keys using Registry Editor.
Here’s a quick guide on doing this in order to fix the “An unhandled win32 exception occurred in iexplorer.exe’ error:
- Press Windows key + R to open up a Run dialog box. Next, inside the text box, type ‘inetcpl.cpl’ and press Enter to open up the Internet Options menu. If you are prompted by the User Account Control (UAC), click Yes to grant administrative privileges.
- Once you manage to find yourself inside the Internet Properties screen, use the menu at the top to select the Advanced tab.
- Inside the Internet Properties screen, scroll down through the Settings menu and check the box associated with Disable script debugging (Internet Explorer).
- Once the modification is enforced, hit Apply to save the changes, then close the Internet Properties window.
- Press Windows key + R once again to open up another dialog box. This time, type ‘regedit’ and press Enter to open up Registry Editor. You will need to grant admin access, so click Yes when prompted by the User Account Control window.
- Inside the Registry Editor, navigate to the following location using the left-hand menu:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug (32 - Bit Machine) HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug (64 - Bit Machine)
Note: The location of the file we need to delete is different depending on the Windows version that you’re using. If you have a 32 – bit Windows version use the first location, else, use the second.
- Once you arrive to the correct location, move down to the right-section, right-click on Debugger and choose Delete from the context menu.
- Once this key is deleted, navigate to this second location:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\ (32 - Bit Machine) HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework (64 - Bit Machine)
Note: Access the registry key associated with your Windows bit version that you’re using.
- When you arrive at the correct location, move over to the right-hand section and delete the DbgManagedDebugger value by right-clicking on it and choosing Delete from the context menu.
- After you manage to delete the value, close the Registry Editor and restart your computer.
- Once the next startup is complete, see if the same issue is still occurring.
In case the “An unhandled win32 exception occurred’ error is still occurring, move down to the next method below.
Solution 6: Install the Latest Version of NET Framework and Repair it
Having NET Framework installed on your computer is vital and plenty of modern games and programs depend on you having it installed. Before repairing it, follow the steps below in order to install the latest version on your computer.
Navigate to this link and click the red download button in order to download the latest version of the Microsoft .NET Framework. After the download has finished, locate the file you downloaded and run it. Note that you will need to have constant access to the Internet. Follow the instructions on-screen to proceed with the installation.
- After installing the latest version, it’s time to check its integrity. On your keyboard, use the Windows Key + R key combination to open the Run dialog box.
- Type in control.exe and click OK in order to open it.
- Click the Uninstall a Program option and click Turn Windows features on or off. Make sure you locate the .NET Framework 4.x.x entry and make sure it’s enabled. ‘x.x’ marks the latest version available for your operating system.
- If the checkbox next to .NET Framework 4.x.x is not enabled, enable it by clicking the box. Click OK to close the Windows Feature window and reboot the computer.
- If .Net Framework 4.x.x is already enabled, you can repair .Net Framework by clearing the box and rebooting the computer. After the computer has restarted, re-enable .Net Framework and restart the computer again.
Solution 7: Perform a Clean Boot
There are various other programs and services which can affect the proper functionality of the Microsoft .NET Framework suite. In most cases, the cause is the antivirus you have installed and you can try disabling it to see if the error persists. However, to make sure nothing can interfere with the installation, we recommend you perform a clean boot which will disable all non-Microsoft programs and services from starting up. This way, you can easily deduct just which program causes this error to happen!
- Use the Windows + R key combination on your keyboard. In the Run dialog box type MSCONFIG and click OK.
- Click on the Boot tab and uncheck the Safe Boot option (if checked).
- Under the General tab in the same window, click to select the Selective startup option, and then click to clear the Load startup items check box to make sure it’s not checked.
- Under the Services tab, click to select the Hide all Microsoft services check box, and then click Disable all.
- On the Startup tab, click Open Task Manager. In the Task Manager window under the Startup tab, right click on each startup item which is enabled and select Disable.
- After this, you will need to perform some of the most boring processes and that is enabling the Startup items one by one and restarting your computer. After that, you need to check whether the problem appears again. You will need to repeat the same process even for the Services which you have disabled in Step 4.
- Once you locate the problematic startup item or service, you can undertake action in order to solve the problem. If it is a program, you can reinstall it or repair If it is a service, you can disable it, etc.
Solution 8: Use SFC to Scan for Memory Leaks
It has been reported that the Microsoft .NET Framework corruption is related to faulty system files. These problems are rooted deep inside the system files and the only way to try to resolve them is by running the System File Checker (SFC). It will scan your system files for errors and possible repair or replace them. Follow the steps below in order to do so!
- Search for “Command Prompt” by typing it either right in the Start menu or by pressing the search button right next to it. Right-click the first entry which will pop up as a search result and select the “Run as administrator” context menu entry.
- Additionally, you can also use the Windows Logo Key + R key combination in order to bring up the Run dialog box. Type in “cmd” in the dialog box which appears and use the Ctrl + Shift + Enter key combination for admin Command Prompt.
- Type in the following commands in the window and make sure you press Enter after typing each one. Wait for the “Operation completed successfully” message or something similar to know that the method worked.
- Try to restart your computer and check to see if the Unhandled Exception has Occurred in your Application error continues to appear on your computer.
Solution 9: Performing a Clean Install
If none of the methods presented below have managed to help you in resolving the issue, it’s very likely that you’re dealing with some kind of Windows inconsistency that cannot be resolved conventionally.
If this scenario is applicable, you should be able to fix the issue by resetting every component associated with your Windows installation. If you want to go this route, you have two ways forward. It all boils down to the procedure that you want to follow:
- Repair install (in-place repair) – This procedure is the best approach when you need to refresh every OS component, but some users might end up considering it a little too tedious for their taste. Keep in mind that you will need a compatible installation media in order to enforce this fix, but the major advantage is that all your personal data (including games, applications and personal media) will be preserved even if you don’t back up your computer.
- Clean install – If you’re looking for the simplest solution, this is the way to go. You will not need an installation media to enforce it (it’s all done through the Windows GUI). But unless you back up your data in advance, be prepared for total data loss.