Windows programs not loading properly when launched outside Parallels Desktop 9 VM

Discussion in 'Installation and Configuration of Parallels Desktop' started by guyo1968, Oct 7, 2013.

  1. guyo1968

    guyo1968 Bit poster

    Messages:
    6
    I'm having problems launching Microsoft Office 2010 applications from outside the Parallels Desktop VM ever since upgrading from Parallels Desktop 8 to 9 on my mid-2010 MacBook Pro 15".

    I have, for example, all Word .docx files associated with the Microsoft Word 2010 Windows application in Mac OS X Mountain Lion.
    If Word 2010 isn't already running within the Parallels Desktop 9 VM and I double-click a .docx file in the Mac OS X Finder, I'll see the icon of the virtualized Word 2010 application show up briefly in the Dock, as if the application is opening (as it should), only to see it spontaneously close down and disappear immediately after (this literally happens in roughly a second and a half).

    If Word 2010 does already happen to be running inside the VM and I double-click a .docx document on Mac OS X, nothing actually happens. Word 2010 remains open within the VM, though the document will NOT open up, as if the document launch request from outside the VM is ignored.

    Double-clicking a .docx file in Windows Explorer within the Parallels Desktop 9 VM, and opening it directly from within Word via File-Open both work as expected.

    Launching Windows applications by double-clicking their respective documents in Mac OS X Mountain Lion's Finder worked perfectly well with Parallels Desktop 8. What happened? Oh, and I've applied the latest update for Parallels Desktop 9, yet this has not fixed the problem.

    Finally - pressing F6 to toggle between the full-screen VM and Mac OS X now only works erratically. F6 wouldn't do anything immediately following the upgrade, though it started working as expected again following a full restart of Mac OS X. It has, however, continued to demonstrate erratic operation since (i.e. F6 won't do anything from time to time, and I'll have to actually click the Parallels Desktop icon in the Dock to switch to the full-screen VM).

    This is turning out to be the least stable of Parallels Desktop upgrades I've experienced so far (and I've gotten here all the way from version 5).

    Help?!
     
  2. guyo1968

    guyo1968 Bit poster

    Messages:
    6
    Bump?

    Anyone?

    This is extremely annoying, and I'm seeing similar reports here on the forums.
     
  3. redpark

    redpark Bit poster

    Messages:
    1
    I'm getting this exact issue - no resolution anywhere...

    I've tried reinstalling Parallels tools, reinstalling Parallels Desktop and even a brand new VM and still get Word documents (in .docx only) not opening as described by guyo1968.

    .doc files opened from Finder will open as expected in the VM, but .docx will not.

    This needs a fix, or a workaround quickly - please!!
     
  4. Andrew@Parallels

    Andrew@Parallels Parallels Team

    Messages:
    617
    Hi All,

    The next time when you reproduce the problem, please submit a problem report: http://kb.parallels.com/9058 and post the ID here.
    We need to check what's going on on the system level. Thanks!
     
  5. redpark2

    redpark2 Bit poster

    Messages:
    1
    Problem ID generated and reported: 29885021
     
  6. Teddy J

    Teddy J Bit poster

    Messages:
    7
    Interested to hear if you're able to solve this problem. Very annoying.
     
  7. Teddy J

    Teddy J Bit poster

    Messages:
    7
    Interested to hear if you're able to solve this problem. Very annoying.
     
  8. mfairfield

    mfairfield Bit poster

    Messages:
    2
    I'm having the same issue along with some other issues too.
     
  9. mangamaster03

    mangamaster03 Bit poster

    Messages:
    1
    I too am having the exact same problem. The first few times it happened, reinstalling parallels tools worked, but now, not even that fixes anything. This is super annoying...
     
  10. mfairfield

    mfairfield Bit poster

    Messages:
    2
    I think this might now have been fixed with the latest update. I'll let you know if the problem re-occurs.
     

Share This Page