Rechercher

NeowinFeed partage un lien

2025-05-25 02:14:06 ·

AMD RX 9070 AI performance benchmark review vs 9070 XT, 7800 XT, Nvidia RTX 5070, 4070

Review

When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works.

AMD RX 9070 AI performance benchmark review vs 9070 XT, 7800 XT, Nvidia RTX 5070, 4070

Sayan Sen

Neowin
@ssc_combater007 ·

May 24, 2025 14:40 EDT

Earlier this month, we shared the first part of our review of AMD's new RX 9070. It was about the gaming performance of the GPU, and we gave it a 7.5 out of 10. The 9070 XT, in contrast, received a full 10 out of 10.
The main reason for the lower score on the non-XT was the relatively high price and thus the poorer value it offered compared to the XT. We thought the price was much closer to the XT than it needed to be.
While the RX 9070 proved to be more power efficient than the XT, for a desktop gaming graphics card, value and performance typically take the front seat compared to something like power efficiency.

However, that may not be the case in terms of productivity which also takes into account things like power savings. Thus, similar to the one we did for the XT model, we are doing a dedicated productivity review for the RX 9070 as well where we compare to against the 9070 XT, 7800 XT, as well as Nvidia's 5070 and 4070.
AI performance is a very important metric in today's world and AMD also promised big improvements thanks to its underlying architectural improvements. We already had a taste of that with the XT model so now it's time to see how good the non-XT does here.

Before we get underway, this is a collaboration between Sayan Sen, and Steven Parker who lent us their test PC for this review. Speaking of which, here are the specs of the test PC:

Cooler Master MasterBox NR200P MAX
ASRock Z790 PG-ITX/TB4
Intel Core i7-14700K with Thermal Grizzly Carbonaut Pad

T-FORCE Delta RGB DDR57600MT/s CL362TB Kingston Fury Renegade SSD
Windows 11 24H2Drivers used for the 7800 XT, 9070 XT and 9070 were Adrenaline v24.30.31.03 / 25.3.1 RC, and for the Nvidia RTX 5070 and 4070, GeForce v572.47 was used.Sapphire Pulse 9070 XT, Nvidia 5070 FE, and Pulse 9070First up, we have Geekbench AI running on ONNX.
The RTX 5070 gets beaten by both the 9070 XT and 9070 in quantized and single precisionperformance. Similarly, the 4070 gets close to the 9070 in half-precisionperformance, but the latter is an enormous 30% faster in quantized score and nearly 12.2% better in single precision.
The reason for this beatdown is the amount of memory available to each card. The Nvidia GPUs have 12GB each and thus only do better in the FP16 precision tests since the other ones are more VRAM-intensive.
Next up, we move to UL Procyon suite starting with the Image generation benchmark.
We chose the Stable Diffusion XL FP16 test since this is the most intense workload available on Procyon suite. Similar to what we saw on Geekbench AI, the Nvidia GPUs to relatively better here as it is FP16 or half precision which means the used VRAM is lower.
So this is something to keep in mind again, if you wish to float32 AI workloads, it is likely that graphics cards with greater than 12 GB buffers would emerge as victors.
There is still a big improvement on the RX 9070 compared to the 7800 XT as we see a ~54% gain. This boost is due to improvements to the core architecture itself as VRAM capacities of both cards are the same at 16 Gigs.
Following image generation, we move to the text generation benchmark.

In this workload, we see the least impressive performance of the 9070 in terms of how much it improves over the 7800 XT. The former is up to ~7.25% faster here. The 9070 is also not as well-performing as the Nvidia 4070 in Phi and Mistral models, although it does do better in both the Llama tests.
Another odd result stood out here where the 5070 underperformed all the cards including the 7800 XT in Llama 2. We ran each test three times and considered the best score and so we are not exactly sure what happened here.
Wrapping up AI testing, we measured OpenCL throughput in Geekbench compute benchmark.
The RX 9070 did not fare well here at all even falling behind the 7800 XT and it is significantly slower than the three other cards. Interestingly, even the RTX 5070 could not beat the 4070 on OpenCL so perhaps this suggests that OpenCL optimization has not been a priority for either AMD or Nvidia this time. It could also be an issue with Geekbench itself.
Conclusion
We reach the end of our productivity performance review of the 9070 and we have to say we are fairly impressed but there is also a slight bit of disappointment. It is clear that the 9070 as well as the 9070 XT really shine when inferencing precision is higher, and that is due to the higher memory buffers they possess compared to the Nvidia 5070. But on FP16, the Nvidia cards pull ahead.
Still RNDA 4, including the RX 9070, see big boost over RDNA 3. As we noted in the image generation benchmark, which is an intense load, there is over a 50% gain.
So what do we make of the RX 9070 as a productivity hardware? We think it's a good card. If someone was looking for a GPU around that can do both gaming and crunch through some AI tasks this is a good card to pick up especially if you are dealing with single precision situations or some other VRAM-intense tasks. And we already know it is efficient so there's that too.
For those however looking for a GPU that can deal with more, AMD recently unveiled the Radeon AI PRO R9700 which is essentially a 32 GB refresh of the 9070 XT with some additional workstation-based optimizations.
Considering everything, we rate AMD's RX 9070 a 9 out of 10 for its AI performance. Price is less of a factor for those looking at productivity cases compared to ones considering the GPU for gaming, and as such, we felt it did quite decent overall and can be especially handy if you need more than 12 GB.
Purchase links: RX 9070 / XTAs an Amazon Associate we earn from qualifying purchases.

Tags

Report a problem with article

Follow @NeowinFeed
#amd #performance #benchmark #review #nvidia

AMD RX 9070 AI performance benchmark review vs 9070 XT, 7800 XT, Nvidia RTX 5070, 4070
Review When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works. AMD RX 9070 AI performance benchmark review vs 9070 XT, 7800 XT, Nvidia RTX 5070, 4070 Sayan Sen Neowin @ssc_combater007 · May 24, 2025 14:40 EDT Earlier this month, we shared the first part of our review of AMD's new RX 9070. It was about the gaming performance of the GPU, and we gave it a 7.5 out of 10. The 9070 XT, in contrast, received a full 10 out of 10. The main reason for the lower score on the non-XT was the relatively high price and thus the poorer value it offered compared to the XT. We thought the price was much closer to the XT than it needed to be. While the RX 9070 proved to be more power efficient than the XT, for a desktop gaming graphics card, value and performance typically take the front seat compared to something like power efficiency. However, that may not be the case in terms of productivity which also takes into account things like power savings. Thus, similar to the one we did for the XT model, we are doing a dedicated productivity review for the RX 9070 as well where we compare to against the 9070 XT, 7800 XT, as well as Nvidia's 5070 and 4070. AI performance is a very important metric in today's world and AMD also promised big improvements thanks to its underlying architectural improvements. We already had a taste of that with the XT model so now it's time to see how good the non-XT does here. Before we get underway, this is a collaboration between Sayan Sen, and Steven Parker who lent us their test PC for this review. Speaking of which, here are the specs of the test PC: Cooler Master MasterBox NR200P MAX ASRock Z790 PG-ITX/TB4 Intel Core i7-14700K with Thermal Grizzly Carbonaut Pad T-FORCE Delta RGB DDR57600MT/s CL362TB Kingston Fury Renegade SSD Windows 11 24H2Drivers used for the 7800 XT, 9070 XT and 9070 were Adrenaline v24.30.31.03 / 25.3.1 RC, and for the Nvidia RTX 5070 and 4070, GeForce v572.47 was used.Sapphire Pulse 9070 XT, Nvidia 5070 FE, and Pulse 9070First up, we have Geekbench AI running on ONNX. The RTX 5070 gets beaten by both the 9070 XT and 9070 in quantized and single precisionperformance. Similarly, the 4070 gets close to the 9070 in half-precisionperformance, but the latter is an enormous 30% faster in quantized score and nearly 12.2% better in single precision. The reason for this beatdown is the amount of memory available to each card. The Nvidia GPUs have 12GB each and thus only do better in the FP16 precision tests since the other ones are more VRAM-intensive. Next up, we move to UL Procyon suite starting with the Image generation benchmark. We chose the Stable Diffusion XL FP16 test since this is the most intense workload available on Procyon suite. Similar to what we saw on Geekbench AI, the Nvidia GPUs to relatively better here as it is FP16 or half precision which means the used VRAM is lower. So this is something to keep in mind again, if you wish to float32 AI workloads, it is likely that graphics cards with greater than 12 GB buffers would emerge as victors. There is still a big improvement on the RX 9070 compared to the 7800 XT as we see a ~54% gain. This boost is due to improvements to the core architecture itself as VRAM capacities of both cards are the same at 16 Gigs. Following image generation, we move to the text generation benchmark. In this workload, we see the least impressive performance of the 9070 in terms of how much it improves over the 7800 XT. The former is up to ~7.25% faster here. The 9070 is also not as well-performing as the Nvidia 4070 in Phi and Mistral models, although it does do better in both the Llama tests. Another odd result stood out here where the 5070 underperformed all the cards including the 7800 XT in Llama 2. We ran each test three times and considered the best score and so we are not exactly sure what happened here. Wrapping up AI testing, we measured OpenCL throughput in Geekbench compute benchmark. The RX 9070 did not fare well here at all even falling behind the 7800 XT and it is significantly slower than the three other cards. Interestingly, even the RTX 5070 could not beat the 4070 on OpenCL so perhaps this suggests that OpenCL optimization has not been a priority for either AMD or Nvidia this time. It could also be an issue with Geekbench itself. Conclusion We reach the end of our productivity performance review of the 9070 and we have to say we are fairly impressed but there is also a slight bit of disappointment. It is clear that the 9070 as well as the 9070 XT really shine when inferencing precision is higher, and that is due to the higher memory buffers they possess compared to the Nvidia 5070. But on FP16, the Nvidia cards pull ahead. Still RNDA 4, including the RX 9070, see big boost over RDNA 3. As we noted in the image generation benchmark, which is an intense load, there is over a 50% gain. So what do we make of the RX 9070 as a productivity hardware? We think it's a good card. If someone was looking for a GPU around that can do both gaming and crunch through some AI tasks this is a good card to pick up especially if you are dealing with single precision situations or some other VRAM-intense tasks. And we already know it is efficient so there's that too. For those however looking for a GPU that can deal with more, AMD recently unveiled the Radeon AI PRO R9700 which is essentially a 32 GB refresh of the 9070 XT with some additional workstation-based optimizations. Considering everything, we rate AMD's RX 9070 a 9 out of 10 for its AI performance. Price is less of a factor for those looking at productivity cases compared to ones considering the GPU for gaming, and as such, we felt it did quite decent overall and can be especially handy if you need more than 12 GB. Purchase links: RX 9070 / XTAs an Amazon Associate we earn from qualifying purchases. Tags Report a problem with article Follow @NeowinFeed #amd #performance #benchmark #review #nvidia

WWW.NEOWIN.NET

AMD RX 9070 AI performance benchmark review vs 9070 XT, 7800 XT, Nvidia RTX 5070, 4070

Review When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works. AMD RX 9070 AI performance benchmark review vs 9070 XT, 7800 XT, Nvidia RTX 5070, 4070 Sayan Sen Neowin @ssc_combater007 · May 24, 2025 14:40 EDT Earlier this month, we shared the first part of our review of AMD's new RX 9070. It was about the gaming performance of the GPU, and we gave it a 7.5 out of 10. The 9070 XT, in contrast, received a full 10 out of 10. The main reason for the lower score on the non-XT was the relatively high price and thus the poorer value it offered compared to the XT. We thought the price was much closer to the XT than it needed to be. While the RX 9070 proved to be more power efficient than the XT, for a desktop gaming graphics card, value and performance typically take the front seat compared to something like power efficiency. However, that may not be the case in terms of productivity which also takes into account things like power savings. Thus, similar to the one we did for the XT model, we are doing a dedicated productivity review for the RX 9070 as well where we compare to against the 9070 XT, 7800 XT, as well as Nvidia's 5070 and 4070. AI performance is a very important metric in today's world and AMD also promised big improvements thanks to its underlying architectural improvements. We already had a taste of that with the XT model so now it's time to see how good the non-XT does here. Before we get underway, this is a collaboration between Sayan Sen (author), and Steven Parker who lent us their test PC for this review. Speaking of which, here are the specs of the test PC: Cooler Master MasterBox NR200P MAX ASRock Z790 PG-ITX/TB4 Intel Core i7-14700K with Thermal Grizzly Carbonaut Pad T-FORCE Delta RGB DDR5 (2x16GB) 7600MT/s CL36 (XMP Profile) 2TB Kingston Fury Renegade SSD Windows 11 24H2 (Build 26100.3194) Drivers used for the 7800 XT, 9070 XT and 9070 were Adrenaline v24.30.31.03 / 25.3.1 RC (press driver provided by AMD), and for the Nvidia RTX 5070 and 4070, GeForce v572.47 was used. (From the left) Sapphire Pulse 9070 XT, Nvidia 5070 FE, and Pulse 9070First up, we have Geekbench AI running on ONNX. The RTX 5070 gets beaten by both the 9070 XT and 9070 in quantized and single precision (FP32) performance. Similarly, the 4070 gets close to the 9070 in half-precision (FP16) performance, but the latter is an enormous 30% faster in quantized score and nearly 12.2% better in single precision (FP32). The reason for this beatdown is the amount of memory available to each card. The Nvidia GPUs have 12GB each and thus only do better in the FP16 precision tests since the other ones are more VRAM-intensive. Next up, we move to UL Procyon suite starting with the Image generation benchmark. We chose the Stable Diffusion XL FP16 test since this is the most intense workload available on Procyon suite. Similar to what we saw on Geekbench AI, the Nvidia GPUs to relatively better here as it is FP16 or half precision which means the used VRAM is lower. So this is something to keep in mind again, if you wish to float32 AI workloads, it is likely that graphics cards with greater than 12 GB buffers would emerge as victors. There is still a big improvement on the RX 9070 compared to the 7800 XT as we see a ~54% gain. This boost is due to improvements to the core architecture itself as VRAM capacities of both cards are the same at 16 Gigs. Following image generation, we move to the text generation benchmark. In this workload, we see the least impressive performance of the 9070 in terms of how much it improves over the 7800 XT. The former is up to ~7.25% faster here. The 9070 is also not as well-performing as the Nvidia 4070 in Phi and Mistral models, although it does do better in both the Llama tests. Another odd result stood out here where the 5070 underperformed all the cards including the 7800 XT in Llama 2. We ran each test three times and considered the best score and so we are not exactly sure what happened here. Wrapping up AI testing, we measured OpenCL throughput in Geekbench compute benchmark. The RX 9070 did not fare well here at all even falling behind the 7800 XT and it is significantly slower than the three other cards. Interestingly, even the RTX 5070 could not beat the 4070 on OpenCL so perhaps this suggests that OpenCL optimization has not been a priority for either AMD or Nvidia this time. It could also be an issue with Geekbench itself. Conclusion We reach the end of our productivity performance review of the 9070 and we have to say we are fairly impressed but there is also a slight bit of disappointment. It is clear that the 9070 as well as the 9070 XT really shine when inferencing precision is higher, and that is due to the higher memory buffers they possess compared to the Nvidia 5070. But on FP16, the Nvidia cards pull ahead. Still RNDA 4, including the RX 9070, see big boost over RDNA 3 (7800 XT). As we noted in the image generation benchmark, which is an intense load, there is over a 50% gain. So what do we make of the RX 9070 as a productivity hardware? We think it's a good card. If someone was looking for a GPU around $550 that can do both gaming and crunch through some AI tasks this is a good card to pick up especially if you are dealing with single precision situations or some other VRAM-intense tasks. And we already know it is efficient so there's that too. For those however looking for a GPU that can deal with more, AMD recently unveiled the Radeon AI PRO R9700 which is essentially a 32 GB refresh of the 9070 XT with some additional workstation-based optimizations. Considering everything, we rate AMD's RX 9070 a 9 out of 10 for its AI performance. Price is less of a factor for those looking at productivity cases compared to ones considering the GPU for gaming, and as such, we felt it did quite decent overall and can be especially handy if you need more than 12 GB. Purchase links: RX 9070 / XT (Amazon US) As an Amazon Associate we earn from qualifying purchases. Tags Report a problem with article Follow @NeowinFeed

·107 Vue

Connectez-vous pour aimer, partager et commenter!
Computerworld UK partage un lien

2025-05-23 20:22:04 ·

Signal to Windows Recall: Drop dead

Windows, as all but the most besotted Microsoft fans know, has historically been a security disaster. Seriously, what other program has a dedicated day each month to reveal its latest security holes?

But now, Windows Recall, the AI-powered “feature” that continuously takes snapshots of your screen to create a searchable timeline of everything you do, has arrived for Copilot+ PCs running Windows 11 version 24H2 and newer.

After a year of controversy and multiple delays prompted by widespread privacy and security concerns, Microsoft has significantly changed Recall’s architecture. The feature is now opt-in, requires Windows Hello biometric authentication, encrypts all snapshots locally, filters out sensitive data such as credit card numbers, and allows users to filter out specific apps or websites from being captured.

I am so unimpressed. A few days ago, in the latest Patch Tuesday release, Microsoft revealed five — count ’em, five! — zero-day security holes in Windows alone. Do you expect me to trust Recall with a track record like this?

Besides, even if I don’t enable the feature, what if our beloved federal government decides that for our protection, it would be better if Microsoft turned on Recall for some users? After all, it’s almost impossible to run Windows these days without having a Microsoft ID, making it easy to pick and choose who gets what “update.”

Other people feel the same way. Recall remains a lightning rod for criticism. Privacy advocates and security experts continue to warn that the very nature of Recall capturing and storing everything displayed on a user’s screen every few seconds is inherently too risky. Even if you don’t use the feature yourself, what about all the people you communicate with who might have Recall turned on? How could you even know?

A friend at the University of Pennsylvania told me that the school has examined Microsoft Recall and found that it “introduces substantial and unacceptable security, legality, and privacy challenges.” Sounds about right to me.

Amusingly enough, Kaspersky, the Russian security company that has its own security issues, also states that you should avoid Recall. Why? Well, yes, when you first activate Recall, you are required to use biometric authentication. After that, your PIN will do nicely. Oh, and its automatic filtering of sensitive data is unreliable. Sure, it will stop taking snapshots when you’re in private mode on Chrome or Edge. Vivaldi? Not so much.

And as Kaspersky points out, if you use videoconferencing with automatic transcription enabled, Recall will save a complete call transcript detailing who said what. Oh boy!

Signal, the popular secure messaging program, wants nothing to do with this. It has introduced a new “Screen security” setting in its Windows desktop app, specifically designed to protect its users from Recall.

Enabled by default on Windows 11, this feature uses a Digital Rights Managementflag to stop any application, including Windows Recall, from capturing screenshots of Signal chats. When Recall or other screenshot tools try to capture Signal’s window, it will produce a blank image.

Why? In a blog post, Signal explained:

“Although Microsoft made several adjustments over the past twelve months in response to critical feedback, the revamped version of Recall still places any content that’s displayed within privacy-preserving apps like Signal at risk. As a result, we are enabling an extra layer of protection by default on Windows 11 in order to help maintain the security of Signal Desktop on that platform, even though it introduces some usability trade-offs. Microsoft has simply given us no other option.”

Actually, you do have another option: Desktop Linux. I said it ages ago, and I’ll say it again now. If you really care about security on your desktop, you want Linux.
#signal #windows #recall #drop #dead

Signal to Windows Recall: Drop dead
Windows, as all but the most besotted Microsoft fans know, has historically been a security disaster. Seriously, what other program has a dedicated day each month to reveal its latest security holes? But now, Windows Recall, the AI-powered “feature” that continuously takes snapshots of your screen to create a searchable timeline of everything you do, has arrived for Copilot+ PCs running Windows 11 version 24H2 and newer. After a year of controversy and multiple delays prompted by widespread privacy and security concerns, Microsoft has significantly changed Recall’s architecture. The feature is now opt-in, requires Windows Hello biometric authentication, encrypts all snapshots locally, filters out sensitive data such as credit card numbers, and allows users to filter out specific apps or websites from being captured. I am so unimpressed. A few days ago, in the latest Patch Tuesday release, Microsoft revealed five — count ’em, five! — zero-day security holes in Windows alone. Do you expect me to trust Recall with a track record like this? Besides, even if I don’t enable the feature, what if our beloved federal government decides that for our protection, it would be better if Microsoft turned on Recall for some users? After all, it’s almost impossible to run Windows these days without having a Microsoft ID, making it easy to pick and choose who gets what “update.” Other people feel the same way. Recall remains a lightning rod for criticism. Privacy advocates and security experts continue to warn that the very nature of Recall capturing and storing everything displayed on a user’s screen every few seconds is inherently too risky. Even if you don’t use the feature yourself, what about all the people you communicate with who might have Recall turned on? How could you even know? A friend at the University of Pennsylvania told me that the school has examined Microsoft Recall and found that it “introduces substantial and unacceptable security, legality, and privacy challenges.” Sounds about right to me. Amusingly enough, Kaspersky, the Russian security company that has its own security issues, also states that you should avoid Recall. Why? Well, yes, when you first activate Recall, you are required to use biometric authentication. After that, your PIN will do nicely. Oh, and its automatic filtering of sensitive data is unreliable. Sure, it will stop taking snapshots when you’re in private mode on Chrome or Edge. Vivaldi? Not so much. And as Kaspersky points out, if you use videoconferencing with automatic transcription enabled, Recall will save a complete call transcript detailing who said what. Oh boy! Signal, the popular secure messaging program, wants nothing to do with this. It has introduced a new “Screen security” setting in its Windows desktop app, specifically designed to protect its users from Recall. Enabled by default on Windows 11, this feature uses a Digital Rights Managementflag to stop any application, including Windows Recall, from capturing screenshots of Signal chats. When Recall or other screenshot tools try to capture Signal’s window, it will produce a blank image. Why? In a blog post, Signal explained: “Although Microsoft made several adjustments over the past twelve months in response to critical feedback, the revamped version of Recall still places any content that’s displayed within privacy-preserving apps like Signal at risk. As a result, we are enabling an extra layer of protection by default on Windows 11 in order to help maintain the security of Signal Desktop on that platform, even though it introduces some usability trade-offs. Microsoft has simply given us no other option.” Actually, you do have another option: Desktop Linux. I said it ages ago, and I’ll say it again now. If you really care about security on your desktop, you want Linux. #signal #windows #recall #drop #dead

WWW.COMPUTERWORLD.COM

Signal to Windows Recall: Drop dead

Windows, as all but the most besotted Microsoft fans know, has historically been a security disaster. Seriously, what other program has a dedicated day each month to reveal its latest security holes? But now, Windows Recall, the AI-powered “feature” that continuously takes snapshots of your screen to create a searchable timeline of everything you do, has arrived for Copilot+ PCs running Windows 11 version 24H2 and newer. After a year of controversy and multiple delays prompted by widespread privacy and security concerns, Microsoft has significantly changed Recall’s architecture. The feature is now opt-in, requires Windows Hello biometric authentication, encrypts all snapshots locally, filters out sensitive data such as credit card numbers, and allows users to filter out specific apps or websites from being captured. I am so unimpressed. A few days ago, in the latest Patch Tuesday release, Microsoft revealed five — count ’em, five! — zero-day security holes in Windows alone. Do you expect me to trust Recall with a track record like this? Besides, even if I don’t enable the feature, what if our beloved federal government decides that for our protection, it would be better if Microsoft turned on Recall for some users? After all, it’s almost impossible to run Windows these days without having a Microsoft ID, making it easy to pick and choose who gets what “update.” Other people feel the same way. Recall remains a lightning rod for criticism. Privacy advocates and security experts continue to warn that the very nature of Recall capturing and storing everything displayed on a user’s screen every few seconds is inherently too risky. Even if you don’t use the feature yourself, what about all the people you communicate with who might have Recall turned on? How could you even know? A friend at the University of Pennsylvania told me that the school has examined Microsoft Recall and found that it “introduces substantial and unacceptable security, legality, and privacy challenges.” Sounds about right to me. Amusingly enough, Kaspersky, the Russian security company that has its own security issues, also states that you should avoid Recall. Why? Well, yes, when you first activate Recall, you are required to use biometric authentication. After that, your PIN will do nicely. Oh, and its automatic filtering of sensitive data is unreliable. Sure, it will stop taking snapshots when you’re in private mode on Chrome or Edge. Vivaldi? Not so much. And as Kaspersky points out, if you use videoconferencing with automatic transcription enabled, Recall will save a complete call transcript detailing who said what. Oh boy! Signal, the popular secure messaging program (well, secure when you use it correctly — unlike, say, the US Secretary of Defense), wants nothing to do with this. It has introduced a new “Screen security” setting in its Windows desktop app, specifically designed to protect its users from Recall. Enabled by default on Windows 11, this feature uses a Digital Rights Management (DRM) flag to stop any application, including Windows Recall, from capturing screenshots of Signal chats. When Recall or other screenshot tools try to capture Signal’s window, it will produce a blank image. Why? In a blog post, Signal explained: “Although Microsoft made several adjustments over the past twelve months in response to critical feedback, the revamped version of Recall still places any content that’s displayed within privacy-preserving apps like Signal at risk. As a result, we are enabling an extra layer of protection by default on Windows 11 in order to help maintain the security of Signal Desktop on that platform, even though it introduces some usability trade-offs. Microsoft has simply given us no other option.” Actually, you do have another option: Desktop Linux. I said it ages ago, and I’ll say it again now. If you really care about security on your desktop, you want Linux.

·119 Vue

Connectez-vous pour aimer, partager et commenter!
NeowinFeed partage un lien

2025-05-23 08:22:20 ·

ExplorerPatcher fix bypasses Windows 11 24H2 upgrade block, and squashes two major bugs

When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works.

ExplorerPatcher fix bypasses Windows 11 24H2 upgrade block, and squashes two major bugs

Sayan Sen

Neowin
@ssc_combater007 ·

May 23, 2025 04:06 EDT

ExplorerPatcher is a popular third-party customization and tweaking app on Windows. The latest update has three major improvements for Windows 11 24H2. First up, the author has made changes so that the app can bypass the Windows 11 24H2 upgrade block. Microsoft informed earlier that 24H2 compatibility block related to customization apps was slowly being removed.
With the latest update, the ExplorerPatcher developer notes that they made changes to improve the app's Desktop Window Manager compatibility with the newest Windows version by renaming the ep_dwm EXE file to ep_dwm_svc.
If you remember, Microsoft started blocking third-party apps like this one back in April 2024 during Insider testing and the safeguard hold continued even after general availability.

In terms of bug fixes, there are several and two of them are related to Windows 11 24H2. The feature "disable rounded corner" now works on the latest Windows feature update.
If you are familiar with Windows 11, one of the many characteristics of its aesthetics is the presence of rounder corners, which Microsoft has also brought over to its other apps, although there is still clearly room for sharper edged tabs too.
So many who disliked the rounded corners on Windows 11 would rely on unofficial apps like ExplorerPatcher to deal with them. Thankfully, the feature now works, as previously it would simply automatically uncheck when detecting a 24H2 build.
The second improvement is about Simple Window Switcher or SWS as the developer of ExplorerPatcher refers to it. SWS is meant as an alternative to the Alt-Tab functionality on stock Windows.
Unlike the "disable rounded corner" option, the SWS feature still worked, although its implementation on Windows 11 24H2 was buggy, as users experienced slowdowns and lag. Underlying code issues can often cause problems like these as recently pointed out by a senior Microsoft engineer.
From the user comments, it is apparent that the window switcher feature exhibited various other issues too. One user 03juan documented the several problems they encountered in great detail. These included being stuck in an infinite loop, high CPU usage, among others.
The full changelog is given below:

Start10: Fixed Pin to Start on 226x1.4541+ and 261xx.2454+.
sws: Added support for 24H2.
ep_dwm: Added support for 24H2.

ep_dwm.exe has been renamed to ep_dwm_svc.exe to get around 24H2 upgrade blocks.
ep_dwm: Now always unregistered on uninstallation, regardless of whether it was running during the uninstallation or not.
Setup: The failure message now displays the associated code line number that failed, to assist in troubleshooting.
Taskbar10: Fixed disabling immersive menus on ARM64.
Taskbar10: Fixed Win+X menu still having Windows Terminal entries when Windows Terminal is not installed, that crashes Explorer when selected.

For now, if you want to have PowerShell entries, Windows Terminal must be uninstalled.

Taskbar10: Fixed Win+X entry clicks doing nothing on 26xxx.5551+ ARM64.
GUI: Added dropdown indicators to dropdown entries.
GUI: The language names now include the country name.Localization: Added Czech translations.Localization: Added Spanishtranslations.ep_taskbar: Added support for "Show desktop button: Hidden" setting.ep_taskbar: Fixed a bug that prevented shortcut global hotkeys from working on 24H2.ep_taskbar: Fixed a bug that prevented the taskbar from resizing properly after DPI changes.ep_taskbar: Added the following languages: German, French, Hungarian, Indonesian, Italian, Korean, Lithuanian, Dutch, Polish, Portuguese, Romanian, Spanish, Turkish, Ukrainian, Chinese.
ep_taskbar: Fixed a number of memory leaks and code/behavior inaccuracies.
ep_taskbar: Fixed incompatibility with 26200.5603, 26120.4151, and 26100.4188.ep_taskbar: Now supports all Windows 10 versions supported by EP.To download the latest version, 22631.5335.68, of ExplorerPatcher, head over to Neowin's software stories page or its official GitHub repo here.
The ExplorerPatcher author has also cautioned that Microsoft Defender will still flag the newer versions of the app, and has provided the following PowerShell to optionally add to anti-virus exclusions:

Add-MpPreference -ExclusionPath "C:\Program Files\ExplorerPatcher"
Add-MpPreference -ExclusionPath "$env:APPDATA\ExplorerPatcher"
Add-MpPreference -ExclusionPath "C:\Windows\dxgi.dll"
Add-MpPreference -ExclusionPath "C:\Windows\SystemApps\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy"
Add-MpPreference -ExclusionPath "C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy"

Bear in mind though, that Defender serves to protect your system from dangerous malware like the recently reported Lumma, which affects nearly 400,000 systems worldwide. So if you do add exceptions manually, make sure to not let a dangerous quarantined threat out.

Tags

Report a problem with article

Follow @NeowinFeed
#explorerpatcher #fix #bypasses #windows #24h2

