In this case it happened that I didn't find a hint to a solution of my problem, but the EBF fixed it. Lesson learned: install latest EBF in a test environment and check if the problem is gone, as you did.

I've had Reimer's experience many times. Although it is apparent the authors of the rdme files are trying hard, the descriptions are still far too terse. Once upon a time I had complete access to the entire Customer Service trouble report database and it had a level of detail 100 times deeper than the rdme files... you could find your exact symptom (someone else ALWAYS has your symptom first) plus a complete record of what got fixed when. That was many years ago... my point is, the information exists, but it's not public.

I gave up reading/searching for fixes after reporting a bug myself; something like "FK didn't work after inserting xyz row". I found the Case # later in the EBF with a description something like, "There was a failure of the abc rountine when the left predicate did not match the right predicate in a sargeable expression...". The engineer's translation was no doubt far more accurate than my report, but completely impossible to understand.

Filtering by target platform and/or product version shurely would be an enhancement. I've already suggested that using the feedback link on the EBF page, but to no avail.