LiveCycle Designer ES2: Word (version XP or onwards) could not be found on the machine

Issue

If you are using LiveCycle Designer ES2 to import Microsoft Word documents from MS Word 2010 or later, you may receive the following error

Word (version XP or onwards) could not be found on the machine

Reason

This error occurs because LC Designer ES2 does not recognise the installation folder for Microsoft Word 2010 or later versions.  LiveCycle Designer ES2 was released before these versions existed and therefore the installation folders were not known/recognised.

Solution

This issue has been fixed in LiveCycle Designer ES3 and last cumulative QuickFixes (QF) for Designer ES2.  Ensure you are using the latest QF for Designer ES2, or request the latest from your support representative.

If you require an urgent fix for this issue you can make the following change in the registry:

Note: we cannot provide support for any problems that may arise as a result of modifying the registry.  Only an experienced user or an administrator should attempt this, and a full registry backup should be performed before making changes.

1. For 32-bit Windows:

  • Create the following path in the registry:
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\Word\InstallRoot
  • Create a new string value named Path with value C:\Program Files\Microsoft Office\Office14\

2. For 64-bit Windows

  • Create the following path in the registry:
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\12.0\Word\InstallRoot
  • Create a new string value named Path with value C:\Program Files (x86)\Microsoft Office\Office14\

You should check the installation folder used in the Path value exists and contains WINWORD.EXE.  You will need to restart LiveCycle Designer for the changes to take effect.

Additional information

This issue is also being discussed in the forums:

http://forums.adobe.com/message/3983628

reference: (183608560/2751566)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 7.5/10 (10 votes cast)
LiveCycle Designer ES2: Word (version XP or onwards) could not be found on the machine, 7.5 out of 10 based on 10 ratings

10 Responses to LiveCycle Designer ES2: Word (version XP or onwards) could not be found on the machine

  1. Pingback: LiveCycle Designer ES2: Word (version XP or onwards) could not be found on the machine

  2. khashayar says:

    sorry thanks foll site to in computer

  3. Pingback: LiveCycle Designer ES2: Word (version XP or onwards) could not be found on the machine | Placedelamode

  4. Jason says:

    Followed exactly, not new to using registry hacks to fix things. My winword.exe was found under C:\Program Files\Microsoft Office\Office14. I tried both that path AND the one you posted here, neither works, I can not convert ANY word document, .doc or .docx, HOW CAN I MAKE THIS WORK, this is an Adobe problem and Adobe needs to post a fix that works.

    • dmcmahon says:

      This issue has been fixed in LiveCycle Designer ES3 and last cumulative QuickFixes (QF) for Designer ES2.
      To assist with your issue we would need to know:
      1. LC Designer version
      2. MS Word version
      3. Windows version (XP, Win7… 32/64-bit)

  5. ArrueiraV says:

    I have just installed ES3 and am having the same issue. The registry hack did not work for me. Here are the specs:
    - Windows 7 64bit
    - Office 2010 64bit
    - LiveCycle Designer ES3
    - Creative Cloud (CS6)

  6. Kelly says:

    We have just upgraded to LiveCycle ES3 to try and resolve this issue.

    We have Windows 7 64 bit with 64 bit MS Office 2010 and are still experiencing this problem. LC ES3 cannot find Word on the machine.

    Any advice?

    • dmcmahon says:

      I have tested this with Designer ES3, Windows 7 64-bit, MS Office 2010 64-bit and it works fine. I can only suggest to try the registry fix which solved the problem above. Pay particular attention to the paths (32 vs 64-bit), and also ensure winword is in the folder you enter in the Path value.

  7. subcan says:

    Thank you so much for this tip.

    I have been wasting long hours trying to find this info.

    Worked like a charm.

    As you note, you need to verify that winword is in the folder. Mine was in “program files” not “program files (x86)”