There was a problem sending the command to the program on Windows 10 / 8 / 7

16 Comments

  1. The above solution is not helpful for VC++ applications.

    I am working on a standard Visual C++ MFC application. There is a file say x.abc, whenver I double click this file, it opens directly in my VC++ app.

    This VC app is running as administrator and that is the requirement of the project.

    Case 1: Now, in Windows 7, when User Access Control (UAC) is ON, and I double click on file with .abc extenstion, it gives error message “There was a Problem sending the command to program” and the file doesn’t open and neither does that app.

    Case 2: If my VC exe is already open and then I double click .abc file, it gives error “There was a Problem sending the command to program” and then the file opens.

    This problem occurs in Windows 7 with UAC ON only.

    Let me know if you have experienced the similar problem.

    By the way, I am using the methods

    EnableShellOpen();

    RegisterShellFileTypes(FALSE);

    VC++ User

  2. For the excel option, unchecking the DDE box does fix this symptom, but causes a catastrophe of an issue, now I cannot open multiple excel instances. IE, no comparative side-by-side excel. This is not a fix, this is a break.

  3. I’m not a programmer, but this work around works for me. When you see the above message, OK it and try clicking on the link again but this time with the Ctrl button held down. It’ll do the same thing again. But try it once more (click again with Ctrl held down) and it will take you to the linked program
    .
    Hopefully, this will give some programmer a clue to what is wrong and produce a real fix.

  4. hi,

    i just feel like to share what worked for me as this thing really annoyed me for several months.

    i researched on several websites/sources and all the solutions i have come across do not work. such solutions include but are not limited to:

    1) clearing of the checkbox of that DDE thing.
    2) registry edit (too risky for non-savvy PC users like me)
    3) unchecking of “run as administrator”

    but just recently, i uninstalled a program called Tune Up utilities and then the annoying error was gone. so what i would suggest for others is to check which programs do you think are incompatible with your MS Office. then uninstall that (those) program (s).

    hope that helps.

    best,

    filousophe

  5. For excel 2013, this doesn’t fix issue, as addition, you should
    edit open command, and replace suffix “/dde” to “/n “%1” /o “%u””,
    then it would be work fine. you can check
    https://gist.github.com/zencodex/b928ddb55ad6322ec960, and save it to
    xxx.reg. I use chinese version excel, so you should edit xxx.reg, and
    convert chinese charactors, double click xxx.reg will fix this issue.

  6. NOTE: replace suffix “/dde” to “%1”, otherwise you coudn’t save excel. sorry for that. and I remove all chinese charactors, you wound’t convert. Have a nice day!

  7. Every Autodesk worker offers new solution, some of them are really useless, like: drink coffee before you open file etc. Non of those solve the problem. It’s just another rubbish from Autodesk team to get profit. So frustrated with their products…

  8. The second (regedit) fix didn’t work for me on Windows 7 64 bit, using Excel 2003. Now I right-click the downloaded xlsx file: “Open the containing folder” no longer functions.

    The medicine seems worse than the sickness.

  9. This is the one. Spent 5 days on this, nothing worked. Thank you!

    Microsoft: Office 2013 is more rubbish than Windows 8 was, and that’s saying something.

  10. This is the one. Spent 5 days on this, nothing worked. Thank you!

    To Microsoft: Office 2013 is more rubbish than Windows 8 was, and that’s saying something.

  11. I had the same problem and tried all the examples above and nothing helped.

    What worked for me was removing my AVG PCTune-up program I installed a few weeks back. As soon as I removed it all my MS-Office products starting working fine without that annoying error message.

    The strange thing is I did not have this issue when I installed the Tune-up program. Only after installing the latest Windows 10 updates. It appears that AVG does not come out with a new patch/update fast enough to keep up with Microsoft Windows 10 updates or Microsoft doesn’t take into account how their updates will affect AVG PCTune-up. Either way removing the AVG PCTune-up program instantly fixed my problem.

Leave a Reply

Your email address will not be published. Required fields are marked *


3 + 2 =