Windows Explorer expands folders inappropriately, jumping the folder you expand to the bottom of the navigation pane

Anonymous
2009-10-28T18:12:01+00:00

When using a left-side Navigation pane, if there are enough folders in the navigation pane such that you have a vertical scroll bar, if you click on a folder with the mouse (so as to see the contends in the right pane), then expand the folder (either by clicking on the + symbol or with the arrow key), then the left pane will automatically scroll up as far as it can such that the folder you expanded is still in view at the bottom of the pane. This removes the folder from under your mouse, where it would be expected to stay.

This is certainly a bug, as it only happens the first time you attempt to expand a folder in the manner. After doing it once, you can scroll the navigation (left) pane so that the folder in question is back in the middle of the pane, and it will expand and contract as expected, remaining under the mouse.

Windows for home | Previous Windows versions | Files, folders, and storage

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
2011-06-30T22:14:30+00:00

Because many people seem to be interested in this issue, I'll post some info on my recent contact with Microsoft regarding this issue.

It seemed that everywhere this issue was talked about, all anybody would get from a Microsoft employee was a boilerplate "Thanks for your feedback" response. Never was the validity of the issue discussed or even acknowledged. I decided to write an email to the man in charge, Steve Ballmer, clearly laying out the problem with links to a walkthrough of the problem, this discussion, and the bug report with 220 votes (at the time). I realized that Steve would never read it himself, but I figured his email must get auto-forwarded to someone who might actually read it.

Two days later I got an email from an Advocacy Specialist from Microsoft saying a "grace case" has been created and the Windows Escalation Team would get in touch with me. The next day an Escalation Engineer emailed me asking when would be a good time to talk on the phone about the issues. So that he would be completely clear with what I was talking about, I recorded a screencast that walked through precisely what the issue was.

Edit: I've made a more condensed video demonstrating the "folder jump bug", view it here.

The end result of our talking was this:

  1. The engineers are aware of this issue.
  2. They may or may not provide a fix for it.

Nothing groundbreaking, but it's one more little push in the right direction. In my opinion, posting in this thread about the problem is virtually worthless. I would suggest:

  1. Voting up and commenting on the bug here:

http://connect.microsoft.com/WindowsServerFeedback/feedback/details/621426/bug-when-expanding-folders-in-explorer-server-2008-r2-and-windows-7

He said that site is closely monitored by the dev team.

  1. Writing intelligent, profanity-free complaints that mention how the bug negatively affects your everyday file-management workflow. Email these up the Microsoft food chain until you get a response. You are a paying customer and you deserve to be heard.

I got tired of dealing with it, so am now using XYplorer when doing heavy file management. It stings to have to pay for a decent file manager, but that is life. If this issue bothers you at all, please comment and vote on the bug, and write an email.

UPDATE 9/13/11: Bug is still present in Windows 8 Developer Preview, see it here.

UPDATE 1/30/12: Finally we have a public acknowledgment that this is in fact a bug that needs to be addressed, and it will apparently be fixed in the upcoming Windows 8 Beta. This is good news, but I know I will be using Win7 for at least another year or two, as will many, many others. We deserve a patch to fix this issue in Win7. Until that happens, keep bugging Microsoft about it.

FINAL THOUGHTS: This is a real bug with 645! votes on their feedback page, however MS has no plans to fix it for their Windows 7 users. The bug is fixed in Windows 8, which means nothing for a vast number of us who have no plans to upgrade. If this bug really gets under your skin, I suggest installing Classic Shell, which has been recommended a few times in this thread. You can choose to only install the 'Classic Explorer' feature which fixes this bug among others, and even brings back the old File Copy UI which is so nice to have back. I've been using it for many months now without any troubles.

Also, to those of you who think they find a solution to this problem by simply changing a few options settings somewhere... thank you for your desire to help all of us, but you must not be having the same problem, and please don't post your 'solution' here. If you read some of the 29 pages of this thread, you'll see every solution imaginable has been suggested. This is a bug in Explorer itself. If you use Windows 7 and plan to keep using it, your options are 1) use Classic Shell, or 2) use a third party file management tool, such as XYplorer. If you stumble across this thread because you just noticed this bug, please vote up the bug, and do either 1 or 2.

