A new leak for Pokemon Legends: Z-A has apparently happened, with images showing showing brand new Mega Evolutions.
We’ll be posting both shots after the break. Keep that in mind before proceeding.
First up, here’s an apparent look at Mega Meganium:
Also shown of Mega Zygarde:
Neither screenshot has been officially confirmed as legitimate just yet. However, both are said to be tied to Ballguy, who has been discussed within the Pokemon community when it comes to previous leaks.
This isn’t the first time we’ve been hearing about leaks for Pokemon Legends: Z-A. Earlier in the year, a list came online that claimed to outline all Mega Evolutions for the game. That was followed up by descriptions that gave plenty of additional information about these forms.
Mega Victreebel was just officially announced for the title this week. We know that Mega Dragonite will be appearing as well.
Pokemon Legends: Z-A will launch for both Nintendo Switch 2 and Switch on October 16, 2025.
Microsoft has confirmed that the August 2025 security updates are causing severe lag and stuttering issues with NDI streaming software on some Windows 10 and Windows 11 systems.
“Severe stuttering, lag, and choppy audio/video might occur when using NDI (Network Device Interface) for streaming or transferring audio/video feeds between PCs after installing the August 2025 Windows security update,” the company said in a new Windows release health update.
“The issue affects streaming apps, including OBS (Open Broadcast Software) and NDI Tools, especially when ‘Display Capture’ is enabled on the source PC. The problem persists even under low bandwidth conditions.”
These streaming issues are triggered after installing the KB5063878 and KB5063709 security updates on Windows 11 24H2 users and Windows 10 21H2/22H2 devices, respectively.
The NDI team has also confirmed this issue, stating that the buggy Windows updates cause NDI traffic to drop unexpectedly after deployment, with performance problems occurring “only with RUDP connections, while traffic sent or received using UDP or Single-TCP remains unaffected.”
NDI also provided impacted customers with a temporary workaround while Microsoft is investigating the bug causing this known issue, which requires them to change the NDI Receive Mode to use TCP or UDP instead of RUDP.
To do that, you will have to go through the following steps:
Go to the Advanced tab and change Receive Mode to Single TCP or UDP, then press OK.
Repeat on any other affected computers.
After this month’s Patch Tuesday, Microsoft has acknowledged other issues caused by the KB5063878 and KB5063709 security updates.
Just days after releasing the August cumulative updates, the company fixed a known issue that caused the security updates delivered via Windows Server Update Services (WSUS) to fail with 0x80240069 errors after installing the KB5063878 update.
One week later, it released emergency Windows updates to resolve another known issue that broke Windows reset and recovery operations after installing the KB5063875 (Windows 11), KB5063709 (Windows 10), and KB5063877 (Windows 10 Enterprise) updates.
Microsoft has confirmed that the August 2025 security updates are causing severe lag and stuttering issues with NDI streaming software on some Windows 10 and Windows 11 systems.
“Severe stuttering, lag, and choppy audio/video might occur when using NDI (Network Device Interface) for streaming or transferring audio/video feeds between PCs after installing the August 2025 Windows security update,” the company said in a new Windows release health update.
“The issue affects streaming apps, including OBS (Open Broadcast Software) and NDI Tools, especially when ‘Display Capture’ is enabled on the source PC. The problem persists even under low bandwidth conditions.”
These streaming issues are triggered after installing the KB5063878 and KB5063709 security updates on Windows 11 24H2 users and Windows 10 21H2/22H2 devices, respectively.
The NDI team has also confirmed this issue, stating that the buggy Windows updates cause NDI traffic to drop unexpectedly after deployment, with performance problems occurring “only with RUDP connections, while traffic sent or received using UDP or Single-TCP remains unaffected.”
NDI also provided impacted customers with a temporary workaround while Microsoft is investigating the bug causing this known issue, which requires them to change the NDI Receive Mode to use TCP or UDP instead of RUDP.
To do that, you will have to go through the following steps:
Go to the Advanced tab and change Receive Mode to Single TCP or UDP, then press OK.
Repeat on any other affected computers.
After this month’s Patch Tuesday, Microsoft has acknowledged other issues caused by the KB5063878 and KB5063709 security updates.
Just days after releasing the August cumulative updates, the company fixed a known issue that caused the security updates delivered via Windows Server Update Services (WSUS) to fail with 0x80240069 errors after installing the KB5063878 update.
One week later, it released emergency Windows updates to resolve another known issue that broke Windows reset and recovery operations after installing the KB5063875 (Windows 11), KB5063709 (Windows 10), and KB5063877 (Windows 10 Enterprise) updates.
Microsoft has confirmed that the August 2025 security updates are causing severe lag and stuttering issues with NDI streaming software on some Windows 10 and Windows 11 systems.
“Severe stuttering, lag, and choppy audio/video might occur when using NDI (Network Device Interface) for streaming or transferring audio/video feeds between PCs after installing the August 2025 Windows security update,” the company said in a new Windows release health update.
“The issue affects streaming apps, including OBS (Open Broadcast Software) and NDI Tools, especially when ‘Display Capture’ is enabled on the source PC. The problem persists even under low bandwidth conditions.”
These streaming issues are triggered after installing the KB5063878 and KB5063709 security updates on Windows 11 24H2 users and Windows 10 21H2/22H2 devices, respectively.
The NDI team has also confirmed this issue, stating that the buggy Windows updates cause NDI traffic to drop unexpectedly after deployment, with performance problems occurring “only with RUDP connections, while traffic sent or received using UDP or Single-TCP remains unaffected.”
NDI also provided impacted customers with a temporary workaround while Microsoft is investigating the bug causing this known issue, which requires them to change the NDI Receive Mode to use TCP or UDP instead of RUDP.
To do that, you will have to go through the following steps:
Go to the Advanced tab and change Receive Mode to Single TCP or UDP, then press OK.
Repeat on any other affected computers.
After this month’s Patch Tuesday, Microsoft has acknowledged other issues caused by the KB5063878 and KB5063709 security updates.
Just days after releasing the August cumulative updates, the company fixed a known issue that caused the security updates delivered via Windows Server Update Services (WSUS) to fail with 0x80240069 errors after installing the KB5063878 update.
One week later, it released emergency Windows updates to resolve another known issue that broke Windows reset and recovery operations after installing the KB5063875 (Windows 11), KB5063709 (Windows 10), and KB5063877 (Windows 10 Enterprise) updates.
Microsoft has confirmed that the August 2025 security updates are causing severe lag and stuttering issues with NDI streaming software on some Windows 10 and Windows 11 systems.
“Severe stuttering, lag, and choppy audio/video might occur when using NDI (Network Device Interface) for streaming or transferring audio/video feeds between PCs after installing the August 2025 Windows security update,” the company said in a new Windows release health update.
“The issue affects streaming apps, including OBS (Open Broadcast Software) and NDI Tools, especially when ‘Display Capture’ is enabled on the source PC. The problem persists even under low bandwidth conditions.”
These streaming issues are triggered after installing the KB5063878 and KB5063709 security updates on Windows 11 24H2 users and Windows 10 21H2/22H2 devices, respectively.
The NDI team has also confirmed this issue, stating that the buggy Windows updates cause NDI traffic to drop unexpectedly after deployment, with performance problems occurring “only with RUDP connections, while traffic sent or received using UDP or Single-TCP remains unaffected.”
NDI also provided impacted customers with a temporary workaround while Microsoft is investigating the bug causing this known issue, which requires them to change the NDI Receive Mode to use TCP or UDP instead of RUDP.
To do that, you will have to go through the following steps:
Go to the Advanced tab and change Receive Mode to Single TCP or UDP, then press OK.
Repeat on any other affected computers.
After this month’s Patch Tuesday, Microsoft has acknowledged other issues caused by the KB5063878 and KB5063709 security updates.
Just days after releasing the August cumulative updates, the company fixed a known issue that caused the security updates delivered via Windows Server Update Services (WSUS) to fail with 0x80240069 errors after installing the KB5063878 update.
One week later, it released emergency Windows updates to resolve another known issue that broke Windows reset and recovery operations after installing the KB5063875 (Windows 11), KB5063709 (Windows 10), and KB5063877 (Windows 10 Enterprise) updates.
Microsoft has confirmed that the August 2025 security updates are causing severe lag and stuttering issues with NDI streaming software on some Windows 10 and Windows 11 systems.
“Severe stuttering, lag, and choppy audio/video might occur when using NDI (Network Device Interface) for streaming or transferring audio/video feeds between PCs after installing the August 2025 Windows security update,” the company said in a new Windows release health update.
“The issue affects streaming apps, including OBS (Open Broadcast Software) and NDI Tools, especially when ‘Display Capture’ is enabled on the source PC. The problem persists even under low bandwidth conditions.”
These streaming issues are triggered after installing the KB5063878 and KB5063709 security updates on Windows 11 24H2 users and Windows 10 21H2/22H2 devices, respectively.
The NDI team has also confirmed this issue, stating that the buggy Windows updates cause NDI traffic to drop unexpectedly after deployment, with performance problems occurring “only with RUDP connections, while traffic sent or received using UDP or Single-TCP remains unaffected.”
NDI also provided impacted customers with a temporary workaround while Microsoft is investigating the bug causing this known issue, which requires them to change the NDI Receive Mode to use TCP or UDP instead of RUDP.
To do that, you will have to go through the following steps:
Go to the Advanced tab and change Receive Mode to Single TCP or UDP, then press OK.
Repeat on any other affected computers.
After this month’s Patch Tuesday, Microsoft has acknowledged other issues caused by the KB5063878 and KB5063709 security updates.
Just days after releasing the August cumulative updates, the company fixed a known issue that caused the security updates delivered via Windows Server Update Services (WSUS) to fail with 0x80240069 errors after installing the KB5063878 update.
One week later, it released emergency Windows updates to resolve another known issue that broke Windows reset and recovery operations after installing the KB5063875 (Windows 11), KB5063709 (Windows 10), and KB5063877 (Windows 10 Enterprise) updates.
Microsoft has confirmed that the August 2025 security updates are causing severe lag and stuttering issues with NDI streaming software on some Windows 10 and Windows 11 systems.
“Severe stuttering, lag, and choppy audio/video might occur when using NDI (Network Device Interface) for streaming or transferring audio/video feeds between PCs after installing the August 2025 Windows security update,” the company said in a new Windows release health update.
“The issue affects streaming apps, including OBS (Open Broadcast Software) and NDI Tools, especially when ‘Display Capture’ is enabled on the source PC. The problem persists even under low bandwidth conditions.”
These streaming issues are triggered after installing the KB5063878 and KB5063709 security updates on Windows 11 24H2 users and Windows 10 21H2/22H2 devices, respectively.
The NDI team has also confirmed this issue, stating that the buggy Windows updates cause NDI traffic to drop unexpectedly after deployment, with performance problems occurring “only with RUDP connections, while traffic sent or received using UDP or Single-TCP remains unaffected.”
NDI also provided impacted customers with a temporary workaround while Microsoft is investigating the bug causing this known issue, which requires them to change the NDI Receive Mode to use TCP or UDP instead of RUDP.
To do that, you will have to go through the following steps:
Go to the Advanced tab and change Receive Mode to Single TCP or UDP, then press OK.
Repeat on any other affected computers.
After this month’s Patch Tuesday, Microsoft has acknowledged other issues caused by the KB5063878 and KB5063709 security updates.
Just days after releasing the August cumulative updates, the company fixed a known issue that caused the security updates delivered via Windows Server Update Services (WSUS) to fail with 0x80240069 errors after installing the KB5063878 update.
One week later, it released emergency Windows updates to resolve another known issue that broke Windows reset and recovery operations after installing the KB5063875 (Windows 11), KB5063709 (Windows 10), and KB5063877 (Windows 10 Enterprise) updates.
Microsoft has confirmed that the August 2025 security updates are causing severe lag and stuttering issues with NDI streaming software on some Windows 10 and Windows 11 systems.
“Severe stuttering, lag, and choppy audio/video might occur when using NDI (Network Device Interface) for streaming or transferring audio/video feeds between PCs after installing the August 2025 Windows security update,” the company said in a new Windows release health update.
“The issue affects streaming apps, including OBS (Open Broadcast Software) and NDI Tools, especially when ‘Display Capture’ is enabled on the source PC. The problem persists even under low bandwidth conditions.”
These streaming issues are triggered after installing the KB5063878 and KB5063709 security updates on Windows 11 24H2 users and Windows 10 21H2/22H2 devices, respectively.
The NDI team has also confirmed this issue, stating that the buggy Windows updates cause NDI traffic to drop unexpectedly after deployment, with performance problems occurring “only with RUDP connections, while traffic sent or received using UDP or Single-TCP remains unaffected.”
NDI also provided impacted customers with a temporary workaround while Microsoft is investigating the bug causing this known issue, which requires them to change the NDI Receive Mode to use TCP or UDP instead of RUDP.
To do that, you will have to go through the following steps:
Go to the Advanced tab and change Receive Mode to Single TCP or UDP, then press OK.
Repeat on any other affected computers.
After this month’s Patch Tuesday, Microsoft has acknowledged other issues caused by the KB5063878 and KB5063709 security updates.
Just days after releasing the August cumulative updates, the company fixed a known issue that caused the security updates delivered via Windows Server Update Services (WSUS) to fail with 0x80240069 errors after installing the KB5063878 update.
One week later, it released emergency Windows updates to resolve another known issue that broke Windows reset and recovery operations after installing the KB5063875 (Windows 11), KB5063709 (Windows 10), and KB5063877 (Windows 10 Enterprise) updates.
Microsoft has confirmed that the August 2025 security updates are causing severe lag and stuttering issues with NDI streaming software on some Windows 10 and Windows 11 systems.
“Severe stuttering, lag, and choppy audio/video might occur when using NDI (Network Device Interface) for streaming or transferring audio/video feeds between PCs after installing the August 2025 Windows security update,” the company said in a new Windows release health update.
“The issue affects streaming apps, including OBS (Open Broadcast Software) and NDI Tools, especially when ‘Display Capture’ is enabled on the source PC. The problem persists even under low bandwidth conditions.”
These streaming issues are triggered after installing the KB5063878 and KB5063709 security updates on Windows 11 24H2 users and Windows 10 21H2/22H2 devices, respectively.
The NDI team has also confirmed this issue, stating that the buggy Windows updates cause NDI traffic to drop unexpectedly after deployment, with performance problems occurring “only with RUDP connections, while traffic sent or received using UDP or Single-TCP remains unaffected.”
NDI also provided impacted customers with a temporary workaround while Microsoft is investigating the bug causing this known issue, which requires them to change the NDI Receive Mode to use TCP or UDP instead of RUDP.
To do that, you will have to go through the following steps:
Go to the Advanced tab and change Receive Mode to Single TCP or UDP, then press OK.
Repeat on any other affected computers.
After this month’s Patch Tuesday, Microsoft has acknowledged other issues caused by the KB5063878 and KB5063709 security updates.
Just days after releasing the August cumulative updates, the company fixed a known issue that caused the security updates delivered via Windows Server Update Services (WSUS) to fail with 0x80240069 errors after installing the KB5063878 update.
One week later, it released emergency Windows updates to resolve another known issue that broke Windows reset and recovery operations after installing the KB5063875 (Windows 11), KB5063709 (Windows 10), and KB5063877 (Windows 10 Enterprise) updates.
Apple is urging users to immediately update their devices to patch a zero-click vulnerability that allowed attackers to compromise iPhones, iPads and Macs, a flaw posing heightened risks for cryptocurrency holders.
In a Thursday advisory, Apple said the image processing vulnerability allowed sophisticated actors to compromise Apple devices. The vulnerability disclosure page notes that it was fixed as part of the macOS Sonoma 14.7.8, macOS Ventura 13.7.8, iPadOS 17.7.10, macOS Sequoia 15.6.1, iOS 18.6.2 and iPadOS 18.6.2 updates.
“Apple is aware of a report that this issue may have been exploited in an extremely sophisticated attack against specific targeted individuals,” the company said.
Cybersecurity experts warned the flaw is particularly dangerous for those in crypto, since they are significantly more exposed to cyberattacks. Access to crypto-integrated systems can lead to financial gains through irreversible transactions for attackers, resulting in highly motivated actors targeting this category.
Juliano Rizzo, founder and CEO at cybersecurity firm Coinspect, told Cointelegraph that this is a zero-click vulnerability that does not require user interaction and “an attachment delivered via iMessage can be processed automatically and lead to device compromise.” Attackers could potentially leverage access to the device to reach wallet data.
The vulnerability affects Apple’s Image I/O framework, which allows applications to read and write most image file formats. Due to improper implementation, processing a malicious image allows for out-of-bounds memory write access.
In other words, attackers can leverage this vulnerability to write to areas of a device’s memory that should be inaccessible. Such an issue, in the hands of a particularly sophisticated attacker, can compromise device security by allowing attackers to execute code on targeted devices.
A device’s memory holds all the programs currently being executed, including critical ones. Being able to write to memory outside the authorized scope allows attackers to alter how other programs operate and execute their own instructions.
Rizzo advised high-value targets who used vulnerable devices for key storage or signing to migrate to new wallet keys if there is any sign of compromise or “if there’s any evidence of targeting” on the device storing the credentials:
“The exact steps depend on the attack specifics, but the key is to stay calm, document a clear plan, and start by securing primary accounts (email, cloud) that attackers could exploit for password resets or further access. Patching is critical, but waiting for updates to finish should never delay immediate account lockdown.”
For average individuals, Rizzo noted that “checking system logs could in theory show anomalies, but in practice this data is hard to interpret.” He said that vendors like Apple are well-positioned to detect exploitation and contact victims directly.
