DevGex Search

This article explores two primary technical approaches in C# for retrieving installed applications on Windows systems: querying the registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and using Windows Management Instrumentation (WMI) with Win32_Product queries. It provides a detailed analysis of implementation principles, code examples, performance differences, and use cases to help developers choose the optimal solution based on practical needs.

This article explores technical methods for obtaining detailed information about serial port devices in C# applications. By analyzing Stack Overflow Q&A data, particularly the best answer (Answer 5) and related discussions, it systematically compares the limitations of using SerialPort.GetPortNames() and delves into advanced solutions based on Windows Management Instrumentation (WMI) and registry queries. The article explains in detail how to query serial port descriptions, manufacturers, device IDs, and other metadata through Win32_PnPEntity and Win32_SerialPort classes, providing complete code examples and error-handling strategies. Additionally, it discusses handling special devices such as Bluetooth serial ports and USB virtual serial ports, as well as how to obtain more comprehensive port information via the registry. These methods are applicable to .NET 2.0 and later versions, helping developers implement functionality similar to Device Manager and enhance application usability and debugging capabilities.

This article provides an in-depth exploration of how to associate SID values under HKEY_USERS with actual usernames in Windows systems through registry queries and WMI technology. It focuses on analyzing two critical registry paths: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\hivelist, as well as methods for obtaining user SID information through WMI's wmic useraccount command. The article includes complete VBScript implementation code and provides detailed analysis of SID structure and security considerations.

This technical paper provides an in-depth analysis of various methods for retrieving product codes from installed MSI packages in Windows systems. Through detailed examination of PowerShell WMI queries, VBScript COM interface access, registry lookup, and original MSI file parsing, the paper compares the advantages, disadvantages, performance characteristics, and applicable scenarios of each approach. Special emphasis is placed on the self-repair risks associated with WMI queries and alternative solutions. The content also covers extended topics including remote computer queries, product uninstallation operations, and related tool usage, offering complete technical reference for system administrators and software developers.

This technical paper provides an in-depth examination of various methods for accurately determining Windows operating system installation dates. Through systematic comparison of registry queries, system commands, and file system analysis, the study evaluates the applicability and limitations of each approach. Special attention is given to the impact of Windows version upgrades on installation date detection, with practical implementation examples across multiple programming environments.

This technical paper provides an in-depth examination of various methods for retrieving Fully Qualified Domain Names (FQDN) in PowerShell environments. Based on highly-rated Stack Overflow solutions, the article systematically analyzes implementation approaches using environment variables, WMI queries, and .NET class libraries. Through detailed code examples and performance comparisons, it offers comprehensive technical guidance for system administrators and developers to select optimal FQDN retrieval strategies based on specific requirements.

This article provides an in-depth exploration of various methods for obtaining Windows operating system version information within PowerShell environments. It focuses on core solutions including the System.Environment class's OSVersion property, WMI query techniques, and registry reading approaches. Through complete code examples and detailed technical analysis, the article helps readers understand the appropriate scenarios and limitations of different methods, with specific compatibility guidance for PowerShell 2.0 and later versions. Content covers key technical aspects such as version number parsing, operating system name retrieval, and Windows 10 specific version identification, offering practical technical reference for system administrators and developers.

This paper delves into two primary methods for retrieving lists of installed programs in Windows systems: WMI queries and registry reading. By analyzing the limitations of the Win32_Product class, it reveals that this class only displays programs installed via Windows Installer, failing to cover all applications. The article details a more comprehensive solution—reading uninstall registry keys, including standard paths and WOW6432Node paths, and explains why this method aligns better with the "Add/Remove Programs" list. Additionally, it supplements with other relevant registry locations, such as HKEY_CLASSES_ROOT\Installer\Products, and provides practical technical advice and precautions.

This article explores various techniques for verifying command execution status in PowerShell, focusing on the method of checking whether return values are null to determine WMI query success. It explains the differences between the $? automatic variable and $LastExitCode, and demonstrates through practical code examples how to elegantly handle command execution results to ensure script robustness and maintainability.

This paper provides an in-depth exploration of the technical challenges and solutions for retrieving the currently logged username in .NET Windows services. Traditional methods such as System.Environment.UserName and WindowsIdentity.GetCurrent() return "System" when the service runs with system privileges, failing to meet practical requirements. The article details a WMI (Windows Management Instrumentation)-based solution that queries the UserName property of the Win32_ComputerSystem class to obtain the actual logged-in username. Additionally, it analyzes limitations in special scenarios like remote desktop connections and presents technical details of an alternative approach through identifying the owner of the explorer.exe process. With code examples and principle analysis, this paper offers comprehensive and practical technical guidance for developers.

