"There is not enough space on the disk" as script writes directly to recovery partition

[encip]

I get stuck here... it's trying to write directly to the recovery partition and it runs out of space.

02/17/2023 13:24:44 - Target file version: 10.0.19041.2251
02/17/2023 13:24:44 - Windows 10, version 2004
02/17/2023 13:24:44 - Windows 10, version 2004 with revision 2251 >= 2247, updates have been applied
02/17/2023 13:24:44 - After patch, find expected version for target file
02/17/2023 13:24:44 - Patch succeed, unmount to commit change

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Saving image
[===============            27.0%                          ]

Error: 112

There is not enough space on the disk.

The DISM log file can be found at C:\windows\Logs\DISM\dism.log
02/17/2023 13:25:14 - Unmount failed: 112

I do believe the partition is big enough (600MB) for the new winre.wim after an "Export-Image" procedure (should be about 450MB)... is there a way to have the script first save the image locally then copy to the Recovery partition?

[takondo]

Hi, can you share which package you are using to update WinRE? Please try using the Safe OS Dynamic Update if you have not done so already (e.g. KB5021043 for Windows 10, versions 20H2 and newer)

[Johnster001]

The information page for KB5021043 makes no mention of it being a fix for this issue, it just says it's a compatibility update and nothing further. Is it officially a patch for CVE-2022-41099?

[takondo]

Yes. The "Windows Safe OS Dynamic Updates" are patches that have been minimized for WinRE deployment.