Windows 11 KB5094126 keeps failing

[RZman]

there is no Memory.dmp

 

[ChatGPT]

Ron, understood. If both are missing:

C:\Windows\Minidump
C:\Windows\MEMORY.DMP

then Windows did not save crash dump data from that blue screen. That is frustrating, but not unusual when the crash happens during a repair/update rollback.
At this point, I would not retry KB5094126 and not run Fix Problems with Windows Update again until we get another clue.

First: pause updates again​

If Windows is back on the desktop:

1. Open Settings.
2. Go to Windows Update.
3. Click Pause updates.
4. Choose 1 week or longer.

This is just to stop Windows from immediately trying the same failed repair/update cycle.

Next: get crash details from Reliability Monitor​

Since there is no dump file, this is the next best place.

1. Press Windows + R.
2. Type:

perfmon /rel

1. Press Enter.
2. Look for today’s red X.
3. Click anything like Windows stopped working, Windows was not properly shut down, or Hardware error.
4. Click View technical details.
5. Copy/paste the details here.

The important fields are usually:

Problem Event Name
BCCode
Parameter 1
Parameter 2
Parameter 3
Parameter 4
Faulting driver/module, if listed

Also check Event Viewer with one command​

Open Terminal / PowerShell as Administrator and run this:
Get-WinEvent -FilterHashtable @{LogName='System'; Id=1001,41,6008} -MaxEvents 10 | Format-List TimeCreated,Id,ProviderName,Message
Copy/paste the output here.
What we are looking for is a BugCheck 1001 entry. That may show the stop code even without a dump file.

Make sure dumps are enabled for next time​

1. Press Windows + R.
2. Type:

sysdm.cpl

1. Press Enter.
2. Click the Advanced tab.
3. Under Startup and Recovery, click Settings.
4. Set Write debugging information to:

Small memory dump (256 KB)

1. Make sure the folder is:

%SystemRoot%\Minidump

1. Click OK.

Check the page file setting​

1. Press Windows + R.
2. Type:

sysdm.cpl

1. Go to Advanced.
2. Under Performance, click Settings.
3. Go to Advanced.
4. Under Virtual memory, click Change.
5. Make sure this is checked:

Automatically manage paging file size for all drives

1. Restart if Windows asks.

Safe checks to run now​

Run these in Terminal as Administrator:
sfc /scannow
Then:
DISM /Online /Cleanup-Image /RestoreHealth
Then:
chkdsk C: /scan
These are safe checks. They do not wipe your files.

My current recommendation​

For now:

Do not retry KB5094126
Do not retry Fix Problems with Windows Update
Do not join Insider
Do not reset the PC yet
Do not keep deleting update folders

The blue screen changed the situation. We need to find out whether this is a driver, RAM, storage, or Windows servicing issue before doing anything else.
Please post the Reliability Monitor details or the PowerShell Event Viewer output. That should give us the next clue.

 

[RZman]

System had set Kernel Memory Dump , fixed it

 

[ChatGPT]

Ron, good catch. If it was set to Kernel Memory Dump, that explains why there was no small file in:
C:\Windows\Minidump
A kernel dump normally writes to:
C:\Windows\MEMORY.DMP
…but if Windows could not write it during the update rollback, you end up with no dump at all.

Make sure it is set this way now​

Please confirm it is now set to:
Small memory dump (256 KB)
And the dump directory is:
%SystemRoot%\Minidump
That way, if it blue screens again, we should get a small uploadable .dmp file.

Also confirm the page file​

This matters for dump creation.

1. Press Windows + R.
2. Type:

sysdm.cpl

1. Go to Advanced.
2. Under Performance, click Settings.
3. Go to Advanced.
4. Under Virtual memory, click Change.
5. Make sure this is checked:

Automatically manage paging file size for all drives

For now, do not trigger the crash again​

Do not retry these yet:

KB5094126
Fix problems using Windows Update
Manual .msu installers
Reset this PC

Next safe step​

Run these from Terminal as Administrator:
sfc /scannow
Then:
DISM /Online /Cleanup-Image /RestoreHealth
Then:
chkdsk C: /scan
Post the final results from those three.

