TaxAct's 2025 tax season has been a complete shitshow. Their support page was down for weeks in April, login servers crashed constantly, and the desktop app has some WebView2 bug that breaks everything on Windows 11. But here's the thing - most of these problems have actual solutions if you know what's really going wrong.
The Login System Is Fundamentally Broken
TaxAct's authentication system can't handle the load. They're using some janky session management that times out constantly and doesn't play nice with modern browsers. The "session expired" error happens even when you just logged in 5 minutes ago.
What's actually happening: Their load balancer is dropping active sessions randomly. When you log in, you might get connected to Server A, but your next page request goes to Server B, which doesn't know you exist.
The real fix: Use browser developer tools (F12) and look at the Network tab. If you see 401 errors on AJAX requests to api.taxact.com, that's the session dropping. Clear all taxact.com cookies and localStorage, then log in fresh. This forces you to get a clean session on their least-loaded server.
I spent 3 hours debugging this shit in March when my client's returns needed to be filed. The "contact support" option was useless because their support system was also broken. Tried calling and got disconnected twice. Just gave up and figured it out myself.
WebView2 Runtime Hell on Windows
Microsoft updated WebView2 in late 2024 and it broke compatibility with TaxAct's desktop application. The error message says "WebView2 runtime not found" but that's misleading - the runtime is there, it's just the wrong version.
Technical details: TaxAct built their desktop app against WebView2 Runtime 109.x.x (I think), but Microsoft's auto-updater pushed everyone to 118.x.x in December 2024. The COM interface changed and TaxAct's code expects the old one. Classic Microsoft move.
Why TaxAct support can't help: They don't control the WebView2 runtime and Microsoft doesn't test backwards compatibility with random tax software. So both companies blame each other while users can't file their taxes.
The nuclear solution that actually works:
- Uninstall TaxAct completely (use Revo Uninstaller to get ALL the files)
- Download the "Evergreen Standalone Installer" of WebView2 Runtime from Microsoft
- Install it manually
- Restart Windows (this matters more than you think)
- Install TaxAct fresh and it'll detect the correct runtime
Takes about 20 minutes but fixes it permanently. I've done this on 8 different computers - Dell OptiPlex, HP Pavilion, bunch of random laptops - works every time. Well, except my neighbor's Dell Inspiron 3000 that has some weird BIOS setting blocking WebView2 installs. Still haven't figured that one out.
The Import Feature Randomly Fails
TaxAct's document import (W-2s, 1099s) works great until it doesn't. The failure modes are:
"Connection timeout" - Their import service is hosted separately and goes down independently of the main site. Usually comes back in a few hours.
"Invalid file format" - Banks and employers sometimes generate PDFs that look perfect but have mangled metadata. TaxAct's parser is pickier than TurboTax's.
"Unable to extract data" - The OCR system craps out on scanned documents or documents with unusual fonts/formatting.
Real solutions:
- Download your tax docs as both PDF and CSV if possible. CSV imports almost never fail.
- If PDF import fails, try printing to PDF from the original (this cleans up the metadata)
- For W-2s, manually entering is often faster than debugging import problems
- Keep original documents because TaxAct's import error messages are useless for troubleshooting
Browser Compatibility Is a Nightmare
TaxAct's web app works differently across browsers because they're using old JavaScript libraries. Chrome has issues, Firefox breaks randomly, Safari loses sessions.
Browser-specific problems I've encountered:
Chrome: Script errors on complex forms like Schedule C. Disable hardware acceleration in Chrome settings to fix.
Firefox: File upload dialogs don't work in private browsing mode. Use regular browsing or switch browsers.
Edge: Sometimes loads blank pages. Add taxact.com to trusted sites.
Safari: Session timeouts happen way faster. Disable "Prevent cross-site tracking" for taxact.com.
The browser that actually works: Firefox ESR (Extended Support Release). It's stable, doesn't auto-update constantly, and TaxAct's developers actually test against it.
Why Peak Season Performance Is So Bad
TaxAct's infrastructure can't handle the load spikes. They probably have great performance 9 months of the year, but March and April turn their servers into molasses.
Peak congestion times (avoid these if possible):
- Weekends in March and April (everyone procrastinates the same way)
- 7-10 PM Eastern (after work, before bed)
- Last week before deadline (total chaos)
Best performance windows:
- Weekday mornings 6-9 AM Eastern
- Lunch hours 11 AM - 2 PM Eastern
- Late night after midnight Eastern
I timed my 2024 Schedule C return: 27 minutes on a Sunday afternoon in March vs 8 minutes at 6:30 AM Tuesday. Same exact data entry. The server performance difference is insane.
When to Just Give Up on TaxAct
Look, I've used TaxAct for 4 years and saved hundreds compared to TurboTax. But there are times when the technical problems aren't worth it:
Deadline panic: If it's April 14th and TaxAct is broken, just bite the bullet and use TurboTax or FreeTaxUSA. Your time and stress aren't worth saving $50.
Complex business returns: TaxAct's business features work fine when they work, but debugging K-1 import failures at midnight isn't fun.
No tech skills: If this troubleshooting guide looks like hieroglyphics, pay extra for software that "just works" or hire a human preparer.
The reality is that TaxAct's technical problems are fixable if you know what you're doing, but they shouldn't exist in the first place for software you're paying $100+ for.