ExplorerPatcher fix bypasses Windows 11 24H2 upgrade block, and squashes two major bugs
When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works. ExplorerPatcher fix bypasses Windows 11 24H2 upgrade block, and squashes two major bugs Sayan Sen Neowin @ssc_combater007 · May 23, 2025 04:06 EDT ExplorerPatcher is a popular third-party customization and tweaking app on Windows. The latest update has three major improvements for Windows 11 24H2. First up, the author has made changes so that the app can bypass the Windows 11 24H2 upgrade block. Microsoft informed earlier that 24H2 compatibility block related to customization apps was slowly being removed. With the latest update, the ExplorerPatcher developer notes that they made changes to improve the app's Desktop Window Manager compatibility with the newest Windows version by renaming the ep_dwm EXE file to ep_dwm_svc. If you remember, Microsoft started blocking third-party apps like this one back in April 2024 during Insider testing and the safeguard hold continued even after general availability. In terms of bug fixes, there are several and two of them are related to Windows 11 24H2. The feature "disable rounded corner" now works on the latest Windows feature update. If you are familiar with Windows 11, one of the many characteristics of its aesthetics is the presence of rounder corners, which Microsoft has also brought over to its other apps, although there is still clearly room for sharper edged tabs too. So many who disliked the rounded corners on Windows 11 would rely on unofficial apps like ExplorerPatcher to deal with them. Thankfully, the feature now works, as previously it would simply automatically uncheck when detecting a 24H2 build. The second improvement is about Simple Window Switcher or SWS as the developer of ExplorerPatcher refers to it. SWS is meant as an alternative to the Alt-Tab functionality on stock Windows. Unlike the "disable rounded corner" option, the SWS feature still worked, although its implementation on Windows 11 24H2 was buggy, as users experienced slowdowns and lag. Underlying code issues can often cause problems like these as recently pointed out by a senior Microsoft engineer. From the user comments, it is apparent that the window switcher feature exhibited various other issues too. One user 03juan documented the several problems they encountered in great detail. These included being stuck in an infinite loop, high CPU usage, among others. The full changelog is given below: Start10: Fixed Pin to Start on 226x1.4541+ and 261xx.2454+. sws: Added support for 24H2. ep_dwm: Added support for 24H2. ep_dwm.exe has been renamed to ep_dwm_svc.exe to get around 24H2 upgrade blocks. ep_dwm: Now always unregistered on uninstallation, regardless of whether it was running during the uninstallation or not. Setup: The failure message now displays the associated code line number that failed, to assist in troubleshooting. Taskbar10: Fixed disabling immersive menus on ARM64. Taskbar10: Fixed Win+X menu still having Windows Terminal entries when Windows Terminal is not installed, that crashes Explorer when selected. For now, if you want to have PowerShell entries, Windows Terminal must be uninstalled. Taskbar10: Fixed Win+X entry clicks doing nothing on 26xxx.5551+ ARM64. GUI: Added dropdown indicators to dropdown entries. GUI: The language names now include the country name.Localization: Added Czech translations.Localization: Added Spanishtranslations.ep_taskbar: Added support for "Show desktop button: Hidden" setting.ep_taskbar: Fixed a bug that prevented shortcut global hotkeys from working on 24H2.ep_taskbar: Fixed a bug that prevented the taskbar from resizing properly after DPI changes.ep_taskbar: Added the following languages: German, French, Hungarian, Indonesian, Italian, Korean, Lithuanian, Dutch, Polish, Portuguese, Romanian, Spanish, Turkish, Ukrainian, Chinese. ep_taskbar: Fixed a number of memory leaks and code/behavior inaccuracies. ❗ ep_taskbar: Fixed incompatibility with 26200.5603, 26120.4151, and 26100.4188.ep_taskbar: Now supports all Windows 10 versions supported by EP.To download the latest version, 22631.5335.68, of ExplorerPatcher, head over to Neowin's software stories page or its official GitHub repo here. The ExplorerPatcher author has also cautioned that Microsoft Defender will still flag the newer versions of the app, and has provided the following PowerShell to optionally add to anti-virus exclusions: Add-MpPreference -ExclusionPath "C:\Program Files\ExplorerPatcher" Add-MpPreference -ExclusionPath "$env:APPDATA\ExplorerPatcher" Add-MpPreference -ExclusionPath "C:\Windows\dxgi.dll" Add-MpPreference -ExclusionPath "C:\Windows\SystemApps\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy" Add-MpPreference -ExclusionPath "C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy" Bear in mind though, that Defender serves to protect your system from dangerous malware like the recently reported Lumma, which affects nearly 400,000 systems worldwide. So if you do add exceptions manually, make sure to not let a dangerous quarantined threat out. Tags Report a problem with article Follow @NeowinFeed #explorerpatcher #fix #bypasses #windows #24h2

WWW.NEOWIN.NET

ExplorerPatcher fix bypasses Windows 11 24H2 upgrade block, and squashes two major bugs

When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works. ExplorerPatcher fix bypasses Windows 11 24H2 upgrade block, and squashes two major bugs Sayan Sen Neowin @ssc_combater007 · May 23, 2025 04:06 EDT ExplorerPatcher is a popular third-party customization and tweaking app on Windows. The latest update has three major improvements for Windows 11 24H2. First up, the author has made changes so that the app can bypass the Windows 11 24H2 upgrade block. Microsoft informed earlier that 24H2 compatibility block related to customization apps was slowly being removed. With the latest update, the ExplorerPatcher developer notes that they made changes to improve the app's Desktop Window Manager compatibility with the newest Windows version by renaming the ep_dwm EXE file to ep_dwm_svc. If you remember, Microsoft started blocking third-party apps like this one back in April 2024 during Insider testing and the safeguard hold continued even after general availability. In terms of bug fixes, there are several and two of them are related to Windows 11 24H2. The feature "disable rounded corner" now works on the latest Windows feature update. If you are familiar with Windows 11, one of the many characteristics of its aesthetics is the presence of rounder corners, which Microsoft has also brought over to its other apps, although there is still clearly room for sharper edged tabs too. So many who disliked the rounded corners on Windows 11 would rely on unofficial apps like ExplorerPatcher to deal with them. Thankfully, the feature now works, as previously it would simply automatically uncheck when detecting a 24H2 build. The second improvement is about Simple Window Switcher or SWS as the developer of ExplorerPatcher refers to it. SWS is meant as an alternative to the Alt-Tab functionality on stock Windows. Unlike the "disable rounded corner" option, the SWS feature still worked, although its implementation on Windows 11 24H2 was buggy, as users experienced slowdowns and lag. Underlying code issues can often cause problems like these as recently pointed out by a senior Microsoft engineer. From the user comments, it is apparent that the window switcher feature exhibited various other issues too. One user 03juan documented the several problems they encountered in great detail. These included being stuck in an infinite loop, high CPU usage, among others. The full changelog is given below: Start10: Fixed Pin to Start on 226x1.4541+ and 261xx.2454+. sws: Added support for 24H2. ep_dwm: Added support for 24H2. ep_dwm.exe has been renamed to ep_dwm_svc.exe to get around 24H2 upgrade blocks. ep_dwm: Now always unregistered on uninstallation, regardless of whether it was running during the uninstallation or not. Setup: The failure message now displays the associated code line number that failed, to assist in troubleshooting. Taskbar10: Fixed disabling immersive menus on ARM64. Taskbar10: Fixed Win+X menu still having Windows Terminal entries when Windows Terminal is not installed, that crashes Explorer when selected. For now, if you want to have PowerShell entries, Windows Terminal must be uninstalled. Taskbar10: Fixed Win+X entry clicks doing nothing on 26xxx.5551+ ARM64. GUI: Added dropdown indicators to dropdown entries. GUI: The language names now include the country name. (3f11766) Localization: Added Czech translations. (Thanks @9hb, @andrewz1986, and @Panzimy!) Localization: Added Spanish (Spain) translations. (Thanks @AlejandroMartiGisbert!) ep_taskbar: Added support for "Show desktop button: Hidden" setting. (#4020) (1be6658) ep_taskbar: Fixed a bug that prevented shortcut global hotkeys from working on 24H2. (#3777, #4016) ep_taskbar: Fixed a bug that prevented the taskbar from resizing properly after DPI changes. (#3796) ep_taskbar: Added the following languages: German, French, Hungarian, Indonesian, Italian, Korean, Lithuanian, Dutch, Polish, Portuguese (Brazil), Romanian, Spanish (Spain), Turkish, Ukrainian, Chinese (Simplified). ep_taskbar: Fixed a number of memory leaks and code/behavior inaccuracies. ❗ ep_taskbar: Fixed incompatibility with 26200.5603 (Dev), 26120.4151 (Beta), and 26100.4188 (Release Preview). (#4321) ep_taskbar: Now supports all Windows 10 versions supported by EP (17763/1809+). (aec8c70, 1edb989) To download the latest version, 22631.5335.68, of ExplorerPatcher, head over to Neowin's software stories page or its official GitHub repo here. The ExplorerPatcher author has also cautioned that Microsoft Defender will still flag the newer versions of the app, and has provided the following PowerShell to optionally add to anti-virus exclusions: Add-MpPreference -ExclusionPath "C:\Program Files\ExplorerPatcher" Add-MpPreference -ExclusionPath "$env:APPDATA\ExplorerPatcher" Add-MpPreference -ExclusionPath "C:\Windows\dxgi.dll" Add-MpPreference -ExclusionPath "C:\Windows\SystemApps\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy" Add-MpPreference -ExclusionPath "C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy" Bear in mind though, that Defender serves to protect your system from dangerous malware like the recently reported Lumma, which affects nearly 400,000 systems worldwide. So if you do add exceptions manually, make sure to not let a dangerous quarantined threat out. Tags Report a problem with article Follow @NeowinFeed

·173 Vue

Connectez-vous pour aimer, partager et commenter!
NeowinFeed partage un lien

2025-05-20 06:03:13 ·

Microsoft's official support proves useless as Windows 11 KB5058411 installs fail

When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works.

Microsoft's official support proves useless as Windows 11 KB5058411 installs fail

Sayan Sen

Neowin
@ssc_combater007 ·

May 20, 2025 01:52 EDT

While Patch Tuesdays bring important security updates for the Windows OS, they can often introduce major bugs. The one this month on Windows 10, KB5058379, that introduced a BitLocker recovery reboot bug, has now been resolved with KB5061768 OOB update. Alongside that, Microsoft also resolved a Windows 11 24H2 upgrade bug related to VBS with a Recovery update KB5059442.
Speaking of Windows 11, users are reporting installation failures with the Windows 11 May 2025 Patch Tuesday update KB5058411 as well. Affected users say that these are failing with various error codes like 0x800f0991, 0x800f0991, 0x800f0838, 0x800736b3, and 0x800f081f.
User Shukang Liang on the Microsoft support forums writes: "Problem with windows update KB5058411 Installation fails and error code 0x800f0991 comes up." The query has been upvoted by 33 other users at the time of writing.

Another user PaulK671 notes 0x800736b3 and 0x800f081f errors as they write:

Error 0x800736b3 and 0x800f0838 when installing KB5058411Hello community,
I’m experiencing a persistent issue when trying to install the KB5058411 cumulative update for Windows 11 Version 24H2, released on May 13, 2025.
Initial symptoms:

Windows Update stalls at 6% download.
Then returns error 0x800f081f.
After manually downloading and executing the .msu file from the Microsoft Update Catalog, I get error 0x800f0838.
The CBS logs and Event Viewer also show error 0x800736b3.

