This issue occurs due to shared dependencies that get accessed by both launchers at the same time. This typically occurs when the leading Origin service runs in the background and a Steam application starts. If Steam is not installed when the error code 106133 pops up, the issue is most likely due to a server issue, a corrupted cache folder or game installation, or an AV interference.
1. Check for a server issue
Before you start troubleshooting the issue locally, let’s ensure that the error code 106133 is not occurring due to an Origin server issue. In the past, this error started to become a widespread issue on both Windows & Mac clients as EA stopped supporting the client for the Windows platform. If you are still using a deprecated Origin build in favor of EA Play, the first thing you should check is the status of Origin servers. The ideal place to start is on directories like DownDetector and Outage.report. Note: On these directories, see if there’s an uptick of users complaining about the same issue recently. It’s a good idea to scroll down to the comment section and check if the error code 106133 is being reported by other users. If you are seeing evidence of a severe issue, it’s also worth it to check the official EA Twitter account or the Reddit hub for evidence of maintenance or outage issues. If your inquiries did not uncover any issues, the issue is likely limited to your machine. In this instance, go to the subsequent technique listed below.
2. Restart your PC
If you only started to see the 106133 recently and you’re no longer able to access any library title on Origin, the first thing you should do is restart your PC. It’s likely that your Origin client just got uninstalled and replaced with the EA Play client and you just need to restart your PC to allow the changes to take effect. Note: Origin terminated operations for its Windows platform in October 2022, migrating players to EA Play. This is a slow process that is carried on based on the region and account library. If you had Origin installed, the client likely just replace it with the new EA Play app. Keep in mind that once the migration is complete, all the library items present on Origin will show up on your EA Play account. UPDATE: There might be instances where some of your game titles are missing. In this case, there’s nothing you can do other than wait for the developers to patch the issue. Most likely, all you need to do is restart your PC to allow the migration to the new app to happen successfully.
3. Set Steam to Run in Offline mode
One way to avoid this launcher conflict is to set steam to Offline mode before re-launching the game title that’s triggering the 106133 error in an Origin window. Note: By doing this you will ensure that the Steam process doesn’t try to access the shared dependency that causes the conflict. Follow the instructions outlined in this article to run Steam in Offline mode, then launch the game title once again and see if you can do it successfully without getting the same error.
4. Update & Repair the malfunctioning game
If you only see this error while launching certain game titles via the legacy Origin app, this might be an issue caused by a game version mismatch or by a game installation inconsistency. In this scenario, you should be able to get the issue fixed by opening the Origin app and updating the game to the latest version before triggering an integrity check. Here’s a quick guide on how to do this:
5. Delete Temporary Origin Files
In certain scenarios, you can expect to see this error due to corrupted temporary files originating in the LocalContent folder of Origin. If you’re still using the Origin legacy app, you can resolve this issue by closing the main Origin service and removing the contents of the Origin folder inside the Roaming folder. Note: These files are in no way essential and deleting them will not have any effect on your game launcher. But in order to be able to delete them, the main Origin service needs to be closed. Here’s how to delete the temporary Origin files:
6. Allow Origin through Antivirus
If you’re utilizing a third-party AV, it’s also possible that it indirectly prevents the Origin launcher from talking with its download server, causing the 106133 error to appear. Note: Windows Defender (Windows Security) does not appear to be causing this error. (this issue is only restricted to certain 3rd party AV suites). If you are using a third-party antivirus suite and are experiencing this issue, you should first disable the real-time protection of your AV and relaunch Origin. If the problem no longer exists, you have two options:
Add the Origin executable (Origin.exe) to the exception (whitelist) list to guarantee that it is not blocked by your antivirus software – The procedures to accomplish this are unique to each third-party antivirus. You can search the Internet for specific instructions.Uninstall the third-party antivirus and switch to Windows Defender – Many users have claimed that Windows Defender does not block Origins, so switching to the system’s default security application might remedy the issue if a third-party AV is causing it.
Here’s a brief instruction on how to remove a third-party antivirus and switch to Windows Defender:
7. Reinstall Origin
If you still see the 106133 error despite ensuring that Origin is not conflicting with Steam, the last resort method should be to uninstall the Origin application together with any residual setup files and dependencies. It’s also advisable to change the default installation directories from within the application after reinstalling to ensure that it’s not leveraging any residual files left behind from the previous installation. Important: Keep in mind that EA has stopped supporting the Origin client for the Windows Platform and the official download page redirects to EA Play. However, you can still use the origin.onl directory to download the latest build release. Follow the steps below to reinstall the Origin application and remove any residual files and dependencies:
