What you’re seeing
- Software Center shows the application as failed with error 0x87D01106 within seconds of starting.
- The client's AppEnforce log says it failed to verify the executable or construct the command line.
- The installer never launches, and no MSI or setup log is created on the client.
- The same app installs fine when an admin runs it manually from the source share.
Common causes
Every environment is different, but these are the causes our engineers find most often:
- The installation program in the deployment type names a file that isn't in the content source, or the filename or extension doesn't match exactly.
- The command line calls a script engine or path that can't be resolved under the local SYSTEM account the client runs as.
- Content was changed on the source share but not redistributed, so clients downloaded an outdated set of files.
- Quotation marks or spaces in the install command are malformed, so the client can't parse it into a valid command.
- The command refers to a mapped drive letter or a network path that the SYSTEM account can't see.
Why it matters
When a deployment fails before the installer even runs, nobody in the target collection gets the software, whether that's a new business application, a browser update or a security agent. Staff wait on tools they need, and patches meant to close vulnerabilities never land. Because the error appears instantly, it can look like a client problem and lead to time wasted reimaging machines when the real fault is in the deployment's configuration.
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 does it install when we run it by hand?
Run by hand, it uses your account, your mapped drives and the full source folder. Configuration Manager runs it as the system account from a downloaded copy of the content, so anything that only exists in your context makes it fail.
Is our Configuration Manager setup broken?
Usually not. This error almost always comes from the settings of one application rather than the infrastructure, which keeps the fix contained.