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: Newest
  1. Anonymous
    2017-01-08T23:32:40+00:00

    Hi Rod Weir.  Yes, there are good Windows Explorer replacements.  Even some of the freebies.  But they don't fix the bug where it persists in software (practically all running on MS Windows) in "Open" or "Save As" dialog windows  Regardless of what Explorer replacement you use, the "File Dialog" windows still have this bug.  Because it's a Window 7 component bug, not just the Explorer.

    And now that I hear it's back in Windows 10 it tells me that the development team for Win 10 started with a copy of Win 7.  That's how large developers have to work.  They may have 2 or 3, or maybe more, streams on the go.  Each with their objective and budget.  What that means is that often a version or two are skipped, and unfortunately all the fixes within those skipped version.  There are many examples of this in the software world.

    Seems that "things learned" (as in past errors) are not passed on to all streams.  Maybe they are, but it seem more likely that Marketing wants to just have changes made so that they have a new product line that they can sell, but aren't really interested in spending time to "fix" past errors.  It does depend on the incident rate of error reporting and exposure by important people in this business.  So the 500 or so for this bug is just not enough, or we are too puny.

    I don't blame the developers or programmers.  They don't have the kind of control to spend money on fixing things.  That is driven purely by Marketing. 

    When Windows 95 came out there was a well developed online feature in place for reporting errors, and there were easily found links to get there.  It may still exist, but if it does, I can't find it.  That's why we have these forums, which it seems they can choose to ignore.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-01-08T17:31:47+00:00

    and still not fixed in the latest insider preview version of Windows 10, Microsoft are clueless

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-12-14T08:05:13+00:00

    How many people read 52 pages of replies or trust sourceforge?

    Clearly, people like Delboy_666 who don't even read the last two pages to find the answer to his problem.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-12-14T02:49:05+00:00

    Hi Delboy_666,  It actually started with Win7, and was never fixed in Win7.  There was a time when Microsoft said this was "by design".  That's why there are hundreds of post on this matter. 

    Now that I hear that it's back in Win10, I am even more confirmed that I will stay with Win8.1.  It runs well, and I don't get the jumping in the Windows Explorer, and I don't get pushed into the "online" Microsoft world, because all my software from Win7 works on Win8.1, including MS Office Pro 2003.  That Office does everything I need, including a number of Macros that run well from the Toolbar.  That Office is 32bit, but Win8.1 64x handles it well.  And so far I have had no problems getting any drivers for new hardware, like printers.  And lastly, there is a ton of free software out there that is written for Win8.1, so I don't have to use Apps, which are just not my kettle of fish for a desktop. 

    For those that like Win10, I am in no way running it down, I am just saying that Win8.1 is just fine for me.

    Was this answer helpful?

    0 comments No comments