Failed to efile from multiple machines with Error 2: We're experiencing Internet transmission problems. Your transmission didn't go through. Intuit's Electronic Filing Center did not receive your return(s). Please try again
If:
PC #1 (Win11 upgraded) → fails
PC #2 (factory Win11, never had TurboTax) → fails
PowerShell works on the same machines
Browser works
Wireshark shows e-file endpoint never sends ServerHello
Then this is no longer a machine corruption issue.
This is almost certainly:
The AWS endpoint behind efile-tax-aws.api.intuit.com is selectively rejecting TurboTax Business 2025’s TLS fingerprint.
And since it fails on two separate Windows 11 systems, that strongly suggests:
A compatibility issue between TurboTax Business 2025 and current Windows 11 TLS behavior
Or an upstream policy change on Intuit/AWS side
Why OAuth Works but E-File Does Not
Different services behind the same domain can have different TLS policies.
Common pattern:
OAuth endpoint → wide compatibility
Entitlement endpoint → wide compatibility
E-file endpoint → stricter TLS policy
AWS ALBs can silently drop connections if:
Cipher order doesn’t match policy
Signature algorithms don’t match
TLS extension set differs
JA3 fingerprint not allowed
Client hello missing required extension
Your Wireshark capture already showed:
ClientHello → no ServerHello → retransmissions → FIN
That means the load balancer is discarding it.
Why PowerShell Works
PowerShell uses:
Native Schannel
Modern TLS 1.2 profile
Current cipher preference
Current extension set
TurboTax is likely using:
A different HTTP stack
Possibly WinInet
Possibly embedded .NET runtime
Possibly custom TLS wrapper
Which produces a slightly different ClientHello fingerprint.
That difference is enough for the e-file endpoint to reject it.
What This Means
This is not:
Your firewall
Your router
Norton
Windows Defender
Certificates
Time sync
WinHTTP
Domain policy
Network path
You have now eliminated all of those on two machines.
This is either:
A TurboTax Business 2025 bug
An Intuit/AWS TLS policy change
An IRS-side endpoint configuration issue
