Turbotax Tribulation and Triumph 2025

Yesterday was October 15th. Among other milestones, it’s the last day one can submit 2024 taxes upon obtaining an extension for filing. I’d planned to do them over the weekend, but a huge project blew into my life instead. So I ended up having to wait until the very last day to file. So yesterday, I experienced Turbotax tribulation and triumph: let me explain…

Surviving Turbotax Tribulation and Triumph 2025

I’ve been using TurboTax since before Intuit bought them in 1993. In fact, I think my accountant used them on my taxes even before then. And when she retired in the 1990s, she told me “you can do them on your own, if you stick with Turbotax.” She was right. And the program just keeps getting better at dealing with nearly all aspects of tax preparation and filing.

What amazes me most, right now, about this program is the connectors it offers into the accounts from whence most financial data flows anyway. I have a lot of activity from my brokerage account because I’m drawing on retirement accounts. Turbotax logs into the brokerage, sucks over all of my 1099s, and populates all the relevant fields for me. Same with bank accounts and such, too. Ditto for social security.

Because I’m self-employed, I get numerous 1099s from the companies I write for. Last year that included TechTarget, AskWoody, IDG (ComputerWorld), and others. Because I’ve been working for all of them for a while, Turbotax already knows their names, EINs and so forth. All I have to do is plug in the income numbers for 2024.

Shoot! My son’s in college and uses money from a 529(c) his grand-dad left him to cover tuition. Turbotax makes that easy, too.

Same as It Ever Was, But Better…

I remember watching my Dad shuffle mountains of paper to file his taxes when I was still living with my parents until 1970 or thereabouts. It used to take him a full day to work all the way through those papers and fill out all the necessary forms. But because Turbotax remembers what I did last year and automatically carries over refunds left over to cover the current year, I can usually get through the whole shebang in under 4 hours. That’s a big improvement.

Here in Windows-World data sources and sinks are increasingly connected. This can pose security headaches, but gosh: it makes working through complex data analysis exercises easier. Even the data-driven member of the eternal duo: Death and Taxes! Done for another year, hooray…

Facebooklinkedin
Facebooklinkedin

Gradual Rollout Strikes Notification Update

I guess it’s inevitable. Upon reading about how Windows 11 25H2 finally extends notification area pop-ups to non-primary displays on multi-monitor rigs, I checked my own production PC. This is, of course, the Asrock B550-based Ryzen 7 5800X with its dual Dell 2717 UHD displays. And wouldn’t you know it? Works on the primary, but not the secondary. As I check the KB5065789 announcement, I learn why. Once again, gradual rollout strikes notification update, and my PC is NOT in the forefront. Sigh.

Explaining Gradual Rollout Strikes Notification Update

If you look at the lead-in graphic, you can see the text from the afore-linked announcement. It reads:

​​​​​​​[Notification Center] New! The Notification Center functionality is now available on secondary monitors. To open it, select the date and time in the system tray on the taskbar. With the August 2025 non-security update (KB5064081), you can also show a larger clock with seconds above the calendar.

What that doesn’t show, alas, is that this occurs under the “Gradual Rollout” heading in that announcement. In turn, that means this feature is trickling out to 25H2 PCs, not all of them at once. I’ll hook a second monitor up to one of my Copilot PCs and see if that machine gets the new functionality. Nope, doesn’t work when I used HDMI to connect up a second monitor to the Lenovo Copilot+ AIO9i model, either.

It Remains the Hardest Part: Waiting…

I’m just going to have to wait for MS to flip whatever switch it takes to get one  or more of my 8 or so 25H2 PCs to attain this capability. I’m no stranger to this position in the Windows-World feature sweepstakes — that is, on the outside, looking in. Sigh again.

 

Facebooklinkedin
Facebooklinkedin

25H2 Notification Gets Time

Earlier this week, Windows 11 25H2 started making its way onto desktops via Windows Update (and other means). By now, I’ve got about half my eligible PCs updated. So far, it’s been a positive experience. Though others have reported issues  — knocks wood — so far, things at Chez Tittel have been hunky-dory. I read this morning at NeoWin that clock time is returning to the notification calendar in 25H2. If you look at the right-hand item in the lead-in screencap, you’ll see what I mean, as 25H2 notification gets time back.

What 25H2 Notification Gets Time Means

The left-hand side of the lead-in shows what the notification calendar looks like in 25H2 without a small settings change. This is the calendar that pops up when you click the date & time area to the far right of the notification area in Windows 11. Note that the left-hand side shows the weekday, month and date up top. The right-hand side shows time in hh:mm:ss AM/PM on one line, and then weekday, month and date below that. The difference is the presence or absence of the clock line.

