What you’re seeing
- The deployment tool's output shows that 'msg' is not recognized as an internal or external command.
- The same command typed into a command prompt on the PC works and pops up the message.
- Users never see notices about pending reboots, maintenance or software installs.
- Other built-in Windows commands run fine when launched by the same tool.
Common causes
Every environment is different, but these are the causes our engineers find most often:
- The deployment agent runs as a 32-bit process on 64-bit Windows, so Windows redirects it to the 32-bit system folder, where msg.exe doesn't exist.
- Some Windows editions, such as Home, don't include the msg utility at all.
- The agent runs under the SYSTEM account with a minimal set of paths that differs from an interactive user's environment.
Why it matters
Pop-up messages are often the only warning users get before a forced reboot or maintenance window. When they silently fail, people lose unsaved work when their machine restarts, and the help desk gets complaints that look like random crashes. During an outage or security event, the inability to message logged-on users also removes a quick way to tell staff to save work, stay off a system or expect disruption.
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
Does this mean our deployment tool is broken?
No. The tool is working; Windows is simply showing a 32-bit program a different view of the system folder. It's a common and well-understood behavior.
Could other scripts be affected in the same way?
Yes. Any script that relies on 64-bit-only system tools can hit the same problem when launched by a 32-bit agent, so it's worth knowing which of yours are exposed.