Universal Intel Chipset Drivers Updater​

What a great and insightful post, and to the point. We are all blessed with your knowledge. If you could, for the future, perhaps try to adjust the dose, our tiny brains cannot comprehend such a ton of information.

Ataemonus a scris:

What a great and insightful post, and to the point. We are all blessed with your knowledge. If you could, for the future, perhaps try to adjust the dose, our tiny brains cannot comprehend such a ton of information.






 

@ Ataemonus  
I understand that you mean the entire log pasted by rvail - hahahaha!

@ rvail
I admit that you surprised me that you pasted such a huge log in the form of text - you're lucky that the forum didn't break down - hahahaha!

Next time:

1. Open:  pastes.io/
2. Paste your code and press "Create New Paste"
3. It will generate a link like here:  pastes.io/eXamp1e and send it to me in a private message.

Such logs may contain confidential data and should not be pasted on a public forum.
I suggest editing your last post and removing all content.
 

Not only that he posted the entire log, but without any context, request, nothing. Talk about low effort post...

Ataemonus a scris:

Not only that he posted the entire log, but without any context, request, nothing. Talk about low effort post...
 

I hope he doesn't get banned for this.

BACK TO THE LOG

I've analyzed the log in detail and can confirm that your second run (with exit code 1618) shows a completely different problem than the one in your earlier screenshot (which had exit code 1603).

Let me break it down:

1. The first error (1603 from your screenshot) – This is a generic "fatal error during installation." In your case, it likely points to a pre-existing, corrupted Intel Chipset Device Software installation on your system. This is not a bug in the updater itself.
2. The second error (1618 from the log you shared) – This is a transient Windows Installer lock error.

ERROR: Installer failed with exit code: 1618
ERROR: MSI installer failed with exit code: 1618

1618 means: ERROR_INSTALL_ALREADY_RUNNING – another installation is already in progress (e.g., Windows Update in the background, a stuck msiexec.exe process, or another installer). Windows Installer can only run one operation at a time.This is not a structural problem with the updater or your hardware. It is a temporary, environmental issue.

3. Good news – the detection fix works

The new version (v2026.08.0017) correctly identified all your hardware:

uniquePlatforms count: 3
Displaying platform entry: KabyLakePCH-H::10.1.1.37
Displaying platform entry: Skylake::10.1.20551.8850
Displaying platform entry: KabyLakePCH-H::10.1.20551.8850

The EOL package was also correctly queued before the main one.

Recommendations:

• For the 1618 error:
  • Open Task Manager and end any running msiexec.exe processes.
  • Temporarily pause Windows Update.
  • Reboot your computer to clear the installer lock, then run the updater again.
• For the 1603 error (if it reappears):
  • Consider manually uninstalling any old Intel Chipset Device Software entries via Programs and Features, then try again.

Two minor, non-blocking notes from the log:

• Enable-ComputerRestore was not recognized – the system restore point creation failed, but the script correctly continued. This is harmless.
• The MSI hash file intel_chipset_10.1.20551.8850.msi.sha256 returned a 404 Not Found – this file has now been added to the GitHub release, so the warning will no longer appear.

If you still experience the 1618 error after a reboot, please run the script again with the -debug flag and share the new log (this time link to  pastes.io  in a private message).

Thank you for your patience – the updater is working as expected, and the remaining issues are environmental.

The 1603 error went away after uninstalling an older Intel chipset driver software.
The 1618 error is still present, even after double-checking for any other processes.running.
pastes.io/cEyZNM88