Skip to content

Universal Intel Chipset Device Updater automatically detects Intel hardware and securely installs latest INF files with multi-layer verification. It has received an average safety score of 9.4/10 in audits conducted by independent AI agents.

License

Notifications You must be signed in to change notification settings

FirstEverTech/Universal-Intel-Chipset-Updater

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

547 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

πŸš€ Universal Intel Chipset Device Updater

Version License Windows PowerShell

Security Audit Reliability Issues VirusTotal

πŸ”§ Automate Your Intel Chipset Updates

Universal Intel Chipset Device Updater is an advanced, security-focused tool that automatically detects your Intel hardware and installs the latest official chipset INF files with enterprise-grade safety measures.

This project was built through a pragmatic collaboration between human expertise and AI-assisted tooling.

Official discussion threads are available on the Win-Raid Forum, Station-Drivers Forum and WinClub Forum.

Why This Tool Exists

Intel's official Chipset Device Software has evolved over 25 years into a complex, bloated package. This tool simplifies the process by automatically detecting and installing only the INF files your system actually needs β€” nothing more, nothing less.

For a detailed technical breakdown and historical context, see:
β†’ The Whole Truth About Intel Chipset Device Software β†’ Behind the Project: Making Of


πŸ“‘ 1. Table of Contents

  1. Table of Contents
  2. Release Highlights
    2.1 Latest Version
    2.2 Previous Releases
  3. Independent Security Audits
  4. Application Overview
  5. Key Features
    5.1 Smart Hardware Detection
    5.2 Multi-Layer Security
    5.3 Seamless Operation
    5.4 Comprehensive Coverage
  6. System Requirements
    6.1 System Requirements Table
    6.2 Windows Version Support
    6.3 Legacy System Notes
  7. Quick Comparison
  8. Quick Start
    8.1 Method 1: One-Click Execution
    8.2 Method 2: PowerShell Direct
    8.3 Method 3: Hardware ID Scanner Only
  9. How It Works
    9.1 Self-Verification & Update Check
    9.2 Hardware Detection
    9.3 Database Query & Matching
    9.4 Security Verification
    9.5 Installation & Cleanup
  10. Security First Approach
    10.1 Verified Security Layers
  11. Usage Scenarios
    11.1 Home Users
    11.2 IT Professionals & Technicians
    11.3 System Builders
  12. Download Options
    12.1 Option 1: SFX Executable (Recommended)
    12.2 Option 2: Script Bundle
    12.3 Option 3: Source Code
  13. Independent Audit Results
  14. Project Structure
  15. Release Structure
    15.1 Primary Files
    15.2 Verification Files
    15.3 Documentation
  16. Frequently Asked Questions (FAQ)
    16.1 Is this tool safe to use?
    16.2 Will this update all my Intel drivers?
    16.3 What are the risks?
    16.4 Where are files downloaded?
    16.5 What if something goes wrong?
    16.6 How does the automatic update check work?
    16.7 What does self-hash verification do?
    16.8 How are updates notified?
    16.9 Why is the certificate "not trusted"?
  17. Intel Platform Support
  18. Performance Metrics
    18.1 Typical Execution Time Breakdown (Updated)
    18.2 Disk Space Usage
    18.3 Memory (RAM) Usage
    18.4 Resource Usage Summary
  19. Known Issues
  20. Ready to Update?
    20.1 Quick Start Guide
    20.2 Verification Steps (Optional)
    20.3 Need Help?
  21. Contributing
  22. License
  23. Acknowledgments
  24. Important Links
  25. Author & Contact
  26. Support This Project

↑ Back to top


πŸŽ‰ 2. Release Highlights

2.1 Latest Version

Universal Intel Chipset Device Updater v10.1-2026.02.2 β†’ Release Notes

πŸ“¦ Latest Release: v10.1-2026.02.2

πŸ†• Highlights

  • Enhanced Pre-Launch Checks:
    • Windows build validation (Win10 LTSC 2019 / build 17763+) now in PowerShell script
    • .NET 4.7.2+ detection moved to PowerShell
    • GitHub connectivity & TLS 1.2 check in PowerShell
    • User can continue despite warnings
  • Simplified BAT Launcher:
    • BAT file now only handles elevation and launching PowerShell
    • Pre-checks moved to PowerShell for better reliability
    • Cleaner exit handling
  • Critical Fixes:
    • Hash verification on older Windows fixed
    • Improved BAT reliability (working directory, elevation, clean exit)
    • Fixed exit code 100 handling for new version launches