Also check the crash record​

Run this in PowerShell as Administrator:
Get-WinEvent -FilterHashtable @{LogName='System'; Id=1001,41,6008} -MaxEvents 10 | Format-List TimeCreated,Id,ProviderName,Message
If there is a BugCheck 1001 entry, paste it here.
Bottom line: fixing the dump setting was the right move. Now we need either the Event Viewer bugcheck details or a new minidump if it crashes again — but I would avoid forcing that crash for now.

 

[RZman]

Automatically manage paging file size for all drives It was NOT checked. It is now

 

[ChatGPT]

Ron, that is an important find. That likely explains why no dump file was created.
If Automatically manage paging file size for all drives was unchecked, Windows may not have had the proper page file configuration needed to write a crash dump during the blue screen.

Do this next​

1. Restart the PC​

Because you changed the page file setting, restart once:
Start > Power > Restart
Do not use Shut down.

After restart​

2. Confirm updates are paused​

1. Open Settings.
2. Go to Windows Update.
3. Make sure updates are paused.

This prevents Windows from immediately trying KB5094126 again.

3. Run the safe health checks​

Open Terminal as Administrator and run these one at a time:
sfc /scannow
Then:
DISM /Online /Cleanup-Image /RestoreHealth
Then:
chkdsk C: /scan
Please post the final result from each one.

Why this matters​

You had two dump-related issues:

Crash dump type was set to Kernel Memory Dump
Page file was not automatically managed

That combination can easily result in no Minidump and no MEMORY.DMP, especially during an update rollback crash.
Now that the page file is fixed, if the system blue screens again, Windows has a much better chance of saving a dump here:
C:\Windows\Minidump

Do not retry the update yet​

For now, still avoid:

KB5094126
Fix problems using Windows Update
Manual .msu installers
Reset this PC

Let’s first see whether sfc, DISM, and chkdsk report anything. That will tell us whether the machine is stable enough to attempt another update path later.

 

[RZman]

There is no Red X on 6-25

 

[ChatGPT]

Ron, that screenshot is actually useful.
You’re right: there is no red X for 6/25. Reliability Monitor only shows:

Warnings:
PowerENGAGE — Unsuccessful application reconfiguration
Windows 11, version 25H2 — Failed Windows Update

Information:
Security Intelligence Update — Successful Windows Update

So Reliability Monitor did not record the blue screen as a normal “Windows stopped working” event. That matches what we already saw: no Minidump and no MEMORY.DMP were created because the dump/pagefile settings were not correct at the time.

What I need from that screen​

Please click View technical details for this one:

Windows 11, version 25H2 — Failed Windows Update
06/25/2026 06:23

Then copy/paste what it says.
It may show an update error code or failure phase.

Also click this one​

Click View technical details for:

PowerENGAGE — Unsuccessful application reconfiguration
06/25/2026 05:53

That may be unrelated, but I want to see whether a third-party app/driver was being reconfigured around the same time as the update repair.

Best next command​

Since Reliability Monitor did not show the crash, Event Viewer may still have the bugcheck record.
Open PowerShell as Administrator and run:
Get-WinEvent -FilterHashtable @{LogName='System'; Id=1001,41,6008} -MaxEvents 20 | Format-List TimeCreated,Id,ProviderName,Message
Copy/paste the result here.

For now, still do not retry the update​

Until we see those details, avoid:

KB5094126
Fix problems using Windows Update
Manual .msu files
Reset this PC

The good news is that you fixed the dump settings now. If another blue screen happens, Windows should be much more likely to create:
C:\Windows\Minidump
But I do not want you to intentionally trigger it again yet.

 

[RZman]

 

[RZman]

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Install the latest PowerShell for new features and improvements! Windows PowerShell update message FAQ - PowerShell | Microsoft Learn

PS C:\Users\Ron> sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
PS C:\Users\Ron> DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.26100.5074

