Windows 10: variety of BSoD on win 10 v2004

I am getting a variety of BSoD errors - each time I reboot my session lasts for a while and then crashes with a new message (lately '21a' seems to be the most prevalent). I am at v2004 (H1) of Windows 10 Pro.

When I do a 'sfc /scannow' I get this error upon completion:
Windows Resource Protection found corrupt files but was unable to fix some of them.For online repairs, details are included in the CBS log file located atwindir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offlinerepairs, details are included in the log file provided by the /OFFLOGFILE flag.

I'm guessing this is related to my BSoD problems.
Is there a way I can find the corrupt files and replace them?

Thanks in advance to all who reply.
Dan

:)

 

Storage Pool with Windows 10 v2004

I found a workaround solution: I installed Win 10 v1909, created the storage pool and then upgraded to v2004. No problem.

So I believe this confirms my suspicion that the problem is in the v2004 "Create Pool" function.

 

Win 10 BSOD after reducing number of CPUs

• Win 10 x64 running in VMware Fusion VM on MacBook Pro w/ 6 physical cores & HT.
• When VM is configured with 5+ CPUs, Windows runs fine.
• When VM is configured with 4 or fewer, BSOD INVALID SYSTEM CONFIG INFO
  • WINLOAD.EFI missing or corrupted
  • Attempt to repair using ISO image fails

OS X 10.15.4, VMware Fusion Pro 11.5.3

Win 10 Enterprise

Version 1703

Build 15063.2108

Any suggestions appreciated, as I need to move this VM to another HW config with fewer physical CPUs.

Thanks!

 

Robocopy broken in Win 10 v2004?

Is robocopy in Win 10 v2004 totally borked?

I have been using a batch file for 5 years now to robocopy my documents, desktop, etc to a folder on my Synology NAS. I bought a new Dell, upgraded it to v2004 (kicking myself). I changed my script to robocopy from my NAS to my new PC. Everything appeared
in the "failed" column. Eventually, running out of ideas, I copied robocopy.exe from my old Dell (Win 10 v1909) and ran the same batch file using the old robocopy. Everything looks like it copied! But the log file generated had nearly no data inside and
the format was a mess.

\\nas\home\robocopy \\nas\home\desktop %userprofile%\desktop /E /DCOPY:T /COPYAT /EFSRAW /R:1 /W:3 /NP /log+:%userprofile%\documents\xfer_data.log

Once I got the data transferred to the new PC, I tried the script to back up data TO the NAS again. Nothing copied. Meanwhile, the ancient SyncToy still works like a champ.