πŸ”§ Technical Updates

  • BAT launcher: Simplified to only handle elevation and launch PowerShell script
  • PowerShell script:
    • Added comprehensive pre-checks (Windows build, .NET, GitHub connectivity)
    • Improved user guidance for older systems
    • Enhanced error handling and logging

πŸ› Bug Fixes

  • Fixed hash verification failures on older Windows 10 LTSB/LTSC builds
  • Fixed pre-check warnings not clearly informing users about TLS/.NET requirements
  • Fixed working directory issues in BAT launcher
  • Fixed exit handling when auto-update triggers launch of new version

πŸ“‹ Included Files

  • universal-intel-chipset-updater.ps1 – Main updater script (with enhanced pre-checks)
  • universal-intel-chipset-updater.bat – Simplified launcher
  • ChipsetUpdater-10.1-2026.02.2-Win10-Win11.exe – Self-extracting package

⚑ Requirements & Notes

  • Minimum Requirements:
    • Windows 10 LTSC 2019 (build 17763) or newer
    • .NET Framework 4.7.2+
  • Older LTSB/LTSC builds may run but GitHub hash verification could fail
  • Intel INF package updates remain manual; community reports highly encouraged

Summary: v10.1-2026.02.2 moves pre-launch checks to PowerShell for better reliability, simplifies the BAT launcher, improves Windows compatibility for older builds, and strengthens user guidance for systems with limited connectivity, while maintaining all hardware-accurate platform detection and INF installation features from previous releases.


πŸ” Technical Deep Dive: Installation Order Fix

Problem: When Intel removes specific HWIDs from newer installer packages, but your hardware still needs those drivers:

  • Example: Package v1.0 has HWID1, HWID2, HWID3
  • Package v1.1 only has HWID2, HWID3 (Intel deprecated HWID1)
  • Installing v1.1 first, then v1.0 would downgrade HWID2 and HWID3

Solution: Sort packages by version (oldest β†’ newest) before installation:

  1. v1.0 installs first β†’ HWID1, HWID2, HWID3 all installed
  2. v1.1 installs second β†’ HWID2 and HWID3 upgraded, HWID1 unchanged
  3. Result: All drivers at their maximum available version, no downgrades

Code Change (line 1716 in PowerShell script):

# OLD CODE:
$sortedPackages = $packageGroups.Keys | Sort-Object { [version]($_ -replace '\s*\(S\)\s*', '') } -Descending

# NEW CODE (removed -Descending to sort oldest β†’ newest):
$sortedPackages = $packageGroups.Keys | Sort-Object { [version]($_ -replace '\s*\(S\)\s*', '') }

This ensures legacy platforms receive optimal driver coverage without sacrificing newer updates for actively supported HWIDs.


πŸ” Technical Deep Dive: Installation Order Fix

Problem: When Intel removes specific HWIDs from newer installer packages, but your hardware still needs those drivers:

  • Example: Package v1.0 has HWID1, HWID2, HWID3
  • Package v1.1 only has HWID2, HWID3 (Intel deprecated HWID1)
  • Installing v1.1 first, then v1.0 would downgrade HWID2 and HWID3

Solution: Sort packages by version (oldest β†’ newest) before installation:

  1. v1.0 installs first β†’ HWID1, HWID2, HWID3 all installed
  2. v1.1 installs second β†’ HWID2 and HWID3 upgraded, HWID1 unchanged
  3. Result: All drivers at their maximum available version, no downgrades

Code Change (line ~1714 in PowerShell script):

# Sort packages by version (oldest first) to prevent downgrade when installing missing HWIDs
$sortedPackages = $uniquePackages.GetEnumerator() | Sort-Object {
    $versionString = $_.Key -replace '-.*$', ''
    try { [version]$versionString } catch { $versionString }
}

foreach ($entry in $sortedPackages) {
    # Installation logic...
}

This ensures legacy platforms receive optimal driver coverage without sacrificing newer updates for actively supported HWIDs.

