> this update disrupts mouse and keyboard functionality within the Windows Recovery Environment (WinRE), making them unresponsive
> Early last week, Microsoft accidentally broke the Windows Media Creation Tool (MCT) just a day ahead of Windows 10's end-of-life. Additionally, the company began requiring Online Accounts for Windows 11 installations, making them increasingly difficult to bypass.
> Every previously reported issue has been addressed or resolved, except for the broken localhost functionality and now this WinRE problem.
Microsoft is just completely pathetic, it's become completely opposite of what companies want and it wouldn't surprise me if it becomes politics soon to switch to Linux on office spaces.
Between these issues, the end of support for Windows 10, and the total lack of respect for customers ("yes/maybe later" is unacceptable), I'm happy for my recent switch to Linux.
Fedora Kinoite (atomic + KDE) has been a breath of fresh air. The Dolphin file manager alone was worth the switch, and connecting my phone via KDE Connect is the most excited I've been about software in a while. The atomic part has been surprisingly painless.
It hasn't been free from small bugs (what software is, nowadays?), but at least I know they're not there because of greed, so it pushes me towards contributing instead of hating the developers.
In Win11 as admin, take ownership of the following files, and remove all permissions for the system user. This prevents any updates and can be easily undone at any time. I turned off updates, and life is much better. I no longer feel guilty about having my system "at risk". It's no longer worth the pain of updates.
Microsoft updates feel like they are boiling the frog, changing the whole OS to something you never signed up for. Why can't they stick to just security and stick their bloatware AI crap in Windows 12
My home mini pc is having Bluetooth issues from last 6-7 months after some update. I can't go back, tried every possible solutions. Best option: wait for them to fix it.
The issue: Sometimes if the Windows boot normally, Bluetooth won't turn on. I have to force restart to have it on. My guess is it's trying to optimize the power or something. I gave up.
My other laptop and work computer are still Windows 10, so some sanity left. I have installed kubuntu on another spare laptop and slowing moving towards linux entirely.
I was running Mint on a 256GB SATA SSD for about 6 months before finally just making the switch and moving it to my 2TB M.2 NVMe drive.
But I had to put my Windows install somewhere because some rare games like Battlefield 6 require onerous anticheat access at the kernel level and refuse to support Linux, so I moved it to my 256GB drive where Linux used to be.
I did that on Friday. And Windows corrupted itself on every boot. Eventually I gave up trying to make it work and shoved it onto a small partition on the end of my M.2 drive. The SSD is a bit older and has some errors on it but Linux worked just fine, but Windows couldn't handle the drive.
Reminded me of the meme about roses dying if the pH balance of the soil isn't perfect, but daisies are like "Fuck yeah, concrete!" growing in literal cracks in the sidewalk.
I wonder if my problems were related to them fucking with things, or if it's just a coincidence.
This update seems to be a real mess. It tries to install for since days and always stops at 38% and then rolls back. Instead of a reasonable error message it keeps retrying, rendering my laptop unusable for 30 min.
I went through the list that ChatGPT, Claude and Perplexity gave me. I can rule out the recovery partition and the update cache at least. I think one part was the windows sandbox feature which is known to make problems. Got a new error after deinstalling. It is just plain frustrating however. Having a PhD in computer science and looking for the needle in the haystack to just be able to use your PC in a reasonable way. If I did not have to use awkward SAP Excel Pluginsto connect to our accounting and other MS stuff, this episode nearly triggered me to finally switch to a decent OS I somehow can understand again.
I'm a really big windows expert. I've reverse engineered alot of it. Big fanboy, one of the most knowledgeable people about it. Ever since interviewing and declining a Microsoft position, it's clear the people their are absolute idiots. My first interview round as a C++/C kernel dev, was for a C# job? I passed and got the offer, then they send me for a systems admin role after I decline? From recruiters, to actual engineers there, the level of incompetence was insane. I will NEVER work or support this company in any way until they get rid of all the H1BSlop they have pushing these horrible updates. I think Apple and Meta are the only major tech companies not held up by velocity and actually have functional organizations. It's not a surprise seeing all of these bugs. And there's multiple bug reports i've submitted that go unsolved in their win32 or kernel API's. ESPECIALLY for new features. It's sad how they've fallen so much. If I can find these bugs in 5 minutes using IDA, how come they aren't catching it in code reviews?
I wonder if this is related to what I experienced. After the update (update and shoutdown reliably updates and restarts again, does not shut down) a parctice of mine switching Control and Fn keys on my Mac so Control key function gets into the same physical position as Ctrl on the PC keyboard, so using Windwos through Microsoft Remote Desktop and at the keyboard of the Windows computer is a smoother switch, is not working anymore. Windows, through the Remote Desktop does not register the Fn key as Ctrl anymore. The whole thing does not make sense to me. The Remote Desktop software on Mac did not change, MacOS should send Remote Desktop the signal of Control key pressed when pressing Fn, the Windows update shall have no effect, yet the sole change here was the Windows update when this annoying thing emerged. I simply had no time to dive into diagnostics and find the underlying reason, it is less resource intensive and less painfull - but one more annoyance on top of the many concerning Windows use - learning to use different Ctrl button location on Mac and PC keyboard again (done before, before learning the Control <> Fn switch trick).
the update immediately prior to this broke password protected fileshares. Had to wait weeks for a patch to be deployed.
What's worse, is that so many similar problems have occured over the last 20 years is that when you try to search for the problem, you are highly likely to not find the actual cause+workaround, but will instead find one from years before that doesn't exactly apply to the current situation.
Honestly, people need to start delaying their updates if possible by roughly a month depending on their severity, much like the corporate world. Better to leave an update in the wild for a couple of weeks before updating your own machine.
22 comments
[ 0.23 ms ] story [ 50.2 ms ] thread> Early last week, Microsoft accidentally broke the Windows Media Creation Tool (MCT) just a day ahead of Windows 10's end-of-life. Additionally, the company began requiring Online Accounts for Windows 11 installations, making them increasingly difficult to bypass.
> Every previously reported issue has been addressed or resolved, except for the broken localhost functionality and now this WinRE problem.
Fedora Kinoite (atomic + KDE) has been a breath of fresh air. The Dolphin file manager alone was worth the switch, and connecting my phone via KDE Connect is the most excited I've been about software in a while. The atomic part has been surprisingly painless.
It hasn't been free from small bugs (what software is, nowadays?), but at least I know they're not there because of greed, so it pushes me towards contributing instead of hating the developers.
C:\Windows\System32\WaaSMedicSvc.dll C:\Windows\System32\usosvc.dll C:\Windows\System32\wuaueng.dll
My home mini pc is having Bluetooth issues from last 6-7 months after some update. I can't go back, tried every possible solutions. Best option: wait for them to fix it.
The issue: Sometimes if the Windows boot normally, Bluetooth won't turn on. I have to force restart to have it on. My guess is it's trying to optimize the power or something. I gave up.
My other laptop and work computer are still Windows 10, so some sanity left. I have installed kubuntu on another spare laptop and slowing moving towards linux entirely.
But I had to put my Windows install somewhere because some rare games like Battlefield 6 require onerous anticheat access at the kernel level and refuse to support Linux, so I moved it to my 256GB drive where Linux used to be.
I did that on Friday. And Windows corrupted itself on every boot. Eventually I gave up trying to make it work and shoved it onto a small partition on the end of my M.2 drive. The SSD is a bit older and has some errors on it but Linux worked just fine, but Windows couldn't handle the drive.
Reminded me of the meme about roses dying if the pH balance of the soil isn't perfect, but daisies are like "Fuck yeah, concrete!" growing in literal cracks in the sidewalk.
I wonder if my problems were related to them fucking with things, or if it's just a coincidence.
One problem that matches that behavior but is under-recognized, you might not have enough space in your Recovery partition.
If so this can be a showstopper you are expected to have your IT department on top of.
I wonder if this is related to what I experienced. After the update (update and shoutdown reliably updates and restarts again, does not shut down) a parctice of mine switching Control and Fn keys on my Mac so Control key function gets into the same physical position as Ctrl on the PC keyboard, so using Windwos through Microsoft Remote Desktop and at the keyboard of the Windows computer is a smoother switch, is not working anymore. Windows, through the Remote Desktop does not register the Fn key as Ctrl anymore. The whole thing does not make sense to me. The Remote Desktop software on Mac did not change, MacOS should send Remote Desktop the signal of Control key pressed when pressing Fn, the Windows update shall have no effect, yet the sole change here was the Windows update when this annoying thing emerged. I simply had no time to dive into diagnostics and find the underlying reason, it is less resource intensive and less painfull - but one more annoyance on top of the many concerning Windows use - learning to use different Ctrl button location on Mac and PC keyboard again (done before, before learning the Control <> Fn switch trick).
the update immediately prior to this broke password protected fileshares. Had to wait weeks for a patch to be deployed.
What's worse, is that so many similar problems have occured over the last 20 years is that when you try to search for the problem, you are highly likely to not find the actual cause+workaround, but will instead find one from years before that doesn't exactly apply to the current situation.
Some machine was have need their screens on 24/7 it was working fine til 25H2 came along and nothing we tried seemed to fix it.
Edit: Oh an added to this is we have no policy allowing any machine to update to 25H2... yet somehow some machines did.
Just another day in the MS ecosystem
Now there is a further update, KB5070773 which fixes this.
Tried it and it works.
So far.