Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com.
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email info@lemmy.world. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try !politicaldiscussion@lemmy.world or !askusa@discuss.online
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
I'm not aware of any Website that goes into detail. There are however books that go into detail of how Windows works internally: https://learn.microsoft.com/en-us/sysinternals/resources/windows-internals
In general to poke around in Windows the sysinternals tools distributed by Microsoft are great. The developer of the Sysinternals tools also gave some talks going through how he uses the tools to debug problems that occurred. Those are freely available on the web.
But in general it is was harder to find information about Windows, than linux. Most of the time when it comes to a problem with Windows a solution is posted, that dosen't explain how the solution was discovered. I found with Linux there is often more information given. And obviously with Linux you can just look at the code in the Kernel if you need to dig deep, with Windows that is not an option.
Definitely the Windows Internals books, I don't think there's anything else quite like it (wrt. Windows). I was also pleasantly surprised by de depth of Windows Via C/C++, which I expected to be one of those beginner tutorials distracted by language basics, but instead it's the opposite, just a really in depth dive into low level Windows APIs.
+1 to the Windows Internal books. Mark Russinovich knows the inside of Windows better than Microsoft did, to the point they picked him up.
The interesting thing you’ll discover when you start getting in to low level Windows internals is how close things are to Linux and how many parallels there are.
I won’t get started on the networking stack since both Microsoft and Linux stole that from BSD!
Also great is “The Case of the Unexplained” series by Mark Russinovich, author of Sysinternals, where he uses the various Sysinternals tools to solve real problems:
https://learn.microsoft.com/en-us/sysinternals/resources/webcasts