Will stay on Win10 until it no longer works! Piss on Microsloth!!!

I allowed the laptop to install the pending Win11 updates last night.
It booted back up afterwards with no issues beyond still being Win11.

Mostly from laziness, I don't care enough to update my computer to W11. It functions just fine for everything I want to do with it.

This message has been edited. Last edited by: egregore,

I've been on Win 11 since it was introduced, and have had no problems. I like it. It is stable, fast, feature rich, easy to configure, and does everything I ask it to do without complaint. Win 11 was rolled out in October 2021. I have never had an OS level crash in 5 1/2 years. Never got the bluescreen, blackscreen or, God save me, mauve screen, thereof of death.

I know and work with a number of computer/network/IT support independent contractors who serve local businesses, and I am not aware of any of them not recommending the most recent version of Win 11.

Frankly, I don't get the hate. I am also in the AppleVerse, and have more complaints with iOS and its phone and iPad derivatives than I do with Win. 11.

I've also not had any problem w/ 11 and this or any update.

Win10 is extended for free on my old comp but I just built a new one a few months ago so I went w/ 11.
I prefer 10 but I'm getting over it.

Looking forward to skipping Win12. And so on, I hope.
I think we should have been able to skip 11.
I remember going from XP all the way to 10.

Are there any updates on this situation? I'm afraid to turn off my computer now

Yeah, as I said in another thread, I was pretty much forced into Windows 11 from 7. After a week, I'm beginning to really like it. I have never had a problem with anything including all of the updates. Just spend some time tweaking it to your liking.

I have paused updates for five weeks. Will people please keep this thread active till resolved?

Newest feature I learned is my Epson photo scanner no longer works. Only thing I can find to make it work is buying a 3rd party software for $100. No thanks. I rarely use it anymore since everything is digital now, but went to scan in my passport photo I just got to renew passport and found out it didn’t work.

quote:

Originally posted by Bassamatic:
Yeah, as I said in another thread, I was pretty much forced into Windows 11 from 7. After a week, I'm beginning to really like it. I have never had a problem with anything including all of the updates. Just spend some time tweaking it to your liking.

Yes, I was forced to Win 11 because I use TurboTax to do my taxes and it now will only work in Windows 11.

Has anyone actually had this happen, or have you only read about it and seen Microsoft's statements?

quote:

Originally posted by 6guns:
Happy Mac user here.

Same for over 30 years...

amals, do you have all your critical data backed up?

No, para, I don't. At least not that I have physically done myself. I don't even know how to do that. I have been very ill lately and am having difficulty following instructions or even posing questions. For now I have paused updates for five weeks to buy time. Thanks for trying to help.

To para or anyone else who might post about this, if I don't respond, it is not that I am ignoring you; it is that I am away from the forum and didn't see the post.

I have the update that supposedly causes the issue. I haven't had any problems with it but I paused updates, afraid that their fix will screw my computer.

I'm also copying my files every night to my cloud drive, both critical and non-critical. At least Beyond Compare only copies the files that have changed or are different.

Around the first week, like Jan 8, I thought I had lost all my work I've done since Dec 30 because I hadn't done any back up since that date. Good thing I actually didn't but I do not like that feeling I had of trying to recreate work or figure out how to get copies of documents I already shredded.

quote:

Originally posted by StorminNormin:

Yes, I was forced to Win 11 because I use TurboTax to do my taxes and it now will only work in Windows 11.

Yup. Same deal except mine is H&R Block.

quote:

Originally posted by amals:
No, para, I don't. At least not that I have physically done myself. I don't even know how to do that. I have been very ill lately and am having difficulty following instructions or even posing questions. For now I have paused updates for five weeks to buy time. Thanks for trying to help.

I hope that you’re better soon, my friend.

Kept my Win10 and protect the system with a paid Malwarebytes subscription. Screw MS with a cactus.

Link: https://www.windowslatest.com/...some-pcs-commerical/

Microsoft confirms Windows 11 KB5074109 January update BSOD, boot issues on some PCs (commerical)
By Mayank Parmar - January 29, 2026

Windows 11 KB5074109 (January 2026 Update) is causing major issues on some PCs, and Microsoft has more details to share. In an updated support document, the company has confirmed that the update is indeed crashing some PCs, but most home users won’t run into the problem, as the bug is currently limited to commercial PCs.

Microsoft has already taken steps to ensure it does not affect consumers.

On January 23, Microsoft confirmed that it was aware of reports that some PCs do not boot anymore.

At that point, Microsoft said it suspected that some PCs were not booting, but could not verify whether the issue was due to a Windows update. Now, the company has confirmed that a limited number of PCs are failing to boot after the update. This is a known issue and is now under active investigation.

This issue affects PCs running Windows 11 KB5074109 (25H2 Build 26200.7623 and 24H2 Build 26100.7623).

If you were affected, you’d see a Black Screen of Death (BSOD). For those unaware, Microsoft recently redesigned the Blue Screen of Death as “Black Screen,” so it matches the look and feel of Windows 11. That’s why you’ll no longer see the original blue screen or the frowning face.

The Black Screen of Death (BSOD) appeared with UNMOUNTABLE_BOOT_VOLUME error and required customers to manually recover their computer. That meant it is no longer possible for affected PCs to boot. To recover the PC, Microsoft said you would need to enter WinRE (Windows Recovery Environment) and use one of the available methods.

Microsoft now says it has identified the root cause in only some commercial PCs (non-consumer) and that it’s due to a Windows Update, not a driver or third-party software.

The January 2026 update didn’t “randomly” brick healthy PCs

According to the company, the no-boot (UNMOUNTABLE_BOOT_VOLUME) issues are happening mostly on machines that were already in a bad state because they failed to install the December 2025 security update, and then rolled it back.

That rollback left the system in an “improper state”, but those PCs were still in a working state until Windows 11 KB5074109 automatically installed. Most likely, some combination of servicing metadata, boot configuration, or disk or driver state ended up half-applied or inconsistent.

On a normal PC, Windows updates assume the system is in a valid baseline state. However, that wasn’t the case with these affected PCs.

When those “improper state” devices tried to install the Windows 11 KB5074109 (or later updates), the update process had to touch low-level components. Because the baseline was already inconsistent, the new update could push it over the edge into a condition where Windows can’t mount the system volume during startup

That’s when you get UNMOUNTABLE_BOOT_VOLUME (0xED), and the machine can’t complete boot without manual recovery steps.

“Recent investigations have determined this issue can occur on devices that failed to install the December 2025 security update and were left in an improper state after rolling back the update,” Microsoft noted in a support document.

“Attempting to install Windows updates while in this improper state could result in the device being unable to boot. We are working on a partial resolution that will prevent additional devices from resulting in a no-boot scenario if they try to install an update while in this improper state. However, this partial resolution will not prevent devices from getting into the improper state in the first place, nor will it repair devices that are already unable to boot. We continue to investigate why these devices are failing to install Windows updates or potentially getting into this improper state,” the company explained.

Microsoft has already deployed a fix that would prevent additional devices from crashing. This means consumers will now never run into this specific issue, at least not until another bug hits Windows.