Issue: Windows 11 boot failure with "No bootable device found" error
Root Cause: BIOS boot order was changed or reset, causing the system to attempt booting from a non-bootable device (likely USB or network) before checking the internal hard drive containing the OS Boot Manager.
Why It Occurred: Common triggers include Windows updates, BIOS resets, CMOS battery issues, or accidentally changing boot priority when a USB device was connected.
Tech Name: Observer Initials:
Date:
| Criterion | Score (0-5) | Notes |
|---|---|---|
| 1. Information Gathering Asked appropriate questions to identify OS, manufacturer, and symptoms. Confirmed error message details before proceeding. |
_____/5 | |
| 2. Technical Accuracy Correctly identified boot order issue. Provided accurate manufacturer-specific boot key. Verified OS Boot Manager presence. |
_____/5 | |
| 3. Communication Clarity Gave clear, step-by-step instructions. Used appropriate technical language without overwhelming user. Confirmed understanding. |
_____/5 | |
| 4. Problem Resolution Guided user to successful boot. Explained root cause in understandable terms. Addressed user concerns about deleted files. |
_____/5 | |
| 5. Professionalism & User Education Maintained courteous tone. Provided preventive advice. Built user confidence. Closed call appropriately. |
_____/5 | |
| TOTAL: _____/25 | ||
Additional Comments:
Issue: Windows 10 desktop experiencing slow network connectivity despite hardwired ethernet connection
Root Cause: DHCP client failure resulting in APIPA (Automatic Private IP Addressing) assignment of 169.254.x.x address. Computer unable to communicate with DHCP server on router to obtain valid IP configuration.
Why It Occurred: Common causes include temporary DHCP server unavailability during boot, network cable disconnect/reconnect, router restart without successful DHCP lease, or Windows network service glitch.
net stop dhcpipconfig /releaseipconfig - should show 169.254.x.xnet start dhcp then ipconfig /renewTech Name: Observer Initials:
Date:
| Criterion | Score (0-5) | Notes |
|---|---|---|
| 1. Problem Isolation Asked about other devices to determine if issue was local or network-wide. Gathered connection type and OS information. |
_____/5 | |
| 2. Diagnostic Command Usage Correctly guided user to Command Prompt. Properly utilized ipconfig command. Identified APIPA address as root cause. |
_____/5 | |
| 3. Solution Implementation Provided correct syntax for ipconfig /release and /renew. Verified successful DHCP lease. Confirmed connectivity restoration. |
_____/5 | |
| 4. Technical Explanation Clearly explained APIPA concept. Described DHCP function in user-friendly terms. Answered follow-up questions accurately. |
_____/5 | |
| 5. User Guidance & Support Provided clear step-by-step command line instructions. Confirmed user actions before proceeding. Empowered user with knowledge for future. |
_____/5 | |
| TOTAL: _____/25 | ||
Additional Comments:
Issue: QuickBooks application crashes immediately after opening on Windows 10
Root Cause: A recent Windows cumulative update (KB5034441) introduced a compatibility conflict with the QuickBooks application runtime, causing it to crash on launch.
Why It Occurred: Windows cumulative updates can modify system libraries, .NET frameworks, or Visual C++ redistributables that third-party applications depend on. When the updated components are incompatible with the application's expected versions, crashes occur.
Tech Name: Observer Initials:
Date:
| Criterion | Score (0-5) | Notes |
|---|---|---|
| 1. Information Gathering Asked about application name, OS version, and timeline. Identified correlation between updates and crash onset. |
_____/5 | |
| 2. Technical Accuracy Correctly identified Windows Update as probable cause. Ruled out permissions first. Targeted specific KB for removal rather than rolling back all updates. |
_____/5 | |
| 3. Communication Clarity Gave clear navigation instructions for Settings. Explained why each step was necessary. Used appropriate technical language. |
_____/5 | |
| 4. Problem Resolution Successfully guided user to uninstall problematic update. Confirmed application worked after restart. Addressed deadline pressure appropriately. |
_____/5 | |
| 5. Professionalism & Preventive Advice Maintained calm under user's stress. Provided actionable prevention steps (pause updates, check vendor). Closed interaction professionally. |
_____/5 | |
| TOTAL: _____/25 | ||
Additional Comments:
Issue: Windows 11 desktop experiencing repeated BSOD (Blue Screen of Death) with stop code DRIVER_IRQL_NOT_LESS_OR_EQUAL after installing a new NVIDIA RTX 4070 graphics card
Root Cause: An incompatible or buggy GPU driver is attempting to access an invalid memory address at an elevated IRQL (Interrupt Request Level), causing a kernel-level exception that triggers the blue screen crash.
Why It Occurred: The user installed the latest NVIDIA driver package, which may contain a bug specific to their hardware revision, motherboard chipset, or BIOS version. Driver version incompatibilities are common with newly released GPU models or freshly published driver packages that have not been widely tested across all configurations.
Tech Name: Observer Initials:
Date:
| Criterion | Score (0-5) | Notes |
|---|---|---|
| 1. Safe Mode Knowledge Correctly guided user through the full Safe Mode boot path. Explained purpose of Safe Mode (minimal drivers). Knew alternative entry methods (Shift+Restart, WinRE). |
_____/5 | |
| 2. Device Manager Usage Navigated directly to Display adapters. Identified the yellow exclamation mark as a device error indicator. Accessed driver properties correctly. |
_____/5 | |
| 3. Driver Rollback Procedure Correctly used Roll Back Driver feature. Explained what rollback does and why it resolves the issue. Mentioned Uninstall Device as an alternative if rollback is unavailable. |
_____/5 | |
| 4. Communication Clarity Gave clear, sequential instructions for each step. Explained BSOD stop code meaning in understandable terms. Confirmed user actions before proceeding to next step. |
_____/5 | |
| 5. Professionalism & User Education Maintained reassuring tone during a stressful situation. Provided preventive advice about future driver updates. Empowered user with Safe Mode knowledge for self-help. Closed interaction professionally. |
_____/5 | |
| TOTAL: _____/25 | ||
Additional Comments:
Issue: Windows 10 computer exhibiting multiple malware symptoms: persistent pop-up advertisements, browser homepage hijacking, disabled Windows Defender, and severe performance degradation
Root Cause: Malware infection consisting of adware, PUPs (Potentially Unwanted Programs), and at least two Trojan components, delivered via a bundled freeware installer (free video converter downloaded from an untrusted website). The malware bundle installed multiple components including a browser hijacker (SearchBaron), a desktop notification adware agent (DesktopNotify Pro), and a fake system utility (SystemBoost Helper) that disabled Windows Defender to prevent detection and removal.
Why It Occurred: The user downloaded free software from an unverified source. The installer used a deceptive "express install" process that silently bundled multiple malicious programs alongside the legitimate video converter. The lack of custom installation review allowed all bundled components to install without the user's informed consent.
gpedit.msc → Computer Configuration → Administrative Templates → Windows Components → Microsoft Defender Antivirus → Turn off Microsoft Defender Antivirus → Enabled)Tech Name: Observer Initials:
Date:
| Criterion | Score (0-5) | Notes |
|---|---|---|
| 1. Threat Containment Immediately directed user to disconnect from the network. Explained the importance of isolation to prevent data exfiltration. Chose appropriate Safe Mode option (with Networking). |
_____/5 | |
| 2. Malware Identification Correctly identified symptoms as malware indicators. Asked about recent downloads to determine infection vector. Recognized disabled antivirus as a sign of active malware defense evasion. |
_____/5 | |
| 3. Removal Methodology Followed proper malware removal sequence: isolate, Safe Mode, remove suspicious programs, scan with anti-malware tool, quarantine threats, verify removal, reset browser, confirm AV operational. |
_____/5 | |
| 4. User Education on Prevention Explained how bundled software works. Advised on safe download practices and custom installation options. Recommended password changes from a clean device. Provided clear future prevention steps. |
_____/5 | |
| 5. Professionalism & Composure Maintained calm and reassuring tone despite severity of infection. Did not blame user for the infection. Managed the multi-step process without rushing or overwhelming the user. Closed interaction professionally. |
_____/5 | |
| TOTAL: _____/25 | ||
Additional Comments:
net stop spooler and press Enter. Wait for it to confirm the service has stopped.net start spooler and press Enter. This restarts the service fresh.services.msc → find Print Spooler → right-click → Restart. The command line method is faster for phone support.net stop spooler and net start spooler sequence is your go-to fix.Issue: User sends multiple documents to a network printer but nothing prints, despite the printer showing as online and ready.
Root Cause: The Windows Print Spooler service became hung due to corrupted or failed print jobs stuck in the queue. These blocked jobs prevented all subsequent print requests from being processed and sent to the printer.
Why It Occurred: A corrupted print job (often caused by a large or complex document, a momentary network interruption during transmission, or a driver incompatibility) entered the queue and failed to complete or cancel cleanly. The spooler continued attempting to process the failed job, blocking the pipeline. This is one of the most common printing issues in enterprise environments.
services.msc and locate the Print Spooler serviceC:\Windows\System32\spool\PRINTERSnet stop spooler followed by net start spooler from an elevated Command Promptservices.msc), printer management, and command-line service control (net stop/net start)Tech Name: Observer Initials:
Date:
| Criterion | Score (0-5) | Notes |
|---|---|---|
| 1. Problem Identification Gathered printer model, OS, and connection details. Verified physical printer status. Asked about other affected users to determine scope. |
_____/5 | |
| 2. Print Queue Management Directed user to open and inspect the print queue. Identified stuck/failed jobs as the root cause. Properly guided cancellation of all queued documents. |
_____/5 | |
| 3. Service Restart Procedure Correctly instructed user to open an elevated Command Prompt. Provided accurate net stop spooler and net start spooler commands. Confirmed service restarted successfully. |
_____/5 | |
| 4. Default Printer Verification Checked that the correct printer was set as default. Verified the fix with a test print. Confirmed output reached the physical printer. |
_____/5 | |
| 5. Professionalism Under Time Pressure Acknowledged the user's deadline and urgency. Maintained a calm, efficient pace. Provided preventive advice without rushing the interaction. Closed the call professionally. |
_____/5 | |
| TOTAL: _____/25 | ||
Additional Comments:
lusrmgr.msc on the machine or domain controller. Navigate to Users, find the account, open Properties, and uncheck "Account is locked out" on the Account tab.Issue: User receives "The referenced account is currently locked out and may not be logged on to" error and cannot access their Windows workstation.
Root Cause: The account exceeded the failed login attempt threshold defined in the local or domain account lockout policy (typically 3–5 attempts). The lockout was triggered by a combination of Caps Lock being enabled during manual login attempts and stale credentials stored on a mobile device repeatedly failing authentication in the background.
Why It Occurred: Account lockout policies exist to defend against brute-force password attacks. In this case, the user changed their workstation password two weeks prior but never updated the saved credentials in their phone's email application. The phone continuously attempted to authenticate with the old password, consuming failed-attempt counts. When the user arrived and mistyped their password due to Caps Lock, the remaining attempts were exhausted and the account locked.
secpol.msc (Local Security Policy)lusrmgr.msc → Users → right-click user → Properties → uncheck "Account is locked out"lusrmgr.msc (Local Users and Groups) or Active Directory Users and Computers to find the account, open Properties, and uncheck "Account is locked out"lusrmgr.msc (Local Users and Groups), understanding account properties and lockout statusTech Name: Observer Initials:
Date:
| Criterion | Score (0-5) | Notes |
|---|---|---|
| 1. Identity Verification (Security) Requested full name, employee ID, department, and username before making account changes. Treated the interaction as a potential social engineering scenario by following verification protocol. |
_____/5 | |
| 2. Account Unlock Procedure Correctly used lusrmgr.msc to locate the user account. Unchecked the "Account is locked out" property. Confirmed the account was unlocked before asking the user to log in. |
_____/5 | |
| 3. Root Cause Investigation Asked about Caps Lock status, number of failed attempts, and recent password changes. Identified stale credentials on the mobile device as a contributing factor. Did not simply unlock and move on. |
_____/5 | |
| 4. Policy Explanation Explained why account lockout policies exist (brute-force protection). Described the failed-attempt threshold clearly. Connected the policy to real-world security without alarming the user. |
_____/5 | |
| 5. User Education Advised updating passwords on all devices after a change. Warned about Caps Lock awareness. Provided actionable, memorable guidance the user can apply independently in the future. |
_____/5 | |
| TOTAL: _____/25 | ||
Additional Comments:
chrome://extensions in the address bar.Issue: Windows 11 desktop takes 10+ minutes to reach the desktop, progressively worsening over two years of ownership
Root Cause: Startup bloat from accumulated software installations. Multiple high-impact applications (Spotify, Discord, Steam, Adobe Updater, iTunesHelper, Corsair utility) registered as startup items, all competing for CPU, memory, and disk I/O during boot. Compounded by low disk space (only 9% free on a 256 GB drive) limiting virtual memory and temp file operations.
Why It Occurred: Most consumer software silently enables auto-start during installation. Over two years of installing applications, the startup queue grew unchecked. The user was unaware that these programs were loading at boot because no single installation caused a dramatic slowdown—the degradation was gradual. Low disk space from accumulated files, cached updates, and temporary data further compounded the problem.
chrome://extensions and remove unused or suspicious extensions that consume memory and CPU.Tech Name: Observer Initials:
Date:
| Criterion | Score (0-5) | Notes |
|---|---|---|
| 1. Performance Diagnosis Approach Asked about system age, OS version, and software installation history. Correctly identified startup bloat as the probable cause based on the gradual degradation pattern. |
_____/5 | |
| 2. Task Manager Proficiency Guided user to open Task Manager via keyboard shortcut. Navigated to Startup tab. Correctly interpreted Startup impact column and identified non-essential items. |
_____/5 | |
| 3. Startup Optimization Clearly distinguished between essential and non-essential startup items. Disabled appropriate programs without affecting security or OS-critical services. Explained that disabling does not uninstall. |
_____/5 | |
| 4. Disk Space Management Checked drive capacity and identified low free space as a contributing factor. Guided user through Disk Cleanup utility. Addressed browser extension bloat as additional overhead. |
_____/5 | |
| 5. User Education on Prevention Explained how programs add startup entries during installation. Recommended periodic Startup tab reviews. Gave clear preventive maintenance guidance to avoid future recurrence. |
_____/5 | |
| TOTAL: _____/25 | ||
Additional Comments:
ping 8.8.8.8 and press Enter. This confirms your network stack is functioning properly.wf.msc in the Windows search bar and open it. This gives us the advanced firewall configuration.wf.msc opens Windows Defender Firewall with Advanced Security. This is the granular interface—not the basic Control Panel firewall view. It shows all inbound and outbound rules with their actions.Issue: VPN client (GlobalProtect) fails to connect from a remote user's home office with "Connection failed—connection timed out" error, despite normal internet connectivity
Root Cause: A Windows Defender Firewall outbound rule was added that blocks VPN protocol ports. The rule titled "Block VPN Ports" prevents the VPN client from establishing an encrypted tunnel to the corporate VPN gateway. Typical VPN ports affected include UDP 500 and UDP 4500 (for IKEv2/IPsec) or TCP 443 (for SSL VPN).
Why It Occurred: The blocking rule was introduced during a Windows update or security policy push over the weekend. Windows cumulative updates can occasionally reset or modify firewall rules, and third-party security software or group policy objects can also inject blocking rules. The user was unaware of the change because it happened silently in the background.
wf.msc (Windows Defender Firewall with Advanced Security)ping 8.8.8.8 to confirm the network stack is functional and internet access is unaffectedwf.msc, navigate to Outbound Rules, sort by Action, and identify any rules blocking VPN-related ports (UDP 500, 4500, TCP 443)Tech Name: Observer Initials:
Date:
| Criterion | Score (0-5) | Notes |
|---|---|---|
| 1. Connectivity Verification Confirmed internet connectivity before investigating VPN-specific issues. Used ping to validate network stack. Methodically ruled out basic network problems first. |
_____/5 | |
| 2. VPN Error Analysis Directed user to find detailed error information in the VPN client. Correctly interpreted "connection timed out" and "unable to establish tunnel" as indicators of blocked traffic rather than authentication failure. |
_____/5 | |
| 3. Firewall Troubleshooting Guided user to wf.msc and navigated to Outbound Rules. Identified the blocking rule by sorting on the Action column. Disabled the rule before deleting to test the theory. |
_____/5 | |
| 4. Security-Conscious Approach Checked credentials and password rotation before escalating. Disabled the rule (rather than immediately deleting) to preserve evidence. Recommended contacting the network team for proper policy configuration. |
_____/5 | |
| 5. Remote User Support Skills Maintained a calm and reassuring tone with a stressed remote worker. Gave clear step-by-step guidance for unfamiliar tools. Empowered user with knowledge to self-diagnose if issue recurs. |
_____/5 | |
| TOTAL: _____/25 | ||
Additional Comments:
chrome://extensions now... Oh wow. There are extensions here I've never seen before. "SearchAssist Pro," "QuickDeals Saver," "BrowseSecure," and "SmartTab Redirect." I only recognize my ad blocker and my password manager.chrome://extensions in the address bar.appwiz.cpl in the Windows search bar to get there directly.Issue: Chrome browser on Windows 10 exhibits homepage hijacking, search redirects to ad-laden pages, and unauthorized toolbar/extension installations
Root Cause: A Potentially Unwanted Program (PUP) was bundled with a freeware PDF converter downloaded from an untrusted third-party site. The PUP installed a browser hijacker ("SearchAssist Browser Companion") and multiple malicious Chrome extensions (SearchAssist Pro, QuickDeals Saver, BrowseSecure, SmartTab Redirect) that modified the browser's homepage, default search engine, new tab page, and injected ad-redirect scripts.
Why It Occurred: The user downloaded freeware from a third-party download site and clicked through the installer without reading each screen. The installer included pre-checked opt-in checkboxes for bundled software that the user inadvertently accepted. This is a common distribution method for PUPs and browser hijackers—they are not technically malware in the traditional sense but operate in a legal gray area by obtaining minimal "consent" through deceptive installer design.
searchassist-home.com) via Settings → On startup → Open a specific pagechrome://extensions and remove all unrecognized or suspicious extensionsappwiz.cpl), sort by installation date, and uninstall the source freeware and any bundled companion programsTech Name: Observer Initials:
Date:
| Criterion | Score (0-5) | Notes |
|---|---|---|
| 1. Threat Identification Correctly recognized symptoms as browser hijacker. Asked about recent downloads to establish the infection vector. Identified the freeware PDF converter as the source. |
_____/5 | |
| 2. Extension & PUP Removal Guided user to chrome://extensions to audit and remove malicious extensions. Used Programs & Features to identify and uninstall the bundled PUP alongside the source freeware. |
_____/5 | |
| 3. Browser Reset Procedure Directed user to reset Chrome settings to default. Explained what the reset does and does not affect (bookmarks/passwords preserved). Ensured homepage and search engine were restored. |
_____/5 | |
| 4. Security Scan Execution Instructed user to run a full Windows Defender scan rather than a quick scan. Explained the importance of checking for residual malicious files after manual cleanup. |
_____/5 | |
| 5. Prevention Education Explained bundleware and how PUPs are distributed through freeware installers. Recommended safe alternatives and official download sources. Advised using Custom/Advanced installation to avoid bundled extras. |
_____/5 | |
| TOTAL: _____/25 | ||
Additional Comments: