Which is good, because the previous version, Version 83.0.478.37 (Official build) (64-bit), appeared to be incompatible with the advertising/tracking used here, and was throwing up page loading timeouts for the advertising or tracking.
Odd that only the last section of the version number changed: that’s often just a build counter, and often doesn’t indicate any change to the software. But in this case, they pushed out the new version, and SDMB started working OK (well, broken as usual) again.
Higher build numbers almost always include code that’s been updated relative to lower build numbers. I don’t follow Edge closely enough to know if the build numbers refer to a daily build process, or if they’re using a continuous process, but either way it’s unlikely they’re producing new builds with no changes.
Glad it’s working now. I’ve never had a problem with Edge on W10, but Chrome is still my primary browser.
There is no universal version numbering scheme and the meaning and scale of each portion of a version number varies even between the same company’s products, but the idea of a build number change without an underlying code change doesn’t make sense. In this case it probably means there was a bugfix or other small change that did not add any new features. The latest version of Edge is now based on Chromium and appears to be following their version scheme, which is described at Version Numbers. In this system, the last number is actually the patch number and the penultimate the build.