Hi Brian,

I've now tried  C:\PROGRA~2\MICROS~1\OFFICE14\WINWORD.EXE, C:\PROGRA~2\MICROS~2\OFFICE14\WINWORD.EXE, C:\PROGRA~1\MICROS~1\OFFICE14\WINWORD.EXE and C:\PROGRA~1\MICROS~2\OFFICE14\WINWORD.EXE with no success. I'll stick with what I've got - it's just I don't like mystery problems!

Thanks to you and Martin for your efforts

If I get a Word document as an attachment, I no longer have the option to open it by clicking on the Open button - I have to save it to desktop, then open it. Winword.exe is set as the option to open doc and docx files and the path is correct.

We know that the double click functionality fails on attachments above a certain size.  We're talking in the MB size; actual size before failure is unknown.  Might this be the case?

Hi Brian,

Even a 17 kb file doesn't open. All Word files used to

If a double click on a .doc or .docx file from a file explorer opens the file then consider removing the content viewer entries.

[quote user="Brian Fluet"]

If a double click on a .doc or .docx file from a file explorer opens the file then consider removing the content viewer entries.

[/quote]

I'm not sure what you mean, Brian. If I save the files to Desktop, I can open them with Word - is that the first part of what you are saying? What do you mean by "remove the content viewer entries? - delete them and add them back? If so, I've just done that and it had no effect

Edit - I've changed the option to Let Windows Choose and run an application" and it now works!

[quote user="Tom Barkas"]Edit - I've changed the option to Let Windows Choose and run an application" and it now works![/quote]

That's where I was going except approaching it from removing the entry rather than changing the setting (if no entry, the system default program should be invoked).

Glad you got it working!  I can't explain why the failure occurred when pointed to winword.exe though.

Thanks for the help, Brian

It sounds like your shortcut to Winword.exe is out of date or incorrect. I had some similar experiences, which lead to my findings on how to get Microsoft Edge to become the default browser. I would not advise anyone to try doing this until Microsoft revise their current invocation of Microsoft Edge. FYI invoking MicrosoftEdge.exe does nothing :-(

Martin

Hi Martin,

 I’m not clear what you mean. I browse to where  Winword.exe appears in Explorer and select it. What has the browser to do with Pegasus and Word? I don’t even use Edge

Sorry, I didn't mean to confuse you. What I was trying to point out was that with Microsoft Edge, the startup is from a shortcut to a Windows class, not the expected pointer to an Exe.

So I was guessing that in the case of Windows 10 and the latest Winword, there could be such a process.  As you mentioned, it was only when you removed the Pegasus Mail commandline path and let Windows choose the association of the document type being tied to one of its applications. Unfortunately I don't have Microsoft Office suite on my machine to test out or investigate what Windows and Office are doing.  Maybe someone else can dive in and research what is/was going on.

Martin

Hi Martin,

I'm easily confused. Just for information, I'm using Windows 10 latest update and Word 2010 in Office 2014

Now you mention Windows 10 and a recent Word version, I am increasingly suspicious.. Can I get you to find a shortcut or icon on your desktop that you can click to invoke Word. Could you then right click it and view the Properties. Then report back what the Target value is. Otherwise do you invoke Word by first invoking Microsoft Office and then selecting Word from its panel.

Reason for asking is that the actual pointer to Word may be in a different format or pointing to a different location (ie not Program Files (X86) )

Martin

Hi Martin,

It's not a recent version of Word - it's Word 2010. Here is the target "C:\Program Files (x86)\Microsoft Office\Office14\WINWORD.EXE"  - the same one I set up in Pegasus

Just a long shot, but I wonder if it is the path to Winword.exe that is the problem. By having blanks in the directory names that can confuse end of the file info and the beginning of parameters to be passed to the application. So I suggest you try coding something like c:\progra~1\winword\word.exe.  The tilde one (~1) indicates that Windows should use the short form of file path.

Martin

Sorry, Martin, you obviously think I'm far more intelligent and clued up than I am :-(. I'm the Man in the Street pre-Internet (though I did use to know Tim Berners-Lee in my Swiss days, if that helps - though as a skier and  Dame in the Pantomime rather than a CERN person)

 Can you put it into very simple language how to change the target from what I have now to the one you suggest? As far as I know, there are no blanks in the directory names, but, like I said, I'm pretty stupid!

Just an aside there are blanks in the directory name:  program files (x86)

                                                                                          |      |   these indicate position of blanks, so short format of file path is needed

so the location is either c:\Progra~1\microsoft\winword.exe   or c:\Progra~2\microsoft\winword.exe.   This has only been important since Windows 10. You will notice that there is a directory c:\Program Files   which is reserved for 64-bit files

Martin.

Hi Martin,

You want me to use "Progra~1" instead of "Program Files (x86)" and use "Microsoft" instead of "Microsoft Office" and leave out "Office14"?

 And type this into Pegasus instead of browsing for the file??

Only change the first part to progra~1  or progra~2.  Leave the rest of the commandline as you had it.  Try with ~1 first, and if that doesn't work try ~2. 

Martin

Hi Martin,

No, neither of those worked. There's still a gap in "Microsoft Office"...