Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Start Menu over Remote Desktop RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hello,

    This is probably a known issue - but does anybody else have problems with the start menu over remote desktop on live mesh?

    Basically, when I click the start button, the start menu pops up, but it doesn't stay up - it almost immediately disappears.

    Just curious if anybody else has run into that - or maybe if I'm doing something wrong.

    Thanks,

    Mike
    Sunday, January 18, 2009 8:17 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Mike,

    We had a similar report back in August, but were unable to reproduce the problem internally.  At this point, then, it is probably best if you submit a new bug of your own as Oren suggests - and we'll take a look again.  Please post your Connect Feedback ID here after you have submitted the bug so that I can follow up internally.  And let me know if you have any questions.

    Thanks,

    Ben.
    Monday, January 19, 2009 5:39 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    I haven't seen that behaviour before - and I can't replicate now when I try to remote desktop to another machine. Does the same happen if you use the keyboard shortcut (ctrl + esc)?
    Sunday, January 18, 2009 11:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hello,

    Thanks for your reply and interest... I figured this must be a little odd...

    Yes - I get the same result using the start key and ctrl/esc.

    The target computer runs Vista Home Premium, SP1. v. 0.9.3424.14. The computer I am connecting to it with has XP and the same version of live mesh.

    Thanks,

    Mike


    Monday, January 19, 2009 4:22 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Mike,

    As you say - it's a weird sounding bug!

    I've found something similar that happens with VNC's remote desktop, possibly following some of the suggestions will help? Since this is happening consistently I doubt it, but the check for pressed keys is a good one to do.

    Apart from that, I'd recommend opening a Connect bug (instructions in the announce on the front page) and collecting logs from both the client and the machine you are connecting to, and submitting them with the bug.

    Good Luck!

    Oren
    Monday, January 19, 2009 6:44 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Mike,

    We had a similar report back in August, but were unable to reproduce the problem internally.  At this point, then, it is probably best if you submit a new bug of your own as Oren suggests - and we'll take a look again.  Please post your Connect Feedback ID here after you have submitted the bug so that I can follow up internally.  And let me know if you have any questions.

    Thanks,

    Ben.
    Monday, January 19, 2009 5:39 PM