This article provides a detailed exploration of how to retrieve process command line information in PowerShell and C#, focusing on methods using WMI and CIM. Through comparative analysis, it explains the advantages and disadvantages of different approaches, including permission requirements, compatibility considerations, and practical application scenarios. The content covers core code examples, technical principles, and best practices, aiming to offer comprehensive technical guidance for developers.

This article provides an in-depth exploration of various methods to retrieve the current username in Windows PowerShell environment, including environment variables, .NET classes, WMI queries, and other technical approaches. Through detailed code examples and comparative analysis, it elucidates the applicable scenarios, performance characteristics, and security considerations of different methods, offering comprehensive technical reference for system administrators and developers.

This article provides an in-depth exploration of two primary methods for obtaining a list of all printers connected to a computer in C# WinForms applications. It begins with the basic approach using the System.Drawing.Printing.PrinterSettings.InstalledPrinters property, which is straightforward and efficient for scenarios requiring only printer names. Subsequently, it delves into the advanced method utilizing the System.Management API to query the Win32_Printer class, enabling access to detailed printer information such as status, default settings, and network attributes. Through code examples and comparative analysis, the article assists developers in selecting the appropriate method based on specific needs, while offering practical considerations and best practices for real-world implementation.

This article provides an in-depth exploration of various command-line methods for detecting USB devices in Windows operating systems. Based on Q&A data and reference articles, it focuses on the advantages of using the USBview tool, supplemented by alternative approaches using WMIC commands and PowerShell commands. The article explains the principles, applicable scenarios, and limitations of each method in detail, offering complete code examples and practical guidance to help readers comprehensively master USB device detection techniques.

This article provides an in-depth exploration of how to accurately obtain CPU core count, physical processor count, and logical processor count in .NET/C# environments. By analyzing the limitations of Environment.ProcessorCount, it introduces methods using WMI queries to Win32_ComputerSystem and Win32_Processor classes, and discusses the impact of hyper-threading technology on processor counting. The article also covers advanced techniques for detecting processors excluded by the system through Windows API calls to setupapi.dll, helping developers comprehensively understand processor information retrieval strategies across different scenarios.

This paper provides an in-depth exploration of implementing remote registry queries in PowerShell scripts through the .NET Microsoft.Win32.RegistryKey class. The analysis begins by examining the limitations of traditional WMI methods for remote registry access, followed by a detailed explanation of the OpenRemoteBaseKey method's implementation principles and usage patterns, including the complete workflow of remote connection establishment, subkey access, and value retrieval. By comparing differences between local registry providers and remote access methods, this paper offers optimized script examples and error handling recommendations to assist system administrators in efficiently managing configuration information across multi-server environments.

This article provides an in-depth exploration of various methods for uninstalling Windows applications using PowerShell, with a focus on two core approaches: WMI-based Win32_Product class and registry query techniques. Through detailed code examples and performance comparisons, it explains the applicable scenarios, efficiency differences, and best practices for different methods, offering comprehensive technical reference for system administrators and developers. The article also discusses the differences between MSI and non-MSI programs during uninstallation, as well as advanced features like silent uninstallation.

This technical article explores methods for querying currently logged-in user information in Windows Server environments using PowerShell. Based on high-scoring Stack Overflow answers, it focuses on the application of the query user command and provides complete PowerShell script implementations. The content covers core concepts including user session state detection, idle time calculation, and domain vs. local user differentiation. Through step-by-step code examples, it demonstrates how to retrieve key information such as usernames, session IDs, login times, and idle status. The article also discusses extended applications for cross-network server session monitoring, providing practical automation tools for system administrators.

This article comprehensively explores various technical approaches for obtaining the total physical memory size in PowerShell environments without relying on WMI. By analyzing the best answer from the Q&A data—using the systeminfo.exe command—and supplementing with other methods such as CIM instance queries and performance counter calculations, it systematically compares the advantages, disadvantages, applicable scenarios, and implementation details of each method. The paper explains why performance counter methods yield fluctuating values and highlights the protocol advantages of CIM over WMI in remote management, providing a thorough technical reference for system administrators and developers.

This article provides a comprehensive guide on querying connected USB device information in Python, focusing on a cross-platform solution using the lsusb command. It begins by addressing common issues with libraries like pyUSB, such as missing device filenames, and presents optimized code that utilizes the subprocess module to parse system command output. Through regular expression matching, the method extracts device paths, vendor IDs, product IDs, and descriptions. The discussion also covers selecting optimal parameters for unique device identification and includes supplementary approaches for Windows platforms. All code examples are rewritten with detailed explanations to ensure clarity and practical applicability for developers.