↑ Back to top

2.2 Previous Releases

↑ Back to top

πŸ” 3. Independent Security Audits

This project has undergone comprehensive analysis by multiple AI security experts to ensure code quality and reliability. The tool achieved an average security score of 9.4/10 across all independent assessments.

Auditor Score Key Assessment
Grok 9.8/10 "This is currently the highest score I have ever given to a community driver-related utility."
ChatGPT 9.6/10 "It does not behave like a hobby script, but like a carefully scoped system utility."
Gemini 9.5/10 "This tool is superior to many generic driver update solutions. It is safe, transparent, and highly efficient."
Copilot 9.4/10 "It is one of the most complete and technically impressive PowerShell-based hardware automation tools publicly available."
DeepSeek 9.2/10 "The Universal Intel Chipset Device Updater represents a remarkable achievement in independent software development."
Claude 8.7/10 "Automating Intel chipset INF updates for enthusiast and IT users β€” this is the best open-source option available."

For detailed audit reports and methodology, see SECURITY-AUDITS.md.

↑ Back to top

πŸ–ΌοΈ 4. Application Overview

Phase 1 Phase 2 Phase 3 Phase 4
Hardware Detection Security Check Update Process Update Process
Security check and update check Hardware detection and version analysis Creating a system restore point Download, verify and install

↑ Back to top

✨ 5. Key Features

πŸ” 5.1 Smart Hardware Detection

  • Automatically scans for Intel chipset components
  • Identifies specific Hardware IDs (HWIDs)
  • Supports chipsets from Sandy Bridge to latest generations
  • Detects both Consumer and Server platforms

πŸ›‘ 5.2 Multi-Layer Security

  • SHA-256 Hash Verification for all downloads
  • Digital Signature Validation (Intel Corporation certificates)
  • Automated System Restore Points before installation
  • Dual-Source Download with backup fallback
  • Administrator Privilege Enforcement

⚑ 5.3 Seamless Operation

  • No installation required - fully portable
  • Automatic version checking and updates
  • Clean, intuitive user interface
  • Detailed logging and debug mode
  • Save to Downloads folder option

πŸ”„ 5.4 Comprehensive Coverage

  • Mainstream Desktop/Mobile platforms
  • Workstation/Enthusiast systems
  • Xeon/Server platforms
  • Atom/Low-Power devices

↑ Back to top

πŸ“‹ 6. System Requirements

6.1 System Requirements Table

Component Minimum Recommended Notes
Windows Version 10 1809 (17763) 11 22H2+ 1809 requires .NET 4.7.2+
.NET Framework 4.6.1 4.8+ 4.7.2+ for TLS 1.2 on older Windows
PowerShell 5.1 7.3+ Windows PowerShell 5.1 included
Administrator Required Required For driver installation
Internet Required Required For hash verification and updates
RAM 2 GB 4 GB+ For INF extraction/installation
Disk Space 500 MB 1 GB+ Temporary files during installation
System Restore Optional Enabled Automatic restore point creation

6.2 Windows Version Support

Version Build Status Notes
Windows 11 All builds βœ… Full Optimized support
Windows 10 22H2+ βœ… Full Recommended
Windows 10 21H2 βœ… Full Stable
Windows 10 21H1 (19043) βœ… Full Legacy
Windows 10 20H2 (19042) βœ… Full Legacy
Windows 10 2004 (19041) βœ… Full Legacy
Windows 10 1909 (18363) βœ… Full Legacy
Windows 10 1903 (18362) βœ… Full Legacy
Windows 10 1809 (17763) βœ… Limited Requires .NET 4.7.2+ for TLS 1.2 support
Windows 10 LTSB 2016 (1607) ⚠️ Limited Manual updates required for TLS 1.2
Windows 10 LTSB 2015 (1507) ⚠️ Limited Manual updates required for TLS 1.2

6.3 Legacy System Notes

  • Windows 10 1809 (17763) and newer: Full TLS 1.2 support out-of-the-box
  • Windows 10 LTSB 2015/2016: May require manual installation of:
  • The tool automatically:
    • Detects Windows version limitations
    • Warns about potential connectivity issues
    • Provides fallback options for offline operation
  • Basic INF detection and installation works even without internet connectivity

