 |  |
|---|
Posted on 10/22/2021 11:30:53 AM PDT by dayglored
Names November as the month for Win 10 H2 update – then reveals major new feature won’t arrive on time
[Dayglored comment: My bolding on the paragraph below about the PowerShell bug.]
Microsoft has released a build of Windows 11 that it claims addresses performance problems the new OS imposed on some systems.
Redmond's announcement of OS Build 22000.282 lists over 60 "improvements and fixes" on top of a lucky 13 "highlights".
One of those highlights is described as fixing "an issue that causes some applications to run slower than usual after you upgrade to Windows 11 (original release)".
Another addresses an issue that could cause Bluetooth mice and keyboards "to respond slower than expected". A third "improves the time estimate for how long you might wait to use your device after it restarts".
Some of the improvements and fixes offer meatier fare – among them addressing "an L3 caching issue that might affect performance in some applications on devices that have AMD Ryzen processors after upgrading to Windows 11 (original release)".
AMD users have, quite reasonably, been rather miffed at being singled out, and more miffed still that their concerns weren't addressed in the first bundle of Win 11 fixes issued last week.
Another fix prevents PowerShell from eating a PC alive by creating an infinite number of child directories. "This issue occurs when you use the PowerShell Move-Item command to move a directory to one of its children. As a result, the volume fills up and the system stops responding," Microsoft explained.
If Server Manager has disappeared while you use Windows 11, Microsoft has found the cause for its absence: silly you, for installing Server Manager using the Remote Server Administration Tools and then using it to remove some features from Hyper-V.
Distorted fonts for Asian alphabets have been clarified, Microsoft Office has been restored to operability after Windows Defender Exploit Protection prevented it from running "on machines that have certain processors," and an issue that could prevent successful printer installation with Internet Printing Protocol has been erased.
Microsoft's Windows teams appear to be rather busy. On the same day as the new Windows 11 fixes were delivered, the IT giant also announced the all-but—picked cut of Windows 10 it will use for the Windows 10 November 2021 update.
"We believe that Build 19044.1288 is the final build for the November 2021 Update," wrote Brandon LeBlanc, a senior manager on the Windows Insider Program.
Insiders can get their hands on the November update in the Release Preview Channel on Windows 10 via Microsoft's "seeker" experience in Windows Update.
"This means Insiders currently on Windows 10, version 21H1 (or lower) in the Release Preview Channel will need to go to Settings > Update & Security > Windows Update and choose to download and install Windows 10, version 21H2," LeBlanc explained.
Microsoft previously teased a modest set of additions to Windows 10 in this update, headlined by Wi-Fi security improvements and GPU compute support in the Windows Subsystem for Linux (WSL) and Azure IoT Edge for Linux on Windows (EFLOW) environments.
Another major feature the 'softies previously promised would appear in the update – a Windows Hello for Business deployment method called "cloud trust" – has dropped out of the release.
LeBlanc described it as "still under development" and now due to appear "in a future monthly update to the November 2021 Update".
We will provide more information as this feature gets closer to availability. Information on exactly when the 21H2 update will make its mainstream debut is also in the "coming-real-soon-now-we-promise" bucket. ®
| |
|---|
Windows 7 still works great.
Leave it to Microsoft to release stuff that’s only usable with Intel chips. And even then chock full of bugs. Microsoft has to be one of the most half-a$$ed companies in history. It is the General Motors Corporation of the computer world.
Indeed.
I still haven’t gotten the windows 11 update on my 2 yr old Dell
“Another fix prevents PowerShell from eating a PC alive by creating an infinite number of child directories. “This issue occurs when you use the PowerShell Move-Item command to move a directory to one of its children. As a result, the volume fills up and the system stops responding,” Microsoft explained.”
Microsoft actually released an OS that does this. What incompetence. Did they even test it? They must have hired some left over Range Rover engineers.
I’ve been using Win 11 on my desktop and Surface Pro 6 since it was released on 10/05. I haven’t had any issues.
FYI:
Block Windows 11 with Registry Editor
1- Open the Start Menu.
2- Type regedit.exe and select the Registry Editor search result.
3- Go to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate.
4- Set the Dword TargetReleaseVersion to 1. ...
5- Set the value of TargetReleaseVersionInfo to 21H1. ...
6- Restart the PC
Stayed with Win10......
I have a Red X on my update page telling me my HP desktop (built for me specifically) won’t run WIN11 and to use a Health Check App to find out what I have to do to run WIN11. I’ve been told by two IT friends to stick with WIN10 that WIN11 is full of tracking and security issues Microsoft wants in our computers.
In this economy, who is going out to spend big bucks on a new PC just to run Microsoft’s bug-ridden WIN11? Not me. My PC does all I want it to.
Thank you very much for the FYI you posted!!
Probably a good idea. There is no compelling reason to upgrade. I just have a compulsion to have the latest of everything.
Among reasons I bought a Surface Pro X was Win 11 (among). Interestingly, only today did MS give the green light on the upgrade.
I’ll wait.
Not doing it.
Nor am I buying a new one either.
-PJ
What puzzles me is that this bug did not exist prior to this release. What the hell? Does PowerShell not test for the validity of a folder move prior to doing it? Does it not check the destination first?
The Move is trivial mistake to make -- moving a folder into a folder that's actually a subfolder of the original. I imagine that hundreds of computers users do that every day. So I can't believe this bug pre-existed. That kind of programming error is egregious enough, but the lack of testing is worse.
And yet it's announced without even a hint of embarrassment. "Oh, yeah, we let you do a command that scribbles all over your disk until it's full, and then locks up and crashes the operating system, so that you have to figure out why it won't boot properly, and how to fix it."
It's really rather horrifying, when you consider what else didn't get properly vetted and tested, that will be quietly announced next week.
I believe KevinB works at Microsoft : )
He invented ‘Clippy’.
Me, I'm taking Microsoft at their word, back a few years:
"Windows 10 is the last Windows you will ever need."They're right about that. I have Win7 (in a non-internet-connected VM) for the stuff that won't run on Win10, and I'll still have a VM of Win10 around after they pull the plug on it, for stuff that only runs in Win10.
These days 80% of my work is done in Linux, 10% in MacOS, 10% in Windows. I suspect in a few years it'll be 96%/2%/2%.
Like any big corporation the rot of middle managament sets in. Problems are covered up to meet deadlines, not solved.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.