When I click and drag Microsoft Office windows, they slide in slow motion then jerk to catch up

Anonymous
2017-01-30T08:03:48+00:00

Hi,

Recently I've been noticing a strange feeling while using Word and Excel. The first time I had seen it, I simultaneously had 26 documents on the screen and 1 spreadsheet, so I wrote it off as a reflection of my PC's inability to perform (but looking back I realize I've done much more demanding things). Today I opened word to work on a homework assignment when I wanted to slide the window to the side of the screen (not snap), so I could fit another window to its side. That's when I saw it for the second time. The best way for me to describe it is like, while you're floating in space, yanking on something (with a mass greater than your own) with an elastic band. So, initially it will move very slowly until you can overcome the elasticity of the band and the inertia of the window (the "mass"), and then it will accelerate very quickly in an attempt to catch up with the mouse movements, with lots of stuttering throughout.

BUT, in my testing, it seems to happen only when a document/spreadsheet is loaded, not when each program is waiting for input on whether to load something or start new.  It doesn't matter whether anything else is running on my desktop, just that Word of Excel are (I haven't tested PowerPoint or any of the other programs, but Outlook runs normally).

I wasn't sure where to turn to for assistance because I've never encountered a problem like this before, and a simple system restart has not been enough. If you need any more information, I'd be happy to give what is needed, but as far as I know, nothing of significance happened that have caused this.

***Post moved by the moderator to the appropriate forum category.***

Microsoft 365 and Office | Install, redeem, activate | For home | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2017-10-19T17:16:11+00:00

Taht's NOT a CPU performance issue nor a BIOS/Firmware setting issue, this happen on multiple system having display refresh rate higher then 60Hz. That's BAD CODE and only Microsoft can fix this.

Was this answer helpful?

100+ people found this answer helpful.
0 comments No comments

104 additional answers

Sort by: Most helpful
  1. Anonymous
    2018-02-26T12:38:09+00:00

    That's my turn to say "are you really sure?".

    Anyhow, it clearly demonstrates that new versions are less efficient, and that users returns are simply not taken into account.

    Eric.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-02-26T12:20:19+00:00

    There are a lot of examples.

    Just to mention one of them, Windows 7 had the nice possibility to customize the colour of all windows. This disappeared in Windows 8. A lot of users complained. And this is still not possible again in Windows 10. Less efficient, and users reaction not taken into account.

    Eric.

    That's not a bug, it's a customization, as you mention yourself.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-02-26T11:21:14+00:00

    There are a lot of examples.

    Just to mention one of them, Windows 7 had the nice possibility to customize the colour of all windows. This disappeared in Windows 8. A lot of users complained. And this is still not possible again in Windows 10. Less efficient, and users reaction not taken into account.

    Eric.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-02-26T06:29:18+00:00

    "Microsoft is releasing always new versions of programs"

    Duh...

    "saying this will make our life easier"

    It has and please give me an example how it has not.

    "finally these programs are working less efficiently"

    Give me an example to back up this claim of yours.

    "users are always reporting bugs, but nothing changes"

    That statement is complete **** that you cannot back up.

    Before you reply you should take a moment and cite sources that back up your outlandish claims first.

    Was this answer helpful?

    0 comments No comments