When you tinker and debug something on windows, you usually have little idea of what went wrong and can derive very little from the experience. At least that was the case back when I still used windows, in the XP and vista days.

I don’t think that is completely fair, I feel like the reason is more that on Linux no easy to follow “solutions” to as many problems as on Windows exist. When you have a problem on Linux you most of the time have to dive deeply into the technical details. On windows it’s often enough to search for a solution on the internet and follow the first tutorial (not the stupid SEO garbage sites). And once whatever problem you had is gone you don’t go and try to understand why the solution worked.

That also really annoyed me a lot when I had to fix Windows problems for work, because I really like to understand why something is working or not. And after some research I actually found Sysinternals which are tools that help you dig deeper into Windows inner workings. There are also some wonderful videos on how to use those tools available by the author of those tools. And there are also books available both on how to troubleshoot with the tools and on how Windows internally works.

Edit: fiexd tyops ;)