The thread has been upvoted by 19 people at the time of writing.
Meanwhile, user Jenny-XS says they came across the 0x800f081f error code when trying to install the May '25 Patch Tuesday.
Microsoft recently published a support article with a long list of Windows 11 and 10 hex error codes that lead to installation failures. Unfortunately, though, none of the codes reported by users match with the ones Microsoft has provided workarounds for.
Thus, it looks like Microsoft will have to update its list sooner rather than later as clearly many hex error codes are still pending and are due for addition to its support documentation.
Interestingly, one of the commenters on the 0x800f0991 error thread, ScotBirch, added that they were able to resolve the issue using the "Fix problems using Windows Update" option. Microsoft had detailed what that is and how it works back in December 2024. You can read the linked article to find out more and see if perhaps it fixes your issues too.

Tags

Report a problem with article

Follow @NeowinFeed
#microsoft039s #official #support #proves #useless

Microsoft's official support proves useless as Windows 11 KB5058411 installs fail
When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works. Microsoft's official support proves useless as Windows 11 KB5058411 installs fail Sayan Sen Neowin @ssc_combater007 · May 20, 2025 01:52 EDT While Patch Tuesdays bring important security updates for the Windows OS, they can often introduce major bugs. The one this month on Windows 10, KB5058379, that introduced a BitLocker recovery reboot bug, has now been resolved with KB5061768 OOB update. Alongside that, Microsoft also resolved a Windows 11 24H2 upgrade bug related to VBS with a Recovery update KB5059442. Speaking of Windows 11, users are reporting installation failures with the Windows 11 May 2025 Patch Tuesday update KB5058411 as well. Affected users say that these are failing with various error codes like 0x800f0991, 0x800f0991, 0x800f0838, 0x800736b3, and 0x800f081f. User Shukang Liang on the Microsoft support forums writes: "Problem with windows update KB5058411 Installation fails and error code 0x800f0991 comes up." The query has been upvoted by 33 other users at the time of writing. Another user PaulK671 notes 0x800736b3 and 0x800f081f errors as they write: Error 0x800736b3 and 0x800f0838 when installing KB5058411Hello community, I’m experiencing a persistent issue when trying to install the KB5058411 cumulative update for Windows 11 Version 24H2, released on May 13, 2025. Initial symptoms: Windows Update stalls at 6% download. Then returns error 0x800f081f. After manually downloading and executing the .msu file from the Microsoft Update Catalog, I get error 0x800f0838. The CBS logs and Event Viewer also show error 0x800736b3. The thread has been upvoted by 19 people at the time of writing. Meanwhile, user Jenny-XS says they came across the 0x800f081f error code when trying to install the May '25 Patch Tuesday. Microsoft recently published a support article with a long list of Windows 11 and 10 hex error codes that lead to installation failures. Unfortunately, though, none of the codes reported by users match with the ones Microsoft has provided workarounds for. Thus, it looks like Microsoft will have to update its list sooner rather than later as clearly many hex error codes are still pending and are due for addition to its support documentation. Interestingly, one of the commenters on the 0x800f0991 error thread, ScotBirch, added that they were able to resolve the issue using the "Fix problems using Windows Update" option. Microsoft had detailed what that is and how it works back in December 2024. You can read the linked article to find out more and see if perhaps it fixes your issues too. Tags Report a problem with article Follow @NeowinFeed #microsoft039s #official #support #proves #useless

WWW.NEOWIN.NET

Microsoft's official support proves useless as Windows 11 KB5058411 installs fail

When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works. Microsoft's official support proves useless as Windows 11 KB5058411 installs fail Sayan Sen Neowin @ssc_combater007 · May 20, 2025 01:52 EDT While Patch Tuesdays bring important security updates for the Windows OS, they can often introduce major bugs. The one this month on Windows 10, KB5058379, that introduced a BitLocker recovery reboot bug, has now been resolved with KB5061768 OOB update. Alongside that, Microsoft also resolved a Windows 11 24H2 upgrade bug related to VBS with a Recovery update KB5059442. Speaking of Windows 11, users are reporting installation failures with the Windows 11 May 2025 Patch Tuesday update KB5058411 as well. Affected users say that these are failing with various error codes like 0x800f0991, 0x800f0991, 0x800f0838, 0x800736b3, and 0x800f081f. User Shukang Liang on the Microsoft support forums writes: "Problem with windows update KB5058411 Installation fails and error code 0x800f0991 comes up." The query has been upvoted by 33 other users at the time of writing. Another user PaulK671 notes 0x800736b3 and 0x800f081f errors as they write: Error 0x800736b3 and 0x800f0838 when installing KB5058411 (Windows 11 24H2 x64 update) Hello community, I’m experiencing a persistent issue when trying to install the KB5058411 cumulative update for Windows 11 Version 24H2 (x64), released on May 13, 2025 (OS Build 26100.4061). Initial symptoms: Windows Update stalls at 6% download. Then returns error 0x800f081f. After manually downloading and executing the .msu file from the Microsoft Update Catalog, I get error 0x800f0838. The CBS logs and Event Viewer also show error 0x800736b3. The thread has been upvoted by 19 people at the time of writing. Meanwhile, user Jenny-XS says they came across the 0x800f081f error code when trying to install the May '25 Patch Tuesday. Microsoft recently published a support article with a long list of Windows 11 and 10 hex error codes that lead to installation failures. Unfortunately, though, none of the codes reported by users match with the ones Microsoft has provided workarounds for. Thus, it looks like Microsoft will have to update its list sooner rather than later as clearly many hex error codes are still pending and are due for addition to its support documentation. Interestingly, one of the commenters on the 0x800f0991 error thread, ScotBirch, added that they were able to resolve the issue using the "Fix problems using Windows Update" option. Microsoft had detailed what that is and how it works back in December 2024. You can read the linked article to find out more and see if perhaps it fixes your issues too. Tags Report a problem with article Follow @NeowinFeed

·182 Vue

Connectez-vous pour aimer, partager et commenter!
TechSpot partage un lien

2025-05-18 22:42:15 ·

Nvidia driver enables RTX 5000 GPU support on Intel Core 2 CPUs &ndash; with a catch

In context: Nvidia recently rolled out a GeForce driver update that quietly made older Intel processors, specifically the Core 2 family, technically compatible with the latest RTX 50-series GPUs. It initially sounded like a promising "loophole" for retro PC enthusiasts, but unfortunately, things haven't played out as expected.
The key to this surprising development lies in a single instruction: POPCNT, or "Population Count." This CPU-level instruction is used to calculate the number of bits set in a binary value, which is vital for many low-level operations in modern software. Until now, Nvidia's drivers required this instruction, excluding older CPUs from using the latest GPUs.
However, with the new driver dropping that requirement, users can now pair their powerful RTX cards with chips that date back over 15 years. Tinkerer Bob Pony quickly tested this on X using an Intel Core 2 Quad Q9450 with an RTX 5060 Ti. He found that it "works," at least in terms of getting the system to boot into Windows 11.
Sadly, things became frustrating as Pony dug deeper. While the setup worked on paper, real-world gaming performance didn't follow. Attempting to run ray-traced games like Quake II RTX led to errors and crashes. Pony stated that the "majority of games" that use ray tracing wouldn't run due to the processor lacking the required instruction sets. Screenshots confirmed the failure.
As it stands, modern games, especially those with ray tracing support, rely on more than just a powerful GPU. Even if the driver no longer requires POPCNT, many games still do, preventing them from running properly.
// Related Stories

It's worth mentioning here that this isn't the first time POPCNT has been a hurdle for aging systems. When Microsoft began previewing Windows 11 24H2, it quietly added POPCNT as a required hardware feature alongside Secure Boot and TPM. That move alone disqualified many older processors, even if users could previously install the OS unofficially.
However, all is not lost. While ray-traced titles are a no-go, there's still value in pairing a modern GPU with an older CPU for classic or mid-tier games. There might also be potential for the community to build a compatibility database by outlining which games continue to play well on quirky setups like these.
#nvidia #driver #enables #rtx #gpu

Nvidia driver enables RTX 5000 GPU support on Intel Core 2 CPUs &ndash; with a catch
In context: Nvidia recently rolled out a GeForce driver update that quietly made older Intel processors, specifically the Core 2 family, technically compatible with the latest RTX 50-series GPUs. It initially sounded like a promising "loophole" for retro PC enthusiasts, but unfortunately, things haven't played out as expected. The key to this surprising development lies in a single instruction: POPCNT, or "Population Count." This CPU-level instruction is used to calculate the number of bits set in a binary value, which is vital for many low-level operations in modern software. Until now, Nvidia's drivers required this instruction, excluding older CPUs from using the latest GPUs. However, with the new driver dropping that requirement, users can now pair their powerful RTX cards with chips that date back over 15 years. Tinkerer Bob Pony quickly tested this on X using an Intel Core 2 Quad Q9450 with an RTX 5060 Ti. He found that it "works," at least in terms of getting the system to boot into Windows 11. Sadly, things became frustrating as Pony dug deeper. While the setup worked on paper, real-world gaming performance didn't follow. Attempting to run ray-traced games like Quake II RTX led to errors and crashes. Pony stated that the "majority of games" that use ray tracing wouldn't run due to the processor lacking the required instruction sets. Screenshots confirmed the failure. As it stands, modern games, especially those with ray tracing support, rely on more than just a powerful GPU. Even if the driver no longer requires POPCNT, many games still do, preventing them from running properly. // Related Stories It's worth mentioning here that this isn't the first time POPCNT has been a hurdle for aging systems. When Microsoft began previewing Windows 11 24H2, it quietly added POPCNT as a required hardware feature alongside Secure Boot and TPM. That move alone disqualified many older processors, even if users could previously install the OS unofficially. However, all is not lost. While ray-traced titles are a no-go, there's still value in pairing a modern GPU with an older CPU for classic or mid-tier games. There might also be potential for the community to build a compatibility database by outlining which games continue to play well on quirky setups like these. #nvidia #driver #enables #rtx #gpu

WWW.TECHSPOT.COM

Nvidia driver enables RTX 5000 GPU support on Intel Core 2 CPUs &ndash; with a catch