Image Version: 10.0.26200.6901

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
PS C:\Users\Ron> chkdsk C: /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
2666240 file records processed.
File verification completed.
Phase duration (File record verification): 8.57 seconds.
41888 large file records processed.
Phase duration (Orphan file record recovery): 11.72 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.12 milliseconds.

Stage 2: Examining file name linkage ...
10877 reparse records processed.
3601108 index entries processed.
Index verification completed.
Phase duration (Index verification): 20.14 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 31.95 seconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.17 milliseconds.
10877 reparse records processed.
Phase duration (Reparse point and Object ID verification): 15.63 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 65.53 milliseconds.
467435 data files processed.
Phase duration (Data attribute verification): 0.26 milliseconds.
CHKDSK is verifying Usn Journal...
39435936 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 57.53 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

974976663 KB total disk space.
240326932 KB in 1328984 files.
1198616 KB in 467436 indexes.
0 KB in bad sectors.
2827387 KB in use by the system.
65536 KB occupied by the log file.
730623728 KB available on disk.

4096 bytes in each allocation unit.
243744165 total allocation units on disk.
182655932 allocation units available on disk.
Total duration: 1.01 minutes (60836 ms).
PS C:\Users\Ron>

 

[ChatGPT]

Ron, that screenshot is the key clue:

Windows 11, version 25H2 (repair version)
Install error - 0xC1900101

That is not a normal Windows Update error anymore. 0xC1900101 is a Windows Setup/repair rollback code and it most commonly points to a driver problem. That also fits perfectly with the blue screen you got:

PAGE_FAULT_IN_NONPAGED_AREA
0x50

So the repair install/update is probably hitting a bad or incompatible driver during the reboot phase, crashing, then rolling back.

Do not click Retry yet​

For now, do not click:

Retry
Retry all
Fix problems using Windows Update

We need to identify the driver/update rollback cause first.

What to do now​

1. Pause updates​

1. Go to Settings > Windows Update.
2. Click Pause updates.
3. Choose Pause for 1 week.

2. Collect the rollback logs​

Please run this in PowerShell as Administrator:

New-Item -ItemType Directory -Force "$env:USERPROFILE\Desktop\RollbackLogs"

Copy-Item -Path 'C:\$Windows.~BT\Sources\Rollback\*' -Destination "$env:USERPROFILE\Desktop\RollbackLogs" -Recurse -Force -ErrorAction SilentlyContinue

Copy-Item -Path 'C:\$Windows.~BT\Sources\Panther\setupact.log' -Destination "$env:USERPROFILE\Desktop\RollbackLogs" -Force -ErrorAction SilentlyContinue

Copy-Item -Path 'C:\$Windows.~BT\Sources\Panther\setuperr.log' -Destination "$env:USERPROFILE\Desktop\RollbackLogs" -Force -ErrorAction SilentlyContinue

Compress-Archive -Path "$env:USERPROFILE\Desktop\RollbackLogs\*" -DestinationPath "$env:USERPROFILE\Desktop\RollbackLogs.zip" -Force

Then upload this file:
Desktop\RollbackLogs.zip
That may show the bad driver or the phase where setup crashed.

3. Also check if setup saved a crash dump there​

Look manually in:
C:\$Windows.~BT\Sources\Rollback
If you see:
setupmem.dmp
zip and upload that too. That file is specifically created when Windows Setup crashes during upgrade/repair rollback.

Likely causes to think about​

Before retrying anything, think about whether you have any of these installed:

Third-party antivirus
VPN software
Drive encryption software
Old printer/scanner drivers
Old storage/NVMe/SATA drivers
RGB/fan control utilities
Backup/imaging software
Virtual machine software
Tuning/cleanup utilities

Any of those can cause 0xC1900101.

My recommendation​

At this point, Ron, the update itself is not the main problem. The system is failing the repair/update setup phase with:
0xC1900101
That usually means driver rollback failure.
Please upload RollbackLogs.zip if it creates successfully. That is the next best evidence now that normal minidumps were missing.

 

[RZman]

I ran the requested items, here are the results.
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Install the latest PowerShell for new features and improvements! Windows PowerShell update message FAQ - PowerShell | Microsoft Learn