How do you make this appear in 25H2? Good question! Here’s a step-by-step:

1. Click through Settings > Time & language > Date & time
2. Toggle Show time in Notification Center from Off (default) to On.

The next time you click on the date & time in notifications, you’ll see the time info above the typical weekday, month and date line. Easy-peasey, right?

Back from Windows 10, But I Never Missed It

If you read the Neowin story linked above (or other copious coverage on this tiny but often-requested UI change), you’ll get the sense that this little change is a big deal. And apparently it is, for some. But as a long-time and ongoing user of Helmut Buhler’s Gadgets from GadgetPack.net, I’ve been able to see a clock (and turn the second hand on) since Windows 8 came along just over 13 years ago. So it’s no big thing for me.

The clock gadget shows an analog clock to which I add the Windows machine name. Always on the desktop: handy!

But for others in Windows-World, it appears to satisfy a long-standing desire. Who am I to say them nay? Enjoy!

Facebooklinkedin
Facebooklinkedin

Winget Update Re-Raises Restart Requirement

Late last April, I wrestled with getting winget updates (aka Microsoft.AppInstaller) to “take.” That is, figuring out how to follow the advice to “restart the application” so the new version could take over. Turns out that nothing short of a restart seemed to guarantee that the update would run in PowerShell/Windows Terminal. Other techniques — killing all active processes, open/close WinTerm, and so forth — did not always suffice. A recent Winget update re-raises restart requirement, as I tried to move from version 1.26.430.0 to 1.26.510.0. It was the same darn thing all over again!

Why Winget Update Re-Raises Restart Requirement

If you read into my April blog post that offered explanations from two winget mavens, you’ll see that the winget upgrade waits until dangling APIs and runtime modules, plus pending package updates, all get resolved before completing its own upward move. For the chronically impatient — including yours truly — that makes a restart/reboot a surefire way to FORCE the changes through as a consequence of shutting down, then starting back up.

It worked last April, and it still works now. But a restart on my production PC with its numerous peripherals and 6 drives showing in File Explorer, is no small thing. It takes over a minute to shut down, and another 2-3 minutes to get through restart and to the desktop. So while it does the job, it also makes me wait rather longer than I’d really like to.

But hey: that’s the way things go in Windows-World sometimes. When things change, waiting for “out with the old, in with the new” can take some time. Maybe I should go get another cup of coffee…

Facebooklinkedin
Facebooklinkedin

Copilot+ PCs Hit 25H2

OK then, yesterday was Patch Tuesday. It included amidst its offerings the eKB enablement package KB5054156. All (both) of my current Copilot+ PCs got the upgrade. The Intel-based AIO got it automatically, with an after-hours upgrade. I just used the self-installing upgrade package (.msu) for ARM64 on the Snapdragon X based ThinkPad T14s Gen 6 laptop. The whole process: download, GUI install, post-GUI install and reboot to desktop took less than 2 minutes. I’ve been waiting for this for some while, so I’m glad that, finally, my Copilot+ PCs hit 25H2 version levels.

When Copilot+ PCs Hit 25H2, Then What?

Time to poke around in Settings (and elsewhere) to see what’s different and potentially new. I just learned that because the AIO doesn’t have a battery I don’t have access to the new Power Mode settings under Settings > System > Power & battery. Go figure!

On the Snapdragon X PC, however, the new “Best Power Efficiency” and “Best Performance” options do indeed appear. I opted into the latter (“Best Performance”) to see what impact it might have.

Learned something else amusing: because I’m remoting into the AIO, I can’t mess with Recall settings (nor, presumably, other AI stuff as well). Apparently, I need to set up Windows Hello authentication locally to make that happen… goes off to do so … OK now it’s working through RDP.

Adventures Ahead, For Sure!

Copilot tells me it’s gained new capabilities (as have other MS app) especially via Click to Do. There’s a new “help agent” in Settings that can actually manipulate Windows configurations and settings to some degree. All kinds of AI stuff all over the place. Now, I just need to find the time to actually DO this. And wouldn’t you know it? Right now, I’m swamped in paying work, so I have less time to learn and play. A welcome change of pace in Windows-World, but one that may frustrate me for a while…

Stay tuned: as soon as I have more time, I’ll share what I’m learning.

Facebooklinkedin
Facebooklinkedin

Beta Build Resets Browser Default: Edge

Notifications started popping like snack food when I logged into my Windows 11 Insider Preview Beta Channel PC this morning. You can see a whole string of them in the lead-in graphic. The generic and interesting error message is some variation of “An app caused a problem.” And bam! this Beta Build resets browser default: Edge is now in charge. Ask me if I’m happy about this. Answer: NO!!

