As it turns out, the issue is most likely being caused by an outdated firmware version of LifeCam facilitated by an incompatibility with the user’s OS version. To resolve this, you will need to install the latest firmware supplied by Microsoft according to your LifeCam webcam model. You can also try updating the main Lifecam driver manually. However, a lot of affected users have reported certain conflicts between Lifecam and ASUS AI Suite. To work around this inconvenience, you will need to update ASUS AI Suite to the latest build or uninstall it altogether. Other potential causes that might cause the “Faulting application name error” is a severely outdated JAVA version or a startup error caused by a USB 2.0 port.
Method 1: Installing the latest firmware for LifeCam
If you see that the issue is inconsistent (it only happens when launching LifeCam executable, but the functionality of the camera works fine in Skype and other apps) it’s probably due to an outdated firmware version. Most affected users that we’re trying to get the Lifecam.exe Initialization error resolved have confirmed that they managed to fix the issue by uninstalling their current software via Programs and Features and then installing the latest firmware update for Lifecam from Microsoft’s official download page. Here’s a quick guide on how to do this and resolve the Lifecam.exe Initialization error or Faulting application name error: In case you’re still encountering the same ‘Lifecam.exe fails on Initialization’ error, move down to the next potential fix below.
Method 2: Updating the drivers with Device Manager
If you noticed that the Lifecam webcam doesn’t work in different circumstances (when launching Skype or other apps that use the webcam), it’s most likely due to a driver issue. This is typically encountered right after the user tries to install an older Lifecam driver via a traditional media such as a CD or DVD. If you’re using Windows 7, Windows 8.1 or Windows 10, you can correct this issue automatically by using Device Manager to force the WU component into updating the webcam driver to the latest version compatible with your OS. In case the issue is being caused by some kind of driver incompatibility, this issue should be resolved automatically after a computer restart. Here’s a quick guide with you to update the Lifecam.exe drivers in order to fix the ‘Lifecam.exe fails on Initialization’ error: In case the issue was not resolved after updating to the latest LifeCam driver or your driver version was already the latest, move down to the next potential fix below.
Method 3: Update / Uninstall ASUS AI Suite (if applicable)
As it turns out, this particular issue can also occur due to some kind of conflict between the LifeCam camera driver and older versions of the ASUS AI Suite. In case this scenario is applicable and you have ASUS AI suite installed on your computer while trying to use Microsoft LifeCam, you need to eliminate the conflict one way or another. To do this, you can either remove the piece of software from ASUS altogether or you can ensure that you’re using the latest version available (ASUS released a patch that fixes the inconsistency). Here’s a quick guide on uninstalling the current ASUS AI Suite and then downloading and installing the latest version in order to eliminate the conflict with Microsoft LifeCam: In case this method didn’t resolve the issue for you, move down to the next potential fix below.
Method 4: Plugging the camera into a USB type 3 slot (if applicable)
As it turns out, newer LifeCam models might trigger startup errors when forced to work with USB 2.0 slots when USB 3.0 is available. If you’re encountering this issue when the camera is plugged into a USB2 Slot on a computer with USB3, try unplugging the camera and plugging it into the newer USB format (USB 3.0). After you do this, let the driver installed on that USB hub, then restart your computer. After the next computer startup is complete, launch the LifeCam application once again and see if the issue is now fixed. In case the issue is still occurring (even when the camera is plugged into USB 3.0) or this scenario wasn’t applicable, move down to the next method below.
Method 5: Update Java version
As some affected users have reported, this issue can also be caused by some outdated JAVA elements that are not compatible with the newer LifeCam version. Some affected users that we’re encountering the same issue have reported that they were able to fix this particular issue by using the Verify Java and Find Out-of-Date utility. After running this web-based check, installing the update Java environment and restarting their computer, most affected users have confirmed that they no longer had issues launching the Microsoft LifeCam.exe. Here’s a quick guide on updating the Java environment to the latest version using the Verify Java and Find Out-of-Date utility: In case the same ‘Lifecam.exe fails on Initialization’ error is still occurring, move down to the final potential fix below.
Method 6: Using a System Restore point
If none of the methods below have allowed you to bypass the ‘Lifecam.exe fails on Initialization’ error, it’s very likely that a recent machine change such as a driver installation, installed update or an AV scan has ended up interfering with the main Lifecam.exe application. If you suspect this scenario is applicable but you have no way of pinpointing the issue, the easiest way to resolve the problem is by using the System Restore utility to revert your computer back to a state when this problem was not occurring. By default, every recent Windows version (Windows 7, Windows 8.1 and Windows 10) is configured to create and store new restore snapshots regularly (during important system events). Unless you modified the default behavior (or a 3rd party did it for you), you should have plenty of System Restore points to choose from. But before starting this process, it’s important to understand that once you go through with it, every change that you made to your system since that restore snapshot was created will also be lost. This includes any installed applications, games and any other system updates that might have got installed during that period. If you are aware of the consequences and you are prepared to use System Restore, here’s a quick guide on using it to restore your computer back to a healthy state when this problem was not occurring:
Fix: Windows Cannot Initialize the Device Driver for this Hardware (Code 37)Google Chrome For Windows 7 Will Continue To Work For Two More Years As…How to fix Failed to initialize BattlEye Service: Generic ErrorFix: Outlook crashes with error 0x80000003 (Failed to Initialize)
