FAQ
TL;DR: The startup RunDLL popup usually comes from 1 scheduled task entry missing quotes around a DLL path (“it only shows C:\Program”). Use Autoruns to disable the bad task or fix it via FRST Fixlist. [Elektroda, Kolobos, post #16939875]
Why it matters: This FAQ helps Windows users stop the persistent “Problem starting C:\Program – module not found” alert after boot.
Quick Facts
- Symptom: RunDLL error appears right after Windows starts and says “the module cannot be found.” [Elektroda, SleepyOne, post #16893300]
- Root cause seen here: malformed task calling a DLL without quotes, so the dialog only shows C:\Program. [Elektroda, Kolobos, post #16939875]
- Tools used by helpers: FRST (Fixlist/Fixlog) and Sysinternals Autoruns to locate startup entries. [Elektroda, Kolobos, post #16906781]
- Typical culprits cited: leftover entries from True Key, Lenovo Customer Feedback, or Windows Live SOXE tasks. [Elektroda, Kolobos, post #16907880]
- Example task calling a DLL-style host: rundll32 with pla.dll appeared in the listings. [Elektroda, krzychupar, post #16893364]
What does “Problem starting C:\Program – module not found” actually mean?
Windows tried to run a DLL via a task or startup entry, but the path lacked quotes. The loader split the path at the space after C:\Program, failed to find the module, and raised a RunDLL error. The helper noted it “only shows C:\Program” when quotes are missing. [Elektroda, Kolobos, post #16939875]
Why does only C:\Program show in the RunDLL popup?
Missing quotation marks around a path with spaces (like C:\Program Files...) cause Windows to read only the first token. The rest is ignored, so the dialog shows C:\Program and reports the DLL as missing. “It only shows C:\Program.” [Elektroda, Kolobos, post #16939875]
How do I fix this with Autoruns (quick 3‑step)?
- Open Autoruns as Administrator and go to the Scheduled Tasks tab.
- Find the task that points to a DLL path; uncheck or delete it, especially entries tied to Windows Live SOXE or similar leftovers.
- Reboot and confirm the popup is gone. [Elektroda, Kolobos, post #16924120]
Can FRST (Farbar) repair the bad entry?
Yes. Build a Fixlist.txt that removes the offending Scheduled Task and any related browser helpers or toolbars, then run FRST to apply. The moderator provided example Fixlist lines removing Lenovo and Avast tasks for cleanup. [Elektroda, Kolobos, post #16907880]
How do I recognize the problematic task entry?
Look for a Scheduled Task or Run entry that calls rundll32 or references a DLL, and where the full path includes spaces without surrounding quotes. The helper emphasized targeting the entry with a DLL. [Elektroda, Kolobos, post #16937229]
FRST didn’t help and the McAfee remover wouldn’t start. What then?
If FRST didn’t resolve it and RemoveMcAfee won’t launch even as admin, switch to Autoruns to disable the exact task causing the popup. This thread reports the remover not starting, so Autoruns inspection became the next step. [Elektroda, SleepyOne, post #16906329]
Could Intel Security True Key leftovers trigger this?
Yes. The advisor suggested uninstalling True Key and listed True Key browser components to remove via Fixlist. Residual entries can leave broken tasks or handlers that fire at startup. [Elektroda, Kolobos, post #16893536]
Is this always malware?
No. In this case, helpers focused on benign leftover tasks with DLL targets and missing quotes, not on active malware. “It should be an entry with a dll file,” indicating configuration debris rather than infection. [Elektroda, Kolobos, post #16937229]
Where in tasks might I see DLL-style calls?
Listings can include rundll32 executions, such as rundll32.exe loading pla.dll with parameters. Such entries illustrate how tasks can host DLLs and misfire when paths are malformed. [Elektroda, krzychupar, post #16893364]
Autoruns doesn’t show the exact entry. What should I search for?
Filter for “dll” and inspect Scheduled Tasks and other tabs for “File not found.” If nothing matches, expand your view; some entries hide under different categories. Screens showed searches that missed tasks when scoped too tightly. [Elektroda, SleepyOne, post #16939811]
What if I can’t find the entry that only shows C:\Program?
The expert warned you may not find it easily, because the underlying issue is missing quotes; Autoruns may show a normal-looking line. Systematically review tasks with DLL targets and disable to test. [Elektroda, Kolobos, post #16939875]
Can leftover Windows Live (SOXE) tasks cause the popup?
Yes. The advisor specifically pointed to disabling the Windows Live SOXE Extractor Definitions Update task in Autoruns as a test, since it referenced a DLL and could be orphaned. [Elektroda, Kolobos, post #16924120]
Do I need to clean other vendor tasks too (Lenovo, Avast)?
Cleaning noise helps. The provided Fixlist removed Lenovo Customer Feedback and Avast settings backup tasks to reduce startup clutter and isolate the culprit. Fewer tasks make troubleshooting faster. [Elektroda, Kolobos, post #16907880]
How many quotes does it take to break a path?
Just one missing quotation pair around a path with spaces can derail a DLL launch and trigger the RunDLL error. “It only shows C:\Program” sums up the result. [Elektroda, Kolobos, post #16939875]
