How to Fix C:\Windows\chipset\driver\hotfix\asusSetup.ini Error at Startup
On ASUS laptops and motherboards, after installing chipset drivers (or running Disk Cleanup / Windows updates), a popup error box sometimes appears at every login: C:\Windows\chipset\driver\hotfix\asusSetup.ini is lost (or a similar path pointing to asusSetup.ini inside Temp).

Your chipset drivers are already installed and working fine – the popup only happens because the ASUS installer cleaned up its temporary extraction folder without removing its scheduled post-reboot task in Windows.
Method 1 (Main Fix). Delete the Leftover Task in Task Scheduler
Checking the regular Startup tab in Task Manager will not show this entry because ASUS registers its post-install hooks inside Windows Task Scheduler. Clearing it takes one minute:
- Press
Win+R, typetaskschd.msc, and press Enter (or open Control Panel → Administrative Tools → Task Scheduler). - In the left tree, expand “Task Scheduler Library” → the
ASUSfolder (often containing a subfolder namedi-Setup...). - Look for tasks triggered “At log on” (check the “Actions” tab at the bottom – you will see
AsusSetup.exepointing tochipset\driver\hotfix\asusSetup.inior aTempfolder). - Right-click the orphaned task and choose “Delete” (or “Disable”).
Reboot to test – the popup will be gone for good.
Method 2. If There Is No ASUS Folder in Task Scheduler – Check the Registry
On certain ASUS driver packages, the leftover call sits in the Registry startup keys instead:
- Press
Win+R, typeregedit, and press Enter. - Press
Ctrl+F, search forasusSetup.ini(orAsusSetup). - It usually lives under one of these two Run keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Run
If you spot a value referencing the missing asusSetup.ini path, right-click and delete it.
File not found). Type asus into the top filter box and uncheck the broken entry.You do not need to reinstall any chipset drivers afterward: the driver itself is already active in Windows, and you have simply removed a forgotten temporary installer shortcut.