Overview of the playback feature
Microsoft delivers the latest Windows security and quality updates monthly. Updates are cumulative. This means that, regardless of which update is currently installed, you only need the most recent quality update to get your machine up to date.
With the fast pace of Windows updates, distributing this large amount of content takes up a lot of bandwidth. Reducing network bandwidth usage is critical for a great experience. Also, users on slower networks can struggle to keep their machines up to date if they cannot download the package.
The cumulative update sizes for Windows 11 are smaller than the same set of updates for Windows 10. How? Through more efficient packaging and removal of reverse differentials from the cumulative update package. The articles below will help you understand the concepts of forward and reverse differentials in the Windows cumulative update. They will also explain how we leveraged differentials to reduce the update sizes for Windows 11.
Now, we aim to bring this feature to Windows Server 2022 in a phased manner to ensure a smooth rollout.
-
Phase 1 (April 11, 2023)
-
What: This release contains changes in the servicing stack. These changes generate the reverse delta on the OS without relying on the reverse delta contained in the cumulative update.
-
Benefit: The servicing stack will generate reverse delta locally. This makes the servicing stack ready for the cumulative updates in phase 2.
-
Fallback:If the reverse delta generation fails, the servicing stack will use the reverse delta contained in the cumulative update.
-
Error tracking: If the reverse delta generation fails, the servicing stack sends a telemetry event with the appropriate error code.
-
-
Phase 2
-
What: The reverse deltas will be completely removed from the cumulative update. The servicing stack (modified in phase 1) will generate the reverse delta on the OS.
-
Benefit: The cumulative update size for Windows Server 2022 will be significantly lower because of the removal of the reverse deltas.
-
Fallback: If playback generation fails, the servicing stack sets the store status as corrupt. When automatic or manual corruption repair starts, the store can be repaired.
-
Error Reporting: The servicing stack sends a telemetry event with an error that indicates that the reverse delta generation failed.
-
Enabling the playback feature in Windows Server 2022 for phase 1
The playback feature will be shipped disabled by default in phase 1. You must explicitly enable it using one of the methods listed below:
-
Using Group Policy installer
-
Running a PowerShell script
Enabling the playback feature using the Group Policy (GP) installer
-
Run the Group Policy installer (.msi). It will install the Group Policy on the machine. Download the .msi
-
Open the Local Group Policy editor.
-
Windows key + R
-
Type gpedit.msc and press the Enter key.
-
-
Go to Computer Configuration > Administrative Templates > KB5025314 230324_01001 Feature Preview > Windows Server 2022
-
Open KB5025314 230324_01001 Feature Preview. Select the Enabled option to Enable Playback Feature. Select OK.
-
Restart the machine.
Tip: Multiple options are available at Use Group Policy to deploy a Known Issue Rollback to enable the feature using a GPO.
Enabling the playback feature using a PowerShell (PS) script
You can install the playback feature using a PowerShell script. It takes a config file that contains a list of computers as input. This is useful especially for enabling the feature on multiple computers.
Setup
-
The configuration file should have blank spaces that separate information like <ComputerName> <Username> <Password> per line.
-
If the username and password are omitted from the configuration file, the script will use the username and password you pass as arguments.
-
The restart flag will restart the remote machine after it enables the feature.
-
The disable flag disables the playback feature.
-
Download the script and configuration files.
Feature enablement
-
Open the command prompt in administrator mode.
-
Run the EnablePlaybackFeature.ps1 script as follows:
-
>powershell.exe -NoProfile -ExecutionPolicy Bypass .\EnablePlaybackFeature.ps1 -ConfigFile <FilePath-with-ComputersList> -UserName <Default-UserName> -Password <default-password> [-Restart] [-Disable]
-
For example: C:\Tools>powershell.exe -NoProfile -ExecutionPolicy Bypass .\EnablePlaybackFeature.ps1 -ConfigFile computers.txt -UserName Administrator -Password Test@123 -Restart
-
Preview plan for phase 1
As part of the feature preview, follow the steps listed below.
Install updates using Windows Update Settings
-
Enable the playback feature by following the steps in Enabling the playback feature in Windows Server 2022 for phase 1.
-
Update the machine to the latest version from the Windows Update Settings UI.
-
When prompted, restart the machine.
-
Verify the version of Windows by running the winver command at the Windows command prompt.
-
Once the update completes and the machine restarts, share the logs. To do that, run the script mentioned in Steps to collect logs.
-
Please report any discrepancies observed to Microsoft.
Install the cumulative update from the Microsoft Update Catalog
-
Enable the playback feature by following the steps in Enabling the playback feature in Windows Server 2022 for phase 1.
-
Download the monthly cumulative update packages from Microsoft Update Catalog.
-
Open the link in a web browser Microsoft Update Catalog.
-
Search for the package using its KB number KB5025230.
-
Download the cumulative package (.msu) that is suitable for your machine.
-
-
Install the cumulative update by double clicking the downloaded .msu package.
-
When prompted, restart the machine.
-
Verify the version of Windows by running the winver command at the Windows command prompt.
-
Once the update completes and the machine restarts, share the logs. To do that, run the script mentioned in Steps to collect logs.
Steps to collect logs
-
Open a web browser and go to https://aka.ms/wucopylogsexternal.
-
Download and run copylogs.exe. This downloads the log collector tool that applies to your machine.
-
The tool will gather logs and create a .zip file in %localappdata%\Temp\WU_logs (for example, C:\Users\<Username>\AppData\Local\Temp\WU_logs).
-
Go to the .zip file and attach it to the support case.
-
You can also contact support by sending an email to wufbhotservice@microsoft.com.
Tip: If you encounter an issue that needs investigation, file a Feedback Hub item from the affected device with [Playback] in the title. Choose the Install and Update > Downloading, installing, and configuring Windows Update category. mailto:wufbhotservice@microsoft.com