Skip to main content
New Participant
November 6, 2025
Question

Quest 3S v81.1034 – A Button stops working only in main UI after update

Hi everyone,

I’m using a Meta Quest 3S running version 81.1034. My A-button works fine during setup and inside games, but it stops working in the main system UI/menu after the update.

I’ve already tried unpairing/re-pairing controllers, rebooting, and even doing a factory reset β€” the issue remains the same.

Has anyone else experienced this after updating to v81.1034?  
I’m trying to determine if this might be a new software bug or something specific to my unit.

Thanks!

14 replies

MetaStoreHelp
Community Manager
November 6, 2025

Hey deybich!

 

We came across your post and wanted to try and help you out!

 

Firstly, we'd advise that you remove any unsupported third-party accessories that may affect the button motion, such as controller covers or attachments.

 

You could also try taking out the battery for 30 seconds, and trying a new one.

 

If either of these steps don't fix the issue, please get in touch with us privately by clicking our username, navigating to our page and selecting 'Send a Message'!

 

We look forward to getting this issue under control!

 

If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
deybichAuthor
New Participant
November 6, 2025

I sent a private message as suggested, but I’m not sure if it went through correctly.

MetaStoreHelp
Community Manager
November 6, 2025

Hey again deybich!

 

Thanks for trying to get in touch with us - there might be a technical error as, at present, we don't have any private correspondence from you.

 

You could try getting in touch with us via email, chat or WhatsApp here!

 

We look forward to hearing from you!

If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
steve40
Honored Contributor
November 6, 2025

Try toggling off all the Experimental Settings and also hand-tracking in your headset. Now unpair your controllers using the phone app. Remove the batteries from the controllers for 5 minutes then put them back in. Now re-pair the controllers using the phone app. After successful pairing, press and hold the power button on the headset for 20 seconds to power it off. Restart the headset and check if the controllers are fully working again. You should now be able to turn hand tracking and the Experimental Settings back on.

deybichAuthor
New Participant
November 6, 2025

These are all the steps that I did

Here’s a quick summary of what I did:

Removed any controller accessories or covers (none were used).

Replaced the controller batteries and waited 30 seconds before reinserting.

Unpaired and re-paired both controllers using the mobile app.

Rebooted the headset through the power + volume down method.

Used the Meta software update tool via USB cable to ensure the firmware was up to date.

Performed a factory reset.

During the factory reset setup, the A button works perfectly β€” for example, selecting language, connecting to Wi-Fi, and going through the initial steps.
However, once the setup is complete and the final user interface loads, the A button completely stops working in the VR system interface.

To rule out a hardware issue, I even swapped the A and B button functions in configuration. When I assigned the A button to perform the B button’s actions, it worked flawlessly β€” confirming the A button itself is fine.

Also, in all games the A button works perfectly, so the issue only affects the main VR interface (menus, selections, calls, etc.)

steve40
Honored Contributor
November 7, 2025

OK, but you did not follow my instructions πŸ˜‰. Good luck.

New Participant
December 4, 2025

I have totally same issue with Quest 2, v81.1034.

New Participant
December 4, 2025

ok but yo have another option.

New Participant
December 27, 2025

I couldn't figure out last time but I found it just use the right trigger behalf of A. 
They replaced the A to jumping in the Immersive Home, and the accept function in UI was moved to the trigger. 

I wish it can be back.