What you’re seeing
- A Windows Installer window asks for the original MSI file or a network path to the installation package.
- The application opens and closes immediately for some users, while it works for others on the same PC.
- MsiInstaller entries in the Application event log mention a missing component or a feature being reconfigured.
- The prompt appears the first time each new user launches the program after it was deployed.
Common causes
Every environment is different, but these are the causes our engineers find most often:
- The app was installed per machine but includes per-user components, so Windows Installer runs a self-repair the first time each new user opens it.
- The deployment share or source folder the package was installed from has been moved, renamed or cleaned up, so the self-repair can't find its files.
- A disk cleanup tool deleted the cached copy of the MSI that Windows keeps for repairs and uninstalls.
- The package was deployed with a transform or property that later changed, leaving the installed product inconsistent.
- Profile or folder permission problems stop the per-user part of the application from being written.
Why it matters
When an application stalls on an installer prompt or crashes at launch, the affected staff simply can't do the work that depends on it. Users without admin rights have no way to supply the source files, so the prompt becomes a hard stop that lands on the help desk. Because the trigger is often per user, the problem keeps resurfacing as new employees join or people move desks, making the rollout look unreliable and eroding confidence in future deployments.
How AskTechGurus fixes it
Skip the trial and error. A certified engineer works on your actual system, finds the root cause, and fixes it properly.
Tell us what’s happening
Submit a ticket in about two minutes. Paste the error, describe what changed, and pick your tier. No charge to submit.
A certified engineer diagnoses it
A vetted, US-based systems engineer claims your ticket, usually within minutes during business hours, and investigates over a secure remote session you can watch and end at any time.
Fixed and verified with you
The engineer resolves the root cause and confirms with you that it’s working. You don’t just get a workaround, and you get a plain-English summary of what was wrong.
Pay only when it’s resolved
Fixed price from $99, invoiced only after you approve the fix. If it isn’t resolved, you don’t pay.
Frequently asked questions
Why do only some users get the prompt?
The repair runs per user, usually for anyone who hadn't opened the app before or who joined after it was deployed. Users set up earlier already have the per-user pieces in place.
Won't reinstalling it for everyone solve the problem?
It may hide the symptom for a while, but if the source location or package is still wrong the prompt tends to return. We confirm why the repair is being triggered before changing anything.