In context: Nvidia recently rolled out a GeForce driver update that quietly made older Intel processors, specifically the Core 2 family, technically compatible with the latest RTX 50-series GPUs. It initially sounded like a promising "loophole" for retro PC enthusiasts, but unfortunately, things haven't played out as expected. The key to this surprising development lies in a single instruction: POPCNT, or "Population Count." This CPU-level instruction is used to calculate the number of bits set in a binary value, which is vital for many low-level operations in modern software. Until now, Nvidia's drivers required this instruction, excluding older CPUs from using the latest GPUs. However, with the new driver dropping that requirement, users can now pair their powerful RTX cards with chips that date back over 15 years. Tinkerer Bob Pony quickly tested this on X using an Intel Core 2 Quad Q9450 with an RTX 5060 Ti. He found that it "works," at least in terms of getting the system to boot into Windows 11. Sadly, things became frustrating as Pony dug deeper. While the setup worked on paper, real-world gaming performance didn't follow. Attempting to run ray-traced games like Quake II RTX led to errors and crashes. Pony stated that the "majority of games" that use ray tracing wouldn't run due to the processor lacking the required instruction sets. Screenshots confirmed the failure. As it stands, modern games, especially those with ray tracing support, rely on more than just a powerful GPU. Even if the driver no longer requires POPCNT, many games still do, preventing them from running properly. // Related Stories It's worth mentioning here that this isn't the first time POPCNT has been a hurdle for aging systems. When Microsoft began previewing Windows 11 24H2, it quietly added POPCNT as a required hardware feature alongside Secure Boot and TPM. That move alone disqualified many older processors, even if users could previously install the OS unofficially. However, all is not lost. While ray-traced titles are a no-go, there's still value in pairing a modern GPU with an older CPU for classic or mid-tier games. There might also be potential for the community to build a compatibility database by outlining which games continue to play well on quirky setups like these.

·216 Vue

Connectez-vous pour aimer, partager et commenter!
PCWorld partage un lien

2025-05-18 12:15:21 ·

Windows 11’s May update brings a smorgasbord of new features

Alongside the latest security fixes, Microsoft just added a number of new features to Windows 11 via the KB5058411 update.
The new Copilot+ AI feature known as Windows Recall and the ability to use Phone Link in the Start menu have been mentioned in previous articles, so we don’t need to mention them again.
One of the best improvements in the update is that Windows Search now supports AI, which means—among other things—that you can now use “natural language” in your search queries to find documents, spreadsheets, presentations, and images.
File Explorer also got some boosts, like how it’s now possible to view Microsoft 365 content directly in File Explorer. File Explorer should also open files and unpack ZIP archives much faster, and as for the colors in the bars, the shades of blue and green are now darker than before.

Other goodies in the update include Microsoft removing the blue-colored background for shortcuts on the desktop, which users complained about, as well as numerous bug fixes, which should mean that the risk of running into “blue screen” crashes has gone down.
Update KB5058411 should automatically download and install to your system, assuming you’re on Windows 11 24H2. If it hasn’t yet, you should be able to jump-start it with a manual check in Windows Update.

Further reading: Windows 11 24H2 is now auto-downloading on PCs
#windows #11s #update #brings #smorgasbord

Windows 11’s May update brings a smorgasbord of new features
Alongside the latest security fixes, Microsoft just added a number of new features to Windows 11 via the KB5058411 update. The new Copilot+ AI feature known as Windows Recall and the ability to use Phone Link in the Start menu have been mentioned in previous articles, so we don’t need to mention them again. One of the best improvements in the update is that Windows Search now supports AI, which means—among other things—that you can now use “natural language” in your search queries to find documents, spreadsheets, presentations, and images. File Explorer also got some boosts, like how it’s now possible to view Microsoft 365 content directly in File Explorer. File Explorer should also open files and unpack ZIP archives much faster, and as for the colors in the bars, the shades of blue and green are now darker than before. Other goodies in the update include Microsoft removing the blue-colored background for shortcuts on the desktop, which users complained about, as well as numerous bug fixes, which should mean that the risk of running into “blue screen” crashes has gone down. Update KB5058411 should automatically download and install to your system, assuming you’re on Windows 11 24H2. If it hasn’t yet, you should be able to jump-start it with a manual check in Windows Update. Further reading: Windows 11 24H2 is now auto-downloading on PCs #windows #11s #update #brings #smorgasbord

WWW.PCWORLD.COM

Windows 11’s May update brings a smorgasbord of new features

Alongside the latest security fixes, Microsoft just added a number of new features to Windows 11 via the KB5058411 update. The new Copilot+ AI feature known as Windows Recall and the ability to use Phone Link in the Start menu have been mentioned in previous articles, so we don’t need to mention them again. One of the best improvements in the update is that Windows Search now supports AI, which means—among other things—that you can now use “natural language” in your search queries to find documents, spreadsheets, presentations, and images. File Explorer also got some boosts, like how it’s now possible to view Microsoft 365 content directly in File Explorer (but requires you to pay for the service). File Explorer should also open files and unpack ZIP archives much faster, and as for the colors in the bars, the shades of blue and green are now darker than before. Other goodies in the update include Microsoft removing the blue-colored background for shortcuts on the desktop, which users complained about, as well as numerous bug fixes, which should mean that the risk of running into “blue screen” crashes has gone down. Update KB5058411 should automatically download and install to your system, assuming you’re on Windows 11 24H2. If it hasn’t yet, you should be able to jump-start it with a manual check in Windows Update. Further reading: Windows 11 24H2 is now auto-downloading on PCs

·232 Vue

Connectez-vous pour aimer, partager et commenter!
Computerworld UK partage un lien

2025-05-16 22:06:00 ·

May’s Patch Tuesday serves up 78 updates, including 5 zero-day fixes

This May Patch Tuesday release is very much a “back-to-basics” update with just 78 patches for Microsoft Windows, Office, Visual Studio, and .NET. Notably, Microsoft has not released any patches for Microsoft Exchange Server or Microsoft SQL Server.

Due to the concerns of publicly reported exploits for five Windows vulnerabilities, the Application Readiness team has recommended a “Patch Now” schedule for Windows and a standard release cadence for the other platforms. To help navigate these changes, the team from Readiness has provided a helpful infographic detailing the risks of deploying updates to each platform.

Known issues

There are still reports of issues with devices with Citrix Session Recording Agentversion 2411 installed on Windows 10 platforms. This is an ongoing issue, with no further reported fixes or updates from Citrix or Microsoft. Otherwise, Microsoft has not reported any issues with this month’s update for its Windows desktop and server platforms.

Major revisions and mitigations

Microsoft has not published any major revisions or mitigations to its patches and security fixes for this May.

Windows lifecycle and enforcement updates

Microsoft has not published any enforcement updates this month.

Testing guidance

Each month, the team at Readiness analyzes the latest Patch Tuesday updates from Microsoft and provides detailed, actionable testing guidance. This guidance is based on assessing a large application portfolio and a comprehensive analysis of the Microsoft patches and their potential impact on Windows platforms and application deployments.

We have broken the most significant changes into feature-based groupings to help with testing prioritization. The Readiness team recommends the following areas for testing for the May Patch Tuesday patch cycle:

Remote Desktop, security, and identification

Test your Remote Desktop Gateway configurations. Establish sessions through the gateway and reconnect a few times to ensure stability.

Validate VPN creation, connection, and deletion. Also test fast reconnection and password change flows with PEAP-MSCHAPv2.

Load system level crypto libraries and validate CheckSignatureInFile behavior using legacycertificates.

Test secure boot scenarios, especially if running dual-boot with Linux. Ensure all logins work after this month’s updates.

Run PowerShell modules with and without AppLocker policies to confirm policy enforcement integrity.

Media and codecs

Check your subtitles in MKV formats for Blu-ray playback.

Test audio/video recording using both internal and external devices.

Validate DRM-protected content, especially in Microsoft Edge and Office apps. Testing regimes should include a cycle of playback, record, and stream — then check your system logs for crashes or errors.

Storage and filesystems

Perform Windows error log creation, appends, and reopen scenarios using Common Log File System APIs.

Simulate SMB folder access from multiple windows. Changes in one view should reflect in the other.

Validate UNC path access across apps. Run these tests with Microsoft Explorer and line-of-business apps that access network shares or log files.

Installation and application infrastructure

Given the focus of the Readiness team, it would be remiss to forget the changes to Microsoft’s update and application infrastructure with the following tests:

Conduct basic install, repair, roll-back and uninstall tests for MSI Installer packages. This process should beautomated by now.

If you’re an organization that employs App Silos, you will need create a test cycle that includes invoking the BFS driver via an isolated app context

Run web, file transfer, and messaging scenarios to test network throughput under load.

In addition to these specific test exercises, we highly recommend a full business logic test of your internal and line-of-business applications that have significant graphics requirements. This is required due to the changes to the Windows kernel and GDIsubsystems).

Readiness recommends your testing in priority in the following order: RDP and remote access, application installations, PowerShell testing, and then storage system testing.

Updates by product family

Each month, we break down the update cycle into product familieswith the following basic groupings:

BrowsersMicrosoft WindowsMicrosoft Office

Microsoft Exchange and SQL Server

Microsoft Developer ToolsAdobeBrowsers

Microsoft has not released any native updates for its browsers this month. However, there were five Chromium updatesthat will update Microsoft Edge. All of these low-profile changes can be added to your standard release calendar.

Microsoft Windows

Microsoft has released three critical updates, plus 41 patches rated as important. The critical updates affect Microsoft’s Remote Desktop platform and the Virtual Machine bus.

Unfortunately, the following Windows desktop updates have been reported as exploited in the wild:

CVE-2025-30400

CVE-2025-32701

CVE-2025-32706

CVE-2025-32709

CVE-2025-30397

As a result of these zero-days, the Readiness team recommends a “Patch Now” schedule for these Windows patches.

Microsoft Office

Microsoft has released two critical rated updatesfor the Microsoft Office platform this month. Both of these patches were updated mid-week for documentation reasons.

Following these critical patches, Microsoft has released a further 16 patches that have been rated as important; they update Microsoft Office in general. Please add these Microsoft Office updates to your standard release calendar.

Microsoft Exchange Server

No updates for Microsoft Exchange or Microsoft SQL server this month. Good news for all the server teams.

Microsoft development platforms

A single critical updateto the Microsoft DevOps platform and four patches rated as important by Microsoft have been released to the developer platforms this month. All of the patches rated as important affect Visual Studio and Microsoft .NET. Add these updates to your standard release schedule.

Adobe ReaderNo Adobe updatesfor this May patch cycle. Given the recent security advances implemented in Windows 11 23H2 and 24H2, I think that we will see much less of Adobe in this column.
#mays #patch #tuesday #serves #updates

