V78.1030 will not install over v78.1027.
Settings shows v78.1030 available. Ater downloading and restarting version unchanged from v78.1027 and software up to date.
Updating via software update tool installs v78.1027.
Come on Meta, first it was the v78.1028 update now this.
Has the update process been broken and the headset can no longer be updated.
Yep - exactly the same as you describe is happening to me. Thanks a lot for starting this post - kudos, I came here to do that. It’s pathetic honestly - nearly 80 firmware revisions in, literally $ billions poured into the product every year, and this. I’ve never owned an update able product where the update process is anywhere near this much of a sickening, broken mess.
Hi NomadsAnIsland! Thank you for bringing this issue to our attention.
We understand that it can be confusing to update your software only to find out that you're still on the older version, even though your device says it's up to date.
It's important to note that our software updates aren't released to all users at the same time. They are rolled out in phases to ensure a smoother transition and allow us to monitor for any issues before wider distribution. This phased rollout helps minimize the impact of potential bugs or problems that might arise with a new update.
With that say, we would still like for you to submit a bug report so that we can better understand the issue and review it with our team.
To submit a bug report, you need to:
We hope that this was helpful and please be sure to check back on the Forum frequently for any news and updates regarding this issue. If you have any other questions or concerns, please do not hesitate to reach back out to us, we are always more than happy to help our VR family!
“We hope this is helpful” eeerm, how could that possibly be helpful? You haven’t offered any help. If this so-called Meta “Community Manger” reply isn’t an A.I. bot then honestly you should be ashamed of yourself.NomadsAnIsland HAS reported the issue & given all relevant details. All you are doing is, asking them to submit the same information again. How is that helpful, at all? Don’t you work at Meta? Can’t you flag the issue to the relevant support team yourself? News flash - THOUSANDS OF YOUR USERS WILL BE AFFECTED BY THIS EXACT SAME ISSUE. Your update code is bunk. You guys seemingly don’t understand how operating systems work.
MetaStoreHelp this issue has nothing to do with updates that are rolled out gradually.
The headset doesn't tell me an update is available before it is rolled out to me.
NomadsAnIsland 78.1030 and 78.1027 have both build 5163765.9120.150 ??
I can’t speak for Nomad but yes - that build number matches my headset, on v 78.1027. It detected as available, downloaded and “installed” .1030 earlier today, only to restart, then report being on 78.1027 still, with now no update available and the same OS last update date for me of 8th July. Same build number, too. The web link to Meta’s update notes is beyond pointless, just mixed up version numbers & no note(s) even published for .1030. Why do we even need a build number? These guys are jokers, it’s an excellent troll, really.
you should possibly work for Meta support as it was obvious to you that the first couple paragraphs of the support response to Nomad were pointless word salad. The fact that they are so cautious about rolling out feature updates speaks volumes to me… Imagine having so little confidence in what you’re doing that even just using the PTC channel to test isn’t enough, instead you have to drip feed even cosmetic changes to your users over actually many months rather than just testing things properly then issuing an update once it’s ready. Sad.
Same issue here on QUEST 3. Yesterday, I noticed ANOTHER v78.1030 update appeared in my headset (also 105Mb), even though I updated 8 days ago with that same version and build number. So I installed the update and restarted the Quest 3. It now says it is "up to date" again, but the version number is STILL v78.1027 "installed 8th July". This is the second time this has happened now (or third time, if I include the v78.1028 (105Mb) update from a couple of weeks ago, which also reported being v78.1027 in the headset after installation)! So I have no idea if the install is failing, or whether it was successful but Meta have neglected to update the software version and build numbers.
PS. I also note that after clicking the update button, nothing seemed to happen for about 10 seconds, then the download progress bar suddenly appeared showing about 80% progress, but then seemed to get stuck. After waiting 5 minutes, I navigated to a different tab and back again, the button had now reverted back to showing "an update is available". I think something is broken with this download button and progress bar. I powered off the Quest 3, and it showed the "software is updating" thing that it does when powering off. This took about 2 minutes, so I assume this was the Universal Interface update actually getting installed.
So version number ending .1031 appeared as available for me today, at around 124 Mb if memory serves.
Yet again, I also experienced the very disconcerting behaviour as described in steve_40’s PS (above). meta software updates should not with this way. When you click to download it & nothing happens, it is reasonable to assume that nothing is happening. How difficult can it possibly be to code an accurate progress bar? Well I ask, but seeing as your PC software, mobile app & even website all seem horrifically bugged, I shouldn’t really be surprised.
In any event, having been told it’s ready to install on headset restart, I restarted me headset & guess what? It installed perfectly & all the bugs are gone now. Just kidding - it did seemingly nothing as my headset still has the same version & build number as before (see above), so exact same outcome as the .1030 update. Better luck next time.
I just came here to ask if anyone has tried the 78.1031 update and whether it has finally fixed the issues. Dayum, of course it didn't! 😟 Interestingly, Meta Support has been stating in various threads that we need to wait for v79. Anyway, I'll skip v78.1031 for now.