Was this answer helpful?

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

586 additional answers

Sort by: Oldest
  1. Anonymous
    2014-06-23T14:49:08+00:00

    Taking an issue that has been introduced during bug fixes and enhancement updates and labeling it as 'working as intended' is not a solution or answer.  Windows explorer did not perform in this manner in previous versions.  If Microsoft can provide documentation that specifies this was intentional by design, share the documentation.  Stating that no fix will be provided for the Windows version (7) that the issue was introduced is not right either.  I am not self-employed and the decision whether to upgrade to a newer version of Windows is not mine to make... my employer makes those decisions.  Therefore, provided the forum moderator cannot produce the documentation specifying this behavior is working as intended, Microsoft can either have a lot more unhappy customers or they can provide a fix for the bug they introduced.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-06-23T21:40:15+00:00

    Taking an issue that has been introduced during bug fixes and enhancement updates and labeling it as 'working as intended' is not a solution or answer.  Windows explorer did not perform in this manner in previous versions.  If Microsoft can provide documentation that specifies this was intentional by design, share the documentation.  Stating that no fix will be provided for the Windows version (7) that the issue was introduced is not right either.  I am not self-employed and the decision whether to upgrade to a newer version of Windows is not mine to make... my employer makes those decisions.  Therefore, provided the forum moderator cannot produce the documentation specifying this behavior is working as intended, Microsoft can either have a lot more unhappy customers or they can provide a fix for the bug they introduced.

    I totally agree.  But just watch what happens next which I think you will find will be exactly nothing.  We have no recourse and they have all the cards in their hands.  It's called a monopoly and it's time regulators got a lot tougher on it.

    MS already has plenty of unhappy customers.  Many of them pay the periodic ransom for the next 'upgrade' only because everybody else is doing it too and they don't want to (can't afford to) be left behind.   Wouldn't it be fun if we all agreed not to buy the next upgrade and wait to see what happens next.  Remember US DoD refusing to take Vista?

    Why, for example, does business and government go on paying for upgrades to Office.  I have yet to encounter much of anything they are doing that could not have been done in Word 2000 and in general use of the products is so unsophisticated that there can be no case for upgrade.  But now we have prettier toolbars that have slowly morphed into that execrable ribbon.  And still the depressingly primitive use of these products continues.  How many do you know who use even simple features like automatic paragraph numbering and automatic cross references?  How many do you know who still use two carriage returns at the end of a paragraph?

    Sigh!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-06-24T18:03:41+00:00

    I totally agree.  But just watch what happens next which I think you will find will be exactly nothing.  We have no recourse and they have all the cards in their hands.  It's called a monopoly and it's time regulators got a lot tougher on it.

    MS already has plenty of unhappy customers.  Many of them pay the periodic ransom for the next 'upgrade' only because everybody else is doing it too and they don't want to (can't afford to) be left behind.   Wouldn't it be fun if we all agreed not to buy the next upgrade and wait to see what happens next.  Remember US DoD refusing to take Vista?

    Why, for example, does business and government go on paying for upgrades to Office.  I have yet to encounter much of anything they are doing that could not have been done in Word 2000 and in general use of the products is so unsophisticated that there can be no case for upgrade.  But now we have prettier toolbars that have slowly morphed into that execrable ribbon.  And still the depressingly primitive use of these products continues.  How many do you know who use even simple features like automatic paragraph numbering and automatic cross references?  How many do you know who still use two carriage returns at the end of a paragraph?

    Sigh!

    Execrable ribbon. Perfect description.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-07-28T23:16:54+00:00

    Yep you are right. We just have to pay for a new way to do the same thing or get left behind. Back to the folder jumping - I am having the same problem even with Classic Shell installed. Back to PowerDesk.

    Was this answer helpful?

    0 comments No comments