Why Beta Build Resets Browser Default: Edge?

Good question! Google AI says:

An automatic default browser reset is a known issue in Windows 11 Insider Preview build 26120.6760. A potential workaround for this specific bug is to use the Settings app to manually re-select your preferred browser for all relevant file and link types.

But hey! I don’t have to like it, do I? I also went looking for a one-click reset tool, but couldn’t find anything useful. So off I hared to Settings > Apps > Default Apps, where I picked anything that came up Edge and changed it to Chrome. Sigh.

Here in Windows-World, it’s always something. Today it was an involuntary Edge default reset. I dealt with it, but I’d rather not have Windows 11 do that again for a while…

Facebooklinkedin
Facebooklinkedin

P3 Ultra Shows Amazing Interior Design

Yesterday, I upgraded the Lenovo ThinkStation P3 Ultra with mixed success. I was able to install and use a Samsung 990 EVO Plus NVMe SSD 4TB. I tried to boot after installing a pair of G.SKILL Ripjaws DDR5 32GB SO-DIMMs. Alas, the PC wouldn’t POST, so I had to send them back. I’ve ordered a pair of matching SK Hynix HMCG88AGBSA095N modules instead, and hopefully they’ll work when I stick them in next week. Throughout this in-and-out process, however the P3 Ultra shows amazing interior design. Let me explain…

How P3 Ultra Shows Amazing Interior Design

I was able to take this SFF PC apart and access the ports for M.2 SSDs and for the lower 2 memory slots without using a single hand tool. All the areas I needed to access, while covered with other components — fan housings, in fact — were easily accessed by releasing latches and swinging items out of the way. You can see this in the lead-in graphic for the NVMe fan housing.

I’ve worked on hundreds of PCs and laptops, including a dozen-plus SFF PCs. This particular model is nearly unique in making itself easy to work on and understand. Indeed, Lenovo has posted short videos that show how to access the chassis, M.2 drives,CPU fan, lower memory modules, and a whole bunch more. Combined, they made it dead easy for me to get things out of the way, and install/remove the components I was after.

The whole process took less than 2 minutes for each action (install NVMe, install 2 SO-DIMMs, remove 2 SO-DIMMs). It’s been an amazing trip so far.

Half-Way Benefits, with More to Come?

I’ve got the new NVMe drive working. I was able to create a full C: drive image backup — using Macrium Reflect X — on that new D: drive. Total time required: 00:37 (yes, that’s thirty-seven seconds, total, disk size of image: 45.57GB). SSD-to-SSD backup is definitely the way to go, and even better if — as is the case here — it’s from the primary (boot/system) internal SSD to a secondary internal SSD. Again: 37 seconds! Wow!!!

When the matching memory modules show up next week (I couldn’t get the PC to post using the G.SKILL Ripjaws DDR5 SO-DIMMs I ordered) I’ll try again. By ordering the same part number as what’s installed, I hope that the next try will succeed. Stay tuned: I’ll let you know.

Here in Windows-World, it’s always nice to find a great design that makes it easy to get in, add or remove components, then get out and back to work. Kudos to Lenovo for a truly magnificent design. I love it!!

Facebooklinkedin
Facebooklinkedin

WTC = What the Clunk?

I bought my first hard disk back in the late 1980s. If memory serves it was a 300MB drive with 8″ platters. It cost about US$1,000. It attached via SCSI to a Macintosh SE desktop, with its 9″ CRT (512×342 resolution). Why tell you all this? Because that old drive was literally a clunker: as it started, or read data, or shut down it would emit a series of thunks and clunks you could hear in the next room. I just added a Seagate IronWolf 12TB NAS drive to my production desktop. This morning as I booted up I found myself saying WTC = What the Clunk? as it started up for the day.

Why I’m Saying WTC = What the Clunk?

I just looked up the innards of this new spinning disk. It’s got 8 platters, each with 2 heads and a total of 1.5GB of capacity. And  those heads and platters are sealed into a helium filled chamber to keep them as quiet as possible. Even so, spinning up apparently takes some mechanical oomph because I heard at least a trio of discernible clunks as the unit spun up this morning.

It had been so long since I’d heard those sounds, I’d forgotten what they sounded like. Now, I’m reminded of what I used to listen to all the time nearly 40 years ago: a steady series of thumps, clunks and thunks as big disks went about what — by today’s standards — can only be called “small business.” Fortunately, as the IronWolf goes about its much, much bigger business it only emits an occasional sound. If I use my imagination, I can hear it as a chuckle at the depth of my disk drive recollections.