↑ Back to top

⚑ 7. Quick Comparison

Feature This Tool Intel DSA Manual Installation
Automatic Detection βœ… Full βœ… Partial ❌ Manual
Security Verification βœ… Multi-layer βœ… Basic ❌ None
System Restore Points βœ… Automatic ❌ None ❌ Manual
Update Notifications βœ… Built-in βœ… Yes ❌ None
Self-updating βœ… Yes ❌ No ❌ No
Portable βœ… No install ❌ Requires install βœ…/❌ Varies
Free βœ… 100% βœ… Yes βœ… Yes

↑ Back to top

🚦 8. Quick Start

8.1 Method 1: One-Click Execution

# Download and run executable file as Administrator:
ChipsetUpdater-10.1-2025.11.7-Win10-Win11.exe (or later version)

# Optionaly, download .ps1 and .bat files, then run BATCH file as Administrator:
Universal-Intel-Chipset-Updater.bat

8.2 Method 2: PowerShell Direct

# Run PowerShell as Administrator, then:
.\Universal-Intel-Chipset-Updater.ps1

8.3 Method 3: Hardware ID Scanner Only

# For diagnostic purposes
Get-Intel-HWIDs.bat

↑ Back to top

πŸ”§ 9. How It Works

πŸ”’ 9.1 Self-Verification & Update Check

  • Integrity Verification - Validates script hash against GitHub release
  • Update Detection - Compares current version with latest available
  • Security First - Ensures tool hasn't been modified or corrupted

πŸ” 9.2 Hardware Detection

  • Scans PCI devices for Intel Vendor ID (8086)
  • Identifies chipset-related components
  • Extracts Hardware IDs and current driver versions

πŸ“Š 9.3 Database Query & Matching

  • Downloads latest INF database from GitHub
  • Matches detected HWIDs with compatible packages
  • Compares current vs latest versions

πŸ›‘ 9.4 Security Verification

  • Creates system restore point automatically
  • Downloads from primary/backup sources
  • Verifies SHA-256 hashes
  • Validates Intel digital signatures

⚑ 9.5 Installation & Cleanup

  • Executes official Intel setup with safe parameters
  • Provides real-time progress feedback
  • Automatic cleanup of temporary files

↑ Back to top

πŸ›‘ 10. Security First Approach

πŸ”’ 10.1 Verified Security Layers

1. Self-Integrity β†’ Script Hash Verification
2. File Integrity β†’ SHA-256 Hash Verification  
3. Authenticity β†’ Intel Digital Signatures
4. Project Origin β†’ FirstEver.tech Digital Signature
5. System Safety β†’ Automated Restore Points
6. Source Reliability β†’ Dual Download Sources
7. Privilege Control β†’ Admin Rights Enforcement
8. Update Safety β†’ Version Verification

↑ Back to top

🎯 11. Usage Scenarios

🏠 11.1 Home Users

  • Keep system updated without technical knowledge
  • Automatic safety checks prevent installation issues
  • One-click operation with clear prompts

πŸ’Ό 11.2 IT Professionals & Technicians

  • Batch deployment across multiple systems
  • Comprehensive logging for troubleshooting
  • Security verification for corporate environments

πŸ›  11.3 System Builders

  • Pre-installation preparation for new builds
  • Driver consistency across multiple systems
  • Time-saving automation vs manual updates

↑ Back to top

πŸ“₯ 12. Download Options

12.1 Option 1: SFX Executable (Recommended)

  • File: ChipsetUpdater-10.1-2025.11.6-Win10-Win11.exe
  • Features: Digital signature, one-click execution, automatic extraction
  • For: Most users, easiest method

12.2 Option 2: Script Bundle

  • Files: universal-intel-chipset-updater.bat + universal-intel-chipset-updater.ps1
  • Features: Full control, modifiable code, transparency
  • For: Advanced users, customization

12.3 Option 3: Source Code

  • Method: git clone the repository
  • Features: Latest development version, full customization
  • For: Developers, contributors

↑ Back to top

πŸ“Š 13. Independent Audit Results

This project has been thoroughly audited by 6 independent AI security experts, achieving an average score of 9.4/10. Multiple auditors confirmed it's the safest and most stable version ever released, suitable for daily use, corporate deployment, and technician toolkits.

