Today's TT update (3/15/2026) did not resolve this bug. As a veteran SW engineer, I realize (and sympathize with) the TT developers having to fix many bugs in a "fire drill" situation, i.e. with tax season in full swing. It is also understandable they have to prioritize the bug list and work on those that affect most customers, OR those the management tells them to work on.
THAT SAID, the most outrageous part of this saga is the complete lack of honest, open, intelligent feedback from the relevant TT sources. I (and probably many of us) would much appreciate a message similar to what I myself was sending out to our customers, along these lines:
"To our TurboTax customers experiencing this problem: I <<insert name or handle>> am part of the SW development team of TurboTax. We are fully aware of the problem and were able to replicate it in our environment. It is indeed a bug we intend to fix. It is in the developer's queue to be addressed in the near term. Estimate of completion is <<insert something here>>. I promise to keep you informed of progress towards resolution, among others by posting follow up notes in this forum".
Wouldn't that be nice?
