Using the -l flag with "pg_ctl start" resolves this issue. This was a significant behavior change since PG 13.18.
I don't recall this changing recently...the documentation hasn't at least...
David - Thank you for the quick response. Would appreciate if you have any thoughts on another logging bug (or behavior change since PG 13.18) that I documented on June 11 in #18955.
That seems Windows OS specific which I'm unable to review and comment upon.