May’s Patch Tuesday serves up 78 updates, including 5 zero-day fixes
This May Patch Tuesday release is very much a “back-to-basics” update with just 78 patches for Microsoft Windows, Office, Visual Studio, and .NET. Notably, Microsoft has not released any patches for Microsoft Exchange Server or Microsoft SQL Server. Due to the concerns of publicly reported exploits for five Windows vulnerabilities, the Application Readiness team has recommended a “Patch Now” schedule for Windows and a standard release cadence for the other platforms. To help navigate these changes, the team from Readiness has provided a helpful infographic detailing the risks of deploying updates to each platform. Known issues There are still reports of issues with devices with Citrix Session Recording Agentversion 2411 installed on Windows 10 platforms. This is an ongoing issue, with no further reported fixes or updates from Citrix or Microsoft. Otherwise, Microsoft has not reported any issues with this month’s update for its Windows desktop and server platforms. Major revisions and mitigations Microsoft has not published any major revisions or mitigations to its patches and security fixes for this May. Windows lifecycle and enforcement updates Microsoft has not published any enforcement updates this month. Testing guidance Each month, the team at Readiness analyzes the latest Patch Tuesday updates from Microsoft and provides detailed, actionable testing guidance. This guidance is based on assessing a large application portfolio and a comprehensive analysis of the Microsoft patches and their potential impact on Windows platforms and application deployments. We have broken the most significant changes into feature-based groupings to help with testing prioritization. The Readiness team recommends the following areas for testing for the May Patch Tuesday patch cycle: Remote Desktop, security, and identification Test your Remote Desktop Gateway configurations. Establish sessions through the gateway and reconnect a few times to ensure stability. Validate VPN creation, connection, and deletion. Also test fast reconnection and password change flows with PEAP-MSCHAPv2. Load system level crypto libraries and validate CheckSignatureInFile behavior using legacycertificates. Test secure boot scenarios, especially if running dual-boot with Linux. Ensure all logins work after this month’s updates. Run PowerShell modules with and without AppLocker policies to confirm policy enforcement integrity. Media and codecs Check your subtitles in MKV formats for Blu-ray playback. Test audio/video recording using both internal and external devices. Validate DRM-protected content, especially in Microsoft Edge and Office apps. Testing regimes should include a cycle of playback, record, and stream — then check your system logs for crashes or errors. Storage and filesystems Perform Windows error log creation, appends, and reopen scenarios using Common Log File System APIs. Simulate SMB folder access from multiple windows. Changes in one view should reflect in the other. Validate UNC path access across apps. Run these tests with Microsoft Explorer and line-of-business apps that access network shares or log files. Installation and application infrastructure Given the focus of the Readiness team, it would be remiss to forget the changes to Microsoft’s update and application infrastructure with the following tests: Conduct basic install, repair, roll-back and uninstall tests for MSI Installer packages. This process should beautomated by now. If you’re an organization that employs App Silos, you will need create a test cycle that includes invoking the BFS driver via an isolated app context Run web, file transfer, and messaging scenarios to test network throughput under load. In addition to these specific test exercises, we highly recommend a full business logic test of your internal and line-of-business applications that have significant graphics requirements. This is required due to the changes to the Windows kernel and GDIsubsystems). Readiness recommends your testing in priority in the following order: RDP and remote access, application installations, PowerShell testing, and then storage system testing. Updates by product family Each month, we break down the update cycle into product familieswith the following basic groupings: BrowsersMicrosoft WindowsMicrosoft Office Microsoft Exchange and SQL Server Microsoft Developer ToolsAdobeBrowsers Microsoft has not released any native updates for its browsers this month. However, there were five Chromium updatesthat will update Microsoft Edge. All of these low-profile changes can be added to your standard release calendar. Microsoft Windows Microsoft has released three critical updates, plus 41 patches rated as important. The critical updates affect Microsoft’s Remote Desktop platform and the Virtual Machine bus. Unfortunately, the following Windows desktop updates have been reported as exploited in the wild: CVE-2025-30400 CVE-2025-32701 CVE-2025-32706 CVE-2025-32709 CVE-2025-30397 As a result of these zero-days, the Readiness team recommends a “Patch Now” schedule for these Windows patches. Microsoft Office Microsoft has released two critical rated updatesfor the Microsoft Office platform this month. Both of these patches were updated mid-week for documentation reasons. Following these critical patches, Microsoft has released a further 16 patches that have been rated as important; they update Microsoft Office in general. Please add these Microsoft Office updates to your standard release calendar. Microsoft Exchange Server No updates for Microsoft Exchange or Microsoft SQL server this month. Good news for all the server teams. Microsoft development platforms A single critical updateto the Microsoft DevOps platform and four patches rated as important by Microsoft have been released to the developer platforms this month. All of the patches rated as important affect Visual Studio and Microsoft .NET. Add these updates to your standard release schedule. Adobe ReaderNo Adobe updatesfor this May patch cycle. Given the recent security advances implemented in Windows 11 23H2 and 24H2, I think that we will see much less of Adobe in this column. #mays #patch #tuesday #serves #updates

WWW.COMPUTERWORLD.COM

May’s Patch Tuesday serves up 78 updates, including 5 zero-day fixes

This May Patch Tuesday release is very much a “back-to-basics” update with just 78 patches for Microsoft Windows, Office, Visual Studio, and .NET. Notably, Microsoft has not released any patches for Microsoft Exchange Server or Microsoft SQL Server. Due to the concerns of publicly reported exploits for five Windows vulnerabilities, the Application Readiness team has recommended a “Patch Now” schedule for Windows and a standard release cadence for the other platforms. To help navigate these changes, the team from Readiness has provided a helpful infographic detailing the risks of deploying updates to each platform. Known issues There are still reports of issues with devices with Citrix Session Recording Agent (SRA) version 2411 installed on Windows 10 platforms. This is an ongoing issue, with no further reported fixes or updates from Citrix or Microsoft. Otherwise (at the time of writing), Microsoft has not reported any issues with this month’s update for its Windows desktop and server platforms. Major revisions and mitigations Microsoft has not published any major revisions or mitigations to its patches and security fixes for this May. Windows lifecycle and enforcement updates Microsoft has not published any enforcement updates this month. Testing guidance Each month, the team at Readiness analyzes the latest Patch Tuesday updates from Microsoft and provides detailed, actionable testing guidance. This guidance is based on assessing a large application portfolio and a comprehensive analysis of the Microsoft patches and their potential impact on Windows platforms and application deployments. We have broken the most significant changes into feature-based groupings to help with testing prioritization. The Readiness team recommends the following areas for testing for the May Patch Tuesday patch cycle: Remote Desktop, security, and identification Test your Remote Desktop Gateway configurations. Establish sessions through the gateway and reconnect a few times to ensure stability. Validate VPN creation, connection, and deletion. Also test fast reconnection and password change flows with PEAP-MSCHAPv2. Load system level crypto libraries and validate CheckSignatureInFile behavior using legacy (2011) certificates. Test secure boot scenarios, especially if running dual-boot with Linux. Ensure all logins work after this month’s updates. Run PowerShell modules with and without AppLocker policies to confirm policy enforcement integrity. Media and codecs Check your subtitles in MKV formats for Blu-ray playback. Test audio/video recording using both internal and external devices. Validate DRM-protected content, especially in Microsoft Edge and Office apps. Testing regimes should include a cycle of playback, record, and stream — then check your system logs for crashes or errors. Storage and filesystems Perform Windows error log creation, appends, and reopen scenarios using Common Log File System APIs. Simulate SMB folder access from multiple windows. Changes in one view should reflect in the other. Validate UNC path access across apps. Run these tests with Microsoft Explorer and line-of-business apps that access network shares or log files. Installation and application infrastructure Given the focus of the Readiness team, it would be remiss to forget the changes to Microsoft’s update and application infrastructure with the following tests: Conduct basic install, repair, roll-back and uninstall tests for MSI Installer packages. This process should be (mostly) automated by now. If you’re an organization that employs App Silos, you will need create a test cycle that includes invoking the BFS driver via an isolated app context Run web, file transfer, and messaging scenarios to test network throughput under load. In addition to these specific test exercises, we highly recommend a full business logic test of your internal and line-of-business applications that have significant graphics requirements. This is required due to the changes to the Windows kernel and GDI (graphic) subsystems). Readiness recommends your testing in priority in the following order: RDP and remote access, application installations, PowerShell testing, and then storage system testing. Updates by product family Each month, we break down the update cycle into product families (as defined by Microsoft) with the following basic groupings: Browsers (Microsoft IE and Edge) Microsoft Windows (both desktop and server) Microsoft Office Microsoft Exchange and SQL Server Microsoft Developer Tools (Visual Studio and .NET) Adobe (if you get this far) Browsers Microsoft has not released any native updates for its browsers this month. However, there were five Chromium updates (CVE-2025-4050, CVE-2025-4372, CVE-2025-4096, CVE-2025-4052, and CVE-2025-405) that will update Microsoft Edge. All of these low-profile changes can be added to your standard release calendar. Microsoft Windows Microsoft has released three critical updates, plus 41 patches rated as important. The critical updates affect Microsoft’s Remote Desktop platform and the Virtual Machine bus (VMBus). Unfortunately, the following Windows desktop updates have been reported as exploited in the wild: CVE-2025-30400 CVE-2025-32701 CVE-2025-32706 CVE-2025-32709 CVE-2025-30397 As a result of these zero-days, the Readiness team recommends a “Patch Now” schedule for these Windows patches. Microsoft Office Microsoft has released two critical rated updates (CVE-2025-30377 and CVE-2025-30386) for the Microsoft Office platform this month. Both of these patches were updated mid-week for documentation reasons. Following these critical patches, Microsoft has released a further 16 patches that have been rated as important; they update Microsoft Office in general (as opposed to Word or Excel). Please add these Microsoft Office updates to your standard release calendar. Microsoft Exchange Server No updates for Microsoft Exchange or Microsoft SQL server this month. Good news for all the server teams. Microsoft development platforms A single critical update (CVE-2025-29813) to the Microsoft DevOps platform and four patches rated as important by Microsoft have been released to the developer platforms this month. All of the patches rated as important affect Visual Studio and Microsoft .NET. Add these updates to your standard release schedule. Adobe Reader (if you get this far) No Adobe updates (published by Microsoft) for this May patch cycle. Given the recent security advances implemented in Windows 11 23H2 and 24H2, I think that we will see much less of Adobe in this column.

·398 Vue

Connectez-vous pour aimer, partager et commenter!
NeowinFeed partage un lien

2025-05-15 17:59:59 ·

Windows 11 KB5058502 is out with a new Copilot shortcut, Push to Talk, and more

When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works.

Windows 11 KB5058502 is out with a new Copilot shortcut, Push to Talk, and more

Taras Buria

Neowin
@TarasBuria ·

May 15, 2025 13:45 EDT

Microsoft is rolling out a new Windows 11 23H2 Release Preview build for Windows Insiders. KB5058502 with build number 22631.5409 is now available with the ability to remap the Copilot key and the Win + C shortcut. There is also Push to Talk to Copilot, a new FAQ section in the Settings, and other changes.
Here is the changelog:

Gradual rollout
The following features and improvements might not be available to all users because they will roll out gradually. Text bolded in brackets indicate the area of the change being documented.New! You can open Copilot on Windows with Win + C. You can personalize your Copilot key and Win + C experience at any time with the existing “Customize Copilot key on keyboard” under Settings > Personalization > Text input. For Enterprise users, see Updated Windows and Microsoft 365 Coplot Chat experience.

