Sometimes Alt + Tab switches to the wrong window (since KB4571744, 19042.487) #40
Comments
adrianghc
changed the title
adrianghc
changed the title
|
@adrianghc I think this might because of a new Alt+Tab setting. You can control it here: |
I already said in my first post that I have that feature disabled (i.e. my setting is to show only windows, no Edge tabs):
And in any case, using Alt+Tab should always switch to the expected window, even with that setting, shouldn't it? As I said, I do strongly suspect that the bug is a consequence of the new feature as it doesn't appear on 2004 but it does on 20H2 and happens with Edge windows. But it's a bug in any case. |
|
I've also been hitting this on 19042.541, with Edge tabs in Alt + Tab disabled. It looks like Edge windows occasionally like to move themselves back to the top of the Alt + Tab stack, messing up the existing order. |
Yes, exactly! Thank you for chiming in. I'm running Edge beta 86 and I also had this issue when Edge beta was on version 85, so I suspect the Edge version may be irrelevant, and that it's purely a Windows bug. |
|
Thanks for the feedback. I've pinged the team. Please also submit via feedback hub, capturing a repro, and share a link to the FBHub item in this thread. |
|
Thanks for pinging them team. I already did the Feedback Hub jazz a while ago, including several repros: https://aka.ms/AA9sxgk |
bitcrazed
added
Status-Fixed
|
Quick update: The team have a fix which is working its way through the build system. Should arrive in a Win 10 Insider Dev (Fast) ring build within the next few weeks. Will update this thread when it lands. |
|
That sounds good, thank you for the quick follow-up and thank you to the team, of course. Though with that timeline, I do have to wonder whether this will arrive to 20H2, which will supposedly release in October. Any chance this may get backported there after its release? In any case, let me say that this is a significantly better experience than the Feedback Hub. Issue reported, issue confirmed a week later and a fix is confirmed to be on the way. Compared to FH, where from my experience issues often languish for years without a fix in sight (looking at the completely broken Task View animations with tons of upvotes over the years), this is leaps and bounds beyond. I'd be very happy to see the scope for this kind of feedback be expanded over time. :) |
Great to hear! Thanks for the rapid response on this one. As Adrian asked, any chance this might be backported to 20H2 given its imminent release? |
It's better because the scale of feedback is tiny here compared to Feedback hub 😄 Rich can only do so much in a day though, so if this gets too popular then you'll likely see things drop off (or his colleagues will notice he's not getting enough sleep). That said, this Alt+Tab bug has been driving me crazy, so I'm also happy that I found this issue about it and had a great experience 😊 |
|
Of course, I understand. I don't expect this kind of channel to be used for everything, but I do hope you can expand the scope of this kind of feedback as far as it is possible while still keeping it an effective and engaging experience. By the way, since you chimed in, might I borrow - with all due respect and with the risk of sounding like a broken record - just a minute of your time and ask you if there is anything you can say about the broken Task View animations? It seems oddly difficult to get anyone to even acknowledge them in any form. |
|
Sleep? What's sleep? We have a 15 week old puppy so don't get sleep anyhow ;) Many thanks for your kind words @adrianghc, and for your support @zooba, as always 😁 Hopefully our demands for quality issues, combined with a growing number of us in MS and helping out in the community will let us remain responsive and helping find and fix issues. |
|
@adrianghc - do you mean the animations you see when you minimize/restore apps to/from the taskbar, etc? If so, please file an issue describing what you're seeing / would like to see. I work with a number of colleagues who're looking deeply into UI quality and consistency as I type, and would be happy to direct to your feedback. Thanks in advance. |
|
@adrianghc @nmraz Checking with the team re. servicing this for 20H1 users. Will let you know when I hear back. |
I mean the animations that appear when you open Task View / Timeline. The window thumbnails jump around and this has been an issue since 1809. It has been reported and upvoted many, many times over the years., e.g. here. I also opened an (admittedly somewhat dramatically written) issue about it here at #38, though it was understandably closed for being out of scope. Then there is the problem with window thumbnails in the taskbar, but someone already filed an issue about that in #12, but I suppose that's not what you meant. Do you mean the problem where windows minimize in a slightly different direction the first time after being opened than the times afterward? |
Thank you very much. :) |
It would be cool if at least one of those colleagues of yours, @bitcrazed, could look into the issue reported in #38 :) |
|
@adrianghc Gotcha, thanks for raising. I've reopened #38 as we'll soon be expanding our scope somewhat anyhow. I'll also forward to our UX lead who's working with several groups and teams to improve UX. Stay tuned! |
|
I've noticed this in the changelog for the latest Insider build 20231:
Is that the fix for this issue? |
Interjecting here, @adrianghc, I think the confirmation will be when you cannot recreate the issue after installing that insider build (or one closer to release). I know that's a pain, but it seems to be the ultimate test for UX problems. At least we know that the MS WinDev folks here are grown-ups and no one has said "works for me :)." "Won't fix" maybe, though I don't see that so far. |
|
Well, I'm on the Beta channel currently, so I won't know firsthand until 21H1 gets much closer to release. |
|
@Felix-Dev Please try and avoid cross-contaminating issues. See my recent response to 38: #38 (comment) |
|
@bitcrazed To be fair, at that point the issue in question had been closed so I used the context of your message "I work with a number of colleagues who're looking deeply into UI quality and consistency as I type" to raise awareness for that issue again. That issue had also been mentioned by the OP in this thread here which coupled with that quoted comment of yours led me to reference that issue. That said, I generally avoid "cross-contaminating issues". |
lmfao good one. unpaid volunteer testers who file bugs that the company doesn't even see. total joke! oh wait. that's windows insiders and microsoft. |
|
@DJSures / @Poopooracoocoo spot on. Can confirm this issue is solved by switching to macOS 11.0.1. |
|
Glad I found this thread, now I have people to share my frustrations with. IMO this unpredictability in Alt+Tab is really horrible. I hope there's a faster way to get the fix, instead of having to wait for months :( I just need stable OS behaviour. I'm not looking to switch to Insider Builds. |
|
Just chiming in to say that I agree the frustrations stated above. While not an issue that MS deems worthy of a fast-tracked fix, my day-to-day productivity has been affected. As a programmer I'm switching between VS, SSMS, and Edge Chromium hundreds of times per day. That's hundreds of opportunities for MS to politely remind me through inaction that this issue isn't important enough to fix in a timely manner, or that their update system is so broken that it's impossible to fix in a timely manner. Either way, I think most reasonable people would consider that unacceptable. |
|
It's just unacceptable that MS shipped this ALT+TAB bug to the general public, a feature that has been around since Windows 2.0 (1987). Seems like there's something completely wrong with that 'crowdsourced QA' Microsoft has been using since 2014! |
|
Adding to the pile of negative comments, this bug is really annoying, unacceptable, even less acceptable is the time is taking to fix it. I don't care about insider, fix it on the final product already. Annoying as hell. |
|
Oh, Gosh. Two days since I've installed Windows, and all these days I thought that my keyboard was broken. Hope the fix will be rolled to the production as soon as possible 🤞 |
|
Any progress? |
|
I've been using the classic ALT+TAB for a while now because of this issue. Hope this can be fixed as soon as possible. While using the classic ALT+TAB solves the random window selection, but I can't see the window when I switching. |
|
All. Merry Xmas. Hope you're all having a great time with your family and/or friends, either virtually or IRL. To those asking if progress is being made, the answer is yes - as I stated here and here, this issue has been fixed, and is working its way through our standard release pipeline. It'll arriving in a servicing release in the New Year. I'll update this thread with details when it arrives. We appreciate your continued patience. |
|
Enough window-window game now please fix it, this bug is really annoying me while coding. |
|
Ha - we’ve been calling it window roulette. No one knows what random window they’re gonna get when coding. It’s been costing the developers a ton of time (and thus costing the company). Because they switch into the wrong visual studio and start coding the wrong module for what they just tested. This is such a costly bug for organizations and contractors. |
|
Guys I thought it was me, but I see here it's a bug, unbelievable, it's annoying for me, and I cannot work with a smaller screen for now. I still wonder why this isn't fixed? |
|
@therist well if you want to know why, it's because Windows is a very low priority for MS. They focus on Azure and subscription services like Office, but mainly the Office Android and iOS apps. |
@Poopooracoocoo I wouldn't go so far as to claim that they don't understand the dominance of Windows, and they don't care. They lost the windows dominance in the dev market, as many moved to Macs, and some even dabbled with Linux. So they implemented a bunch of dev features, like creating WSL, to try and win people back. Admittedly it takes a lot of effort to build everything. Look at VS Code, look at Typescript, everything for free, and they are high quality products. So they are really trying to get developers to use as many of their products as they can. Same goes for Azure, and to be honest Azure is in some regards much better then Google Cloud, and I believe it grows much faster, so it's kind of hot for them, and it's understandable if they have a lot of resources committed there. This alt + tab issue just feels like an unnecessary issue that usually comes from the ambition of a junior dev, a feature updated without proper testing. It's not like they wanna fuck with us. If I assume that Windows 10 code base is 50% bigger and more complex, than the initial code base of Windows 10 when it was released, I would probably be right. Not to mention any comparison with Windows 7. And on top of everything they have to support a lot of legacy shit, and continue implementing a lot of other cutting edge shit. I'd just say don't brake basic things like alt + tab, do some testing and less rushing. |
Seems 2021 now, still not fix👏👏 |
Thank you!
Not everyone is a Windows Insiders and certainly not everyone can/is allowed/wants to run insider builds on their work machines.
While this might not be a "critical security fix", it ruined a 30+ year muscle memory for me that is essential for day to day working. It's like if command prompt would suddenly fail to open every second or third time or Windows Explorer refused to copy files now and then and so on. Not critical, but is it a good idea to have basic OS functions broken? |
|
@therist They're freaking massive. Windows 10 should be easier to maintain than 7 with UWP. But truth is that even Microsoft still uses win32. They simply haven't allocated any resources to development of Windows as an operating system. We wouldn't have control panel. Apps like Event Viewer would support HiDPI. Microsoft themselves don't use MSIX or their Store. The list goes on and on. And as a more recent example, it's why Apple was able to shift desktop computing to ARM. They went all in. It's not just developers that suffer using Windows 10 and encountering its bugs every single fucking day. For many it's the only "real" operating system. Chrome OS doesn't have the same programs, largely because it's either Android apps or websites, and macOS is out of reach for many due to the prices.
But the thing is that it went untested. The whole point of being a junior dev is that you learn from people who are more experienced. They do want to fuck up Windows by not allocating any resources to it, whether they know it or not. It's especially disappointing given that it's mostly newer code that is fucked up. Look at the task view and look at how the touch keyboard from version 1709 to version 2004. |
This thread is getting ridiculous. What, you expect them to push out an update on New Year's or on the weekend afterwards? This won't be pushed out before Patch Tuesday, and rightfully so. |
|
Can confirm that this is fixed. Running build 21277 |
|
Its been 2 months and a half that this bug drives me crazy and affects my productivity because of its unpredictability, how come it's been nearly A QUARTER and that's not fixed? |
|
When can it be fixed? It's 2021 now |
|
Maybe stop spamming everyone's inboxes with useless comments. People want to be notified when the issue is fixed, not hear endless whining. It may be frustrating, but just give the previous commenter a thumbs up and move on, especially when it was recent. |
|
Sorry all. Despite all the polite asks to please be patient while this fix rolls out via our standard servicing mechanisms (most recently here), this issue is still receiving less than useful responses, so I've locked the conversation and will update it with details of when and how this fix will be delivered to in-market GA OS builds. |
|
All: As per the Windows 10 Build 19042.782 (20H2) to Beta and Release Preview release notes:
Those of you who are on the Beta and Pre Release channel builds will see this fix after you've updated to 19042.782. A GA update will follow in due course when quality is confirmed. |
|
Closing this issue as there's no further work to be done to remedy the reported issue. The fix is shipping in currently released insider builds and will arrive in GA builds in the next Windows release. Thanks all for reporting this issue, and for your support and patience while we drive the fix. |
and others
Environment
Description
Sometimes, when pressing Alt + Tab the wrong window is being switched to. Specifically, if one has three windows A, B and C (appearing in the Alt + Tab menu in that order) and is switching between A and B using Alt + Tab, sometimes window C switches to the foreground instead. When this happens, it can be observed that the selection on the Alt + Tab menu is not on the second entry, as it should be, but on the third. This problem has been appearing most likely since KB4571744 (19042.487). Also, it appears to only occur when one of the open Windows is Edge, though I cannot confirm this with absolute certainty as the problem cannot be reproduced entirely reliably and appears often, but irregularly.
I suspect this may be related to the Alt + Tab changes for Edge tabs, even though I have that feature disabled. Needless to say, it's very annoying to work with several windows and not switch to the one you expect.
Steps to reproduce
Expected behavior
When switching between two windows using Alt + Tab, the active window should alternate between those two only.
Actual behavior
When Edge is one of the windows, this sometimes the wrong window switches to the foreground.
The text was updated successfully, but these errors were encountered: