Quest Support Contact / RMA link not working
My friend from South Korea has issues with controllers and has been writing with Support for 6 weeks now, around 14 Mails (!) back and forth. She is a streamer, but has a tough time talking in english. Her controllers have issues with not recognizing input and stick drift. She has been offered an advanced replacement, but the links for these didnt work. She has received the RMA link and tried to proceed with the “Complete Request” step. However, the page redirects her to a checkout screen where it says that shipping to South Korea is not available. They sent her several links, always the same result and that they want to try again and get back to her etc.. This has been a very time consuming experience, with no result. Now after 6 weeks (!) they say they have technical issues and can only do a normal RMA, where she would have to send them back first and then after a few weeks would receive a replacement.. This is really difficult for her, as she cant really do a break for her streams for that long, effectively she would have to buy new ones instead. While she has the resources, its a waste of money to do that and she would like to see this worked out instead. Is there a way to get in touch with someone from support, so I could help figure this out with her. I am confused that this is such a difficult experience to get resolved with the support and we think that quest should have a way to make this possible.
Meta Quest 3S not recognized on Web/Support – Unable to redeem Batman: Arkham Shadow bundle.
Hi everyone,I'm reaching out because I am having issues with my new Meta Quest 3S. I purchased it 6 days ago from the official Meta Store on Mercado Libre.Even though I have already created my Meta Horizon account and activated the headset (which shows up as "connected" in the mobile app), the Meta Web portal does not recognize my device. When I try to contact official support, the website says there is "no support service available for me" because it doesn't see my Quest 3S registered.Mainly, I need help redeeming the Batman: Arkham Shadow bundle. This game was the main reason for my purchase, and despite the promotion being active until 12/31/2026, I haven't received the redemption notification or option in the store.Details for reference:Device: Meta Quest 3S (128GB/256GB).Purchase Source: Official Meta Store (Mercado Libre).Activation Date: 6 days ago.Issue: Device visible in Horizon Mobile App but invisible on Meta Web/Support site.I have already tried restarting the headset and re-logging into my account, but the issue persists. I would appreciate any help to get my device recognized and my game redeemed.Thank you for your time and help.
Quest 3 refuses to boot and only shoots air.
I woke up and heard my quest 3 just shooting out air in like an off and on pattern every 2 or 3 seconds and I tried to put it on, unresponsive from the screen, I tried to hold the power button which actually worked except when I even clicked it down again the blowing immediately resumed with a sudden gray flash of the color that the screen makes to mimic black, then it would turn off the screen and continue blowing, when I plug it in with a charger that works with other devices the power port refuses to display a color or even a sound to show that its charging.
Support problem
I have an Oculus Quest 3 bought in Amazon 5 months ago and the Meta Support does not recognize the serial number when trying to open a ticket. I have a problem with one of the controllers that have became crazy and does not respond to the track movement. Does anyone know how to manage an issue like this?Quest 3 Safety Issue - DOA - Support Loop with 6 Agents
Hi , I received my Quest 3 on April 2nd from Amazon and the Right Controller is DOA(Dead on Arrival). It gets dangerously hot and drains the battery to 0% rapidly even when the headset is completely powered off. This is a major safety hazard and a clear hardware defect (fire risk). I’ve been stuck in a support loop for 3 days with SIX different agents (Miley, Joyce, Morrison, Levi, Deejay, and Mea). One agent promised to escalate this to a "Specialized Team" but the next day I just got another generic template asking for the same info I already sent. It’s clear no one is actually reading the case history or taking the safety risk seriously. I’m not waiting weeks for a standard RMA on a brand-new device. I’ve already offered a Security Deposit for an Advanced Replacement so Meta has no financial risk. Also, since my Horizon+ trial is running while the device is unusable, I expect at least 30 Euro in Quest Cash for the downtime and this terrible experience. If Meta can't authorize a deposit-based replacement for this controller immediately, I’ll just return the entire Quest 3 unit to Amazon for a full refund. A retail return of a defective unit will cost Meta significantly more in fees and lost value than just shipping me a working controller now. Can a moderator please escalate this to a Senior Supervisor? ThanksUnable to return my quest3 back for replacement under warranty via DHL missing rqd labels
My quest 3 is defective and I'm trying to send it back. Meta have sent me the return labels for DHL, and I have attached them to the parcel. DHL suspend the shipment saying that it lacks the required dangerous goods label. They return it. I chat to support and support escalate it. Someone gets in touch, ignoring the comments I've passed on from DHL. They generate new versions of the same labels (ie missing DG label) which they attach. I respond to their email saying that without the DG label it will get suspended again. They reply and tell me Please refer back to your courier for more clarification as far from our end everything looks fine. So right now I'm completely stuck
Rift S "Sensors can't track headset"
I've recently switched to a new computer, and after installing the Meta Horizon Link app I am unable to get my Rift S headset through the initial setup process. The app recognizes my headset, shows a green check-mark on the connection status, and the display inside the headset turns on and shows three dots in the center. Attempting to go through the device setup, the second step tells me "Sensors can't track headset" and I cannot progress further. If I skip setup the headset still only shows the three dots. I have tried using multiple USB ports and multiple display ports. I have made sure the environment is well lit and suitable for VR use. I have made sure the cable is securely plugged into the headset. I have reinstalled the app, making sure to clear all existing files out of appdata and program files. I have reinstalled the device drivers. I have restarted Windows many times and made sure it is up to date. I have made sure the privacy settings in Windows are set correctly. I am also unable to contact support because the form is not recognizing the ID from my Rift S headset I have been using through the desktop app for multiple years.
Quest 3 Pairing Error on iOS: App accepts pairing code, finds headset, but fails to connect
Hi everyone, need some help with a stuck setup. I'm trying to pair my new Quest 3 to my iPhone to finish the setup (and claim a referral), but I'm hitting a wall. The Specific Issue: The app detects the headset via Bluetooth, and I am able to enter the 5-digit pairing code shown in the lenses. However, immediately after entering the code, the app attempts to pair/connect but then fails with an error (screenshot attached). My Theory: I suspect this is a network permission bug. The Meta Horizon app needs "Local Network" access to finish the handshake, but the iOS system popup asking for this permission never appears. When I check iPhone Settings -> Meta Horizon, the "Local Network" toggle is completely missing. Only Location, Bluetooth, and Notifications are listed. What I have already tried: Reinstalled the app multiple times. Reset Network Settings on my iPhone (to force permission prompts). Factory Reset the Quest 3 multiple times. Tried connecting via Personal Hotspot (cellular data) to bypass my router. Tried forcing the prompt by initiating Casting from the headset (didn't work). Screenshot: Has anyone solved this specific "code accepted but pairing failed" loop on iOS recently? Is there a way to force the Local Network permission? Thanks!