PS C:\Users\Ron> sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
PS C:\Users\Ron> DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.26100.5074

Image Version: 10.0.26200.6901

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
PS C:\Users\Ron> chkdsk C: /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
2666240 file records processed.
File verification completed.
Phase duration (File record verification): 8.57 seconds.
41888 large file records processed.
Phase duration (Orphan file record recovery): 11.72 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.12 milliseconds.

Stage 2: Examining file name linkage ...
10877 reparse records processed.
3601108 index entries processed.
Index verification completed.
Phase duration (Index verification): 20.14 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 31.95 seconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.17 milliseconds.
10877 reparse records processed.
Phase duration (Reparse point and Object ID verification): 15.63 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 65.53 milliseconds.
467435 data files processed.
Phase duration (Data attribute verification): 0.26 milliseconds.
CHKDSK is verifying Usn Journal...
39435936 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 57.53 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

974976663 KB total disk space.
240326932 KB in 1328984 files.
1198616 KB in 467436 indexes.
0 KB in bad sectors.
2827387 KB in use by the system.
65536 KB occupied by the log file.
730623728 KB available on disk.

4096 bytes in each allocation unit.
243744165 total allocation units on disk.
182655932 allocation units available on disk.
Total duration: 1.01 minutes (60836 ms).
PS C:\Users\Ron>

 

[ChatGPT]

Ron, those results are actually very good.

SFC: No integrity violations
DISM: Restore operation completed successfully
CHKDSK: Found no problems
Bad sectors: 0 KB

That means your Windows system files and file system look healthy. So this is not looking like basic Windows corruption or disk damage.
The failure is now pointing more strongly at this:
0xC1900101 = driver/firmware/setup rollback problem
That also matches the blue screen you saw:
PAGE_FAULT_IN_NONPAGED_AREA 0x50

What this means​

Your PC is probably failing when Windows Setup/Repair tries to reboot into the update/repair phase and load a driver.
Common causes are:

Antivirus/security software
VPN software
Storage/NVMe/SATA driver
Old chipset driver
Printer/scanner driver
RGB/fan/motherboard utility
Backup/imaging software
Virtual machine software
USB device driver

Do not retry the update yet​

For now, do not click:

Retry
Retry all
Fix problems using Windows Update
KB5094126 manual installer

Your repair/update path is failing with a driver-style rollback, not ordinary corruption.

Next best step: get the rollback logs​

Please run this in PowerShell as Administrator:

New-Item -ItemType Directory -Force "$env:USERPROFILE\Desktop\RollbackLogs"

Copy-Item -Path 'C:\$Windows.~BT\Sources\Rollback\*' -Destination "$env:USERPROFILE\Desktop\RollbackLogs" -Recurse -Force -ErrorAction SilentlyContinue

Copy-Item -Path 'C:\$Windows.~BT\Sources\Panther\setupact.log' -Destination "$env:USERPROFILE\Desktop\RollbackLogs" -Force -ErrorAction SilentlyContinue

Copy-Item -Path 'C:\$Windows.~BT\Sources\Panther\setuperr.log' -Destination "$env:USERPROFILE\Desktop\RollbackLogs" -Force -ErrorAction SilentlyContinue

Compress-Archive -Path "$env:USERPROFILE\Desktop\RollbackLogs\*" -DestinationPath "$env:USERPROFILE\Desktop\RollbackLogs.zip" -Force

Then upload:
RollbackLogs.zip
It should be on your Desktop.

If the zip command says there are no files​

Run this and paste the result:
dir 'C:\$Windows.~BT\Sources\Rollback' -Force

One question before we go further​

Do you have any third-party antivirus, VPN, backup/imaging, or drive encryption software installed?
Examples:

Norton
McAfee
Bitdefender
Avast
AVG
Malwarebytes real-time protection
Acronis
Macrium Reflect
EaseUS
NordVPN
ExpressVPN
Cisco/AnyConnect
VirtualBox
VMware

If yes, that may be the thing blocking the repair/update.

My current recommendation​

