Hi,

When I add shortcuts in the Office Customization Tool for the desktop for Word, Excel, Outlook etc, I get the follow error message, please note that if I look at the preconfigured shortcuts for the start menu, they do not have a Start In folder specified.

So I added the start in folder off: C:\Program files (x86)\Microsoft Office\Office15\

Fine, no problem right? Well by doing so and clicking OK, the OCT tool adds the same string to the Arguements field and if I try delete that and OK it, it comes back when I open it again:

Sure enough, after install when launching the programs with these shortcuts I get error messages starting with:

"Sorry, we couldnt find your file. Is it possible it was moved, renamed or deleted? (C:\Program.doc)"

I guess I could create a script to create my desktop shortcuts, but I rather keep the deployment simple with the built in functionality.

Am I doing something wrong or is this just a bug?

• Edited by Trana010 Thursday, November 01, 2012 3:59 AM

Any one found a answer to this?? I'm having the same problem. I also tried using the %programfiles(x86)% variable and [inastalldir] for the start in path but no good.

Any help would be appriciated....

• Proposed as answer by Bob10444444 Friday, November 09, 2012 7:35 PM

We are looking into the issue with the shortcut locations within the 2013 OCT. I will let you know once I hear something back from our Product Group.

Doak[MSFT]

• Proposed as answer by Nanothx Saturday, November 10, 2012 10:13 PM

Same thing here.

• Proposed as answer by Bob10444444 Friday, November 09, 2012 7:35 PM

Modify your shortcut and blank out the Arguments Field by putting in a space.  Save it and you should be good.  We did find that this will not work for a Lync shortcut.

• Marked as answer by Trana010 Monday, November 12, 2012 2:27 AM

You can also type in a single open bracket [ in the "Start in" field to workaround this issue.

We are still looking into a fix for this.

Doak[MSFT]

• Proposed as answer by Stewart Hill Tuesday, January 08, 2013 5:15 AM

Unbelievable that this is still an issue in SP1.

I was thinking the same thing. The original issue was reported almost 2 years ago.

Microsoft, please stop ignoring the small things and fix the products we all pay a fortune for. 

Mike

• Edited by BradatQueen's Wednesday, March 26, 2014 6:35 PM Additional point to add.

just downloaded the OCT, dated May 16, 2015 and the issue is still very much present

think about it. If MS fixed all issues, half of us would lose their jobs. MS keeps the economy going. Go, MS, go!