View Full Audit Report β€’ Security Policy

For current limitations and workarounds, please see: KNOWN_ISSUES.md

↑ Back to top

πŸ“ 14. Project Structure

Key Files and Directories:

src/ - Main scripts directory

data/ - Data files

docs/ - Documentation

assets/ - Screenshots

ISSUE_TEMPLATE/ - Issue templates

/ - Root directory files

↑ Back to top

πŸ“¦ 15. Release Structure

Each version (v10.1-2025.11.6) includes:

15.1 Primary Files

  • ChipsetUpdater-10.1-2025.11.6-Win10-Win11.exe - Main executable (digitally signed)
  • universal-intel-chipset-updater.bat - Batch wrapper
  • universal-intel-chipset-updater.ps1 - PowerShell script

15.2 Verification Files

  • ChipsetUpdater-10.1-2025.11.6-Win10-Win11.sha256 - EXE hash
  • universal-intel-chipset-updater-10.1-2025.11.6-ps1.sha256 - PS1 script hash
  • FirstEver.tech.cer - Digital certificate

15.3 Documentation

  • CHANGELOG.md - Version history
  • SECURITY-AUDITS.md - Security reports

↑ Back to top

❓ 16. Frequently Asked Questions (FAQ)

πŸ€” 16.1 Is this tool safe to use?

Yes! This tool has undergone comprehensive independent security audits by 6 different AI experts with an average score of 9.1/10. Multiple auditors confirmed it's the safest and most stable version ever released, suitable for daily use, corporate deployment, and technician toolkits.

Security measures include:

  • Hash verification of all downloads
  • Automatic system restore points before installation
  • Official Intel drivers only from trusted sources
  • Comprehensive pre-installation checks

Version 10.1-2025.11.6 is strongly recommended by security auditors for optimal safety and performance.

πŸ”„ 16.2 Will this update all my Intel drivers?

This tool specifically updates chipset INF files. It does not update GPU, network, or other device drivers.

⚠️ 16.3 What are the risks?

As with any system modification, there's a small risk of temporary system instability. The automated restore point minimizes this risk significantly.

πŸ’Ύ 16.4 Where are files downloaded?

Files are temporarily stored in C:\Windows\Temp\IntelChipset\ and automatically cleaned up after installation.

πŸ”§ 16.5 What if something goes wrong?

The tool creates a system restore point before making changes. You can also check detailed logs in the temp directory.

πŸ”„ 16.6 How does the automatic update check work?

The tool compares your current version with the latest version on GitHub. If a newer version is available, it offers to download it directly to your Downloads folder with full verification.

πŸ”’ 16.7 What does self-hash verification do?

Before execution, the tool calculates its own SHA-256 hash and compares it with the official hash from GitHub. This ensures the file hasn't been modified, corrupted, or tampered with.

πŸ“§ 16.8 How are updates notified?

The tool automatically checks for updates on each run and clearly notifies you if a newer version is available, with options to continue or update.

🏷️ 16.9 Why is the certificate "not trusted"?

The FirstEver.tech certificate is self-signed for project authenticity. Public trust requires expensive commercial certificates, but the included certificate allows verification of file origin.

↑ Back to top

πŸ’» 17. Intel Platform Support

Generation Code Name Status Notes
12th-14th Gen Alder/Raptor Lake βœ… Full Latest support
10th-11th Gen Comet/Tiger Lake βœ… Full Complete support
8th-9th Gen Coffee/Whiskey Lake βœ… Full Stable support
6th-7th Gen Skylake/Kaby Lake βœ… Full Mature support
4th-5th Gen Haswell/Broadwell βœ… Full Legacy support
2nd-3rd Gen Sandy/Ivy Bridge βœ… Full Extended support

↑ Back to top

πŸ“Š 18. Performance Metrics

18.1 Typical Execution Time Breakdown (Updated)

Phase Time Description
Compatibility Pre-Check 5–10 seconds OS build, .NET Framework, TLS 1.2 availability, administrator privileges and GitHub connectivity verification
Verification & Update Check 5–10 seconds Self-integrity hash verification and updater version check
Hardware Detection 10–25 seconds Full system scan and Intel chipset device identification (HWID enumeration)
System Restore Point Creation 30–60 seconds Automatic creation of a Windows System Restore Point before applying any changes
Package Download & Verification 5–10 seconds Download and integrity verification of required Intel INF metadata packages
Installation 60–120 seconds INF file installation, registry updates and device reconfiguration