You are past the “run SFC/DISM” stage. Those passed.
The next useful evidence is the rollback log, because it may tell us which driver caused:
0xC1900101
Once we see that, we can decide whether to update, disable, or temporarily uninstall that driver/software before trying Windows Update again.

 

[RZman]

ecurse -Force -ErrorAction SilentlyContinue
>>
>> Copy-Item -Path 'C:\$Windows.~BT\Sources\Panther\setupact.log' -Destination "$env:USERPROFILE\Desktop\RollbackLogs" -Force -ErrorAction SilentlyContinue
>>
>> Copy-Item -Path 'C:\$Windows.~BT\Sources\Panther\setuperr.log' -Destination "$env:USERPROFILE\Desktop\RollbackLogs" -Force -ErrorAction SilentlyContinue
>>
>> Compress-Archive -Path "$env:USERPROFILE\Desktop\RollbackLogs\*" -DestinationPath "$env:USERPROFILE\Desktop\RollbackLogs.zip" -Force


Directory: C:\Users\Ron\Desktop


Mode LastWriteTime Length Name
---- ------------- ------ ----
d----- 06/25/2026 10:11 RollbackLogs
Exception calling "Write" with "3" argument(s): "Exception of type 'System.OutOfMemoryException' was thrown."
At
C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\Microsoft.PowerShell.Archive\Microsoft.PowerShell.Archive.psm1:820
char:29
+ ... $destStream.Write($buffer, 0, $numberOfBytesRead)
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: ) [], MethodInvocationException
+ FullyQualifiedErrorId : OutOfMemoryException

 

[ChatGPT]

Ron, no worries — that error is from PowerShell’s built-in zip tool choking on a large file in the rollback folder.
System.OutOfMemoryException
That does not mean your PC is out of RAM. It usually means Compress-Archive hit a large dump/log file and failed.
Also, I do not see a zip attachment yet, so nothing uploaded from that attempt.

Do this instead​

We’ll make a smaller log package and skip huge files.

1. Check what is in the RollbackLogs folder​

Run this in PowerShell:
Get-ChildItem "$env:USERPROFILE\Desktop\RollbackLogs" -Recurse | Sort-Object Length -Descending | Select-Object FullName,Length | Format-Table -AutoSize
If you see something huge like:

setupmem.dmp
memory.dmp
*.evtx

that is probably what broke the zip.

2. Create a small logs-only folder​

Run this:
New-Item -ItemType Directory -Force "$env:USERPROFILE\Desktop\RollbackLogsSmall"
Then run:

Copy-Item "$env:USERPROFILE\Desktop\RollbackLogs\*.log" "$env:USERPROFILE\Desktop\RollbackLogsSmall" -Force -ErrorAction SilentlyContinue
Copy-Item "$env:USERPROFILE\Desktop\RollbackLogs\*.xml" "$env:USERPROFILE\Desktop\RollbackLogsSmall" -Force -ErrorAction SilentlyContinue
Copy-Item "$env:USERPROFILE\Desktop\RollbackLogs\*.txt" "$env:USERPROFILE\Desktop\RollbackLogsSmall" -Force -ErrorAction SilentlyContinue

3. Zip only the small logs​

Run:
Compress-Archive -Path "$env:USERPROFILE\Desktop\RollbackLogsSmall\*" -DestinationPath "$env:USERPROFILE\Desktop\RollbackLogsSmall.zip" -Force
Then upload this file:
C:\Users\Ron\Desktop\RollbackLogsSmall.zip

If that also fails​

Use this command instead:
tar -a -c -f "$env:USERPROFILE\Desktop\RollbackLogsSmall.zip" -C "$env:USERPROFILE\Desktop\RollbackLogsSmall" .

If there is a setupmem.dmp​

If the file list shows this:
setupmem.dmp
tell me the size of it. Do not try to zip it yet if it is large.
That file would be very important because it may contain the crash from the failed repair install, but we’ll handle it separately.

Bottom line​

The zip failed because the rollback folder likely contains one or more large files. We only need the small text logs first:

setupact.log
setuperr.log
setupapi.dev.log
BlueBox.log

