╔═══════════════════════════════════════
║ Welcome!
I am Christopher Etter, a Professional Services consultant.
Because you are here, I welcome you as my customer! These documents are free for you to use. I work diligently to serve you with material such as this. I would appreciate it if PSPRO (professionalservices.pro), my name, and this 'Credits' section remain attached to these works so that I accrue name recognition via your success and peer recommendation. Thank you very much, and I hope these documents help you solve your current information technology issue!
┌───────────────────────────────────────
│ Before You Begin
These documents are text-based in order to be mobile-friendly and printer-friendly. Glitz & glam are fine for large monitors, but in a pinch you may legibly use a phone display with these documents to troubleshoot the computers in front of you. Multiple monitors on the troubled computers are not required, and here you won't find graphics that your phone squeezes so badly it takes zooming, scrolling, and a jeweler's loupe to see them.
No one can troubleshoot a computer without administrative permissions. Most troubleshooting tools will not run without them. All documents assume that your user account has local administrative permissions on the computers you are troubleshooting. If you are at a customer site where permissions are not granted, ensure that the customer knows that until you have them you are only being paid to speculate.
These documents assume that the customer is not blocking use of Sysinternals. There are other methods of performing procedures documented here that do not rely on use of Sysinternals. You can query the Internet for alternative tools/methods. I explain them using Sysinternals because that is the easiest. Encourage the customer to permit use of Sysinternals during your engagement, even if they restrict them only to the accounts you will use.
┌───────────────────────────────────────
│ Instructions
• These 'Instructions' documents are 'click-by-click' guides to getting something done in Microsoft Windows.
• Instructions--Antimalware.On-Access.Scanner.Test--Self-Contained
• Instructions--Debugging--Application.Verifier
• Instructions--Debugging--DebugView
• Instructions--Debugging--Driver.Verifier
• Instructions--Debugging--Dump.Configuration.and.Initiation
• Instructions--Debugging--Global.Flags
• Instructions--Debugging--WinDBG--Configuration
• Instructions--Debugging--Windows.Error.Reporting--Process.Dump.Configuration
• Instructions--Debugging--Windows.Error.Reporting--TestWER--JIT.Debugger.Test
• Instructions--Debugging--Windows.Performance.Recorder
• Instructions--driverview.exe
• Instructions--listdlls.exe
• Instructions--PKI--CAPI2.Log
• Instructions--procmon.exe
• Instructions--procexp.exe
• Instructions--procdump.exe
• Instructions--sigcheck.exe
• Instructions--SYSTEM.Access
• Instructions--tasklist.exe--Find.Injections
┌───────────────────────────────────────
│ Articles
• These 'Articles' documents are in-depth looks at something about Microsoft Windows or a third-party application.