I won’t even go back to the earlier days when I worked on Data General and DEC PDP minicomputers that used 14″ platters. Those came (and went) as removable disk packs. They made some industrial strength noise, for sure, in the days before Windows-World came along. But that’s a whole ‘nother story…

Facebooklinkedin
Facebooklinkedin

Remote Desktop Connection LSA Error

Over the past couple of years, I’ve noticed that establishing an RDP session from my primary desktop to other PCs sometimes fails under specific circumstances. I’m researching a story about this for Mayank Pamar at WindowsLatest, so keep an eye out for that opus. It’ll probably hit next week. When I attempt to get into some of my Windows 11 PCs (the only kind of physical PC I have any more), my login will occasionally be refused if I use a Microsoft Account (MSA). Indeed I’ll see a Remote Desktop Connection LSA error that reads “The Local Security Authority cannot be contacted.”

What Causes Remote Desktop Connection LSA Error?

Interestingly, there are a number of possible causes. Some are easy to fix, others fall on third parties. Here’s a partial list:

  • OS can’t validate credentials, particularly MSA logins (the most common and obvious reason, but one users cannot easily fix themselves)
  • Secure channel negotiation (to exchange credentials) fails
  • Time sync or DNS resolution fails
  • Credential policies are somehow misconfigured

Time sync and DNS stuff is probably the most approachable, so they’re worth trying. For the former that means Settings > Time & Language > Date & time > Sync now (under Additional Settings). For the latter, it’s only meaningful if using manual DHCP assignment, in which case Setting > Network & Internet > Ethernet or Wi-Fi > Edit DNS Settings > define preferred and backup DNS server addresses. Most users will get their DNS server assignments via DHCP.

The other items are a bit more convoluted. I’ll get to them in my upcoming story. Here in this brief blog, I’ll “leave them as an exercise for the reader” in the classic ploy used to avoid heavy lifting in so many, many textbooks I’ve read over the years…

A Typical (and Useful) Workaround

If I can’t get into a PC using my MSA, I’ll set up a local account on the affected machine with admin privileges and use that to RDP into the machine instead. This might cause issues on machines where you want or need access to account-speicific files or data (e.g. the associated C:\users\<name> folder hierarchy). But otherwise it works OK. In a small and unscientific survey of my local fleet, I’ve had to do this on just under half the machines (4 out of 9), most of which are running Insider Preview releases (and thus, have their foibles).

Here in Windows-World, if you can’t do things the way you want to, you must sometimes do them some other way. Obtaining RDP access to some of my test and experimental PCs puts me in those shoes from time to time. So it goes!

Facebooklinkedin
Facebooklinkedin

Wi-Fi Kernel Dump Error Is Neutrino-Like

Here’s something interesting I’ve never seen before. The other day, I was trying to update the recently re-awaked ThinkStation P3 Ultra. Among the many items in the queue, through Lenovo Vantage, was an Intel Wireless LAN Driver. Indeed the same driver also showed up in the Intel Driver and Support Assistant. Despite repeated efforts through both facilities, the driver update always failed. This morning, I observed traces of those failures in Reliability Monitor. This Wi-Fi Kernel dump error is neutrino-like in that it registers in Relimon, but doesn’t diminish the Reliability Index (see the lead-in graphic).

More on Why a Wi-Fi Kernel dump error is neutrino-like

The error code in the Relimon details cite to the following string:LKD_0x41A1_Netwtw08!unknown_function. Online research tells me two useful things about this info:

1. It’s tied to Intel’s wireless driver (confirms what I’d suspected)

2. the LKD stands for Live Kernel Dump, indicating that Windows detected a hardware-related fault serious enough to provoke a snapshot of the error, but that it did NOT crash the system

The lack of a crash explains why Relimon imposes no charge on its Reliability Index even though the event is labeled “Critical” of type “Hardware error.” Shoot! I didn’t even know this was possible. Very interesting!

What About that Wi-Fi Driver?

A quick peek into Device Manager showed me that the Wi-Fi 6E AX211 160MHz driver was throwing a “device cannot start (Code 10)” error. Because both Lenovo Vantage and Intel DSA weren’t fixing things, I decided to go clean and start over. I right-clicked the device in DevMgr, then selected Uninstall from the pop-up menu. After a reboot, I visited the Lenovo Downloads & Software page, entered the Serial# for the P3 Ultra, and grabbed the latest Wi-Fi driver package. After installation, DevMgr obligingly reports that “The device is working properly.” Problem solved!

I figure when two update tools both choke on a driver, it’s time to remove the offending software, download, and try again. Here in Windows-World, even drastic measures need the added protection of “fingers crossed.” Thus, I’m glad that strategy worked.

 

Facebooklinkedin
Facebooklinkedin

Author, Editor, Expert Witness