Try creating RollbackLogsSmall.zip and upload that one.

 

[RZman]

I don't see these files on my desktop What would they be in?

 

[ChatGPT]

Ron, they would not appear as loose files on the Desktop unless the copy worked. They should be inside a folder named:
RollbackLogs
or, if the smaller command was run:
RollbackLogsSmall
The zip file, if it was created, would be named:

RollbackLogs.zip
RollbackLogsSmall.zip

But since your zip command failed with the memory error, you may only have the folder, not the .zip.

Easiest way to open it​

Press Windows + R, paste this, and press Enter:
%USERPROFILE%\Desktop\RollbackLogs
If that opens, the files are in there.
If it says the folder does not exist, try:
%USERPROFILE%\Desktop\RollbackLogsSmall

If you still do not see it​

Run this in PowerShell:
explorer "$env:USERPROFILE\Desktop"
Then look for a folder named:
RollbackLogs

To show exactly what was created​

Run this and paste the result:
dir "$env:USERPROFILE\Desktop" | findstr Rollback
That will tell us whether the folder or zip exists.

If the folder exists but there are lots of files​

Open:
RollbackLogs
Look mainly for files named:

setupact.log
setuperr.log
setupapi.dev.log
BlueBox.log

Those are the ones we need first. If you see them, you can select just those files, right-click, and choose:
Send to > Compressed zipped folder
Name it:
RollbackLogsSmall.zip
Then upload that zip here.

 

[RZman]

There is nothing on my desktop that begins Rollback

 

[RZman]

I am getting the CRT warning again

 

[ChatGPT]

Ron, understood. That likely means one of two things:
1. You are looking at the OneDrive Desktop, but PowerShell created the folder on the local Desktop, or
2. The copy/zip failed before anything useful was placed there.
Let’s make this simpler and use Downloads instead of Desktop.

Step 1 — Try opening the exact folder PowerShell created​

Press Windows + R, paste this, and press Enter:
C:\Users\Ron\Desktop\RollbackLogs
If it opens, that is the folder.
If Windows says it cannot find it, continue below.

Step 2 — Search for the folder​

Open PowerShell and run:
Get-ChildItem -Path "C:\Users\Ron","C:\Users\Ron\Desktop","C:\Users\Ron\Downloads","$env:OneDrive\Desktop" -Directory -Filter "Rollback*" -ErrorAction SilentlyContinue | Select-Object FullName
If it finds anything, paste the result here.

Step 3 — Easier method: create the log package in Downloads​

Run this in PowerShell as Administrator:

$dest="$env:USERPROFILE\Downloads\WU-RollbackLogs"
New-Item -ItemType Directory -Force $dest

Copy-Item 'C:\$Windows.~BT\Sources\Panther\setupact.log' $dest -Force -ErrorAction SilentlyContinue
Copy-Item 'C:\$Windows.~BT\Sources\Panther\setuperr.log' $dest -Force -ErrorAction SilentlyContinue
Copy-Item 'C:\$Windows.~BT\Sources\Rollback\*.log' $dest -Force -ErrorAction SilentlyContinue
Copy-Item 'C:\$Windows.~BT\Sources\Rollback\*.txt' $dest -Force -ErrorAction SilentlyContinue
Copy-Item 'C:\$Windows.~BT\Sources\Rollback\*.xml' $dest -Force -ErrorAction SilentlyContinue

Get-ChildItem $dest

That last line should show what files were copied.

Step 4 — Zip that folder​

If files appear, run:
Compress-Archive -Path "$env:USERPROFILE\Downloads\WU-RollbackLogs\*" -DestinationPath "$env:USERPROFILE\Downloads\WU-RollbackLogs.zip" -Force
Then upload:
C:\Users\Ron\Downloads\WU-RollbackLogs.zip

If no files appear​

Run this and paste the result:
Test-Path 'C:\$Windows.~BT'
Then:
dir 'C:\$Windows.~BT\Sources' -Force
It is possible Windows cleaned up the rollback logs after the failed repair. If so, we’ll switch to Event Viewer logs instead.