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. ®
The 1 year old laptop upgraded to Win 11. But the desktop which about 3 years old in two months cannot as it has wrong processor. To force it to install is a tough process. Will result in no security updates from MS.
I am sorry. I just replied to you in a different thread. It is not difficult to bypass processor or TPM requirements. And currently all of the “security updates” are currently coming through without a hitch.
For others:
108 posted on 10/26/2021, 7:43:42 AM by fireman15
https://freerepublic.com/focus/f-chat/4004188/posts?q=1&;page=108
Great post and thread! Since I took the latest update with the AMD fix my Windows 11 hyper-v virtual machine does seem to be running smoother. But it is a little hard to guage since I have not run any benchmarks. I went ahead and did a clean install into a Windows 10 virtual machine specifically to run benchmarks to compare with the Windows 11 machine. I have set them up with the same exact specs. I have some other projects going but will try to run those benchmarks in the next few days out of curiosity.
I/we would be very interested to learn your results, please feel free to share. Thanks!
This is regarding benchmarking on the virtual machines that I set up with clean installs of Windows 10 and Windows 11. Getting any meaningful results is more difficult than one would assume. Netperf, Iometer and Passmark are all focused on evaluating hardware. PCMark 10 was my tool of choice but it needs OpenGL 4.3 to complete its tests and come up with a score.
Since Microsoft disabled and then removed RemoteFX vGPU from Hyper-V for security reasons and I have not successfully implemented a Discrete Device Assignment (DDA) to create a passthrough for the GPU on my laptop I am not able to comply with this requirement. PCMark 10 still starts up and gives a few numbers before the test abruptly terminates itself but I am not sure that they are meaningful. The devil is always in the details. Meaningful benchmarking Hyper-V machines to compare Windows 10 vs Windows 11 is a bit more challenging than I originally anticipated without buying a professional tool.
Any suggestions you have would be appreciated.
Hmm, that’s a puzzler alright. If you will allow, I’ll forward your description to a colleague who is better versed than I am in Windows things and see if he has any words of wisdom. He’s not on FR, so I ask your permission first — is that okay?
Thanks, that would be great. Hyper-V has never been known for its ability to utilize GPU hardware... that is not really what it is meant for. It used to be a fairly. When you created a type 1 machine you were able to add a physical or RemoteFX GPU in the settings for it. There were other easy methods as well. I am not sure that the DDA passthrough method even works with the version of Hyper-V that comes with Windows 10 Pro. I have had no luck with it. It hardly matters as any game playing that I would do with this laptop would be on the physical machine anyway because it is already limited in its gaming abilities. I was just hoping to do some benchmarking with the real world applications included in PCMark 10 and also 3DMark v2. It is all more of a technical challenge at this point.
I ended up modifying the settings for the Remote Desktop Connection App using the group policy editor in a way that would supposedly allow a GPU passthrough. But this was in vain as well. It no longer does anything at all for your GPU when you open your virtual machine in a Remote Desktop session as opposed to a session in a normal Hyper-V window.
I did run PCMark 10 on the Clean Windows 11 Pro and Clean Windows 10 Pro virtual machines. And even though the tests would not complete because the display adapters support openGL only up to 1.1... The numbers on the identically configured machines showed that Windows 11 was faster in this possibly not valid match up. I will try to share the screen saves shortly.
.png?)
.png?)
The results of the benchmark for Windows 11 shown in the first screensave were better than the benchmark of Windows 10. This could be completely meaningless for a number of reasons but still interesting as I typically expect each new generation of Microsoft OS's to require more power than the last. It is possible that this new rewrite streamlined things a bit.
I should mention that these virtual machines are stored and run on my laptop’s 2GB storage drive and not on the primary SSD which slows things down considerably but should be the same handicap for each.
Wow, great info. I’ll let you know when I’ve had a chance to confer with my colleague, who as I said knows far more about the details of Windows than I do (he’s got all the certifications and whatnot, having been a high-level WinAdmin for well over a decade). Hopefully he’ll have some pithy insights. :-)
I am going to research more about GPU support in the VMware alternatives. I normally use Hyper-V for Windows 7, 10 and recent Linux builds for assumed slightly better performance and convenience. I have set up VMware machines for earlier operating systems but they typically do not need GPU support so this has not been a concern previously.
I did download 3D ThinAnywhere which offers GPU support but it is meant for virtual machines hosted by Linux servers... so far I have not been able to get it to work with my Windows based Hyper-V machines. It really is just more of a technical challenge that I have gotten side tracked on.
I should probably also have mentioned that the PCMark 10 benchmark on Windows 11 was performed on the latest released version of Windows 11, Build 22000.282 which fixed the latency issue with the cache on Ryzen processors among other things. When I upgrade the NVME SSD on my laptop I probably will be doing a clean install of Windows 11... Kind of liking it as I use it more.
Sloppy programming brought about by programmers and managers knowing they can be sloppy and just do daily ‘updates’ as they desire. No need to create solid code and a good product, just get it out there as sloppy as it may be and ‘update’ it.
You make a good point. My feeling is that Windows 10 has so many patches applied, that at this point it is becoming more cumbersome because of it. If you take a physical computer or virtual machine running Windows 10 that is a couple of years old and has never been updated. It takes hours and who knows how many restarts to apply all the patches through Windows Update. This may be the primary reason that Windows 11 seems to run a little faster in many benchmarks... not so many patches applied.
It was kind of sad that the AMD bug still existed in Microsoft’s first official release of 11. And even the fix included in the latest release, Build 22000.282 does not completely fix it. So the pattern you describe continues and likely will eventually bog down Windows 11 as well.
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.