I'm being hit by a bug that's supposedly fixed in version 22.214.171.124i.ROUT. SMU is not available on software download.
I'm already running version 4.3.2. Where do i get this 20i version of 4.3.2? What does it mean?
if the bug is fixed in 126.96.36.199i that means the fix is in 4.3.2 official release.
What is the bug id and why do you think you have the same problem?
Thanks for your reply /A:
|Known Affected Releases:|
|Known Fixed Releases:|
Known Affected Releases is manually filled in and looking at the bug history I see it was changed from 4.3.1 to 4.3.2. In any case it is less trusted (as manual) compare to Known Fixed Releases as this field is automatically filled and based on the real commits.
"i" means Internal Production Build.
Internal builds always have format xx.yy.zz[ww(i)]. So very first 4.3.2 internal build was 4.3.2.i1
The bug fix went into build 20, 188.8.131.52i.
CCO-posted version is the latest internal build where the build number field gets dropped or set to  and hence all fixes from x.y.z.# are included in CCO releases x.y.z
Just for you information, the latest internal build was 184.108.40.206I and hence the CCO 4.3.2 = 220.127.116.11I.
Thank you very much for the thorough answer, /A.
Just so I don't misunderstand: from what you're saying I gather that 4.3.2 on CCO a couple of months ago might not be the same as today? Is this correct?
No, it is the same. once it is published there are no more new internal builds and 18.104.22.168I in the last one which was published on CCO since the beginning. Any new updates for 4.3.2 are delivered using SMUs only.
Great to know. Now the problem is: why is the bug still there and why is there no SMU.
Let's see what TAC has to say about it.
Thank you very much!