2026.07.0 update again (same version, different build)

[SteveInBend]

Per my usual process, I will wait at least a week or two before installing after I receive notification of the download being ready for installation.

Let someone else be the guinea pig!

Sponsored

 

[John G.]

I got it again after installing the first update last week.

I just pushed the button and let the newer version rip. I hope this fixes the bug I got from installing the first update last week which caused my truck to no longer recognize my fob.

 

[sccmexpert]

Just got a notification that 2026.07.0 was ready to install. Just one thing, it’s already installed.

Think I’ll pass on installing it again.

 

[godfodder0901]

Just got a notification that 2026.07.0 was ready to install. Just one thing, it’s already installed.

Think I’ll pass on installing it again.

Several threads on this already. Bug fixes.

 

[sccmexpert]

Then it should have a new version number. Not the same version number.

 

[Fmc]

Do you mind me asking what you’re using to monitor the 12v performance from one update to the next?

Nothing..other than the fact last week the widget showed 8 hours of sleep when u woke up and now it shows 12 mins to 2 hours. Completely unscientific but I have not seen long sleep since the update

 

[Time2Roll]

If only there was some way to distinguish different versions of the software so people could tell them apart. Possibly some sort of numbering system. Too bad for Rivian no one has invented such a thing.

Yes so what is the point of the dot zero at the end anyway

 

[Dark-Fx]

Then it should have a new version number. Not the same version number.

It's a different build number.

 

[sccmexpert]

It's a different build number.

As you can see from my screenshot, the build number's are the same, at least in the customer facing view. Now on the actual build that I can't see, they may be different.

At any rate, the developers should have incremented it at least .1 customer facing.

 

[Dark-Fx]

As you can see from my screenshot, the build number's are the same, at least in the customer facing view. Now on the actual build that I can't see, they may be different.

At any rate, the developers should have incremented it at least .1 customer facing.

It shows up on the vehicle. It's a checksum. I'm not talking of only the version number.

 

[ndmiller]

Its the same version with the fixes.

 

[Gfeidler]

The second version of this update appears to have fixed my issues with Apple music and dolby atmos.

 

[RivianTrackr]

Only fix was restoring elevation data that was erased.

 

[tate16t]

Only fix was restoring elevation data that was erased.

It makes more sense now that the version number did not change for the second iteration.

 

[Hillbilly]

It would be nice if Rivian could fix why I have to reset my Bluetooth every time I get in my truck in order to put it in drive.

Sponsored