Windows 11 Insider Preview Build 22449

 Announcing Windows 11 Insider Preview Build 22449 

UPDATE 7:10PM PDT: Recently, Windows Insiders in both the Dev and Beta Channels began reporting that Start and Taskbar were unresponsive and Settings and other areas of the OS wouldn’t load. We quickly discovered an issue with a server-side deployment that went out to Insiders and canceled that deployment. If you were impacted by this issue, you can use the following steps to get back into a working state on your PC.

• Step 1: Use CTRL-ALT-DEL and choose to open Task Manager.
• Step 2: Choose “More details” at the bottom of Task Manager to expand Task Manager.
• Step 3: Go to “File” and choose “Run new task”.
• Step 4: Type “cmd” in the “Open” field.
• Step 5: Paste the following (everything in bold):
  reg delete HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\IrisService /f && shutdown -r -t 0
• Step 6: Hit enter, and then your PC should reboot. After rebooting, everything should be back to normal.

What’s new in Build 22449

SMB compression behavior change

We first introduced SMB compression in Windows Server 2022 & Windows 11. SMB compression allows an administrator, user, or application to request compression of files as they transfer over the network. This removes the need to first deflate a file manually with an application, copy it, then inflate on the destination PC. Compressed files will consume less network bandwidth and take less time to transfer, at the cost of slightly increased CPU usage during transfers.

Based on testing and analysis, we have changed the default behavior of compression. Previously, the SMB compression decision algorithm would attempt to compress the first 524,288,000 bytes (500MiB) of a file during transfer and track that at least 104,857,600 bytes (100MiB) compressed within that 500-MB range. If fewer than 100 MiB were compressible, SMB compression stopped trying to compress the rest of the file. If at least 100 MiB compressed, SMB compression attempted to compress the rest of the file. This meant that very large files with compressible data – for instance, a multi-gigabyte virtual machine disk – were likely to compress but a relatively small file – even a very compressible one – would not compress.