Warframe Companion Error 160 | Most Effective Fix

If you are seeing Error 160 in the Warframe Companion app right now, you are not alone. As of March 18, 2026, there is a confirmed worldwide issue where the app fails to authenticate users, often showing “Logged Out” in the Profile tab and throwing Error 160 when you try to sign back in.

Because this is an app-side server issue following recent infrastructure updates, standard troubleshooting often fails, but here is what you can do to try and bypass it:

Most Effective Fixes

1. The “DNS” Fix

Many users have found that the error is caused by a failure to retrieve specific security packages over certain ISP networks.

• Android/iOS: Go to your Network Settings and manually set your Private DNS to 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare).

• Toggle Data: If you are on Wi-Fi, switch to Mobile Data (or vice-versa) and try to log in again.

2. Verify Cross-Platform Play Status

In 2026, the Companion App is strictly synced with Cross-Platform Save.

• The “In-Game” Conflict: Ensure you are completely logged out of Warframe on your PC or Console. The app cannot pull your data if an active session is detected.

• Account Linking: Log in to the official Warframe website on a mobile browser first. If the website asks you to re-verify your email or link a platform, the app will throw Error 160 until that web-based prompt is cleared.

3. Clear App “Ghost” Data

If the app thinks you are logged in but the server disagrees, it creates a loop:

• Android: Go to Settings > Apps > Warframe Companion > Storage and select Clear Cache AND Clear Data.

• iOS: You must Delete the app, restart your iPhone, and reinstall it from the App Store to fully flush the authentication token.

---

Current Status Update

Reports from the official forums and Reddit (as of 1 hour ago) suggest that Digital Extremes is currently working on a hotfix. Many players in North America and Europe are reporting infinite loading screens alongside this error. If the steps above don’t work, the problem is likely on the server-side, and you will need to wait for a back-end fix from the developers.