Thank you for the detailed feedback – it confirms exactly what I suspected. The fact that the updater worked flawlessly on a
fresh Windows 10 22H2 installation proves that the
1603 error was caused by something specific to your previous system, not by a bug in the tool.
Regarding other driver tools
I can assure you that
no other tool has a more up‑to‑date INF database than my updater. I maintain a complete archive of every INF file from every official Intel Chipset Device Software package ever released. So if another program suggests a
downgrade, you should
ignore it completely – they simply cannot detect the true latest version for your devices.
The
1968/1970 dates are also normal. Intel stopped embedding valid timestamps in newer INF files; when the system sees no date, it falls back to the earliest possible (1968‑01‑01 or 1970‑01‑01). Any tool that relies on those dates will be misled.
About uninstall-intel-chipset.bat
You wrote:
"it seems overly complicated, even if I could get it to work."
Could you clarify –
did you actually run the uninstall tool, or not?
Its logic is very straightforward:
- It scans the Windows registry (uninstall keys) for entries containing
"Intel(R) Chipset Device Software" (old Intel installers) or "SetupChipset" (newer MSI‑based installers).
- For each found entry it extracts the uninstall command – whether it’s an .exe uninstaller or an msiexec product code.
- If the original installer files have been deleted, it simply cleans up the leftover registry keys so they no longer block future installations.
Intel installers work in such a way that once the INF files are updated, the installer itself can be removed without affecting the drivers.
The uninstall tool is meant to remove
only the installer entry, not the already installed INF files.
What I’d like to know
- Did the uninstall tool detect any installed versions of "Intel Chipset Device Software" on your (internal) Windows system?
- If yes, did it show you the version and then successfully remove it?
If it
did detect something, there is another approach we could try:
- Download and reinstall the exact version that was detected (if you can't find an installer, I can provide one).
- Use the installer’s own repair/modify option (or simply run it again to trigger a reinstall).
- Then uninstall it properly – a reinstall/repair often fixes a broken installation state.
Let me know what the uninstall tool reported – this will help solve error 1603.
ผู้เขียนหัวข้อ