New! To open the Press to talk with Copilot on Windows, hold the Copilot key or Win + C for two seconds if you don’t have a Copilot key. Press Esc or stay silent for a few seconds to end the call. You can also use Alt + Spacebar to talk with Copilot on Windows. This feature enables you to interact with Copilot using your voice, providing instant responses while you continue your tasks.Improved support for web search providers in Windows Search for the EEA, including with increased discoverability.New! Find answers to commonly asked questions about your PC and Windows 11 in the new FAQs section on the Settings > System > About. It covers topics like system setup, performance, and compatibility – all in one place.

Taskbar] New! Admins can configure taskbar policies so users can unpin specific apps, ensuring they are not repinned during the next policy refresh. To turn on this feature, use the new PinGeneration option.Fixed: Voice access may freeze with error “working on it” when dictating.New! There are some new updates to the new Widgets on Lock experience for devices in the European Economic Area. In addition to accessibility and craftsmanship improvements, the Lock screen weather widget now supports customization. To configure your weather widget, go to Settings > Personalization> Lock screen and select the “Customize widget” option from the weather widget more options menu. More widgets will be customizable in the future.New! Make last-minute edits such as cropping, rotating, and adding filters to images shared through the Windows Share window.
New! When you drag a local file from File Explorer or your desktop, a tray appears at the top of your screen. Drop the file into a suggested app or select More… to open the Windows share window.Fixed: Voice typing won’t start from the touch keyboard when using the Chinesenarrow layout.
Fixed: When using the Symbols section of the touch keyboard, pressing the key to change pages may unexpectedly insert a character into password fields.

Normal rollout

This update includes the following features and improvements that are rolling out as part of this update. Text bolded in brackets indicates the area of the change being documented.Fixed: This update addresses an issue where devices encounter a blue screen error in Windows.Fixed: An issue that stopped the HoloCamera app from saving pictures on HoloLens due to incorrect folder access and a related problem with Mixed Reality Capture.Fixed: This update addresses an issue in the Input Service that causes increased memory usage, potentially impacting performance in multi-user, multi-lingual, and remote desktop usage.Fixed: This update brings profiles up to date for certain mobile operators.Fixed: This update addresses an issue when Explorer and the Start Menu stop working when a device is connected to an AAD account.Fixed: The Windows Update service stopped working when devices running Windows 11 22H2 or 23H2 tried to download the Windows 24H2 feature update through Windows Server Update Services.

You can find the official announcement here.

Tags

Report a problem with article

Follow @NeowinFeed
#windows #kb5058502 #out #with #new

Windows 11 KB5058502 is out with a new Copilot shortcut, Push to Talk, and more
When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works. Windows 11 KB5058502 is out with a new Copilot shortcut, Push to Talk, and more Taras Buria Neowin @TarasBuria · May 15, 2025 13:45 EDT Microsoft is rolling out a new Windows 11 23H2 Release Preview build for Windows Insiders. KB5058502 with build number 22631.5409 is now available with the ability to remap the Copilot key and the Win + C shortcut. There is also Push to Talk to Copilot, a new FAQ section in the Settings, and other changes. Here is the changelog: Gradual rollout The following features and improvements might not be available to all users because they will roll out gradually. Text bolded in brackets indicate the area of the change being documented.New! You can open Copilot on Windows with Win + C. You can personalize your Copilot key and Win + C experience at any time with the existing “Customize Copilot key on keyboard” under Settings > Personalization > Text input. For Enterprise users, see Updated Windows and Microsoft 365 Coplot Chat experience. New! To open the Press to talk with Copilot on Windows, hold the Copilot key or Win + C for two seconds if you don’t have a Copilot key. Press Esc or stay silent for a few seconds to end the call. You can also use Alt + Spacebar to talk with Copilot on Windows. This feature enables you to interact with Copilot using your voice, providing instant responses while you continue your tasks.Improved support for web search providers in Windows Search for the EEA, including with increased discoverability.New! Find answers to commonly asked questions about your PC and Windows 11 in the new FAQs section on the Settings > System > About. It covers topics like system setup, performance, and compatibility – all in one place. Taskbar] New! Admins can configure taskbar policies so users can unpin specific apps, ensuring they are not repinned during the next policy refresh. To turn on this feature, use the new PinGeneration option.Fixed: Voice access may freeze with error “working on it” when dictating.New! There are some new updates to the new Widgets on Lock experience for devices in the European Economic Area. In addition to accessibility and craftsmanship improvements, the Lock screen weather widget now supports customization. To configure your weather widget, go to Settings > Personalization> Lock screen and select the “Customize widget” option from the weather widget more options menu. More widgets will be customizable in the future.New! Make last-minute edits such as cropping, rotating, and adding filters to images shared through the Windows Share window. New! When you drag a local file from File Explorer or your desktop, a tray appears at the top of your screen. Drop the file into a suggested app or select More… to open the Windows share window.Fixed: Voice typing won’t start from the touch keyboard when using the Chinesenarrow layout. Fixed: When using the Symbols section of the touch keyboard, pressing the key to change pages may unexpectedly insert a character into password fields. Normal rollout This update includes the following features and improvements that are rolling out as part of this update. Text bolded in brackets indicates the area of the change being documented.Fixed: This update addresses an issue where devices encounter a blue screen error in Windows.Fixed: An issue that stopped the HoloCamera app from saving pictures on HoloLens due to incorrect folder access and a related problem with Mixed Reality Capture.Fixed: This update addresses an issue in the Input Service that causes increased memory usage, potentially impacting performance in multi-user, multi-lingual, and remote desktop usage.Fixed: This update brings profiles up to date for certain mobile operators.Fixed: This update addresses an issue when Explorer and the Start Menu stop working when a device is connected to an AAD account.Fixed: The Windows Update service stopped working when devices running Windows 11 22H2 or 23H2 tried to download the Windows 24H2 feature update through Windows Server Update Services. You can find the official announcement here. Tags Report a problem with article Follow @NeowinFeed #windows #kb5058502 #out #with #new

WWW.NEOWIN.NET

Windows 11 KB5058502 is out with a new Copilot shortcut, Push to Talk, and more

When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works. Windows 11 KB5058502 is out with a new Copilot shortcut, Push to Talk, and more Taras Buria Neowin @TarasBuria · May 15, 2025 13:45 EDT Microsoft is rolling out a new Windows 11 23H2 Release Preview build for Windows Insiders. KB5058502 with build number 22631.5409 is now available with the ability to remap the Copilot key and the Win + C shortcut. There is also Push to Talk to Copilot, a new FAQ section in the Settings, and other changes. Here is the changelog: Gradual rollout The following features and improvements might not be available to all users because they will roll out gradually. Text bolded in brackets indicate the area of the change being documented. [Copilot] New! You can open Copilot on Windows with Win + C. You can personalize your Copilot key and Win + C experience at any time with the existing “Customize Copilot key on keyboard” under Settings > Personalization > Text input. For Enterprise users, see Updated Windows and Microsoft 365 Coplot Chat experience. New! To open the Press to talk with Copilot on Windows, hold the Copilot key or Win + C for two seconds if you don’t have a Copilot key. Press Esc or stay silent for a few seconds to end the call. You can also use Alt + Spacebar to talk with Copilot on Windows. This feature enables you to interact with Copilot using your voice, providing instant responses while you continue your tasks. [Search on Taskbar] Improved support for web search providers in Windows Search for the EEA, including with increased discoverability. [Settings] New! Find answers to commonly asked questions about your PC and Windows 11 in the new FAQs section on the Settings > System > About. It covers topics like system setup, performance, and compatibility – all in one place. Taskbar] New! Admins can configure taskbar policies so users can unpin specific apps, ensuring they are not repinned during the next policy refresh. To turn on this feature, use the new PinGeneration option. [Voice access] Fixed: Voice access may freeze with error “working on it” when dictating. [Widgets] New! There are some new updates to the new Widgets on Lock experience for devices in the European Economic Area (EEA). In addition to accessibility and craftsmanship improvements, the Lock screen weather widget now supports customization. To configure your weather widget, go to Settings > Personalization> Lock screen and select the “Customize widget” option from the weather widget more options menu. More widgets will be customizable in the future. [Windows Share] New! Make last-minute edits such as cropping, rotating, and adding filters to images shared through the Windows Share window. New! When you drag a local file from File Explorer or your desktop, a tray appears at the top of your screen. Drop the file into a suggested app or select More… to open the Windows share window. [Input] Fixed: Voice typing won’t start from the touch keyboard when using the Chinese (Simplified) narrow layout. Fixed: When using the Symbols section of the touch keyboard, pressing the key to change pages may unexpectedly insert a character into password fields. Normal rollout This update includes the following features and improvements that are rolling out as part of this update. Text bolded in brackets indicates the area of the change being documented. [Blue screen error] Fixed: This update addresses an issue where devices encounter a blue screen error in Windows. [HoloLens] Fixed: An issue that stopped the HoloCamera app from saving pictures on HoloLens due to incorrect folder access and a related problem with Mixed Reality Capture. [Memory leak] Fixed: This update addresses an issue in the Input Service that causes increased memory usage, potentially impacting performance in multi-user, multi-lingual, and remote desktop usage. [Country and Operator Settings Asset (COSA)] Fixed: This update brings profiles up to date for certain mobile operators. [Windows Shell] Fixed: This update addresses an issue when Explorer and the Start Menu stop working when a device is connected to an AAD account. [Windows Update & Servicing] Fixed: The Windows Update service stopped working when devices running Windows 11 22H2 or 23H2 tried to download the Windows 24H2 feature update through Windows Server Update Services (WSUS). You can find the official announcement here. Tags Report a problem with article Follow @NeowinFeed

·252 Vue

Connectez-vous pour aimer, partager et commenter!

Nous rejoindre

Langues

AMD RX 9070 AI performance benchmark review vs 9070 XT, 7800 XT, Nvidia RTX 5070, 4070

Signal to Windows Recall: Drop dead

ExplorerPatcher fix bypasses Windows 11 24H2 upgrade block, and squashes two major bugs

Microsoft's official support proves useless as Windows 11 KB5058411 installs fail

Nvidia driver enables RTX 5000 GPU support on Intel Core 2 CPUs &amp;ndash; with a catch

Windows 11’s May update brings a smorgasbord of new features

May’s Patch Tuesday serves up 78 updates, including 5 zero-day fixes

Windows 11 KB5058502 is out with a new Copilot shortcut, Push to Talk, and more

Nvidia driver enables RTX 5000 GPU support on Intel Core 2 CPUs – with a catch