18.2 Disk Space Usage

Stage Estimated Usage Notes
SFX archive (download) ~0.7 MB Self-extracting EXE
Extracted scripts (BAT + PS1) ~90 KB Temporary working files
System Restore Point 100–300 MB Managed by Windows (shadow copy storage)
Downloaded Intel package 2–10 MB EXE or MSI, platform-dependent
Extracted package contents 10–30 MB Temporary extraction of INF files
Peak temporary disk usage ~150–350 MB During restore point creation and extraction
Persistent disk usage after completion < 5 MB Scripts and logs only

Important notes:

  • System Restore Point size is the dominant factor and depends on Windows configuration.
  • All extracted installer files are automatically removed after completion.
  • No drivers or binaries remain installed β€” only INF metadata.

18.3 Memory (RAM) Usage

Component Estimated Usage Notes
BAT launcher < 5 MB cmd.exe overhead
PowerShell runtime 40–80 MB Script execution, parsing and hashing
INF parsing & HWID scan 20–40 MB Temporary in-memory data structures
Installer extraction (EXE/MSI) 30–100 MB Short peak during unpacking
Peak RAM usage ~100–200 MB Worst-case during package extraction

Memory characteristics:

  • RAM usage is short-lived and released immediately after each phase.
  • No background services or resident processes.
  • Safe even for systems with 2 GB RAM.

18.4 Resource Usage Summary

  • Required free disk space: ~350 MB (safe upper bound)
  • Typical disk usage: ~150–250 MB
  • Peak RAM usage: ~100–200 MB
  • Persistent footprint after exit: negligible

↑ Back to top

πŸ› 19. Known Issues

For current limitations and workarounds, please see: KNOWN_ISSUES.md

↑ Back to top

πŸš€ 20. Ready to Update?

20.1 Quick Start Guide

  1. Download latest release from Releases page
  2. Verify digital signature and hashes (optional but recommended)
  3. Run as Administrator for full system access
  4. Follow prompts - tool handles everything automatically
  5. Restart if prompted to complete installation

20.2 Verification Steps (Optional)

  • Check file hashes match published SHA256 files
  • Verify digital signature with included certificate
  • Review security audit reports for confidence

20.3 Need Help?

↑ Back to top

🀝 21. Contributing

We welcome contributions! Please feel free to submit pull requests, report bugs, or suggest new features.

Areas for Contribution:

  • Additional hardware platform support
  • Translation improvements
  • Documentation enhancements
  • Testing on various Windows versions

↑ Back to top

πŸ“„ 22. License

This project is licensed under the MIT License - see the LICENSE file for details.

↑ Back to top

πŸ™ 23. Acknowledgments

  • Intel Corporation for providing official driver packages
  • Security researchers for independent audits
  • Open source community for continuous improvement
  • Beta testers for real-world validation

↑ Back to top

πŸ”— 24. Important Links

↑ Back to top

πŸ§‘β€πŸ’» 25. Author & Concatc

Marcin Grygiel aka FirstEver

↑ Back to top

πŸ’– 26. Support This Project

This project is maintained in my free time. Your support helps cover development costs and server expenses.

PayPal Buy Me a Coffee GitHub Sponsors

Your support means everything! If this project helped you, please consider:

  • If this project helped you, please give it a ⭐ star on GitHub
  • Sharing with friends and colleagues
  • Reporting issues or suggesting features
  • Supporting development financially

Marcin Grygiel   AI

Note: This tool is provided as-is for educational and convenience purposes. While we strive for accuracy, always verify critical INF updates through official channels. The complete HWID database is available for transparency and community contributions.

↑ Back to top

About

Universal Intel Chipset Device Updater automatically detects Intel hardware and securely installs latest INF files with multi-layer verification. It has received an average safety score of 9.4/10 in audits conducted by independent AI agents.

Topics

Resources

License

Contributing

Security policy

Stars

Watchers

Forks

Packages

No packages published