Participant

Solved

Meta Quest update button not doing anything after PTC V66

180 replies
59861 views

Im on ptc v66 and I got the update for the official rollout of v66. When I click update the download progress pops up for a second and goes away. The button to update is greyed out and stuck “updating…” I’ve let it sit for quite a while. Reset several times and nothing. If you leave update and go back it has the option to update now again. Resets do nothing

TheeScientistAnswer

Honored Contributor

Hi everyone! 👋 I hope you're all doing well. I have some great news to share from our Internal team. It seems that the issue has been resolved! Now, to get things back on track, it would be recommended to reboot your headset. You can find the step-by-step instructions on how to do it successfully at this link here. It's super helpful and will guide you through the process smoothly. If you're still facing any problems, shoot a private message to MetaStoreHelp. They'll be more than happy to help and take a closer look into the matter for you.

Don't worry be happy.

Show previous replies

F

Ferminuki

New Participant

Quest OS: 65.0.0.546.341.596219110

device: Quest 3

not in PTC.

Not work in spain

MilkorVR

Participant

So, i just factory reset my quest 3, i just pair but it says that 1 hour or more “to update the software”, i just wait 2 hours, and then it says “estimating time” and yes im connected to wifi.

Somebody help?

MilkorVR

Participant

Thank you!

TheeScientist

Honored Contributor

Thanks to all of who have shared the information! I'll make sure to relay this information and any other new details to our Internal team. I'll keep you all in the loop once we have any new updates. 🙂

Don't worry be happy.

D

diogomendes

New Participant

Thank you TheeScientist, great to have you around in these times!

66.0.0.547.370.604713589
65.0.0.499.343
No
Yes
Not that I found.
Q3

3

3dillusionscouk

Inspiring

the headset shows 66 is available, I choose update now and then restart as instructed, but it just keeps saying 66 is available.

I tried powering down with the 'update before power down' slider enabled, it briefly says updating, but then when I check, it still says 66 is available.

Is this related to having developer mode enabled?

Choleni

Honored Contributor

Hi 3d-illusions.co.uk 🙂

no, it's not.

Several people have issues updating to v66.

Look here.....not only people coming from ptc are affected

Solved: Quest update button not doing anything ptc v66 - Meta Community Forums - 1203827

3

3dillusionscouk

Inspiring

Thanks, I'll stop trying to get it working then 😂

F

FinlessBob

Up and Coming

Exact same thing here. I am on PTC V66 same as others and same version numbers.

T

tomy1971

New Participant

same here, Meta update is a mess..... why they don't offer it for download.... that stupid..... some get updated some not.... come on guys....

K

Karlostavitch

New Participant

Quest 3, non PTC 65.0.0.546.341.596219110

currently unable to use Quest Pro controllers since 65 update.

K

kenzyun

New Participant

I have the same issue.
Quest 3
PTC
66.0.0.547.370.604713589

M

marcussacana

Participant

I got this problem as well then I tried to collect the logs during the update and this is what I got, Take a look at this point:

06-11 23:00:14.377   808   808 W update_engine: [WARNING:payload_verifier.cc(159)] Failed to get the raw hash with RSA key. Trying other keys.
06-11 23:00:14.381   808   808 I update_engine: [INFO:payload_verifier.cc(191)] Failed to verify the signature with 1 keys.
06-11 23:00:14.383   808   808 E update_engine: [ERROR:payload_verifier.cc(137)] None of the 1 signatures is correct. Expected hash before padding:
06-11 23:00:14.386   808   808 I update_engine: [INFO:utils.cc(401)] Logging array of length: 32
06-11 23:00:14.389   808   808 I update_engine: [INFO:utils.cc(418)] 0x00000000 : b0 83 af a0 d5 14 84 44 a9 af d9 0e 5f 3e 27 af 
06-11 23:00:14.392   808   808 I update_engine: [INFO:utils.cc(418)] 0x00000010 : af 8f a9 e1 5b e6 3c 04 21 fd 6d 85 93 88 f5 f0 
06-11 23:00:14.395   808   808 E update_engine: [ERROR:payload_verifier.cc(140)] But found RSA decrypted hashes:
06-11 23:00:14.400   808   808 E update_engine: [ERROR:payload_metadata.cc(214)] Manifest hash verification failed.
06-11 23:00:14.409   808   808 E update_engine: [ERROR:delta_performer.cc(374)] Mandatory metadata signature validation failed
06-11 23:00:14.411   808   808 E update_engine: [ERROR:download_action.cc(222)] Error ErrorCode::kDownloadMetadataSignatureMismatch (26) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
06-11 23:00:14.416   808   808 I update_engine: [INFO:delta_performer.cc(217)] Discarding 654043 unused downloaded bytes
06-11 23:00:14.421   808   808 I update_engine: [INFO:libcurl_http_fetcher.cc(623)] Requesting libcurl to terminate transfer.
06-11 23:00:14.425   808   808 I update_engine: [INFO:multi_range_http_fetcher.cc(177)] Received transfer terminated.
06-11 23:00:14.428   808   808 I update_engine: [INFO:multi_range_http_fetcher.cc(129)] TransferEnded w/ code 206
06-11 23:00:14.436   808   808 I update_engine: [INFO:multi_range_http_fetcher.cc(131)] Terminating.
06-11 23:00:14.439   808   808 I update_engine: [INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kDownloadMetadataSignatureMismatch
06-11 23:00:14.442   808   808 I update_engine: [INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
06-11 23:00:14.447   808   808 I update_engine: [INFO:update_attempter_android.cc(550)] Processing Done.
06-11 23:00:14.450   808   808 E update_engine: UnmapAllSnapshots should never be called.
06-11 23:00:14.453  1084  3952 D OsUpdateMonitorService: onStatusUpdate(0, 0.0)
06-11 23:00:14.453  1084  3952 D OsUpdateMonitorService: onPayloadApplicationComplete(26)
06-11 23:00:14.454   808   808 I update_engine: [INFO:metrics_reporter_android.cc(159)] Current update attempt downloads 0 bytes data
06-11 23:00:14.461  2055  7322 I OSUpdateService: Intent with action apply_update_failed
06-11 23:00:14.461  2055  7322 W OSUpdateManager: Applying update failed: Installation failed. Error code: 26, err: 26
06-11 23:00:14.485  2055  7322 I OSUpdateEventLogger: logOSApplyUpdateFailed
06-11 23:00:14.514  2055  7322 I OSUpdateEventLogger: reportSoftError, message = Installation failed. Error code: 26
06-11 23:00:14.514  2055  7322 E update_engine_error_26: Installation failed. Error code: 26
06-11 23:00:14.515  2055  7323 E ACRA    : com.facebook.common.errorreporting.SoftErrorException: update_engine_error_26 | Installation failed. Error code: 26

K

Kawarider

Participant

Same issue here! Here we go again. Wonder how long this will take 😆

Show more replies

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO