Dual boot - windows boots but can't login - Blurred screen then blue loop

[glennpm]

Details

- Dual boot system; Windows 11 & Ubuntu

- I run Ubuntu most of the time but a couple of days ago I re-booted in an attempt to login to Windows, but didn’t get my Grub screen. Last boot to Windows was fine with no issues back a couple of weeks ago. during the first recent boot attempt the system seemed to be trying to run a boot service perhaps, AOMEI Backupper. I thought there may have been a boot script by AOMEI Backupper but nothing to prove this.

- DELL Inspirion laptop

- On boot, I get the std Windows screen but no box to add PIN or password for normal or safe modes. I get into SAFE mode via a Windows startup iso

- When I click or "enter" I get a blurred screen, then blue screen, then back to the std Windows boot screen

- Best search yielded this, [SOLVED] - windows 10 Blurred and stuck on the login screen (fuzzy blurry)

- I ran all the Windows install/repair iso options to no avail.



BOOT Mode is set to: UEFI with Legacy OPROH; Secure

UEFI BOOT:

HDD1-Windows Boot Manager (Samsung SSD 870 EVO 1TB)

ISB1-1

HDD2-ubuntu (Samsung SSD 870 EVO

********

DISKPART> list volume

Volume ### Ltr Label Fs Type Size Status Info

._ _ _

— — — — — —.— ————————— ——————

Volume e L CCC0MA_X64F UDF DVD-ROM 5549 MB Healthy

Volume i C Windows NTFS Partition 150 GB Healthy

Volume 2 D D_on_DELL NTFS Partition 703 GB Healthy

Volume 3 ESP FAT32 Partition 499 MB Healthy Hidden

Volume 4 WINRETOOLS NTFS Partition 750 MB Healthy Hidden

Volume 5 F NTFS Partition 853 MB Healthy Hidden

Volume 6 G PBR Image NTFS Partition 7409 MB Healthy Hidden

Volume 7 H WD4TB-Dell NTFS Partition 3399 GB Healthy

Volume 8 I RAW Partition 299 GB Healthy

Volume 9 J Ventoy-Baks exFAT Partition 831 GB Healthy

Volume 10 VTOYEFI FAT Partition 32 MB Healthy

DISKPART> select volume

********

I've run these commands:

K:\sources>bootrec.exe /fixmbr

The operation completed successfully.

K:\sources>bootrec.exe /fixboot

Access is denied.

K:\sources>bootrec.exe /scanos

Scanning all disks for Windows installations.

’lease wait, since this may take a while...

Successfully scanned Windows installations.

Total identified Windows installations: 0

The operation completed successfully.

K:\sources>bootrec.exe /rebuildbcd

Scanning all disks for Windows installations.

Please wait, since this may take a while...

Successfully scanned Windows installations.

Total identified Windows installations: 0

The operation completed successfully.

K:\sources>bcdboot C:\windows

Boot files successfully created.

X:\sources>

**********

Deleted all files inside caches, %windir%\system32\config\systemprofile\appdata\local\microsoft\windows\caches

***********

I also restored the latest AOMEI disk image and still have the same issue. Seems like there is an issue with my boot records

#########

PASTEBIN urls:

Paste from boot-repair application Ubuntu Pastebin

Paste from boot-info Ubuntu Pastebin

 

[ChatGPT]

Thanks — that SFC output confirms the component store still needs repair. Next we should run DISM (the Component Store repair) using a clean Windows 10 22H2 source, then re-run SFC and retry the upgrade.
If you already have a matching Windows 10 22H2 ISO, we’ll use it. If not, tell me and I’ll post the official Microsoft download instructions/links.
Follow these exact steps (copy/paste). After each step, paste the final lines of the command output (or tell me “done”) and I’ll tell you the next move.
Step 0 — quick checks

• Make sure the ISO you use matches your installed Windows edition/arch (Windows 10 Home x64 22H2).
• Ensure you have ~30 GB free on C:. Check with:
  wmic logicaldisk get caption,filesystem,freespace,size

Step 1 — (optional but recommended) run DISM health checks first
Open an elevated Command Prompt (Run as Administrator) and run:
Dism /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-Image /ScanHealth
Paste the final lines of ScanHealth (it tells whether the component store is flagged as repairable).
Step 2 — mount the ISO (if you have it) and note drive letter

• In File Explorer right‑click the ISO → Mount. Note the drive letter (for example D.
• Confirm the installer files: run (replace X: with that drive letter)
  dir X:\sources\install.*

If you see install.wim → use the WIM command below. If you see install.esd → use the ESD command.
Step 3 — run DISM RestoreHealth using the ISO as source
Replace X: with the ISO drive letter.
If you have install.wim:
Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:X:\sources\install.wim:1 /LimitAccess
If you have install.esd:
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:X:\sources\install.esd:1 /LimitAccess
Notes:

• /LimitAccess prevents contacting Windows Update; we’ll use the ISO as the source.
• If DISM reports “source files not found” or another error, stop and paste the DISM error text here — I’ll provide the fallback.
• This step can take 10–30 minutes. Paste the last ~8–12 lines of the DISM output when it finishes.

Fallback if you don’t have an ISO or DISM fails with source errors

• You can let DISM use Windows Update as the source by omitting /LimitAccess:
  Dism /Online /Cleanup-Image /RestoreHealth
  (Only do this if the machine has working internet and Windows Update isn’t blocked.)

Step 4 — run SFC again
After DISM completes successfully, run:
sfc /scannow
Paste the final lines of the SFC output. Ideally it will now say “Windows Resource Protection did not find any integrity violations” or “found and repaired”.
Step 5 — retry the in‑place upgrade

• Mount the same fresh ISO and run setup.exe as Administrator → choose Keep personal files and apps.
• If it fails again, immediately paste the last lines of these logs:

Get-Content 'C:\$WINDOWS.~BT\Sources\Panther\setuperr.log' -Tail 300 | Out-String
Get-Content 'C:\$WINDOWS.~BT\Sources\Panther\setupact.log' -Tail 400 | Out-String
Get-Content 'C:\Windows\logs\SetupDiag\SetupDiagResults.xml' -Raw | Out-String
That will let me pinpoint the blocking component/driver.
Optional: run a quick chkdsk if you haven’t already (recommended when upgrades fail with file corruption):

• Schedule a check and reboot:
  chkdsk C: /f
  (If it says schedule, accept and reboot. Let it finish before proceeding.)

If you want the official ISO / Media Creation Tool link now, say “Get ISO link” and I’ll paste Microsoft’s download link and short instructions.
Which do you want to do now — run DISM with a mounted ISO (tell me the drive letter) or get the ISO link so you can download/mount it?

 

[glennpm]

clear

2025-08-14 09:00:42, Info CBS All CSI corruption was fixed, ensure CorruptionDetectedDuringAcr is clear
2025-08-14 09:00:42, Info CBS Failed to clear CorruptionDetectedDuringAcr store corrupt flag (slow mode trigger). [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2025-08-14 09:00:42, Info CBS CheckSur: hrStatus: 0x0 [S_OK], download results: <none>
2025-08-14 09:00:42, Info CBS Count of times corruption detected: 2
2025-08-14 09:00:42, Info CBS Seconds between initial corruption detections: -1
2025-08-14 09:00:42, Info CBS Seconds between corruption and repair: -1
2025-08-14 09:00:43, Info CBS Reboot mark cleared
2025-08-14 09:00:43, Info CBS Winlogon: Simplifying Winlogon CreateSession notifications
2025-08-14 09:00:43, Info CBS Winlogon: Deregistering for CreateSession notifications
2025-08-14 09:00:43, Info CBS Exec: Processing complete, session(Corruption Detecting): 31198491_768520717 [HRESULT = 0x00000000 - S_OK]
2025-08-14 09:00:43, Info CBS Session: 31198491_768520717 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK]
2025-08-14 09:00:43, Info CBS Deleting directory: \\?\C:\Windows\CbsTemp\31198491_768520717\
2025-08-14 09:00:43, Info CBS Moving directory from \\?\C:\Windows\CbsTemp\31198491_768520717\ to \\?\C:\Windows\CbsTemp\31198491_768520717\{79A54834-5F23-442C-A0B1-57A58244211B}
2025-08-14 09:00:43, Info CBS Failed to move \\?\C:\Windows\CbsTemp\31198491_768520717\ to temp directory \\?\C:\Windows\CbsTemp\31198491_768520717\{79A54834-5F23-442C-A0B1-57A58244211B} [HRESULT = 0x80070020 - ERROR_SHARING_VIOLATION]
2025-08-14 09:00:43, Info CBS Failed moving directory: \\?\C:\Windows\CbsTemp\31198491_768520717\ to temp, will delete in-place instead [HRESULT = 0x80070020 - ERROR_SHARING_VIOLATION]
2025-08-14 09:00:43, Info CBS Deletion of: \\?\C:\Windows\CbsTemp\31198491_768520717\ successful
2025-08-14 09:00:43, Info CBS Session: 31198491_1901437179 initialized by client DISM Package Manager Provider, external staging directory: (null), external registry directory: (null)
2025-08-14 09:02:43, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2025-08-14 09:02:43, Info CBS TiWorker signaled for shutdown, going to exit.
2025-08-14 09:02:43, Info CBS Deleting the contents of directory: \\?\C:\Windows\CbsTemp
2025-08-14 09:02:43, Info CBS Deletion of: \\?\C:\Windows\CbsTemp successful
2025-08-14 09:02:43, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2025-08-14 09:02:43, Info CBS Execution Engine Finalize
2025-08-14 09:02:43, Info CBS Execution Engine Finalize
2025-08-14 09:02:43, Info CBS Lock: Lock removed: TiWorkerClassFactory, level: 30, total lock:3
2025-08-14 09:02:43, Info CBS Lock: Lock removed: CCbsWorker, level: 5, total lock:2
2025-08-14 09:02:43, Info CBS Ending the TiWorker main loop.
2025-08-14 09:02:43, Info CBS Starting TiWorker finalization.
2025-08-14 09:02:43, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2025-08-14 09:02:43, Info CBS CBS Engine already deactivated
2025-08-14 09:02:43, Info CBS CBS Engine already deactivated
2025-08-14 09:02:43, Info CBS CbsCoreFinalize: ComponentAnalyzerFinalize
2025-08-14 09:02:43, Info CBS CbsCoreFinalize: PackageTrackerFinalize
2025-08-14 09:02:43, Info CBS CbsCoreFinalize: CoreResourcesUnload
2025-08-14 09:02:43, Info CBS CbsCoreFinalize: SessionManagerFinalize
2025-08-14 09:02:43, Info CBS Lock: Lock removed: CSIInventoryCriticalSection, level: 64, total lock:10
2025-08-14 09:02:43, Info CBS Lock: Lock removed: CCbsSessionManager, level: 11, total lock:9
2025-08-14 09:02:43, Info CBS CbsCoreFinalize: CapabilityManagerFinalize
2025-08-14 09:02:43, Info CBS CbsCoreFinalize: PublicObjectMonitorFinalize
2025-08-14 09:02:43, Info CBS CbsCoreFinalize: Enter vCoreInitializeLock
2025-08-14 09:02:43, Info CBS CbsCoreFinalize: WcpUnload
2025-08-14 09:02:43, Info CSI 00000009 Direct SIL provider: Number of files opened: 42671.
2025-08-14 09:02:43, Info CBS CbsCoreFinalize: DrupUnload
2025-08-14 09:02:43, Info CBS CbsCoreFinalize: CfgMgr32Unload
2025-08-14 09:02:43, Info CBS CbsCoreFinalize: DpxUnload
2025-08-14 09:02:43, Info CBS CbsCoreFinalize: SrUnload
2025-08-14 09:02:43, Info CBS CbsCoreFinalize: CbsEsdUnload
2025-08-14 09:02:43, Info CBS CbsCoreFinalize: CbsTraceInfoUninitialize
2025-08-14 09:02:43, Info CBS CbsCoreFinalize: CbsEventUnregister
2025-08-14 09:02:43, Info CBS CbsCoreFinalize: AppContainerUnload
2025-08-14 09:02:43, Info CBS CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2025-08-14 09:02:43, Info CBS Ending TiWorker finalization.
2025-08-14 09:02:43, Info CBS Ending the TrustedInstaller main loop.
2025-08-14 09:02:43, Info CBS Starting TrustedInstaller finalization.
2025-08-14 09:02:43, Info CBS Winlogon: Stopping notify server
2025-08-14 09:02:43, Info CBS Winlogon: Unloading SysNotify DLL
2025-08-14 09:02:43, Info CBS Lock: Lock removed: WinlogonNotifyLock, level: 8, total lock:6
2025-08-14 09:02:43, Info CBS Ending TrustedInstaller finalization.

 

[ChatGPT]

Good — those CBS lines show DISM/SFC work progressed and “All CSI corruption was fixed” appeared, though there were a couple of benign cleanup warnings (sharing/flag clearing). That’s promising.
Next we’ll confirm system integrity, check disk health/free space, then retry the in‑place upgrade from a fresh ISO (with a couple of precaution options). If it fails again we’ll capture the exact setup/diagnostic logs and fix the blocking item.
Do the following steps, in order, and paste any command output I ask for (or just “done” where it completes normally). I’ll interpret outputs and tell you exactly what to do next.
1) Reboot now

• This releases any file locks (CBS temp sharing violations we saw) and ensures services restarted after DISM. Do that first.

2) Re-run SFC to verify clean state
Open an elevated Command Prompt and run:
sfc /scannow
When it finishes, copy and paste the final 6–8 lines of the output here (or tell me the exact result).
3) Check disk health (quick)
Still elevated, run:
chkdsk C: /scan
(If your Windows edition supports /scan it runs online; if it prompts to schedule a full offline check use chkdsk C: /f and reboot to let it run if you prefer a full check.)
Paste any error/repair messages if chkdsk reports problems.
4) Confirm free space
Run:
wmic logicaldisk get caption,filesystem,freespace,size
Confirm C: has at least ~30 GB free (20 GB minimum, 30 GB preferred). If it’s under ~20 GB free, delete temp files / uninstall large unused programs until you have enough.
5) Use a fresh ISO and run setup (recommended options)

• If you don’t have a fresh Windows 10 22H2 ISO, tell me and I’ll post the Microsoft Media Creation instructions / link.
• Mount the ISO (right‑click → Mount) and note the drive letter (for example D.
• Important: keep the system in Clean Boot (msconfig steps you already did), and disconnect non‑essential USB devices.
• Run setup.exe from the mounted ISO as Administrator (right‑click → Run as administrator).
• When asked, choose “Keep personal files and apps”.
• When prompted about updates, try this sequence:
  • First attempt: choose NOT to download updates (sometimes downloading during upgrade triggers failures). If that fails, try again enabling updates.

If the upgrade succeeds — great. If it fails, capture the logs immediately.
6) Capture the exact setup failure logs (if it fails)
If setup fails again, run these exactly in an elevated PowerShell and paste the outputs here:
Get-Content 'C:\$WINDOWS.~BT\Sources\Panther\setuperr.log' -Tail 300 | Out-String
Get-Content 'C:\$WINDOWS.~BT\Sources\Panther\setupact.log' -Tail 400 | Out-String
Get-Content 'C:\Windows\logs\SetupDiag\SetupDiagResults.xml' -Raw | Out-String
If the Rollback folder exists also collect:
Get-Content 'C:\$WINDOWS.~BT\Sources\Rollback\setuperr.log' -Tail 300 | Out-String
Get-Content 'C:\$WINDOWS.~BT\Sources\Rollback\setupact.log' -Tail 400 | Out-String
7) (Optional) Run SetupDiag yourself and attach results
If SetupDiag didn’t already run or you want a fresh run:

• Download SetupDiag.exe (Microsoft) onto the machine, then run:
  SetupDiag.exe -Mode:Offline -Path C:\$WINDOWS.~BT\Sources\Panther -Output C:\Users\Public\SetupDiagOutput.xml
• Then paste the XML content:
  Get-Content C:\Users\Public\SetupDiagOutput.xml -Raw | Out-String

8) If upgrade still fails and logs point to a driver/service

• I’ll give exact removal commands (devcon/pnputil or registry Enum key removal) for the offending driver, or a targeted WinRE hive action if it’s still a registry write/permission problem.

9) Practical fallback (to get networking/drivers working now)
If you want to avoid another upgrade attempt while we debug, plug a USB‑Ethernet or USB Wi‑Fi dongle into Windows so you can install drivers/Windows Update (sometimes simply getting the system fully updated fixes any remaining driver/registry issues). That’s a practical short‑term workaround.
Summary / next action for you right now

• Reboot (if you haven’t already), run sfc /scannow and chkdsk (or schedule), confirm free space, mount a fresh ISO and run setup with “Keep personal files and apps” — first try with “Don’t download updates.” If it fails, paste the logs requested in step 6.

Paste the sfc final lines after you run it and tell me whether you have a mounted ISO (and its drive letter) or if you want the Media Creation Tool link. I’ll guide the upgrade retry or parse the logs immediately.

 

[glennpm]

2025-08-14 09:10:10, Info CBS CheckSur: hrStatus: 0x0 [S_OK], download results: <none>
2025-08-14 09:10:10, Info CBS Count of times corruption detected: 2
2025-08-14 09:10:10, Info CBS Seconds between initial corruption detections: -1
2025-08-14 09:10:10, Info CBS Seconds between corruption and repair: -1
2025-08-14 09:10:10, Info CBS Reboot mark cleared
2025-08-14 09:10:10, Info CBS Winlogon: Simplifying Winlogon CreateSession notifications
2025-08-14 09:10:10, Info CBS Winlogon: Deregistering for CreateSession notifications
2025-08-14 09:10:10, Info CBS Exec: Processing complete, session(Corruption Repairing): 31198492_2158488242 [HRESULT = 0x00000000 - S_OK]
2025-08-14 09:10:10, Info CBS Session: 31198492_2158488242 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK]
2025-08-14 09:10:10, Info CBS Deleting directory: \\?\C:\Windows\CbsTemp\31198492_2158488242\
2025-08-14 09:10:10, Info CBS Moving directory from \\?\C:\Windows\CbsTemp\31198492_2158488242\ to \\?\C:\Windows\CbsTemp\31198492_2158488242\{CD12E0AB-0CED-4EC9-B5FB-76BCBB21398E}
2025-08-14 09:10:10, Info CBS Failed to move \\?\C:\Windows\CbsTemp\31198492_2158488242\ to temp directory \\?\C:\Windows\CbsTemp\31198492_2158488242\{CD12E0AB-0CED-4EC9-B5FB-76BCBB21398E} [HRESULT = 0x80070020 - ERROR_SHARING_VIOLATION]
2025-08-14 09:10:10, Info CBS Failed moving directory: \\?\C:\Windows\CbsTemp\31198492_2158488242\ to temp, will delete in-place instead [HRESULT = 0x80070020 - ERROR_SHARING_VIOLATION]
2025-08-14 09:10:10, Info CBS Deletion of: \\?\C:\Windows\CbsTemp\31198492_2158488242\ successful
2025-08-14 09:10:10, Info CBS Session: 31198492_3281420414 initialized by client DISM Package Manager Provider, external staging directory: (null), external registry directory: (null)
2025-08-14 09:12:10, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2025-08-14 09:12:10, Info CBS TiWorker signaled for shutdown, going to exit.
2025-08-14 09:12:10, Info CBS Deleting the contents of directory: \\?\C:\Windows\CbsTemp
2025-08-14 09:12:10, Info CBS Deletion of: \\?\C:\Windows\CbsTemp successful
2025-08-14 09:12:10, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2025-08-14 09:12:10, Info CBS Execution Engine Finalize
2025-08-14 09:12:10, Info CBS Execution Engine Finalize
2025-08-14 09:12:10, Info CBS Lock: Lock removed: TiWorkerClassFactory, level: 30, total lock:3
2025-08-14 09:12:10, Info CBS Lock: Lock removed: CCbsWorker, level: 5, total lock:2
2025-08-14 09:12:10, Info CBS Ending the TiWorker main loop.
2025-08-14 09:12:10, Info CBS Starting TiWorker finalization.
2025-08-14 09:12:10, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2025-08-14 09:12:10, Info CBS CBS Engine already deactivated
2025-08-14 09:12:10, Info CBS CBS Engine already deactivated
2025-08-14 09:12:10, Info CBS CbsCoreFinalize: ComponentAnalyzerFinalize
2025-08-14 09:12:10, Info CBS CbsCoreFinalize: PackageTrackerFinalize
2025-08-14 09:12:10, Info CBS CbsCoreFinalize: CoreResourcesUnload
2025-08-14 09:12:10, Info CBS CbsCoreFinalize: SessionManagerFinalize
2025-08-14 09:12:10, Info CBS Lock: Lock removed: CSIInventoryCriticalSection, level: 64, total lock:10
2025-08-14 09:12:10, Info CBS Lock: Lock removed: CCbsSessionManager, level: 11, total lock:9
2025-08-14 09:12:10, Info CBS CbsCoreFinalize: CapabilityManagerFinalize
2025-08-14 09:12:10, Info CBS CbsCoreFinalize: PublicObjectMonitorFinalize
2025-08-14 09:12:10, Info CBS CbsCoreFinalize: Enter vCoreInitializeLock
2025-08-14 09:12:10, Info CBS CbsCoreFinalize: WcpUnload
2025-08-14 09:12:10, Info CSI 00000010 Direct SIL provider: Number of files opened: 42671.
2025-08-14 09:12:10, Info CBS CbsCoreFinalize: DrupUnload
2025-08-14 09:12:10, Info CBS CbsCoreFinalize: CfgMgr32Unload
2025-08-14 09:12:10, Info CBS CbsCoreFinalize: DpxUnload
2025-08-14 09:12:10, Info CBS CbsCoreFinalize: SrUnload
2025-08-14 09:12:10, Info CBS CbsCoreFinalize: CbsEsdUnload
2025-08-14 09:12:10, Info CBS CbsCoreFinalize: CbsTraceInfoUninitialize
2025-08-14 09:12:10, Info CBS CbsCoreFinalize: CbsEventUnregister
2025-08-14 09:12:10, Info CBS CbsCoreFinalize: AppContainerUnload
2025-08-14 09:12:10, Info CBS CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2025-08-14 09:12:10, Info CBS Ending TiWorker finalization.
2025-08-14 09:12:10, Info CBS Ending the TrustedInstaller main loop.
2025-08-14 09:12:10, Info CBS Starting TrustedInstaller finalization.
2025-08-14 09:12:10, Info CBS Winlogon: Stopping notify server
2025-08-14 09:12:10, Info CBS Winlogon: Unloading SysNotify DLL
2025-08-14 09:12:10, Info CBS Lock: Lock removed: WinlogonNotifyLock, level: 8, total lock:6
2025-08-14 09:12:10, Info CBS Ending TrustedInstaller finalization.

 

[ChatGPT]

Good progress — CBS shows the component‑store corruption was repaired (the remaining messages are cleanup/sharing warnings, not blockers). Let’s verify everything is clean, check disk health/free space, then retry the in‑place upgrade from a fresh ISO. If it fails again we’ll capture the exact setup failure logs and fix the blocker.
Do these steps now (copy/paste the commands I list, one at a time). After each, paste the short output I ask for (or say “done” if it completed without noteworthy text).
1) Verify SFC now
Run (Admin):
sfc /scannow
When it finishes, paste the final 6–8 lines of output (or the exact sentence it shows — e.g., “Windows Resource Protection did not find any integrity violations” or “found and repaired …”).
2) Quick disk health check
Run (Admin):
chkdsk C: /scan
If your Windows edition doesn’t support /scan, run:
chkdsk C: /f
If it asks to schedule, say Y and reboot to let it run — tell me if it found/fixed issues.
3) Confirm free space (need ≥ ~30 GB recommended)
Run:
wmic logicaldisk get caption,filesystem,freespace,size
Report the FreeSpace value for C: (it’s in bytes — I can help interpret).
4) Get a fresh Windows 10 22H2 ISO (if you don’t already have one)

• If you already mounted an ISO, tell me the drive letter now (e.g., D.
• If not, say “Get ISO link” and I’ll paste the official Microsoft Media Creation Tool / ISO link and short instructions.

5) Run the in‑place upgrade from the mounted ISO

• Mount the ISO (Explorer → right‑click → Mount). Note the drive letter (X.
• From an elevated Explorer or CMD, run:
  X:\setup.exe
• Choose “Keep personal files and apps.” When the update prompt appears, try the first attempt with “Don’t download updates.” (If that fails, we can retry with updates on.)

If the upgrade succeeds — excellent. If it fails, collect logs immediately as below.
6) If setup fails again — collect three logs (copy/paste)
Run these in an elevated PowerShell and paste their outputs here:
Get-Content 'C:\$WINDOWS.~BT\Sources\Panther\setuperr.log' -Tail 300 | Out-String
Get-Content 'C:\$WINDOWS.~BT\Sources\Panther\setupact.log' -Tail 400 | Out-String
Get-Content 'C:\Windows\logs\SetupDiag\SetupDiagResults.xml' -Raw | Out-String
(If the Rollback folder exists, also send the Rollback setuperr/setupact tails.)
7) Optional: run SetupDiag yourself
If SetupDiag didn’t produce results earlier, run (from an elevated prompt) after failure:
SetupDiag.exe -Mode:Offline -Path C:\$WINDOWS.~BT\Sources\Panther -Output C:\Users\Public\SetupDiagOutput.xml
Then:
Get-Content C:\Users\Public\SetupDiagOutput.xml -Raw | Out-String
What I’ll do when you paste the outputs

• If SFC is now clean and DISM succeeded earlier, but the installer still fails, the setup logs will show the exact driver/service/file causing the failure — I’ll give a targeted removal/fix (devcon/pnputil/regkey removal or WinRE hive step).
• If disk errors show up we’ll fix them before retry.
• If free space is low we’ll free space and retry.

If you prefer a practical short‑term workaround instead of more upgrade attempts:

• Plug a USB‑Ethernet or USB Wi‑Fi adapter into Windows so you can get online, run Windows Update and install the Dell Realtek driver — that may remove the urgency to repair the upgrade immediately.

Which do you want to do now: run sfc and chkdsk (and paste results), or have me post the Media Creation Tool/ISO link?

 

[glennpm]

I have run this many times now and don't understand why repairs are not being made. I feel like this is not succeeding.

 

[ChatGPT]

You’ve done a huge amount of correct troubleshooting and it’s completely understandable to be frustrated — you’ve worked through SFC, DISM, clean‑boot, registry changes, PCI resets from Linux and more. Good news: the component store repairs appear to have completed (DISM/CBS evidence), so we’re not blind — we just need to get the single blocking item that’s still preventing Setup from finishing. The logs you already pasted show the install failing with 0x800703F1 during the final/unpack phase and that SetupDiag ran but didn’t auto‑point the cause.
Below are three clear, safe next paths (short → more invasive) and exact commands / steps for each. Pick one and I’ll walk you through it step‑by‑step.
Option A — Capture the exact failing component (recommended next)
Why: setuperr.log / SetupDiag usually show exactly which driver, file or plugin failed. Once we have that single line we can fix it directly instead of re‑trying blind upgrades.
What I need you to run now (copy/paste into an elevated PowerShell prompt) — then paste the outputs here:
1) Tail the main error log (paste result):
Get-Content 'C:\$WINDOWS.~BT\Sources\Panther\setuperr.log' -Tail 300 | Out-String
2) Tail the main activity log (paste result):
Get-Content 'C:\$WINDOWS.~BT\Sources\Panther\setupact.log' -Tail 400 | Out-String
3) If SetupDiag file exists, paste it (it’s usually decisive):
Get-Content 'C:\Windows\logs\SetupDiag\SetupDiagResults.xml' -Raw | Out-String
4) If Rollback folder exists, paste its error tail:
Get-Content 'C:\$WINDOWS.~BT\Sources\Rollback\setuperr.log' -Tail 300 | Out-String
If you prefer, download and re-run SetupDiag yourself and paste the generated XML:

• Download SetupDiag.exe from Microsoft (one small exe), copy it to the laptop and run:
  SetupDiag.exe -Mode:Offline -Path C:\$WINDOWS.~BT\Sources\Panther -Output C:\Users\Public\SetupDiagOutput.xml
  Get-Content C:\Users\Public\SetupDiagOutput.xml -Raw | Out-String

Why this first: the logs almost always point to a single driver or migration plugin that blocks finalization (printer driver, audio driver, VPN filter driver, backup/instrumentation). Once you paste those tails I’ll read them and tell you the precise action (uninstall driver, delete Enum key, remove a scheduled task, etc.).
Option B — Short workaround: get Windows online with a USB network adapter, finish updates & drivers
Why: This is the pragmatic “get you working now” route. If we can get Windows Update + OEM drivers installed, the realtek NIC and other issues often resolve, and the in‑place upgrade may be unnecessary.
What to do:

• Plug a cheap USB‑Ethernet dongle or USB Wi‑Fi adapter into the laptop (they normally work out‑of‑the‑box).
• Windows Update should run, then install Dell chipset + network drivers you already downloaded. Or copy the Realtek driver folder to C:\Drivers and install offline:
  pnputil /add-driver "C:\Drivers\Realtek*.inf" /install
• Reboot and re‑try setup if you still want the in‑place repair.

Option C — Clean reinstall of Windows 10 (safe if you want to stop chasing this)
Why: If logs keep pointing to obscure leftover system state and you have a Clonezilla image (you do), a clean install is deterministic and often the fastest way to a stable system. You can preserve Ubuntu/GRUB if you do the install carefully.
How to do a clean install that preserves Ubuntu:
1) Make a Windows 10 USB (Media Creation Tool or Rufus with official ISO).
2) Boot the Windows installer, choose Custom install. Important: select only the Windows partition(s) (the partition labeled as your current C: and its WinRE/EFi partitions if prompted). Do NOT delete or format the drive(s) containing Ubuntu partitions. If Windows wants to create or modify the EFI partition, allow it — we’ll restore GRUB afterwards.
3) After Windows completes and you can log in, GRUB may be overwritten and Ubuntu won’t show — restore GRUB from an Ubuntu Live USB:

• Boot Ubuntu Live → open Terminal:
  sudo mount /dev/sdXY /mnt # (replace sdXY with your Ubuntu root partition)
  sudo mount /dev/sdXZ /mnt/boot/efi # (mount EFI if separate; sdXZ is EFI partition)
  sudo grub-install --boot-directory=/mnt/boot /dev/sdX # sdX = disk (not partition)
  sudo chroot /mnt
  sudo update-grub
  exit
  sudo umount /mnt/boot/efi /mnt
• Reboot, GRUB should reappear and list both Ubuntu and Windows.
  4) Restore any Windows data from your Clonezilla image if needed.

If you want, I’ll provide the exact commands for your drive layout before you start. I’ll also show a small checklist to avoid accidentally removing Ubuntu. This is the most aggressive option but is guaranteed.
Extra targeted things I can do now (if you want to keep trying repairs)

• Re-run secedit to reset registry ACLs (I gave the command earlier) — sometimes Write/ACL problems prevent Setup writing driver metadata. I can guide you through that again.
• Run devcon to remove specific stubborn device instances (we used these earlier for the Realtek). If the log points to a device instance GUID I’ll give the exact devcon command.
• If the setuperr shows a failing migration plugin (printer/audio), I’ll give the exact uninstall instructions for that vendor.

My recommendation (one clear next move)

• Step 1: paste the tails of setuperr.log + setupact.log + SetupDiagResults.xml (Option A). That’s low effort and will almost certainly reveal the single blocking component. If you prefer to skip log collection and just get your PC usable now, choose Option B (USB network adapter) so you can finish driver updates and then we’ll circle back.

I’ll be standing by — paste the outputs from those tail commands and I’ll parse the cause and give the exact one‑line fix. If you prefer I can walk you through any of the three options interactively; tell me which you want to do.

 

[glennpm]

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

Try the new cross-platform PowerShell Install PowerShell on Windows, Linux, and macOS - PowerShell

PS C:\Windows\system32> Get-Content 'C:\$WINDOWS.~BT\Sources\Panther\setuperr.log' -Tail 300 | Out-String
2025-08-14 06:45:17, Error MOUPG CMoSetupOneSettingsHelperT<class CEmptyType>::InitializeSettings(324): Result = 0x80072EE7
2025-08-14 06:45:17, Error MOUPG CSetupHost::InitializeOneSettings(1341): Result = 0x80072EE7
2025-08-14 06:45:17, Error MOUPG SetupHost: OneSettings initialization failed: [0x80072EE7]
2025-08-14 06:45:37, Error MOUPG CFCDCATQuery::RetrieveResponse(311): Result = 0x80072EE7[gle=0x00002ee7]
2025-08-14 06:45:37, Error MOUPG CFCDCATQuery::Query(210): Result = 0x80072EE7[gle=0x00002ee7]
2025-08-14 06:45:37, Error MOUPG CFCAcquirerDCAT::QueryWeb(991): Result = 0x80072EE7
2025-08-14 06:45:37, Error MOUPG CFCAcquirerDCAT:ownload(1308): Result = 0x80072EE7
2025-08-14 06:45:37, Error MOUPG CFCPayloadDU:ownload(267): Result = 0x80072EE7
2025-08-14 06:45:37, Error MOUPG DUSetup: Error on downloading SetupDU Payload: [0x80072EE7]
2025-08-14 06:45:37, Error MOUPG CDlpActionDU::ExecuteFacilitatorDUSetup(2183): Result = 0x80072EE7
2025-08-14 06:45:48, Error DU DU::CDUSession::Search: Failed to end the asynchronus search. hr = 0x80240438
2025-08-14 06:45:48, Error SP pDUSearchAndDownload: DU search failed. hr = 0x80240438
2025-08-14 06:45:48, Error MOUPG DUSetup: Failed to execute DUSetup seach and download [0x80240438]
2025-08-14 06:45:48, Error CONX Windows::Compat::Appraiser::IsMeteredConnection (207): Failed to get NetworkCostType assuming metered network [0x80004005].[gle=0x80004005]
2025-08-14 06:46:28, Error CONX Windows::Compat::Appraiser::Utilities::SendRequest (1528): Failed to connect to the internet, or send request, or request encountered HTTP error: [12007].[gle=0x80072ee7]
2025-08-14 06:46:28, Error CONX Windows::Compat::Appraiser::Utilities:ownloadCabFile (4889): Failed to send request using default proxy[gle=0x80072ee7]
2025-08-14 06:47:06, Error MOUPG CFCDCATQuery::RetrieveResponse(311): Result = 0x80072EFD[gle=0x00002efd]
2025-08-14 06:47:06, Error MOUPG CFCDCATQuery::Query(210): Result = 0x80072EFD[gle=0x00002efd]
2025-08-14 06:47:06, Error MOUPG CFCAcquirerDCAT::QueryWeb(991): Result = 0x80072EFD
2025-08-14 06:47:06, Error MOUPG CFCAcquirerDCAT:ownload(1308): Result = 0x80072EFD
2025-08-14 06:47:06, Error MOUPG CFCPayloadDU:ownload(267): Result = 0x80072EFD
2025-08-14 06:47:06, Error MOUPG DUImage: Error on downloading ImageDU Payload: [0x80072EFD]
2025-08-14 06:47:06, Error MOUPG CDlpActionDU::ExecuteFacilitatorDUImage(1473): Result = 0x80072EFD
2025-08-14 06:47:06, Error CSI 00000001 (F) STATUS_OBJECT_NAME_NOT_FOUND #40# from Windows::Rtl::SystemImplementation:irectRegistryProvider::SysQueryValueKey(flags = 0, key = b00 ('\REGISTRY\MACHINE\SYSTEM\Setup'), vn = [l:7 ml:8]'Compact', kvic = 2, kvi = 2, disp = 0)[gle=0xd0000034]
2025-08-14 06:47:06, Error CSI 00000002 (F) STATUS_OBJECT_NAME_NOT_FOUND #39# from Windows::Rtl::SystemImplementation::CKey::QueryValue(flags = 0, kn = [l:31]'\Registry\Machine\SYSTEM\Setup\', vn = [l:7 ml:8]'Compact', ic = KeyValuePartialInformation, info = {l:0 b:}, disp = 0)[gle=0xd0000034]
2025-08-14 06:47:07, Error CSI 00000003 (F) STATUS_OBJECT_NAME_NOT_FOUND #84# from Windows::Rtl::SystemImplementation:irectRegistryProvider::SysQueryValueKey(flags = 0, key = 970 ('\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts'), vn = [l:21 ml:22]'Arial Nova (TrueType)', kvic = 2, kvi = 2, disp = 0)[gle=0xd0000034]2025-08-14 06:47:07, Error CSI 00000004 (F) STATUS_OBJECT_NAME_NOT_FOUND #83# from Windows::Rtl::SystemImplementation::CKey::QueryValue(flags = 0, kn = [l:69]'\Registry\Machine\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts\', vn = [l:21 ml:22]'Arial Nova (TrueType)', ic = KeyValuePartialInformation, info = {l:0 b:}, disp = 0)[gle=0xd0000034]
2025-08-14 06:47:19, Error DU DU::CDUSession::Search: Failed to end the asynchronus search. hr = 0x80240438
2025-08-14 06:47:19, Error SP CDownloadDUUpdates:oExecuteInternal: Failed to search for updates. hr = 0x80240438
2025-08-14 06:47:19, Error SP CSetupPlatform:ownloadDynamicUpdates: Failed to download updates. Error: 0x80240438
2025-08-14 06:47:19, Error MOUPG DUImage: Failed to execute critical search and download [0x80240438]
2025-08-14 06:47:31, Error DU DU::CDUSession::Search: Failed to set WU internal configuration property for targeted scans. hr = 0x80070057
2025-08-14 06:47:41, Error SP Failed to get driver packages from the online system. Error: 0x800703F1[gle=0x0000007a]
2025-08-14 06:47:41, Error SP CDownloadDUUpdates:oExecuteInternal: Failed to filter updates. hr = 0x800703f1
2025-08-14 06:47:41, Error SP CSetupPlatform:ownloadDynamicUpdates: Failed to download updates. Error: 0x800703F1
2025-08-14 06:47:41, Error MOUPG DUImage: Failed to execute driver search and download [0x800703f1]
2025-08-14 07:08:41, Error CONX Windows::Compat::Appraiser::WicaDeviceInventory::RunDeviceInventory (464): Failed to get device inventory from devinv: [0x80004005].[gle=0x80004005]
2025-08-14 07:08:41, Error CONX Windows::Compat::Appraiser::WicaDeviceInventory::GetInventory (352): Device inventory failed setup devices run, trying other runs: [0x80004005].[gle=0x80004005]
2025-08-14 07:08:41, Error CONX Windows::Compat::Appraiser::WicaDeviceInventory::GetInventory (378): AtLeastOne table validation failed, trying other runs: [0x8007000d].[gle=0x8007000d]
2025-08-14 07:08:41, Error CONX Windows::Compat::Appraiser::WicaEngine::RunComponents (1343): CollectInventories Failed: [0x80004005].[gle=0x80004005]
2025-08-14 07:08:41, Error CONX Windows::Compat::Appraiser::WicaFactory:oWicaRun (366): Failed to run engine: [0x80004005].[gle=0x80004005]
2025-08-14 07:08:41, Error CONX Windows::Compat::Appraiser::SetupAppraiser::ScanInternal (285): WicaRun failed: [0x80004005].[gle=0x80004005]
2025-08-14 07:12:24, Error ITaskFolder:eleteTask failed. hr = 0x80070002
2025-08-14 07:15:51, Error SP pSPRemoveUpgradeRegTree: failed to delete reg tree HKLM\SYSTEM\Setup\Upgrade[gle=0x00000005]
2025-08-14 07:16:11, Error MIG Ignoring replacement manifest with no settingsVersionRange or versionRange attribute in migration element: Microsoft-Windows-Container-Manager
2025-08-14 07:16:12, Error [0x080831] MIG CSIAgent: Invalid xml format: FormatException: "script" attribute is mandatory. class Mig::CMXEMerge *__cdecl Mig::CMXEMigrationXml::LoadMerge(class UnBCL::XmlNode *,int,class Mig::CMXEMigrationXml *,class Mig::CMXEXmlComponent *)
2025-08-14 07:16:21, Error [0x0808fe] MIG Plugin {050ed09e-a530-41e6-8ac9-a9a96e74a2c1}: [shmig] shell\shmig\assocuserchoices.cpp(273)\shmig.dll!00007FF8BC8BB7E1: (caller: 00007FF8BC8C9A57) ReturnHr(1) tid(1384) 80070002 The system cannot find the file specified.

2025-08-14 07:16:21, Error [0x0808fe] MIG Plugin {050ed09e-a530-41e6-8ac9-a9a96e74a2c1}: [shmig] shell\shmig\usersettings.cpp(118)\shmig.dll!00007FF8BC8C9A7F: (caller: 00007FF8F46BA8D3) LogHr(1) tid(1384) 80070002 The system cannot find the file specified.
Msg:[Gather failed for (offline-capable) plugin #0]

2025-08-14 07:16:23, Error [0x0808fe] MIG Plugin {050ed09e-a530-41e6-8ac9-a9a96e74a2c1}: [shmig] shell\shmig\assocuserchoices.cpp(273)\shmig.dll!00007FF8BF59B7E1: (caller: 00007FF8BF5A9A57) ReturnHr(1) tid(1bc) 80070002 The system cannot find the file specified.

2025-08-14 07:16:23, Error [0x0808fe] MIG Plugin {050ed09e-a530-41e6-8ac9-a9a96e74a2c1}: [shmig] shell\shmig\usersettings.cpp(118)\shmig.dll!00007FF8BF5A9A7F: (caller: 00007FF8F46BA8D3) LogHr(1) tid(1bc) 80070002 The system cannot find the file specified.
Msg:[Gather failed for (offline-capable) plugin #0]

2025-08-14 07:16:26, Error [0x0808fe] MIG Plugin {050ed09e-a530-41e6-8ac9-a9a96e74a2c1}: [shmig] shell\shmig\assocuserchoices.cpp(273)\shmig.dll!00007FF8BF59B7E1: (caller: 00007FF8BF5A9A57) ReturnHr(1) tid(e24) 80070002 The system cannot find the file specified.

2025-08-14 07:16:26, Error [0x0808fe] MIG Plugin {050ed09e-a530-41e6-8ac9-a9a96e74a2c1}: [shmig] shell\shmig\usersettings.cpp(118)\shmig.dll!00007FF8BF5A9A7F: (caller: 00007FF8F46BA8D3) LogHr(1) tid(e24) 80070002 The system cannot find the file specified.
Msg:[Gather failed for (offline-capable) plugin #0]

2025-08-14 07:16:56, Error MIG Ignoring replacement manifest with no settingsVersionRange or versionRange attribute in migration element: Microsoft-Windows-Container-Manager
2025-08-14 07:17:00, Error [0x080831] MIG CSIAgent: Invalid xml format: FormatException: Component with display name: Plugin/{C939EC0F-2F56-4CE8-AF56-2336596A5FA7} already loaded __cdecl Mig::CMXEMigrationXml::CMXEMigrationXml(class Mig::CPlatform *,class UnBCL::String *,class UnBCL::XmlDocument *,class UnBCL::String *,class UnBCL::String *)
2025-08-14 07:18:58, Error [0x0808fe] MIG Plugin {ff9c714f-b864-4f43-ae39-ec07d7385abe}: Unable to determine inbox status of driver 'kdnic.inf' for 'ROOT\KDNIC\0000'. Error = 0x000003F1
2025-08-14 07:18:59, Error [0x0808fe] MIG Plugin {ff9c714f-b864-4f43-ae39-ec07d7385abe}: Unable to determine inbox status of driver 'oem11.inf' for 'ROOT\DELLUTILS\0000'. Error = 0x000003F1
2025-08-14 07:19:01, Error [0x0808fe] MIG Plugin {ff9c714f-b864-4f43-ae39-ec07d7385abe}: Unable to determine inbox status of driver 'oem10.inf' for 'ROOT\DELLINSTRUMENTATION\0000'. Error = 0x000003F1
2025-08-14 07:19:09, Error SP CSetupPlatform::ResurrectAutomation: Failed to resurrect automation: 0x80070002[gle=0x00000002]
2025-08-14 07:20:08, Error SP Failed to enumerate driver packages, Err = 0x3f1[gle=0x000003f1]
2025-08-14 07:20:08, Error SP Failed to get published Driver Store INFs failed, Err = 0x3f1[gle=0x000003f1]
2025-08-14 07:20:08, Error SP PnpCleanupDrivers failed. Error: 0x000003F1
2025-08-14 07:20:10, Error SP Failed to get driver packages from the online system. Error: 0x800703F1[gle=0x0000007a]
2025-08-14 07:20:10, Error SP Operation failed: Process Drivers for Migration. Error: 0x800703F1[gle=0x000000b7]
2025-08-14 07:20:10, Error SP COperationQueue::Sort: Could not find an execution phase for 91
2025-08-14 07:20:10, Error SP Operations can no longer be sorted following an attempt to retry a failed operation.
2025-08-14 07:20:10, Error SP ExecuteOperations: Failed execution phase Pre-Finalize. Error: 0x800703F1
2025-08-14 07:20:10, Error MOUPG MoSetupPlatform: ExecuteCurrentOperations reported failure!
2025-08-14 07:20:10, Error MOUPG MoSetupPlatform: Using action error code: [0x800703F1]
2025-08-14 07:20:10, Error MOUPG CDlpActionPreFinalize::ExecuteRoutine(579): Result = 0x800703F1
2025-08-14 07:20:10, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >::Execute(493): Result = 0x800703F1
2025-08-14 07:20:10, Error MOUPG CDlpTask::ExecuteAction(3300): Result = 0x800703F1
2025-08-14 07:20:10, Error MOUPG CDlpTask::ExecuteActions(3454): Result = 0x800703F1
2025-08-14 07:20:10, Error MOUPG CDlpTask::Execute(1631): Result = 0x800703F1
2025-08-14 07:20:10, Error MOUPG CSetupManager::ExecuteTask(2630): Result = 0x800703F1
2025-08-14 07:20:10, Error MOUPG CSetupManager::ExecuteTask(2593): Result = 0x800703F1
2025-08-14 07:20:10, Error MOUPG CSetupManager::ExecuteInstallMode(944): Result = 0x800703F1
2025-08-14 07:20:10, Error MOUPG CSetupManager::ExecuteDownlevelMode(410): Result = 0x800703F1
2025-08-14 07:20:24, Error MOUPG CSetupManager::Execute(295): Result = 0x800703F1
2025-08-14 07:20:24, Error MOUPG CSetupHost::Execute(433): Result = 0x800703F1

PS C:\Windows\system32>

****************

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

Try the new cross-platform PowerShell Install PowerShell on Windows, Linux, and macOS - PowerShell

PS C:\Windows\System32\WindowsPowerShell\v1.0> Get-Content 'C:\$WINDOWS.~BT\Sources\Panther\setupact.log' -Tail 400 | Out-String
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Save config data
2025-08-14 07:20:10, Warning SP FindGlobalPath: Cannot find volume name for \\?\GLOBALROOT\Device\HardDisk0\Partition2. Error: 0x00001126
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CEnableSafeOSPageFile
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Enable Page File in SafeOS
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CFinalizeCriticalBoundary
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Finalize critical boundary
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CCleanupSnapshot
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Cleanup snapshot
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CUntagSourcesFolder
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Untag Sources Folder
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CUpdateBootCode
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Update Boot Code
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CUpdateBootSector
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Update Boot Sector
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CSuspendBitlocker
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Suspend bitlocker if needed
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CRemoveSRCheckpoints
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Remove System Restore checkpoints
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CAddBootEntry
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Add boot entry for C:\$WINDOWS.~BT\NewOS\WINDOWS. Locale = en-US
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CEnableTelemetryForImage
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Enable telemetry for C:\$WINDOWS.~BT\NewOS
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CSetBootCommand
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Set boot command %SYSTEMDRIVE%\$WINDOWS.~BT\Sources\SetupPlatform.exe /presysprep for phase DismPreSysprep
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CSetBootCommand
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Set boot command %SYSTEMDRIVE%\$WINDOWS.~BT\Sources\SetupPlatform.exe /postsysprep for phase DismPostSysprep
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CSetBootCommand
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Set boot command %SYSTEMDRIVE%\$WINDOWS.~BT\Sources\SetupPlatform.exe /preoobe for phase DismPreOobe
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CSetBootCommand
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Set boot command %SYSTEMDRIVE%\$WINDOWS.~BT\Sources\SetupPlatform.exe /postoobe for phase DismPostOobe
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CSetBootCommand
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Set boot command %SYSTEMDRIVE%\$WINDOWS.~BT\Sources\SetupPlatform.exe /onerror for phase DismOnError
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CSetEntropy
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Set entropy for C:\$WINDOWS.~BT\NewOS
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CSysprepSpecializeOffline
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Run sysprep specialization offline on C:\$WINDOWS.~BT\NewOS
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CPrepareNewOSForFirstBoot
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Prepare the new OS for first boot
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CRelocateOS
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Relocate OS from C:\$WINDOWS.~BT\NewOS to C:\
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CAddBootEntry
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Add boot entry for C:\WINDOWS. Locale = en-US
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CBackupRecoveryPartition
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Backup the recovery partition to C:\$WINDOWS.~BT\Sources\RecoveryPartitionBackup
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CPrepareRecoveryImage
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Prepare the recovery image
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CSetupRecoveryPartition
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Setup the recovery partition
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CCloseLogFiles
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Close log files
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class COrchestrateOSSwitch
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Orchestrate OS switch for NewOS with safe OS SafeOS and rollback OS ExternalRollback. DelayedSwitch: 0
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CExtractFilesFromWIM
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Extract files from WIM file PathForNewOSFile, index 1 to C:\$WINDOWS.~BT\Sources\SafeOS
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CAddSafeOSBootEntry
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Add safe OS boot entry
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CMountWIM
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Mount WIM file C:\$WINDOWS.~BT\Sources\SafeOS\winre.wim, index 1 to C:\$WINDOWS.~BT\Sources\SafeOS\SafeOS.Mount
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CUnmountWIM
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Unmount the image C:\$WINDOWS.~BT\Sources\SafeOS\SafeOS.Mount
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CEnableTelemetryForImage
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Enable telemetry for C:\$WINDOWS.~BT\Sources\SafeOS\SafeOS.Mount
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CPrepareSafeOSForRollback
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Prepare SafeOS for rollback
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CSetDefaultBootEntry
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Set SafeOS boot entry as the default boot entry
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CSetSafeOSBootCommand
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Set safe OS boot command
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class COrchestrateOSSwitch
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Orchestrate OS switch for NewOS with safe OS SafeOS and rollback OS ExternalRollback. DelayedSwitch: 1
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CEmptyOperation
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Boot WinPE
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CApplyEAs
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Apply EAs for C:\$WINDOWS.~BT\NewOS
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CCreateRegistryForNewSystem
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Create registry key HKLM\SYSTEM\Setup\FirstBoot\Cleanup (value name: %SystemDrive%\$WINDOWS.~BT) on the new system
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CStartSystemServices
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Start system services
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CRemoveFODPackage
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Remove FeaturesOnDemand
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CEmptyOperation
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Complete servicing operations
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CSetProductKey
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Set product key
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CCreateRegistryForNewSystem
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Create registry key HKLM\Software\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform\Activation (value name: DownlevelActivation) on the new system
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CInstallEula
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Install Eula
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CCreateRegistryForNewSystem
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Create registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Flighting\Build (value name: UpdateId) on the new system
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CCreateRegistryForNewSystem
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Create registry key HKLM\System\Setup\Upgrade (value name: DownlevelBuildNumber) on the new system
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CCreateRegistryForNewSystem
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Create registry key HKLM\SYSTEM\Setup\MoSetup\Volatile (value name: DownlevelBuildNumber) on the new system
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CCreateRegistryForNewSystem
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Create registry key HKLM\SYSTEM\Setup\MoSetup\Volatile (value name: DownlevelProductName) on the new system
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CCreateRegistryForNewSystem
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Create registry key HKLM\Software\Microsoft\Windows\CurrentVersion\ReserveManager (value name: PostUpgradeFreeSpace) on the new system
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CCreateRegistryForNewSystem
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Create registry key HKLM\System\CurrentControlSet\Services\i8042prt\Parameters (value name: PollingIterations) on the new system
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CCreateRegistryForNewSystem
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Create registry key HKLM\System\CurrentControlSet\Services\i8042prt\Parameters (value name: PollingIterationsMaximum) on the new system
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CCreateRegistryForNewSystem
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Create registry key HKLM\System\CurrentControlSet\Services\i8042prt\Parameters (value name: ResendIterations) on the new system
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CCreateRegistryForNewSystem
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Create registry key HKLM\System\CurrentControlSet\Services\i8042prt\Parameters (value name: WppRecorder_TraceGuid) on the new system
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CCreateRegistryForNewSystem
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Create registry key HKLM\System\CurrentControlSet\Services\i8042prt\Parameters (value name: LayerDriver JPN) on the new system
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CCreateRegistryForNewSystem
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Create registry key HKLM\System\CurrentControlSet\Services\i8042prt\Parameters (value name: LayerDriver KOR) on the new system
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CCreateRegistryForNewSystem
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Create registry key HKLM\System\CurrentControlSet\Services\i8042prt\Parameters (value name: OverrideKeyboardIdentifier) on the new system
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CCreateRegistryForNewSystem
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Create registry key HKLM\System\CurrentControlSet\Services\i8042prt\Parameters (value name: OverrideKeyboardType) on the new system
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CCreateRegistryForNewSystem
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Create registry key HKLM\System\CurrentControlSet\Services\i8042prt\Parameters (value name: OverrideKeyboardSubtype) on the new system
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CCreateFileForNewSystem
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Create file C:\$WINDOWS.~BT\NewOS\ProgramData\Microsoft\Windows\ClipSVC\GenuineTicket\GenuineTicket.xml on the new system
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CCreateFileForNewSystem
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Create file C:\$WINDOWS.~BT\NewOS\Windows\Setup\LatentAcquisition\ActionList.xml on the new system
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CUpgradeSecurity
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Upgrade security
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CGatherData
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Gather data, scope: EVERYTHING
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CStopSuspendedServices
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Ensure suspended services are stopped
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CFirstBootApply
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: First boot apply
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CStopSuspendedServices
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Ensure suspended services are stopped
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class COOBEBootApply
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: OOBE boot apply
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CApplyDataOffline
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Offline portion of first and oobe boot apply operations
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CCompleteFileOps
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Complete file operations for offline portion of first and oobe boot apply
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CRefreshLocalizedString
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Refresh localized strings
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CProvisioningMigration
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Execute provisioning migration
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CStartSuspendedServices
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Start suspended services
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CGatherEndInstall
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Gather end install, scope: EVERYTHING
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CMigrateFramework
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Migrate framework (Full)
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CMigrateBootSettings
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Migrate boot settings
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CGatherOCs
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Gather Optional Component status
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CApplyOCs
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Apply Optional Component status
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CCreateRegistryForNewSystem
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Create registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\OOBE (value name: InstallType) on the new system
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CProcessDrivers
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Process Drivers for Migration
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CApplyDrivers
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Apply Drivers
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CProcessDrivers
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Process External Drivers
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CSimpleCleanup
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Cleanup external drivers after installation
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CApplyDrivers
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Apply Drivers
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CCreateRegistryForNewSystem
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Create registry key HKLM\SYSTEM\Setup\MoSetup (value name: CorrelationVector) on the new system
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CRegisterSyncProcess
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Register sync process: SetupHost.exe with args /Success /Media /ClientId Media360 /ReportId 17d3dc84-d532-4050-ade9-ae0a9a38c6e0
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CRegisterSyncProcess
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Register sync process: SetupHost.exe with args /RollbackSys /Media /ClientId Media360 /ReportId 17d3dc84-d532-4050-ade9-ae0a9a38c6e0
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: Deserializing operation type: class CRegisterSyncProcess
2025-08-14 07:20:10, Info SP SERIALIZEVERBOSE: After restoring name is: Register sync process: SetupHost.exe with args /RollbackUser /Media /ClientId Media360 /ReportId 17d3dc84-d532-4050-ade9-ae0a9a38c6e0
2025-08-14 07:20:11, Warning SP FindGlobalPath: Cannot find volume name for \\?\GLOBALROOT\Device\HardDisk0\Partition2. Error: 0x00001126
2025-08-14 07:20:11, Warning SP FindGlobalPath: Cannot find volume name for \\?\GLOBALROOT\Device\HardDisk0\Partition5. Error: 0x0000007B
2025-08-14 07:20:11, Warning SP FindGlobalPath: Cannot find volume name for \\?\GLOBALROOT\Device\HardDisk0\Partition6. Error: 0x0000007B
2025-08-14 07:20:11, Info SP SERIALIZEVERBOSE: Deserializing mount data from C:\$WINDOWS.~BT\Sources\mountpaths.dat
2025-08-14 07:20:11, Info SP SERIALIZEVERBOSE: Deserializing mount path type: class CDeploymentBase::CMountedPathInfo
2025-08-14 07:20:11, Info SP SERIALIZEVERBOSE: After restoring mount path is: C:\$WINDOWS.~BT\Sources\SafeOS\SafeOS.Mount
2025-08-14 07:20:11, Info IBSLIB RollbackReinitialize in progress...
2025-08-14 07:20:11, Info IBSLIB RollbackReinitialize finished.
2025-08-14 07:20:11, Info MOUPG MoSetupPlatform: NewSystem object resurrected!
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [STRING] -> [SetupBuildString]=[10.0.19041.3685.amd64fre.vb_release_svc_prod1.231018-1735] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [SetupCompilationType]=[0x0] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [SetupVersionMajor]=[0xA] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [SetupVersionMinor]=[0x0] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [SetupVersionBuildNumber]=[0x4A61] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [SetupVersionCSDBuildNumber]=[0xE65] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [SetupBuildDate]=[0x3866A] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [STRING] -> [SetupBranchName]=[vb_release_svc_prod1] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [SetupBranchHash]=[0x4C0851F0] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [SystemPhysicalMemory]=[0xFEAD50] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [SystemProcessorCount]=[0x4] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [SystemCpuModel]=[0x9] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [SystemProcessorArchitecture]=[0x9] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [STRING] -> [SystemManufacturer]=[Dell Inc.] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [STRING] -> [SystemProductName]=[Inspiron 5548] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [STRING] -> [SystemCpuDescription]=[Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [SourcesFolderTaggedAsHardReserve]=[0x2] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [NativeProcessorArchitecture]=[0x9] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [Setup360Scenario]=[0x1] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [Setup360Mode]=[0x2] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [WindowsLicenseState]=[0x2] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [IsWebSetupCreatedMedia]=[0x1] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [LegacySetupInterrupt]=[0x0] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [SetupMediaDriveType]=[0x5] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [ReflectDrivers]=[0x0] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [PostRollbackContext]=[0x0] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [SetupUpgradeAttempts]=[0x0] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [SetupPriority]=[0x1] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [MediaLayoutTime]=[0x1] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [DUSetupOptIn]=[0x1] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [DUSetupTime]=[0x1D] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [SystemPartitionTotalSpace]=[0x1EF] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [SystemPartitionFreeSpace]=[0x1CC] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [SystemPartitionFreeSpaceWinRe]=[0x1CC] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [CompatBlockEncountered]=[0x0] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [CompatHardBlockedProviders]=[0x0] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [CompatSysReqScanTime]=[0x3F] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [DigitalPKeyCmdUsed]=[0x0] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [PKeyGatherOSStateExitCode]=[0x0] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [PKeyLocationFound]=[0x8] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [PKeyLocationsTried]=[0x82] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [DefaultPKeyUsed]=[0x1] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [PKeyValidateTime]=[0x6] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [UpdateMediaNotSupported]=[0x80] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [EulaTime]=[0x3] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [NewSetupMigChoicesOffered]=[0xB] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [NewSetupMigChoice]=[0x8] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [CompatMigScanTime]=[0x2] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [DUImageOptIn]=[0x1] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [DUImageTime]=[0x44] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [CompatActionableScanTime]=[0x4CB] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [CompatPollingTime]=[0x0] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [CompatInstallReqTime]=[0x4CB] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [OSPartitionInstallDiskSpaceReqWithoutReservesInfo]=[0x3C1C] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [OSPartitionInstallReqFreeSpace]=[0x14955] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [OSPartitionInstallReqTotalSpace]=[0x25800] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [OSPartitionInstallReqRequiredSpace]=[0x3C1C] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [DiskSpaceInstallReqBlocked]=[0x0] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [DiskSpaceInstallReqExtDriveUsed]=[0x0] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [SummaryTime]=[0xDA] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [InstallModeFinalizeSkipped]=[0x0] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [TargetOsImageIndex]=[0x1] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [TargetOsArchitecture]=[0x9] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [TargetOsVersionMajor]=[0xA] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [TargetOsVersionMinor]=[0x0] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [TargetOsVersionBuildNumber]=[0x4A61] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [TargetOsServicePackBuildNumber]=[0xEDB] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [TargetOsServicePackLevel]=[0x0] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [TargetOsAllowPartitionChanges]=[0x1] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [TargetOsAllowUninstall]=[0x1] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [TargetOsCompact]=[0x0] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [TargetOsDisableNEO]=[0x0] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [ImageDeployTime]=[0xCD] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [MigratePackageRemovedFODRetrievalCount]=[0x1] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [DataMigrationTime]=[0xC8] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [DebuggerOptionsTime]=[0x0] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [DriverMigrationTime]=[0x3E] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [HostOsMajorVersion]=[0xA] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [HostOsMinorVersion]=[0x0] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [HostOsBuildNumber]=[0x4A65] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [HostOsArchitecture]=[0x2] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [HostOsStageType]=[0x1] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [HostOsEditionType]=[0x2] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [SetupFailureCount]=[0x2] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [HostOsLanguage]=[0x409] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [HostOsSkuId]=[0x2BD] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [HostOsSuiteMask]=[0x300] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [HostOsProductType]=[0x1] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [HostOsCompact]=[0x0] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [HostOsWimBoot]=[0x0] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [SourceOsMajorVersion]=[0xA] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [SourceOsMinorVersion]=[0x0] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [SourceOsBuildNumber]=[0x4A61] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [SourceOsBuildQFE]=[0x15E8] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [QUADWORD] -> [SetupStartTime]=[0x1dc0d08860ca763] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [STRING] -> [WebSetupClientVersion]=[10.0.19041.572] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [STRING] -> [WebSetupInstanceId]=[ce630d4c-53d3-4743-9efd-67de494eb32d] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [STRING] -> [WuId]=[31091994-52ac-4b21-81f4-f4626aaadffa] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [STRING] -> [PKeyDownlevelInstallChannel]=[Retail] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [STRING] -> [ProductKeyEditionId]=[Core] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [STRING] -> [TargetOsEditionId]=[Core] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [STRING] -> [TargetOsLanguage]=[en-US] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [STRING] -> [TargetOsInstallationType]=[Client] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [STRING] -> [HostOsEditionId]=[Core] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [STRING] -> [HostOsInstallationType]=[Client] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [STRING] -> [HostOsSkuName]=[Windows 10 Home] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [STRING] -> [HostOsBranchName]=[vb_release] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [STRING] -> [SourceOsEditionId]=[Core] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [STRING] -> [SourceOsLanguage]=[en-US] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info CONX ConX::Compatibility::CCompatibilityHost::SetCorrelationVectorwsc:setup: Correlation Vector [PMCtgrg9kkiaJpQw.20.3.0]
2025-08-14 07:20:11, Info CONX ConX::Compatibility::CCompatibilityHost::SetCorrelationVectorwsc:wica: Correlation Vector [PMCtgrg9kkiaJpQw.20.4.0]
2025-08-14 07:20:11, Info CONX Compatibility Finalize called
2025-08-14 07:20:11, Info [0x090008] PANTHR CBlackboard::Open: C:\$WINDOWS.~BT\Sources\Panther\CompatScanCache.dat succeeded.
2025-08-14 07:20:11, Info [0x090009] PANTHR CBlackboard::Close: c:\$windows.~bt\sources\panther\compatscancache.dat.
2025-08-14 07:20:11, Info CONX ConX::Compatibility::CCompatibilityHost:eserializeData: There're 1242 bytes of persisted data for provider wsc:wica:.
2025-08-14 07:20:11, Info [0x090008] PANTHR CBlackboard::Open: C:\$WINDOWS.~BT\Sources\Panther\CompatScanCache.dat succeeded.
2025-08-14 07:20:11, Info [0x090009] PANTHR CBlackboard::Close: c:\$windows.~bt\sources\panther\compatscancache.dat.
2025-08-14 07:20:11, Info CONX ConX::Compatibility::CCompatibilityHost:eserializeData: Successfully deserialized 1242 bytes of persisted data for provider wsc:wica:.
2025-08-14 07:20:11, Info CONX ConX::Compatibility::CCompatibilityHost::SerializeData: Provider wsc:wica: is serializing 1242 bytes of data.
2025-08-14 07:20:11, Info [0x090008] PANTHR CBlackboard::Open: C:\$WINDOWS.~BT\Sources\Panther\CompatScanCache.dat succeeded.
2025-08-14 07:20:11, Info [0x090009] PANTHR CBlackboard::Close: c:\$windows.~bt\sources\panther\compatscancache.dat.
2025-08-14 07:20:11, Info MOUPG Finalize: Requesting ASIMOV upload.
2025-08-14 07:20:11, Info MOUPG Finalize: Remapping install error [0x800703F1] -> [0xC1900108] for telemetry.
2025-08-14 07:20:11, Info MOUPG Finalize: Reporting result value: [0xC1900108]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [Setup360MappedResult]=[0xC1900108] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [Setup360Result]=[0x800703F1] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [Setup360Extended]=[0x50015] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [CUSTOM] -> [WindowsUpdateExit] -> [Media360][6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [CUSTOM] -> [Downlevel] -> [Media360][6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][31091994-52ac-4b21-81f4-f4626aaadffa][][Failed][Windows 10 Home][19045][1][2][0x800703f1][0x50015][19041]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: TraceOneSettingsEvent -> [0x80072EE7][0][os=windows;scenarioId=1;platformEdition=Core;platformInstallationType=Client;sku=101;AppVer=10.0.19041.3685;appBuildLab=vb_release_svc_prod1][][Media360][6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG Finalize: Retrieving downlevel ticks from registry...
2025-08-14 07:20:11, Info MOUPG Finalize: Converting [418] downlevel ticks to seconds...
2025-08-14 07:20:11, Info MOUPG Finalize: Reporting total downlevel time: [2090 seconds]
2025-08-14 07:20:11, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [Setup360DownlevelTime]=[0x82A] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:11, Info MOUPG MoSetupPlatform: Releasing NewSystem object...
2025-08-14 07:20:11, Info Set Watson bucketing parameter #3 to 1
2025-08-14 07:20:11, Info SP CDeploymentBase::CleanupMounts: Unmounting directory C:\$WINDOWS.~BT\Sources\SafeOS\SafeOS.Mount
[5440] Received unmount request for image with guid aef7408d-b7cb-4453-a212-68f4c8070cd5.
[5440] Unmount for image at C:\$WINDOWS.~BT\Sources\SafeOS\SafeOS.Mount complete.
2025-08-14 07:20:23, Info SP Persist diagnostics data for new system for future uploading
2025-08-14 07:20:23, Info Persisting diagnostics data to C:\$WINDOWS.~BT\Sources\Diagnostics\diagnostics.dat
2025-08-14 07:20:23, Info Diagnostics data saved successfully
2025-08-14 07:20:23, Warning SP SPUninitializeNetwork: Not running in Windows PE; will not try to uninitialize network
2025-08-14 07:20:23, Info SP OPERATIONTRACK: CNewSystem Release
2025-08-14 07:20:23, Info MOUPG MoSetupPlatform: NewSystem object released!
2025-08-14 07:20:23, Info MOUPG MoSetupPlatform: Release Identifier -> [FinalizeExit]
2025-08-14 07:20:23, Info MOUPG MoSetupPlatform: Releasing Setup Platform object...
2025-08-14 07:20:23, Info SP Releasing the setup platform
2025-08-14 07:20:23, Info SP StopTelemetry: 1
2025-08-14 07:20:23, Info SP UploadTelemetryData: 0
2025-08-14 07:20:23, Info SP CorrelationVector: PMCtgrg9kkiaJpQw.31
2025-08-14 07:20:23, Info SP Try to merge diagnostics data from default new system data file
2025-08-14 07:20:23, Info Initializing diagnostics helper; data file = C:\$WINDOWS.~BT\Sources\Diagnostics\diagnostics.dat
2025-08-14 07:20:23, Info Found existing diagnostics data, attempting to load it.
2025-08-14 07:20:23, Warning Merging diagnostics data fails since not opted-in
2025-08-14 07:20:23, Info SP Finish merge diagnostics data
2025-08-14 07:20:23, Info SP Start uploading diagnostics data for setup platform
2025-08-14 07:20:23, Info SP Not opted-in to SQM. Diagnostics data will NOT be uploaded
2025-08-14 07:20:23, Info Key CollectTrace is not available.
2025-08-14 07:20:23, Info SP Upload telemetry data based on environment variable
2025-08-14 07:20:23, Info Copy telemetry file: source folder: C:\$WINDOWS.~BT\Sources\Panther, destination folder: C:\ProgramData\Microsoft\Diagnosis\ETLLogs
2025-08-14 07:20:23, Info Copy etl files: source: C:\$WINDOWS.~BT\Sources\Panther\DlTel-Merge.etl, destination: C:\ProgramData\Microsoft\Diagnosis\ETLLogs\DlTel-Merge.etl
2025-08-14 07:20:23, Info pCopyTelemetryFile: Wrote CV PMCtgrg9kkiaJpQw.31 to ETL C:\ProgramData\Microsoft\Diagnosis\ETLLogs\DlTel-Merge.etl:$ETLUNIQUECVDATA
2025-08-14 07:20:23, Info Diagtrack service is running
2025-08-14 07:20:23, Warning Failed to flush queues: 0x800704c6
2025-08-14 07:20:23, Warning Either AlwaysRestartDiagTrack was specified, or ForceUpload failed with error code=0x800704c6, restarting the diagtrack service to upload the etl
2025-08-14 07:20:24, Info Restart Diagtrack service successfully
2025-08-14 07:20:24, Info SP Closing Panther Logging
2025-08-14 07:20:24, Info MOUPG MoSetupPlatform: Setup Platform object released!
2025-08-14 07:20:24, Info MOUPG Finalize: Leaving Execute Method
2025-08-14 07:20:24, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2004]
2025-08-14 07:20:24, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2003]
2025-08-14 07:20:24, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2001]
2025-08-14 07:20:24, Info MOUPG ProgressHandlerAction: Sending final progress message for action [0].
2025-08-14 07:20:24, Info MOUPG ProgressHandlerAction FinalUpdate: 0x0, 0x0 / 0x0, 0x0
2025-08-14 07:20:24, Info MOUPG ProgressHandlerAction: Sending final progress message for action [0].
2025-08-14 07:20:24, Info MOUPG ProgressHandlerAction FinalUpdate: 0x0, 0x0 / 0x0, 0x0
2025-08-14 07:20:24, Info MOUPG Signalling actions thread to shut down.
2025-08-14 07:20:24, Info MOUPG Waiting for actions thread to exit.
2025-08-14 07:20:24, Info MOUPG Actions thread has exited.
2025-08-14 07:20:24, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2004]
2025-08-14 07:20:24, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2000]
2025-08-14 07:20:24, Warning MOUPG CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x3000]
2025-08-14 07:20:24, Info MOUPG DlpTask: Leaving Execute Method
2025-08-14 07:20:24, Info MOUPG SetupManager::ExecuteCustomScript: Type = [0x3]
2025-08-14 07:20:24, Info MOUPG SetupManager::ExecuteCustomScript: No scripts found. Finished type [0x3]
2025-08-14 07:20:24, Info MOUPG SetupNotify: Specifying extended data [0x50015] for error [0x800703F1].
2025-08-14 07:20:24, Info MOUPG CSetupUIManager: Showing error message
2025-08-14 07:20:24, Info MOUPG CInstallUI::ShowErrorMessage: Posted MSG_INSTALLUI_SWITCH_TO_ERROR_PAGE
2025-08-14 07:20:24, Info MOUPG CInstallUI::CInstallUIMessageWindow::SwitchToErrorPage
2025-08-14 07:20:24, Info MOUPG SetupHost: Reporting error event -> [0x800703F1, 0x50015]
2025-08-14 07:20:24, Info MOUPG CInstallUI::SwitchToErrorPage
2025-08-14 07:20:24, Warning MOUPG SetupNotify::ReportEvent - Report ID or Event Reporter not available.
2025-08-14 07:20:24, Info MOUPG SetupManager: FailureCount = [2]
2025-08-14 07:20:24, Info MOUPG SetupManager: Requesting cleanup level [0x2] from parent process.
2025-08-14 07:20:24, Info MOUPG Setup phase change: [SetupPhaseError] -> [SetupPhaseUnpack]
2025-08-14 07:20:24, Info MOUPG SetupManager: Deleting task: [Prepare]...
2025-08-14 07:20:24, Info MOUPG SetupManager: Deleting task: [Install]...
2025-08-14 07:20:24, Info MOUPG SetupManager: Deleting task: [Exit]...
2025-08-14 07:20:24, Info MOUPG SetupManager: Found unpack task! Restarting layout action...
2025-08-14 07:20:24, Info MOUPG CInstallUI::ShowMessageBox: Showing MessageBox
2025-08-14 07:20:24, Error MOUPG CSetupManager::Execute(295): Result = 0x800703F1
2025-08-14 07:20:24, Error MOUPG CSetupHost::Execute(433): Result = 0x800703F1
2025-08-14 07:20:24, Info MOUPG SetupHost: Using Diagnostic tool: ["C:\$WINDOWS.~BT\Sources\SetupDiag.exe" /Scenario:Upgrade /ZipLogs:False /Format:xml /Output:C:\Windows\logs\SetupDiag\SetupDiagResults.xml /RegPath:HKEY_LOCAL_MACHINE\SYSTEM\Setup\SetupDiag\Results]
2025-08-14 07:20:24, Info MOUPG SetupHost: Diagnostic results location: [C:\Windows\logs\SetupDiag\SetupDiagResults.xml]
2025-08-14 07:20:24, Info MOUPG SetupHost: Diagnostic Analysis timeout value: [90000] ms
2025-08-14 07:20:24, Info MOUPG SetupHost: Diagnostic Analysis - START
2025-08-14 07:20:24, Info MOUPG CSetupDiagnostics: Tracing Data [TIME] -> [DiagnosticAnalysisStart]=[2025-08-14 07:20:24] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:34, Info MOUPG SetupHost: Diagnostic tool execution result: [0x0]
2025-08-14 07:20:34, Info MOUPG CSetupDiagnostics: Tracing Data [DWORD] -> [DiagnosticAnalysisResult]=[0x0] [6845ac34-b116-420e-a53b-0cc845176d26][17d3dc84-d532-4050-ade9-ae0a9a38c6e0][][0x1]
2025-08-14 07:20:49, Info MOUPG CInstallUI::Quit: Posted MSG_INSTALLUI_FORCE_QUIT
2025-08-14 07:20:49, Info MOUPG CInstallUI::CInstallUIMessageWindow::ForceQuit
2025-08-14 07:20:49, Info MOUPG Force ending Message pump
2025-08-14 07:20:49, Info MOUPG CInstallUI::ExitInstance
2025-08-14 07:20:49, Info CONX Uninitializing compatibility provider wsc:setup:...
2025-08-14 07:20:49, Info CONX Uninitializing compatibility provider wsc:wica:...
2025-08-14 07:20:49, Info MOUPG SetupUI: Calling PowerClearRequest with type [0x1]...
2025-08-14 07:20:49, Info MOUPG SetupUI: Power request cleared!
2025-08-14 07:20:49, Info MOUPG **************** SetupHost Logging End ****************

PS C:\Windows\System32\WindowsPowerShell\v1.0>

*******

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

Try the new cross-platform PowerShell Install PowerShell on Windows, Linux, and macOS - PowerShell

PS C:\Windows\system32> Get-Content 'C:\Windows\logs\SetupDiag\SetupDiagResults.xml' -Raw | Out-String
<?xml version="1.0" encoding="utf-16"?>
<SetupDiag xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="SetupDiag">
<Version>1.6.0.0</Version>
<ProfileName>FindAbruptDownlevelFailure</ProfileName>
<ProfileGuid>55882B1A-DA3E-408A-9076-23B22A0472BD</ProfileGuid>
<LogErrorLine>2025-08-14 07:20:10, Error DISM DISM Driver Manager: PID=5048 TID=8948 Failed to enumerating driver packages in the driver store. - CDmiDriverStore::GetDriverPackageCollection(hr:0x800703f1)</LogErrorLine>
<FailureData>Error: SetupDiag reports abrupt down-level failure.Last Operation: FinalizeError: 0x800703F1 - 0x50015</FailureData>
<FailureData>LogEntry: 2025-08-14 07:20:10, Error DISM DISM Driver Manager: PID=5048 TID=8948 Failed to enumerating driver packages in the driver store. - CDmiDriverStore::GetDriverPackageCollection(hr:0x800703f1)</FailureData>
<FailureData>Refer to "Tutorial - Debug system error codes - Win32 apps" for error information.</FailureData>
<FailureDetails>ErrorCode = 0x800703F1, ExCode = 0x50015, Oper = Finalize</FailureDetails>
<SetupPhaseInfo>
<PhaseName>Pre-Finalize</PhaseName>
<PhaseStartTime>8/14/2025 7:19:09 AM</PhaseStartTime>
<PhaseEndTime>1/1/0001 12:00:00 AM</PhaseEndTime>
<PhaseTimeDelta>0:00:00:00.0000000</PhaseTimeDelta>
<CompletedSuccessfully>false</CompletedSuccessfully>
</SetupPhaseInfo>
<SetupOperationInfo>
<OperationName>Process Drivers for Migration</OperationName>
<OperationStartTime>8/14/2025 7:20:08 AM</OperationStartTime>
<OperationEndTime>1/1/0001 12:00:00 AM</OperationEndTime>
<OperationTimeDelta>0:00:00:00.0000000</OperationTimeDelta>
<CompletedSuccessfully>false</CompletedSuccessfully>
</SetupOperationInfo>
</SetupDiag>


PS C:\Windows\system32>

 

[ChatGPT]

Thanks — this is the crucial info I needed. The setup logs and SetupDiag show the real cause: Setup fails during the Pre‑Finalize / “Process Drivers for Migration” step because the installer cannot enumerate the Driver Store. In short, Setup can’t read/iterate the driver packages (DISM Driver Manager error CDmiDriverStore::GetDriverPackageCollection hr=0x800703F1) — that’s why the whole upgrade aborts with 0x800703F1.
You’ve already tried many repairs and we repaired the component store (DISM/SFC). The remaining blocker is driver‑store / driver metadata corruption or registry ACLs that prevent enumeration/writes. We can try two next things in order (least invasive → more aggressive). I’ll give exact commands to run and explain what to expect. Do step 1 first and paste the requested outputs; if that doesn’t fix it we’ll go to step 2.
Step 1 — Reset system security descriptors (restore default ACLs) and re-check driver store enumeration
Why: broken registry or file ACLs often stop Setup from reading/writing driver metadata. Resetting to Microsoft defaults is safe and often fixes the driver‑store enumeration errors.

1. Run this as Administrator (copy/paste)
   secedit /configure /cfg %windir%\inf\defltbase.inf /db defltbase.sdb /verbose

• Wait for it to finish. It may take a minute. When done, reboot.

1. After reboot, open an elevated Command Prompt and run these (copy & paste the outputs here):

pnputil /enum-drivers
icacls "C:\Windows\System32\DriverStore\FileRepository" | Out-String
dir /b "C:\Windows\System32\DriverStore\FileRepository" | find /v "" /c (this counts folder entries)
Get-PnpDevice -PresentOnly | findstr /i "Realtek" (PowerShell; paste output; verifies devices present)
Why I ask for those:

• pnputil will show whether Windows can now enumerate the driver packages. If pnputil succeeds and shows many oem*.inf entries, that would likely let Setup proceed.
• icacls shows whether SYSTEM and Admins have full control on the DriverStore folder.
• the dir count gives a sense if FileRepository looks intact or near-empty.

If pnputil now enumerates drivers successfully, try the in‑place upgrade again (mounted ISO → setup.exe) and pick “Keep personal files and apps”. If it still fails, paste the pnputil output and the newest setuperr tail and we proceed.
If Step 1 DOES NOT fix it, proceed to Step 2.
Step 2 — Repair the DriverStore (more invasive) — move the FileRepository out of the way so Windows can recreate a clean store
Why: if the FileRepository contents or driver store registry entries are corrupted beyond ACL repair, Setup’s driver enumeration will keep failing. We can move the repository aside and create an empty one. Windows will then repopulate it on demand (you’ll need to reinstall some drivers), but this often clears the enumeration error blocking setup. You should only do Step 2 if you have your Clonezilla image (you do) and are comfortable reinstalling drivers if needed — I’ll guide you.
IMPORTANT: This operation is potentially disruptive; do it only if Step 1 fails and you accept the risk. I’ll give safe commands you can run from Windows Recovery Environment (WinRE) to avoid files being in use.
A — Boot to WinRE (recommended) — so files are not locked:

• Boot from a Windows install USB or Recovery drive → Troubleshoot → Advanced options → Command Prompt.

B — In WinRE Command Prompt copy/paste exactly:
robocopy "C:\Windows\System32\DriverStore\FileRepository" "D:\DriverStore_Backup" /MIR /COPYALL /R:1 /W:1
(if D: is another drive — if no extra drive available, use C:\DriverStore_Backup instead — but best to use other disk/USB)
rename "C:\Windows\System32\DriverStore\FileRepository" "FileRepository.old"
mkdir "C:\Windows\System32\DriverStore\FileRepository"
icacls "C:\Windows\System32\DriverStore\FileRepository" /grant System:F /grant Administrators:F /t
If robocopy copies successfully, you’ll have a backup; then renaming removes the corrupt repository from active use and creates a blank new one with correct ACLs.
C — Reboot into Windows and verify:

• In elevated CMD:
  pnputil /enum-drivers
  dir /b "C:\Windows\System32\DriverStore\FileRepository" | find /v "" /c

D — Re-run the in‑place upgrade (from mounted ISO) or try to install the Realtek INF via pnputil. Windows will now be able to enumerate driver packages (or at least not be blocked by the corrupt store). You’ll probably need to reinstall some OEM drivers, but you already have the Inspiron driver files.
If Steps 1+2 both fail, the last safe move is an in‑place repair again (we tried) or a clean reinstall — you have Clonezilla so that is viable.
What I need from you now
1) Run the secedit command (one line) as Admin and reboot. Then run and paste the outputs of:

• pnputil /enum-drivers
• icacls "C:\Windows\System32\DriverStore\FileRepository"
• dir /b "C:\Windows\System32\DriverStore\FileRepository" | find /v "" /c

(If any command errors, paste the full error text.)
2) Tell me whether (after step 1) pnputil enumerates multiple oem*.inf driver packages. If yes, retry setup and tell me result.
If after step 1 pnputil still fails / driver store enumeration still fails, tell me and I will give the precise WinRE robocopy/rename commands for Step 2 (I’ll tailor them to your disk letters so you don’t accidentally overwrite anything).
One quick thing while you run Step 1: you can also paste the exact pnputil output you got earlier (you posted some devcon output previously); if it now shows drivers we can proceed quickly.
I’ll stay here and parse the pnputil/icacls outputs the moment you paste them and tell you the safe next command.

 

[glennpm]

Shpuld I still reeboot with this error?

-------------------------------------------
Thursday, August 14, 2025 9:30:03 AM
Warning 5: Access is denied.
Error creating database.
Error 9: The storage control block address is invalid.
----Configuration engine was initialized with one or more errors.----


----Un-initialize configuration engine...

 

[ChatGPT]

Short answer: yes — go ahead and reboot. The secedit message shows it hit some errors while applying the default ACL template, but a reboot is the safe next step and will let Windows finish clearing locks and complete any partial changes. After reboot we’ll verify what succeeded and then continue.
Follow these steps now (exact, ordered — copy/paste where needed)
1) Reboot now

• Do a normal Restart. This clears file locks (the CBS Temp sharing errors you saw) and lets services pick up any ACL changes secedit did manage.

2) After reboot — check secedit result and system health
Open an elevated Command Prompt and run these three quick checks and paste the outputs here:
secedit /export /cfg C:\Users\Public\secedit_export.inf
sfc /scannow
DISM /Online /Cleanup-Image /CheckHealth
(These confirm secedit exported OK, SFC status, and whether the component store is healthy.)
3) Then check the Driver Store ACLs and driver enumeration
Run these (Admin CMD). Paste their outputs:
pnputil /enum-drivers
icacls "C:\Windows\System32\DriverStore\FileRepository"
dir /b "C:\Windows\System32\DriverStore\FileRepository" | find /v "" /c
If pnputil now lists many oem*.inf entries, great — driver enumeration is fixed and you can retry the in‑place upgrade. If pnputil still fails with the same registry/driver‑store error, paste the pnputil output here.
If secedit failed again or the DB error persists
Do not panic — we have safe fallbacks:
A) Retry secedit after fixing permissions on the security DB (only if comfortable)
Open Admin CMD and run:
takeown /f "%windir%\Security\Database" /r /d y
icacls "%windir%\Security\Database" /grant "Administrators":F /t
dir "%windir%\Security\Database"
If that shows files, then re-run:
secedit /configure /cfg %windir%\inf\defltbase.inf /db defltbase.sdb /verbose
Reboot and re-check pnputil and icacls for DriverStore as above.
B) If that still fails — move the DriverStore out of the way from WinRE (I’ll give exact commands)
We’ll do this only if pnputil/DriverStore enumeration still fails after the reboot + secedit retry. It’s more invasive but targeted and usually clears the CDmiDriverStore enumeration error that blocks Setup.
What I recommend right now
1) Reboot.
2) Run the three verification commands I asked for and paste their output here.
3) If you prefer, tell me to skip the secedit retry and go straight to the DriverStore move (WinRE) — I’ll provide step‑by‑step commands tailored to your drive letters.
If you want, reboot now and post the outputs requested in step 2 — I’ll interpret them immediately and give the precise next action.

 

[glennpm]

Directory \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ is owned twice or has its security set twice
Original owner: Microsoft-Windows-shell32, version 10.0.19041.5553, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
New owner: Microsoft-Windows-shell32, version 10.0.19041.5553, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2025-08-14 09:41:43, Info CSI 0000011c Warning: Overlap: Directory \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\ is owned twice or has its security set twice

Original owner: Microsoft-Windows-shell32, version 10.0.19041.5553, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

New owner: Microsoft-Windows-shell32, version 10.0.19041.5553, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2025-08-14 09:41:43, Info CSI 0000011d CSIPERF - FilePI Queue 171ms
2025-08-14 09:41:44, Info CSI 0000011e CSIPERF - FilePI Queue 142ms
2025-08-14 09:41:44, Info CSI 0000011f [SR] Verify complete
2025-08-14 09:41:44, Info CSI 00000120 [SR] Verifying 100 components
2025-08-14 09:41:44, Info CSI 00000121 [SR] Beginning Verify and Repair transaction
2025-08-14 09:41:47, Info CSI 00000122 CSIPERF - FilePI Queue 531ms
2025-08-14 09:41:47, Info CSI 00000123 [SR] Verify complete
2025-08-14 09:41:47, Info CSI 00000124 [SR] Verifying 100 components
2025-08-14 09:41:47, Info CSI 00000125 [SR] Beginning Verify and Repair transaction
2025-08-14 09:41:48, Info CSI 00000126 [SR] Verify complete
2025-08-14 09:41:48, Info CSI 00000127 [SR] Verifying 100 components
2025-08-14 09:41:48, Info CSI 00000128 [SR] Beginning Verify and Repair transaction
2025-08-14 09:41:49, Info CSI 00000129 CSIPERF - FilePI Queue 158ms
2025-08-14 09:41:49, Info CSI 0000012a [SR] Verify complete
2025-08-14 09:41:49, Info CSI 0000012b [SR] Verifying 100 components
2025-08-14 09:41:49, Info CSI 0000012c [SR] Beginning Verify and Repair transaction
2025-08-14 09:41:51, Info CSI 0000012d CSIPERF - FilePI Queue 320ms
2025-08-14 09:41:51, Info CSI 0000012e [SR] Verify complete
2025-08-14 09:41:51, Info CSI 0000012f [SR] Verifying 100 components
2025-08-14 09:41:51, Info CSI 00000130 [SR] Beginning Verify and Repair transaction
2025-08-14 09:41:52, Info CSI 00000131 [SR] Verify complete
2025-08-14 09:41:52, Info CSI 00000132 [SR] Verifying 100 components
2025-08-14 09:41:52, Info CSI 00000133 [SR] Beginning Verify and Repair transaction
2025-08-14 09:41:53, Info CSI 00000134 [SR] Verify complete
2025-08-14 09:41:53, Info CSI 00000135 [SR] Verifying 100 components
2025-08-14 09:41:53, Info CSI 00000136 [SR] Beginning Verify and Repair transaction
2025-08-14 09:41:55, Info CSI 00000137 [SR] Verify complete
2025-08-14 09:41:55, Info CSI 00000138 [SR] Verifying 100 components
2025-08-14 09:41:55, Info CSI 00000139 [SR] Beginning Verify and Repair transaction
2025-08-14 09:41:57, Info CSI 0000013a CSIPERF - FilePI Queue 368ms
2025-08-14 09:41:57, Info CSI 0000013b [SR] Verify complete
2025-08-14 09:41:57, Info CSI 0000013c [SR] Verifying 100 components
2025-08-14 09:41:57, Info CSI 0000013d [SR] Beginning Verify and Repair transaction
2025-08-14 09:41:57, Info CSI 0000013e [SR] Verify complete
2025-08-14 09:41:57, Info CSI 0000013f [SR] Verifying 100 components
2025-08-14 09:41:57, Info CSI 00000140 [SR] Beginning Verify and Repair transaction
2025-08-14 09:41:58, Info CSI 00000141 [SR] Verify complete
2025-08-14 09:41:58, Info CSI 00000142 [SR] Verifying 100 components
2025-08-14 09:41:58, Info CSI 00000143 [SR] Beginning Verify and Repair transaction
2025-08-14 09:41:59, Info CSI 00000144 [SR] Verify complete
2025-08-14 09:41:59, Info CSI 00000145 [SR] Verifying 100 components
2025-08-14 09:41:59, Info CSI 00000146 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:00, Info CSI 00000147 CSIPERF - FilePI Queue 214ms
2025-08-14 09:42:00, Info CSI 00000148 [SR] Verify complete
2025-08-14 09:42:00, Info CSI 00000149 [SR] Verifying 100 components
2025-08-14 09:42:00, Info CSI 0000014a [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:01, Info CSI 0000014b [SR] Verify complete
2025-08-14 09:42:01, Info CSI 0000014c [SR] Verifying 100 components
2025-08-14 09:42:01, Info CSI 0000014d [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:03, Info CSI 0000014e [SR] Verify complete
2025-08-14 09:42:03, Info CSI 0000014f [SR] Verifying 100 components
2025-08-14 09:42:03, Info CSI 00000150 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:04, Info CSI 00000151 [SR] Verify complete
2025-08-14 09:42:04, Info CSI 00000152 [SR] Verifying 100 components
2025-08-14 09:42:04, Info CSI 00000153 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:04, Info CSI 00000154 [SR] Verify complete
2025-08-14 09:42:04, Info CSI 00000155 [SR] Verifying 100 components
2025-08-14 09:42:04, Info CSI 00000156 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:05, Info CSI 00000157 [SR] Verify complete
2025-08-14 09:42:05, Info CSI 00000158 [SR] Verifying 100 components
2025-08-14 09:42:05, Info CSI 00000159 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:06, Info CSI 0000015a [SR] Verify complete
2025-08-14 09:42:06, Info CSI 0000015b [SR] Verifying 100 components
2025-08-14 09:42:06, Info CSI 0000015c [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:07, Info CSI 0000015d CSIPERF - FilePI Queue 107ms
2025-08-14 09:42:07, Info CSI 0000015e [SR] Verify complete
2025-08-14 09:42:07, Info CSI 0000015f [SR] Verifying 100 components
2025-08-14 09:42:07, Info CSI 00000160 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:08, Info CSI 00000161 CSIPERF - FilePI Queue 199ms
2025-08-14 09:42:08, Info CSI 00000162 [SR] Verify complete
2025-08-14 09:42:08, Info CSI 00000163 [SR] Verifying 100 components
2025-08-14 09:42:08, Info CSI 00000164 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:09, Info CSI 00000165 [SR] Verify complete
2025-08-14 09:42:09, Info CSI 00000166 [SR] Verifying 100 components
2025-08-14 09:42:09, Info CSI 00000167 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:10, Info CSI 00000168 [SR] Verify complete
2025-08-14 09:42:10, Info CSI 00000169 [SR] Verifying 100 components
2025-08-14 09:42:10, Info CSI 0000016a [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:11, Info CSI 0000016b [SR] Verify complete
2025-08-14 09:42:11, Info CSI 0000016c [SR] Verifying 100 components
2025-08-14 09:42:11, Info CSI 0000016d [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:11, Info CSI 0000016e [SR] Verify complete
2025-08-14 09:42:11, Info CSI 0000016f [SR] Verifying 100 components
2025-08-14 09:42:11, Info CSI 00000170 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:12, Info CSI 00000171 [SR] Verify complete
2025-08-14 09:42:12, Info CSI 00000172 [SR] Verifying 100 components
2025-08-14 09:42:12, Info CSI 00000173 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:13, Info CSI 00000174 [SR] Verify complete
2025-08-14 09:42:13, Info CSI 00000175 [SR] Verifying 100 components
2025-08-14 09:42:13, Info CSI 00000176 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:14, Info CSI 00000177 [SR] Verify complete
2025-08-14 09:42:14, Info CSI 00000178 [SR] Verifying 100 components
2025-08-14 09:42:14, Info CSI 00000179 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:15, Info CSI 0000017a [SR] Verify complete
2025-08-14 09:42:15, Info CSI 0000017b [SR] Verifying 100 components
2025-08-14 09:42:15, Info CSI 0000017c [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:16, Info CSI 0000017d [SR] Verify complete
2025-08-14 09:42:16, Info CSI 0000017e [SR] Verifying 100 components
2025-08-14 09:42:16, Info CSI 0000017f [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:17, Info CSI 00000180 [SR] Verify complete
2025-08-14 09:42:17, Info CSI 00000181 [SR] Verifying 100 components
2025-08-14 09:42:17, Info CSI 00000182 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:17, Info CSI 00000183 [SR] Verify complete
2025-08-14 09:42:18, Info CSI 00000184 [SR] Verifying 100 components
2025-08-14 09:42:18, Info CSI 00000185 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:18, Info CSI 00000186 [SR] Verify complete
2025-08-14 09:42:18, Info CSI 00000187 [SR] Verifying 100 components
2025-08-14 09:42:18, Info CSI 00000188 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:19, Info CSI 00000189 [SR] Verify complete
2025-08-14 09:42:20, Info CSI 0000018a [SR] Verifying 100 components
2025-08-14 09:42:20, Info CSI 0000018b [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:20, Info CSI 0000018c [SR] Verify complete
2025-08-14 09:42:20, Info CSI 0000018d [SR] Verifying 100 components
2025-08-14 09:42:20, Info CSI 0000018e [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:21, Info CSI 0000018f [SR] Verify complete
2025-08-14 09:42:21, Info CSI 00000190 [SR] Verifying 100 components
2025-08-14 09:42:21, Info CSI 00000191 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:22, Info CSI 00000192 [SR] Verify complete
2025-08-14 09:42:22, Info CSI 00000193 [SR] Verifying 100 components
2025-08-14 09:42:22, Info CSI 00000194 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:23, Info CSI 00000195 [SR] Verify complete
2025-08-14 09:42:23, Info CSI 00000196 [SR] Verifying 100 components
2025-08-14 09:42:23, Info CSI 00000197 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:24, Info CSI 00000198 [SR] Verify complete
2025-08-14 09:42:24, Info CSI 00000199 [SR] Verifying 100 components
2025-08-14 09:42:24, Info CSI 0000019a [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:25, Info CSI 0000019b [SR] Verify complete
2025-08-14 09:42:25, Info CSI 0000019c [SR] Verifying 100 components
2025-08-14 09:42:25, Info CSI 0000019d [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:25, Info CSI 0000019e Warning: Overlap: Directory \??\C:\Windows\SysWOW64\drivers\en-US\ is owned twice or has its security set twice

Original owner: Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.19041.1, arch Host= amd64 Guest= x86, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}

New owner: Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.19041.1, arch Host= amd64 Guest= x86, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}
2025-08-14 09:42:25, Info CSI 0000019f Warning: Overlap: Directory \??\C:\Windows\SysWOW64\wbem\en-US\ is owned twice or has its security set twice

Original owner: Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.19041.1, arch Host= amd64 Guest= x86, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}

New owner: Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.19041.1, arch Host= amd64 Guest= x86, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}
2025-08-14 09:42:25, Info CSI 000001a0 Warning: Overlap: Directory \??\C:\Windows\help\mui\0409\ is owned twice or has its security set twice

Original owner: Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.19041.1, arch Host= amd64 Guest= x86, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}

New owner: Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.19041.1, arch Host= amd64 Guest= x86, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}
2025-08-14 09:42:26, Info CSI 000001a1 [SR] Verify complete
2025-08-14 09:42:26, Info CSI 000001a2 [SR] Verifying 100 components
2025-08-14 09:42:26, Info CSI 000001a3 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:26, Info CSI 000001a4 [SR] Verify complete
2025-08-14 09:42:27, Info CSI 000001a5 [SR] Verifying 100 components
2025-08-14 09:42:27, Info CSI 000001a6 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:27, Info CSI 000001a7 [SR] Verify complete
2025-08-14 09:42:27, Info CSI 000001a8 [SR] Verifying 100 components
2025-08-14 09:42:27, Info CSI 000001a9 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:27, Info CSI 000001aa [SR] Verify complete
2025-08-14 09:42:27, Info CSI 000001ab [SR] Verifying 100 components
2025-08-14 09:42:27, Info CSI 000001ac [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:28, Info CSI 000001ad [SR] Verify complete
2025-08-14 09:42:28, Info CSI 000001ae [SR] Verifying 100 components
2025-08-14 09:42:28, Info CSI 000001af [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:29, Info CSI 000001b0 CSIPERF - FilePI Queue 166ms
2025-08-14 09:42:29, Info CSI 000001b1 CSIPERF - FilePI Queue 104ms
2025-08-14 09:42:30, Info CSI 000001b2 [SR] Verify complete
2025-08-14 09:42:30, Info CSI 000001b3 [SR] Verifying 100 components
2025-08-14 09:42:30, Info CSI 000001b4 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:30, Info CSI 000001b5 [SR] Verify complete
2025-08-14 09:42:30, Info CSI 000001b6 [SR] Verifying 100 components
2025-08-14 09:42:30, Info CSI 000001b7 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:31, Info CSI 000001b8 [SR] Verify complete
2025-08-14 09:42:31, Info CSI 000001b9 [SR] Verifying 100 components
2025-08-14 09:42:31, Info CSI 000001ba [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:33, Info CSI 000001bb [SR] Verify complete
2025-08-14 09:42:33, Info CSI 000001bc [SR] Verifying 100 components
2025-08-14 09:42:33, Info CSI 000001bd [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:34, Info CSI 000001be [SR] Verify complete
2025-08-14 09:42:34, Info CSI 000001bf [SR] Verifying 100 components
2025-08-14 09:42:34, Info CSI 000001c0 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:35, Info CSI 000001c1 [SR] Verify complete
2025-08-14 09:42:35, Info CSI 000001c2 [SR] Verifying 100 components
2025-08-14 09:42:35, Info CSI 000001c3 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:36, Info CSI 000001c4 CSIPERF - FilePI Queue 216ms
2025-08-14 09:42:36, Info CSI 000001c5 [SR] Verify complete
2025-08-14 09:42:36, Info CSI 000001c6 [SR] Verifying 100 components
2025-08-14 09:42:36, Info CSI 000001c7 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:37, Info CSI 000001c8 [SR] Verify complete
2025-08-14 09:42:37, Info CSI 000001c9 [SR] Verifying 100 components
2025-08-14 09:42:37, Info CSI 000001ca [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:38, Info CSI 000001cb [SR] Verify complete
2025-08-14 09:42:38, Info CSI 000001cc [SR] Verifying 100 components
2025-08-14 09:42:38, Info CSI 000001cd [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:39, Info CSI 000001ce [SR] Verify complete
2025-08-14 09:42:39, Info CSI 000001cf [SR] Verifying 100 components
2025-08-14 09:42:39, Info CSI 000001d0 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:40, Info CSI 000001d1 [SR] Verify complete
2025-08-14 09:42:40, Info CSI 000001d2 [SR] Verifying 100 components
2025-08-14 09:42:40, Info CSI 000001d3 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:41, Info CSI 000001d4 Warning: Overlap: Directory \??\C:\Program Files (x86)\ is owned twice or has its security set twice

Original owner: Microsoft-Windows-shell32, version 10.0.19041.5553, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}

New owner: Microsoft-Windows-shell32, version 10.0.19041.5553, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2025-08-14 09:42:41, Info CSI 000001d5 Warning: Overlap: Directory \??\C:\ProgramData\Microsoft\Windows\Start Menu\ is owned twice or has its security set twice

Original owner: Microsoft-Windows-shell32, version 10.0.19041.5553, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}

New owner: Microsoft-Windows-shell32, version 10.0.19041.5553, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2025-08-14 09:42:41, Info CSI 000001d6 Warning: Overlap: Directory \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ is owned twice or has its security set twice

Original owner: Microsoft-Windows-shell32, version 10.0.19041.5553, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}

New owner: Microsoft-Windows-shell32, version 10.0.19041.5553, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2025-08-14 09:42:41, Info CSI 000001d7 Warning: Overlap: Directory \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\ is owned twice or has its security set twice

Original owner: Microsoft-Windows-shell32, version 10.0.19041.5553, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}

New owner: Microsoft-Windows-shell32, version 10.0.19041.5553, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2025-08-14 09:42:41, Info CSI 000001d8 [SR] Verify complete
2025-08-14 09:42:41, Info CSI 000001d9 [SR] Verifying 100 components
2025-08-14 09:42:41, Info CSI 000001da [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:42, Info CSI 000001db [SR] Verify complete
2025-08-14 09:42:42, Info CSI 000001dc [SR] Verifying 100 components
2025-08-14 09:42:42, Info CSI 000001dd [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:43, Info CSI 000001de [SR] Verify complete
2025-08-14 09:42:43, Info CSI 000001df [SR] Verifying 100 components
2025-08-14 09:42:43, Info CSI 000001e0 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:44, Info CSI 000001e1 [SR] Verify complete
2025-08-14 09:42:44, Info CSI 000001e2 [SR] Verifying 100 components
2025-08-14 09:42:44, Info CSI 000001e3 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:45, Info CSI 000001e4 [SR] Verify complete
2025-08-14 09:42:45, Info CSI 000001e5 [SR] Verifying 100 components
2025-08-14 09:42:45, Info CSI 000001e6 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:46, Info CSI 000001e7 CSIPERF - FilePI Queue 221ms
2025-08-14 09:42:46, Info CSI 000001e8 [SR] Verify complete
2025-08-14 09:42:47, Info CSI 000001e9 [SR] Verifying 100 components
2025-08-14 09:42:47, Info CSI 000001ea [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:47, Info CSI 000001eb [SR] Verify complete
2025-08-14 09:42:48, Info CSI 000001ec [SR] Verifying 100 components
2025-08-14 09:42:48, Info CSI 000001ed [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:48, Info CSI 000001ee [SR] Verify complete
2025-08-14 09:42:48, Info CSI 000001ef [SR] Verifying 100 components
2025-08-14 09:42:48, Info CSI 000001f0 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:50, Info CSI 000001f1 [SR] Verify complete
2025-08-14 09:42:50, Info CSI 000001f2 [SR] Verifying 100 components
2025-08-14 09:42:50, Info CSI 000001f3 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:51, Info CSI 000001f4 [SR] Verify complete
2025-08-14 09:42:51, Info CSI 000001f5 [SR] Verifying 100 components
2025-08-14 09:42:51, Info CSI 000001f6 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:52, Info CSI 000001f7 [SR] Verify complete
2025-08-14 09:42:52, Info CSI 000001f8 [SR] Verifying 100 components
2025-08-14 09:42:52, Info CSI 000001f9 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:53, Info CSI 000001fa [SR] Verify complete
2025-08-14 09:42:53, Info CSI 000001fb [SR] Verifying 100 components
2025-08-14 09:42:53, Info CSI 000001fc [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:54, Info CSI 000001fd [SR] Verify complete
2025-08-14 09:42:54, Info CSI 000001fe [SR] Verifying 100 components
2025-08-14 09:42:54, Info CSI 000001ff [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:54, Info CSI 00000200 [SR] Verify complete
2025-08-14 09:42:54, Info CSI 00000201 [SR] Verifying 100 components
2025-08-14 09:42:54, Info CSI 00000202 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:55, Info CSI 00000203 [SR] Verify complete
2025-08-14 09:42:55, Info CSI 00000204 [SR] Verifying 100 components
2025-08-14 09:42:55, Info CSI 00000205 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:56, Info CSI 00000206 CSIPERF - FilePI Queue 227ms
2025-08-14 09:42:56, Info CSI 00000207 [SR] Verify complete
2025-08-14 09:42:56, Info CSI 00000208 [SR] Verifying 77 components
2025-08-14 09:42:56, Info CSI 00000209 [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:57, Info CSI 0000020a [SR] Verify complete
2025-08-14 09:42:57, Info CSI 0000020b [SR] Repairing 0 components
2025-08-14 09:42:57, Info CSI 0000020c [SR] Beginning Verify and Repair transaction
2025-08-14 09:42:57, Info CSI 0000020d [SR] Repair complete
2025-08-14 09:44:59, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2025-08-14 09:44:59, Info CBS TiWorker signaled for shutdown, going to exit.
2025-08-14 09:44:59, Info CBS Deleting the contents of directory: \\?\C:\Windows\CbsTemp
2025-08-14 09:44:59, Info CBS Deletion of: \\?\C:\Windows\CbsTemp successful
2025-08-14 09:44:59, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2025-08-14 09:44:59, Info CBS Execution Engine Finalize
2025-08-14 09:44:59, Info CBS Execution Engine Finalize
2025-08-14 09:44:59, Info CBS Lock: Lock removed: TiWorkerClassFactory, level: 30, total lock:3
2025-08-14 09:44:59, Info CBS Lock: Lock removed: CCbsWorker, level: 5, total lock:2
2025-08-14 09:44:59, Info CBS Ending the TiWorker main loop.
2025-08-14 09:44:59, Info CBS Starting TiWorker finalization.
2025-08-14 09:44:59, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2025-08-14 09:44:59, Info CBS CBS Engine already deactivated
2025-08-14 09:44:59, Info CBS CBS Engine already deactivated
2025-08-14 09:44:59, Info CBS CbsCoreFinalize: ComponentAnalyzerFinalize
2025-08-14 09:44:59, Info CBS CbsCoreFinalize: PackageTrackerFinalize
2025-08-14 09:44:59, Info CBS CbsCoreFinalize: CoreResourcesUnload
2025-08-14 09:44:59, Info CBS CbsCoreFinalize: SessionManagerFinalize
2025-08-14 09:44:59, Info CBS Lock: Lock removed: CSIInventoryCriticalSection, level: 64, total lock:10
2025-08-14 09:44:59, Info CBS Lock: Lock removed: CCbsSessionManager, level: 11, total lock:9
2025-08-14 09:44:59, Info CBS CbsCoreFinalize: CapabilityManagerFinalize
2025-08-14 09:44:59, Info CBS CbsCoreFinalize: PublicObjectMonitorFinalize
2025-08-14 09:44:59, Info CBS CbsCoreFinalize: Enter vCoreInitializeLock
2025-08-14 09:44:59, Info CBS CbsCoreFinalize: WcpUnload
2025-08-14 09:44:59, Info CSI 0000020e Direct SIL provider: Number of files opened: 197189.
2025-08-14 09:44:59, Info CBS CbsCoreFinalize: DrupUnload
2025-08-14 09:44:59, Info CBS CbsCoreFinalize: CfgMgr32Unload
2025-08-14 09:44:59, Info CBS CbsCoreFinalize: DpxUnload
2025-08-14 09:44:59, Info CBS CbsCoreFinalize: SrUnload
2025-08-14 09:44:59, Info CBS CbsCoreFinalize: CbsEsdUnload
2025-08-14 09:44:59, Info CBS CbsCoreFinalize: CbsTraceInfoUninitialize
2025-08-14 09:44:59, Info CBS CbsCoreFinalize: CbsEventUnregister
2025-08-14 09:44:59, Info CBS CbsCoreFinalize: AppContainerUnload
2025-08-14 09:44:59, Info CBS CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2025-08-14 09:44:59, Info CBS Ending TiWorker finalization.
2025-08-14 09:44:59, Info CBS Ending the TrustedInstaller main loop.
2025-08-14 09:44:59, Info CBS Starting TrustedInstaller finalization.
2025-08-14 09:44:59, Info CBS Lock: Lock removed: WinlogonNotifyLock, level: 8, total lock:6
2025-08-14 09:44:59, Info CBS Ending TrustedInstaller finalization.
2025-08-14 09:48:00, Info CBS TI: --- Initializing Trusted Installer ---
2025-08-14 09:48:00, Info CBS TI: Last boot time: 2025-08-14 09:35:21.500
2025-08-14 09:48:00, Info CBS Starting TrustedInstaller initialization.
2025-08-14 09:48:00, Info CBS Lock: New lock added: CCbsPublicSessionClassFactory, level: 30, total lock:4
2025-08-14 09:48:00, Info CBS Lock: New lock added: CCbsPublicSessionClassFactory, level: 30, total lock:5
2025-08-14 09:48:00, Info CBS Lock: New lock added: WinlogonNotifyLock, level: 8, total lock:6
2025-08-14 09:48:00, Info CBS Ending TrustedInstaller initialization.
2025-08-14 09:48:00, Info CBS Starting the TrustedInstaller main loop.
2025-08-14 09:48:00, Info CBS TrustedInstaller service starts successfully.
2025-08-14 09:48:00, Info CBS No startup processing required, TrustedInstaller service was not set as autostart
2025-08-14 09:48:00, Info CBS Startup processing thread terminated normally
2025-08-14 09:48:00, Info CBS TI: Startup Processing completes, release startup processing lock.
2025-08-14 09:48:00, Info CBS Starting TiWorker initialization.
2025-08-14 09:48:00, Info CBS Lock: New lock added: TiWorkerClassFactory, level: 30, total lock:2
2025-08-14 09:48:00, Info CBS Ending TiWorker initialization.
2025-08-14 09:48:00, Info CBS Starting the TiWorker main loop.
2025-08-14 09:48:00, Info CBS TiWorker starts successfully.
2025-08-14 09:48:00, Info CBS Lock: New lock added: CCbsWorker, level: 5, total lock:3
2025-08-14 09:48:00, Info CBS Universal Time is: 2025-08-14 13:48:00.945
2025-08-14 09:48:00, Info CBS Loaded Servicing Stack v10.0.19041.6088 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.6088_none_7e3cb1287c69f05e\cbscore.dll
2025-08-14 09:48:00, Info CBS Build: 19041.1.amd64fre.vb_release.191206-1406
2025-08-14 09:48:00, Info CSI 00000001@2025/8/14:13:48:00.945 WcpInitialize: wcp.dll version 10.0.19041.6088 (WinBuild.160101.0800)
2025-08-14 09:48:00, Info CBS Lock: New lock added: CCbsSessionManager, level: 11, total lock:9
2025-08-14 09:48:00, Info CBS Lock: New lock added: CSIInventoryCriticalSection, level: 64, total lock:10
2025-08-14 09:48:00, Info CBS NonStart: Set pending store consistency check.
2025-08-14 09:48:00, Info CBS Session: 31198498_215287709 initialized by client DISM Package Manager Provider, external staging directory: (null), external registry directory: (null)
2025-08-14 09:50:02, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2025-08-14 09:50:02, Info CBS TiWorker signaled for shutdown, going to exit.
2025-08-14 09:50:02, Info CBS Deleting the contents of directory: \\?\C:\Windows\CbsTemp
2025-08-14 09:50:02, Info CBS Deletion of: \\?\C:\Windows\CbsTemp successful
2025-08-14 09:50:02, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2025-08-14 09:50:02, Info CBS Execution Engine Finalize
2025-08-14 09:50:02, Info CBS Execution Engine Finalize
2025-08-14 09:50:02, Info CBS Lock: Lock removed: TiWorkerClassFactory, level: 30, total lock:3
2025-08-14 09:50:02, Info CBS Lock: Lock removed: CCbsWorker, level: 5, total lock:2
2025-08-14 09:50:02, Info CBS Ending the TiWorker main loop.
2025-08-14 09:50:02, Info CBS Starting TiWorker finalization.
2025-08-14 09:50:02, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2025-08-14 09:50:02, Info CBS CBS Engine already deactivated
2025-08-14 09:50:02, Info CBS CBS Engine already deactivated
2025-08-14 09:50:02, Info CBS CbsCoreFinalize: ComponentAnalyzerFinalize
2025-08-14 09:50:02, Info CBS CbsCoreFinalize: PackageTrackerFinalize
2025-08-14 09:50:02, Info CBS CbsCoreFinalize: CoreResourcesUnload
2025-08-14 09:50:02, Info CBS CbsCoreFinalize: SessionManagerFinalize
2025-08-14 09:50:02, Info CBS Lock: Lock removed: CSIInventoryCriticalSection, level: 64, total lock:10
2025-08-14 09:50:02, Info CBS Lock: Lock removed: CCbsSessionManager, level: 11, total lock:9
2025-08-14 09:50:02, Info CBS CbsCoreFinalize: CapabilityManagerFinalize
2025-08-14 09:50:02, Info CBS CbsCoreFinalize: PublicObjectMonitorFinalize
2025-08-14 09:50:02, Info CBS CbsCoreFinalize: Enter vCoreInitializeLock
2025-08-14 09:50:02, Info CBS CbsCoreFinalize: WcpUnload
2025-08-14 09:50:02, Info CBS CbsCoreFinalize: DrupUnload
2025-08-14 09:50:02, Info CBS CbsCoreFinalize: CfgMgr32Unload
2025-08-14 09:50:02, Info CBS CbsCoreFinalize: DpxUnload
2025-08-14 09:50:02, Info CBS CbsCoreFinalize: SrUnload
2025-08-14 09:50:02, Info CBS CbsCoreFinalize: CbsEsdUnload
2025-08-14 09:50:02, Info CBS CbsCoreFinalize: CbsTraceInfoUninitialize
2025-08-14 09:50:02, Info CBS CbsCoreFinalize: CbsEventUnregister
2025-08-14 09:50:02, Info CBS CbsCoreFinalize: AppContainerUnload
2025-08-14 09:50:02, Info CBS CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2025-08-14 09:50:02, Info CBS Ending TiWorker finalization.
2025-08-14 09:50:02, Info CBS Ending the TrustedInstaller main loop.
2025-08-14 09:50:02, Info CBS Starting TrustedInstaller finalization.
2025-08-14 09:50:02, Info CBS Lock: Lock removed: WinlogonNotifyLock, level: 8, total lock:6
2025-08-14 09:50:02, Info CBS Ending TrustedInstaller finalization.

 

[ChatGPT]

Thanks — the logs show SFC/DISM finished their repair work (good) but SFC warned about a few overlapping ownership entries (harmless warnings). The key remaining blocker is the driver‑store enumeration error that previously caused Setup to abort. Let’s check whether the driver store is now readable and, if not, move it aside and create a clean one so Setup can finish.
Do these checks now (least‑risk). Copy/paste each command into an elevated Command Prompt or PowerShell and paste the outputs here if anything looks unexpected.
1) Verify driver store enumeration (critical)
Run (Admin CMD):
pnputil /enum-drivers

• Expected good result: a long list of oem*.inf entries (driver packages).
• If you get errors (0x3f1 / 0x800703F1 or similar), paste the exact output here.

2) Check permissions on the DriverStore
Run (Admin CMD):
icacls "C:\Windows\System32\DriverStore\FileRepository"
Run this count too:
dir /b "C:\Windows\System32\DriverStore\FileRepository" | find /v "" /c

• icacls should show SYSTEM and Administrators with FullControl (F). If ACLs look incorrect or show ACCESS DENIED, tell me the output.

If pnputil now enumerates drivers successfully

• Good — try the in‑place upgrade again from your mounted ISO (run setup.exe as Administrator) with Clean Boot active and “Don’t download updates” on first attempt. If it fails, paste the new setuperr tail (we’ll parse).

If pnputil still fails or you get access errors on DriverStore

• We’ll move the DriverStore out of the way (WinRE) so Windows can recreate a clean repo. This is a safe, targeted repair but has consequences: you may need to reinstall a few drivers afterwards (you already have the Dell driver pack). Only proceed if you’re comfortable and you keep your Clonezilla image (you do).

Step 3 — Backup & move DriverStore (WinRE) — instructions
Important: perform this from WinRE/Recovery or Booting from a Windows USB so the DriverStore files aren’t in use.
A) Boot to WinRE

• Insert your Windows install USB → Boot → Troubleshoot → Advanced options → Command Prompt.

B) Identify drive letters in WinRE
In the WinRE prompt run:
diskpart
list volume
exit
Note the letter for the Windows OS volume (usually C: in normal boot, but could be different in WinRE). Also note a different volume (USB or other internal disk) you can copy backup to — I’ll call it D: below. If you have no second disk/USB, you can backup onto C: but external is safer.
C) Back up FileRepository (copy whole repo)
Run (adjust letters if needed):
robocopy "C:\Windows\System32\DriverStore\FileRepository" "D:\DriverStore_Backup" /MIR /COPYALL /R:1 /W:1 /LOG:"D:\DriverStoreBackupLog.txt"

• This mirrors the entire folder to D:\DriverStore_Backup and logs actions. If robocopy reports errors, paste the log.

D) Rename and recreate a blank FileRepository
Run:
rename "C:\Windows\System32\DriverStore\FileRepository" "FileRepository.old"
mkdir "C:\Windows\System32\DriverStore\FileRepository"
icacls "C:\Windows\System32\DriverStore\FileRepository" /grant "SYSTEM:F" /grant "Administrators:F" /t
E) Reboot to Windows normally

• After boot, check:

pnputil /enum-drivers
dir /b "C:\Windows\System32\DriverStore\FileRepository" | find /v "" /c
icacls "C:\Windows\System32\DriverStore\FileRepository"

• If pnputil now enumerates (or at least does not error), run setup.exe from the mounted ISO and proceed with the in‑place upgrade.

F) Reinstall drivers if needed

• If Windows complains about missing drivers after the change, install the Dell driver package you downloaded:
  pnputil /add-driver "D:\Reference...\WIN10\64*.inf" /install
• Reboot.

Notes / cautions

• Back up before Step 3 — you have Clonezilla (good). The robocopy step makes a driver backup too.
• Moving the DriverStore means Windows will need to re-populate it as drivers are installed; keep the Dell driver set ready.
• If Disk/WinRE letters differ, substitute the correct letters. If you’re unsure, paste the output of diskpart list volume and I’ll give exact commands with your letters.

If you prefer to try one more non‑invasive attempt first

• Run pnputil /enum-drivers and icacls (Step 1 & 2). If pnputil still errors, we should go to the WinRE move.

Tell me the pnputil / icacls outputs now. If pnputil lists drivers, retry the upgrade and tell me the result. If it errors, say “I’m ready to do the WinRE move” and paste the output of diskpart list volume so I create the exact robocopy/rename commands for your system.

 

[glennpm]

D:\Temp>pnputil /enum-drivers
Microsoft PnP Utility

Failed to enumerate driver packages: The configuration registry database is corrupt.

 

[ChatGPT]

Thanks — that pnputil output confirms Windows still can’t enumerate the driver store because the configuration/driver metadata is corrupted. The next step that almost always fixes this is to move the DriverStore FileRepository out of the way and create a fresh, empty FileRepository that Windows (and Setup) can enumerate — then reinstall any missing drivers. Because this touches the driver store it’s a potentially disruptive action, so I’ll give a precise, safe sequence and explain every step. You already have a Clonezilla image, so you have a recovery path — good.
Before you start — choose the backup target

• Do you have an external USB drive you can use to hold the backup copy of the current DriverStore? (recommended)
• If not, we can copy the DriverStore to another internal drive letter (D. You previously used D:\Temp, so D: exists. Copying to the same physical disk is less ideal but acceptable if you don’t have an external disk.

Tell me which you’ll use:

• “USB” (I’ll assume the external drive letter is E: or tell me the actual letter), or
• “Use D:” (we’ll use D:\DriverStore_Backup)

Once you confirm the backup destination I’ll give the exact WinRE commands to paste (one block). If you prefer, I’ll show the commands now with placeholders and you can substitute the drive letter.
What I will do when you confirm

• Give an exact WinRE command list (diskpart to verify letters, robocopy to back up the repository, rename to remove the corrupt store, create new FileRepository folder, set ACLs), plus the follow-up checks in Windows and the driver reinstall steps (pnputil commands) and how to retry the in-place upgrade.

If you want to proceed, reply with the backup target (e.g., “Use D:” or “Use E: (external)”) and I’ll post the exact, copy/paste WinRE commands and the exact post‑reboot commands to run.
If you’d rather not move the DriverStore yet and want one more low‑impact try:

• I can walk you through running pnputil as SYSTEM one more time (PsExec), or re‑run secedit with the takeown/icacls steps — but given the persistent pnputil error, the DriverStore move is the fix most people need at this stage.

Which do you want: move DriverStore now (tell me backup drive letter) or try another low‑impact attempt first?

 

[glennpm]

F:\DriverStore_BAK

 

[ChatGPT]

Good — thanks. Since you picked F:\DriverStore_BAK as the backup target, here are the exact, safe WinRE commands to back up the current DriverStore, remove the corrupt store from active use, create a fresh empty store with correct ACLs, and the post‑boot checks & driver reinstall steps.
Important notes before you start

• You already have a Clonezilla image — great. This procedure is effective but will require reinstalling any OEM drivers that Windows can’t find automatically.
• Make sure F: really is the drive you intend to use — confirm in WinRE with diskpart before copying. If F: is wrong, stop and tell me the correct letter.
• Do this from WinRE (boot from Windows install USB → Troubleshoot → Advanced options → Command Prompt). I give precisely the commands to paste into that WinRE Command Prompt.

WinRE command block — copy/paste these lines in order
(Replace F: only if your intended backup drive letter differs.)
diskpart
list vol
exit
REM -- Confirm the Windows volume letter (usually C and that F: exists. If DiskPart shows different letters, use those instead below.
REM -- Make a backup of the FileRepository to F:\DriverStore_BAK
robocopy "C:\Windows\System32\DriverStore\FileRepository" "F:\DriverStore_BAK" /MIR /COPYALL /R:2 /W:1
REM -- If robocopy reported success, rename the live repository (this takes it out of use)
rename "C:\Windows\System32\DriverStore\FileRepository" "FileRepository.old"
REM -- Create a fresh empty repository and set ACLs
mkdir "C:\Windows\System32\DriverStore\FileRepository"
icacls "C:\Windows\System32\DriverStore\FileRepository" /grant "SYSTEM":F /grant "Administrators":F /T
REM -- Verify folder exists and ACLs applied
dir "C:\Windows\System32\DriverStore"
icacls "C:\Windows\System32\DriverStore\FileRepository"
REM -- Exit WinRE and reboot to Windows
wpeutil reboot
What each step does (brief)

• diskpart/list vol: verify drive letters (do this and check the letters shown).
• robocopy /MIR /COPYALL: makes a faithful backup of FileRepository contents to F:\DriverStore_BAK.
• rename FileRepository -> FileRepository.old: removes the corrupt store from active use without deleting it.
• mkdir + icacls: creates an empty FileRepository and ensures SYSTEM and Administrators have full control.
• reboot: returns you to normal Windows where we can verify.

After reboot — post‑WinRE checks (run as Administrator; paste output)
1) Check driver enumeration:
pnputil /enum-drivers
2) Confirm new FileRepository is empty (or enumerates):
dir /b "C:\Windows\System32\DriverStore\FileRepository" | find /v "" /c
3) Check ACLs:
icacls "C:\Windows\System32\DriverStore\FileRepository"
Expected results

• pnputil should not return the “configuration registry database is corrupt” error anymore and should either list driver packages or at least run without error.
• dir count will likely be small (fresh empty store) — Windows will populate as drivers get installed.
• icacls should show SYSTEM and Administrators with Full control.

Reinstall drivers (recommended)
You already downloaded the Dell drivers. After the new store is in place, reinstall the vendor drivers using the INF files (example commands — adjust path to where you put the driver files):
REM example: install all .inf files from your driver folder (change path as needed)
pnputil /add-driver "D:\Reference\Computer\Inspiron_laptop_i15-5548\Drivers\Win10\64*.inf" /install
Or install the single Realtek INF explicitly:
pnputil /add-driver "D:\Reference\Computer\Inspiron_laptop_i15-5548\Drivers\WIN10\64\rt640x64.inf" /install
Then reboot.
Retry the in‑place upgrade

• Mount the fresh Windows 10 22H2 ISO and run setup.exe as Admin → choose Keep personal files and apps. Try with “Don’t download updates” first. If upgrade still fails, capture the same set of logs (setuperr tail, setupact tail, SetupDiag XML) and paste them.

If robocopy fails or you can’t use F:

• Tell me the diskpart output (paste it) and I’ll tailor the backup path.
• If there’s insufficient free space on F:, we can copy fewer items (e.g., only copy FileRepository.old’s largest folders) — I’ll guide that.

If you prefer a less invasive method first

• I can try one last secedit / ownership attempt (takeown + icacls on the Security DB) and rerun secedit, but given pnputil still reports the same registry/db corruption, the FileRepository rename is the most reliable fix.

When you’re ready

• Confirm you’ll run the WinRE commands above and that F: is the correct backup drive (or give the correct letter).
• After you run them and reboot, paste the outputs of pnputil /enum-drivers and icacls for the new repository and I’ll guide the driver reinstall and retry of the upgrade.

If you want, I can also provide the exact pnputil lines to install the Dell driver set you already downloaded — tell me the folder path on your Windows system and I’ll produce the command exactly.

 

[glennpm]

I stopped the backup due to many "Access denied", for example

Waiting 1 seconds... Retrying...
New File 9620 adobepdf.PNF
2025/08/14 10:05:23 ERROR 5 (0x00000005) Copying File C:\Windows\System32\DriverStore\FileRepository\adobepdf.inf_amd64_6376be62e8c4244f\adobepdf.PNF
Access is denied.

ERROR: RETRY LIMIT EXCEEDED.

New Dir 5 C:\Windows\System32\DriverStore\FileRepository\adobepdf.inf_amd64_6376be62e8c4244f\Amd64\
New File 66 ADGELP.INI
2025/08/14 10:05:23 ERROR 5 (0x00000005) Copying File C:\Windows\System32\DriverStore\FileRepository\adobepdf.inf_amd64_6376be62e8c4244f\Amd64\ADGELP.INI
Access is denied.
Waiting 1 seconds... Retrying...
New File 66 ADGELP.INI
2025/08/14 10:05:24 ERROR 5 (0x00000005) Copying File C:\Windows\System32\DriverStore\FileRepository\adobepdf.inf_amd64_6376be62e8c4244f\Amd64\ADGELP.INI
Access is denied.
Waiting 1 seconds... Retrying...
New File 66 ADGELP.INI
2025/08/14 10:05:25 ERROR 5 (0x00000005) Copying File C:\Windows\System32\DriverStore\FileRepository\adobepdf.inf_amd64_6376be62e8c4244f\Amd64\ADGELP.INI
Access is denied.

ERROR: RETRY LIMIT EXCEEDED.

New File 28058 ADPDF9.PPD
2025/08/14 10:05:25 ERROR 5 (0x00000005) Copying File C:\Windows\System32\DriverStore\FileRepository\adobepdf.inf_amd64_6376be62e8c4244f\Amd64\ADPDF9.PPD

 

[ChatGPT]

Thanks — that Access Denied from robocopy is expected if you ran the copy while Windows was running (files in use / protected by ACLs). Don’t worry — we can do this safely. The reliable method is to do the backup / rename from WinRE (Windows Recovery Environment) where the running OS hasn’t locked the DriverStore. I’ll give you a short, exact procedure you can paste into the WinRE Command Prompt — it includes a permission fix (takeown/icacls) and a robust robocopy using backup mode. If any step errors, paste the error text and I’ll adjust.
Important: run these from WinRE, not while booted into Windows

• Boot using your Windows install USB (or the Recovery drive) → Troubleshoot → Advanced options → Command Prompt.
• Confirm the drive letters shown by diskpart (they can differ in WinRE).

Exact WinRE command sequence
(verify F: is your backup drive; if different, replace F
diskpart
list vol
exit
REM confirm Windows is on C: and F: is present — if diskpart showed different letters, use those
REM take ownership & grant permissions (so robocopy can read protected files)
takeown /f "C:\Windows\System32\DriverStore\FileRepository" /r /d Y
icacls "C:\Windows\System32\DriverStore\FileRepository" /grant "NT AUTHORITY\SYSTEM":F /grant "Administrators":F /t
REM robust backup using backup mode (/B) and preserve ACLs & attributes
robocopy "C:\Windows\System32\DriverStore\FileRepository" "F:\DriverStore_BAK" /MIR /COPYALL /B /R:2 /W:1 /NFL /NDL /V /LOG:F:\DriverStore_Backup_Log.txt
REM after robocopy completes, rename the live repository out of the way
rename "C:\Windows\System32\DriverStore\FileRepository" "FileRepository.old"
REM create a fresh repository and set ACLs
mkdir "C:\Windows\System32\DriverStore\FileRepository"
icacls "C:\Windows\System32\DriverStore\FileRepository" /grant "NT AUTHORITY\SYSTEM":F /grant "Administrators":F /T
REM show results and log
dir "C:\Windows\System32\DriverStore"
icacls "C:\Windows\System32\DriverStore\FileRepository"
type F:\DriverStore_Backup_Log.txt
REM reboot into Windows
wpeutil reboot
What to expect and troubleshooting notes

• Running takeown + icacls in WinRE ensures robocopy has permission to read files normally protected by TrustedInstaller. The /B switch runs robocopy in Backup mode which helps bypass some ACL restrictions (WinRE/System context required).
• If robocopy still returns Access Denied for a small subset, copy will continue for the rest; the log file F:\DriverStore_Backup_Log.txt will show any failures. Paste that file here if errors appear.
• If robocopy cannot copy a lot of files or fails due to I/O, tell me the exact error and the diskpart output (so we can check the target drive health/space).
• If backup is impossible (no space / persistent denies), you can skip the backup and rename the live folder directly (rename is quick and usually works in WinRE). That loses the copy but still unblocks Setup.

After reboot (what I’ll have you run in Windows)
Open an elevated CMD and run (paste outputs here):
pnputil /enum-drivers
dir /b "C:\Windows\System32\DriverStore\FileRepository" | find /v "" /c
icacls "C:\Windows\System32\DriverStore\FileRepository"

• If pnputil no longer errors, attempt the in‑place upgrade (setup.exe from the mounted ISO) or install your Realtek INF via:
  pnputil /add-driver "D:\Reference...\rt640x64.inf" /install

If pnputil still errors, paste the pnputil error text and the output of the three checks above; I’ll provide the next steps (we may try another ACL fix or a direct registry/driver-store surgery).
If you want me to provide the WinRE commands again as a single copy/paste block for you to run now, say “Ready — give me the WinRE block” and I’ll paste the same block. If you prefer to rename without backup (faster), tell me “Skip backup — rename now” and I’ll give the smaller set of commands to run in WinRE.
Which do you want to do now — (A) run the WinRE sequence with robocopy backup to F:, or (B) skip the backup and rename the FileRepository.old right away?

 

[glennpm]

Good, I'll start now.

Do you ever take a "electron break", a.k.a., "cpffee break"