Universal Intel Chipset Drivers Updater​

Hi everyone!

Just a quick update on the Universal Intel Chipset Updater.

The tool has been running absolutely flawlessly for quite some time now — no new bug reports, no issues, despite being used by thousands of people.
Most questions I get turn out to be related to the users' own systems, not the updater itself.

Error 1603 during MSI installation​
Since everything has been stable, I recently took some time to help a user who was struggling with a corrupted previous installation of the Intel Chipset Device Software.
Because of that corruption, they couldn't install any newer versions — even those offered by my updater — and kept running into Error 1603.

I helped them clean up the broken installation manually, and in the end, they were finally able to use the updater successfully. 

This issue isn't limited to Intel Chipset Device Software — Error 1603 can affect any MSI package when the old installation is damaged.
So I documented the entire solution, hoping it might help others in the future.

Full case and solution here:
github.com/FirstEverTech/Universal-Intel-Chipset-Updater/issues/14#issuecomment-4010882232

Hope this helps someone!

Heads-up for Admins: Upcoming Update with Admin-Friendly Features
I'm happy to announce that tomorrow I'll be releasing a new version of the Universal Intel Chipset Device Updater
with several enhancements specifically designed for administrators and automated deployments. 

What's new?
The script will now include dedicated command-line options. These allow for fully unattended execution, silent operation,
and fine-grained control – perfect for integrating into MDM solutions like Microsoft Intune, SCCM, Workspace ONE, or PDQ Deploy.

Key improvement:
The PowerShell script (.ps1) can now be used completely independently – no more need for the batch wrapper (Run.bat).
Of course, if you're already using the .bat file, it will continue to work without any issues; the script is fully backward compatible.

Why this matters for admins:
By using the .ps1 directly, you avoid the common pitfalls associated with self-extracting executables (SFX) – no more concerns
about unsigned code, local certificate warnings, or antivirus false positives. The script is just plain text, easily reviewable,
and can be executed with your preferred execution policy settings.

Once the new version is live, you'll be able to grab it from the usual place (GitHub) and soon also from the PowerShell Gallery.
Stay tuned!