Windows Troubleshooting Platform Components
The Windows Troubleshooting Platform consists of three main components:
- Windows troubleshooting packs A collection of Windows PowerShell 2.0 scripts that diagnose and resolve problems. Because they are based on Windows PowerShell, administrators with scripting experience can create their own troubleshooting packs. You can use this capability to automate troubleshooting of problems unique to your environment, such as those relating to your internal applications or network.
- Windows troubleshooting engine The tool that runs the troubleshooting pack's Windows PowerShell scripts. The Windows PowerShell scripts within a troubleshooting pack use a set of developer interfaces provided by the troubleshooting engine to identify root causes, prompt the user for information, and mark problems as resolved.
- The troubleshooting wizard The primary user interface for the troubleshooting packs. The wizard first displays the publisher and description of the troubleshooting pack to the user. The Windows PowerShell scripts within the troubleshooting pack can prompt the user through the wizard interface. After the troubleshooting pack has completed, the wizard displays the troubleshooting results in a report. You can bypass the wizard interface to run the troubleshooting pack from a command line or use Extensible Markup Language (XML)-based answer files to run a troubleshooting pack automatically.
In this tutorial:
- Troubleshooting Hardware, Driver, and Disk Issues
- Windows 7 Improvements for Hardware and Driver Troubleshooting
- Windows Troubleshooting Platform
- Built-in Troubleshooting Packs
- Windows Troubleshooting Platform Components
- Creating Custom Troubleshooting Packs
- Running Troubleshooting Packs Remotely
- Windows 7 Reliability Monitor
- Windows 7 Resource Monitor
- Windows Memory Diagnostics
- Disk Failure Diagnostics
- Self-Healing NTFS
- Improved Driver Reliability
- Improved Error Reporting
- The Process of Troubleshooting Hardware Issues
- How to Troubleshoot Problems That Prevent Windows from Starting
- How to Troubleshoot Problems Installing New Hardware
- How to Troubleshoot Problems with Existing Hardware
- How to Troubleshoot Unpredictable Symptoms
- How to Diagnose Hardware Problems
- How to Use Device Manager to Identify Failed Devices
- How to Check the Physical Setup of Your Computer
- How to Check the Configuration of Your Hardware
- How to Verify That System Firmware and Peripheral Firmware Are Up to Date
- How to Test Your Hardware by Running Diagnostic Tools
- How to Simplify Your Hardware Configuration
- How to Diagnose Disk-Related Problems
- How to Use Built-In Diagnostics
- How to Use Reliability Monitor
- How to Use Event Viewer
- How to Use Data Collector Sets
- How to Use Windows Memory Diagnostics
- Memory Failures
- How Windows Automatically Detects Memory Problems
- How to Schedule Windows Memory Diagnostics
- How to Start Windows Memory Diagnostics When Windows Is Installed
- How to Start Windows Memory Diagnostics from the Windows DVD
- How to Configure Windows Memory Diagnostics
- How to Troubleshoot Disk Problems
- How to Prepare for Disk Failures
- How to Use ChkDsk
- ChkDsk Examples
- ChkDsk Syntax
- How to Use the Graphical ChkDsk Interface
- How to Determine Whether ChkDsk Is Scheduled to Run
- ChkDsk Process on NTFS Volumes
- How to Use the Disk Cleanup Wizard
- How to Disable Nonvolatile Caching
- How to Troubleshoot Driver Problems
- How to Find Updated Drivers
- How to Roll Back Drivers in Windows 7
- How to Use Driver Verifier
- How to Use the File Signature Verification
- How to Use Device Manager to View and Change Resource Usage
- How to Use Windows 7 System Restore
- How to Troubleshoot USB Problems
- How to Solve USB Driver and Hardware Problems
- Understanding USB Limitations
- How to Identify USB Problems Using Performance Monitor
- How to Examine USB Hubs
- How to Troubleshoot Bluetooth Problems
- Troubleshooting Tools
- DiskView
- Handle
- Process Monitor