A Windows Update Broke Login Button, and Microsoft's Advice is To Click Where It Used To Be (tomshardware.com)
- Reference: 0180251943
- News link: https://tech.slashdot.org/story/25/12/01/1710222/a-windows-update-broke-login-button-and-microsofts-advice-is-to-click-where-it-used-to-be
- Source link: https://www.tomshardware.com/software/windows/windows-update-makes-sign-in-password-icon-invisible-microsoft-says-you-can-still-click-on-empty-space-to-enter-your-password
The issue affects Windows Insider channel users who installed the non-security preview update. The company's suggested workaround is straightforward if somewhat absurd: [2]click where the button should be , and the password field will appear. Microsoft said it is working to resolve the issue.
[1] https://www.tomshardware.com/software/windows/windows-update-makes-sign-in-password-icon-invisible-microsoft-says-you-can-still-click-on-empty-space-to-enter-your-password
[2] https://support.microsoft.com/en-us/topic/august-29-2025-kb5064081-os-build-26100-5074-preview-3f9eb9e1-72ca-4b42-af97-39aace788d93
Paging Dr. Jones? (Score:4, Funny)
So it's like Indiana Jones searching for the Holy Grail? You must exercise a leap of faith to find the screen.
Re:Paging Dr. Jones? (Score:4, Funny)
You could also put a few grains of password into a bag, and set it where you "Think" it should go.
Re: (Score:2)
*Places grains of password in a bag, and places bag where it "should" go.*
*Monitor and desk starts shaking.*
"Oh, shi....."
Does anyone know what "preview" means? (Score:2)
Much as I hate to defend Microsoft, if this is an update that's clearly marked as a "preview" or "testing", then it shouldn't be a shock if it breaks since that's the purpose of doing a test release.
Re:Does anyone know what "preview" means? (Score:4, Insightful)
In any Tech circle, even on a test release, this is what is known as an "Embarrassing lack of basic QA/QC"
Re: (Score:2)
As someone who used to test PTR builds for WoW for game breaking bugs prior to release to the PTR servers, prior to Activision buying them *(Austin, TX location)... I can tell you that one must "Log into the build" as QA step #1. You have a QA team for EXACTLY this type of thing. They CLEARLY didn't so much as log into this build to do any testing of ANY kind. They used AI to write code, assumed it was right, and that it would break nothing, SKIPPED the other 99% of their job, and hit the "Rease to Producti
Re: (Score:2)
Like whoever QA's the Google Spell Check...
Re: (Score:2)
Well, preview/testing or not (but released to the public), being a 50 y.o. company who can't implement a button that just work should be the last nail in their coffin and send everybody toward Linux, at an even more accelerated pace than Windows 11 requirements did.
I can't see any good reason for a button text/bitmap/whatever being separated from its action area.
Oh, wait ? Something to do with those web based user interfaces and/or flat design (by the way, a flat design button where only the text is consi
Re: Does anyone know what "preview" means? (Score:2)
It's Tomshardware they've turned into a total dumpster fire in the last few years. They even recently added subscriptions. The site is the poster child for enshitification.
Re: (Score:3)
If it made the news, I'm *assuming* it is quite a common issue.
A common issue in a key part of the system.
If your QA team doesn't even log in to the system using most methods while testing, why do you have it? Logging in is functionality 101.
If they hadn't had so many fuck ups in the recent past, I'd be lenient too. But this is becoming a farce.
Re: (Score:2)
Depends on what "preview” means. If it means an alpha build meant to be internal, such a bug is fine. To me this build was meant to be shown and tested by customers and closer to a beta build. Nothing ruins testing like the inability to test anything.
One time my company was asked to test some software for a supplier. The software would not run after install on any of our computers. There were no errors displayed to give us hints about what could be wrong. Despite weeks of correspondence with their d
They are using AI to code core Windows functions (Score:4, Insightful)
And then having people check it. The result is every single update can randomly break shit that doesn't get caught.
Having people check the AI code at slop doesn't really work because the entire point of AI coding is to do it fast and cheap so there's going to be enormous pressure to do as little checking as possible.
Not that it matters. Microsoft has a monopoly. Any viable competitor will simply get taken out by well-known and well understood anti-competitive tactics. And because we refuse to enforce those laws because we refuse to vote for politicians who will enforce those laws Microsoft can basically do whatever they want. With the occasional bribe to some of the larger governments that might try to regulate them.
I think Europe is actually trying to quit the habit but I don't think they will be able to. I can tell you right now that there is no alternative for Microsoft Excel when you're doing large complex spreadsheets. Open offices nice but it just doesn't cut it. Some of that's because of shitty little patents Microsoft has but the system is designed to let them keep generating new patents that make it difficult to compete. And some of it is just that it's rough going writing office software so it's tough to compete with someone who can pay people to do that kind of boring dreary work.
And of course you have the aforementioned anti-competitive tactics that work like a charm.
I'm not even going to say we need to decide what's more important, software freedom or whatever bullshit that makes us vote for pro corporate anti-capitalist political candidates (and mark my words pro corporate is just as anti-capitalist as any socialist or communist just in a different direction)
It doesn't matter what the reasons are the end result is we don't enforce laws.
Re: (Score:3)
> I can tell you right now that there is no alternative for Microsoft Excel when you're doing large complex spreadsheets.
If you need accuracy then you shouldn't be using Excel especially if it's complex. It's just plain unmanageable. I've wasted too many hours fixing peoples errors to even begin explaining why here...
Re: (Score:2)
you're not wrong, but the reality is it's easily accessible to nearly everyone working in nearly every company. Do you really think Karen in Finance is going to request an RDS instance and vibe code a nice react frontend for her CRUD?? No she's going to open up excel and paste in some numbers, and it will never ever end.
Short! (Score:2)
MS stock is only down 1% today. Still time to get in.
They claim to use AI for 30% of their coding. If they had even one person QC this build, this would have been caught. You can't log in to test without hitting this bug.
[1]https://www.cnbc.com/2025/04/2... [cnbc.com]
If this is the future, we're all in trouble. And yes. I run Ubuntu, but none of my corporate programs run on Ubuntu. I have to use MS. As does most of the world.
[1] https://www.cnbc.com/2025/04/29/satya-nadella-says-as-much-as-30percent-of-microsoft-code-is-written-by-ai.html
Why does WIndows password field need focus? (Score:1)
Why, when I type my password in the Windows login screen, is it ignored if the password field does not have focus ?
Would it be so very very hard for a Microsoft engineer to get an AI to write code to check any characters input anywhere in the screen against the password and allow access on a match ?
ran into this (Score:2)
I have a user where this happened and I figured out to direct him to click where the icon used to be. Though we manage Windows Updates through WSUS and we don't push out Preview patches, go figure. I don't want to be Microsoft's QA team.
Alternate headline (Score:2)
> renders the password icon invisible on the lock screen, ... click where the button should be
"Microsoft takes Security Through Obscurity too far."
AI QA (Score:2)
It is funny you all think humans do QA for Microsoft these days.
And how many people use a mouse to click the login button instead of just pressing enter.
I have a better idea (Score:2)
Just install Linux where windows used to me,
That's a "It works on my system" bug (Score:2)
I cannot see how that would be something you miss, it's so obvious that it must be a layered bug, that only happens due to other updates / drivers, etc... I feel bad whoever gets blamed. There's a bug on a local coffee businesses website, where if you're running Wayland, and you open the site on Firefox, it will be completely unusable, any other OS, or X11, it's fine. I've been in contact with them, gone over it with them, they have no idea why it's happening, that's the same kind of thing that's probabl
Well, they can't test everything (Score:2)
Software is hard.
Times are tough.
We all have to do our part.
Windows 11: Click Where the Functionality Once Was (Score:2)
Great new marketing slogan! MS, take note
Vibe coding (Score:2)
How's that vibe coding working out for you Microsoft? This is simply beyond enshitification.
Use AI to write code, they said... (Score:2)
It will be fine, they said...
- Hey, AI! Pimp my login button.
- Alright, mate. But you haven't said it can't be transparent!
"Microsoft said it's working to resolve the issue" (Score:3)
Translates to = "Working to fire whoever let this hit without QA/QC testing" ;-D
Re: (Score:3)
This is the beta build. So it IS the QA/QC testing. A total nothingburger story.
Re: (Score:3)
Basic QA 101, of ANY kind, prior to release = "Logging into the Build" Its functionally "Step one" and was clearly skipped. This is an utterly embarrassing lack of any QA of any kind. Even PTR test builds for WoW, were sent through QA/QC prior to release. I know, as I was one of the people flagging those bugs when I worked for Blizzard ;-)
Re: (Score:2)
> This is the beta build.
Exactly. Problems like this should be discovered long before a Beta release. This isn't some kind of esoteric corner case.
> So it IS the QA/QC testing.
Translation: Microsoft has outsourced its QA to volunteers.
Re: (Score:2)
> Translation: Microsoft has outsourced its QA to volunteers.
You mean MS has outsourced QA to AI. I would think volunteers would have found that issue quickly.
Re: (Score:2)
The volunteers are those in the "Insider" program -- downloading and running Beta software.
Re: (Score:2)
> A total nothingburger story.
Totally. This is the kind of "Bug found in QC/QA test version of software" headline you'd get from www.totallyexpectedtohappen.com.
WTF Slashdot? I'm all for raging against Microsoft's corporate hegemony cesspool but this is just fucking stupid.
Re: "Microsoft said it's working to resolve the is (Score:2)
You cant fire someone for following current company policy.
Re: (Score:2)
ANY level of QA prior to hitting the "Release to Production" button, such as "Logging into the Build even one time" would have caught this. This is what as known in the QA world as "Getting caught with your pants down"
Re: (Score:2)
"even one time"
Unless you never use a password, in which case, you log in via all the other available options BUT password. You don't notice it missing. Passwords are so 1980s, get with the program.
I don't use biometrics because .. lets just say they are their own version of compromised. You cannot be compelled to give up your Password (legally) (hammer method is still valid) but a fingerprint, face ID etc that doesn't require you to speak can be compelled. I have no idea why people think it is "more secure
Re: (Score:2)
So a passwordless, domain connected PC, connected to a Microsoft network? That would 100% not surprise me ;-D
Re: (Score:3)
The QA/QC team are probably like me legitimately asking "there's a button"?
No I'm serious... I haven't seen a logon button since Windows XP. I mean I'm sure it's there, but who doesn't just type in their password / pin and then hit enter?