You probably know you need the system to be using UEFI Secure Boot with the CSM disabled.  In addition, you need a TPM 2.0 enabled.

When you try the upgrade, it should give some type of error.  If it does not, all I can suggest is go the linked site and download and run the setupdiag.exe utility.  It will create a folder containing files we may need and a report you can copy and paste.  The utility depends on an upgrade being tried recently so it can gather the necessary files.

The report might help but we may need additional files from that folder, like the setupact.log.

https://docs.microsoft.com/en-us/windows/deployment/upgrade/setupdiag

Thanks for helping.

The upgrade to W11 fails at 75% with a bluescreen INVALID_DATA_ACCESS_TRAP error.

I run the setupdiag.exe you linked but I cannot copy and paste or attach files here. How can I share the Logs.zip with you safely?

Here you can find the Logs.zip:
https://1drv.ms/u/s!AvnP7SM2WcvMoasYcYSgFaE-l1sW-g?e=v2ap1h

Also checking the setupmem.dmp:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

INVALID_DATA_ACCESS_TRAP (4)
Arguments:
Arg1: 0000000000000000
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2640

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 36505

    Key  : Analysis.Init.CPU.mSec
    Value: 906

    Key  : Analysis.Init.Elapsed.mSec
    Value: 148146

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 106

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x4

    Key  : Bugcheck.Code.Register
    Value: 0x4

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1


FILE_IN_CAB:  setupmem.dmp

BUGCHECK_CODE:  4

BUGCHECK_P1: 0

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  cbservice.exe

STACK_TEXT:  
ffffd502`bae4ece8 fffff806`8d86e954     : 00000000`00000000 ffff8002`9063cee0 ffffffff`8000266c fffff806`8d868430 : nt!KeBugCheck
ffffd502`bae4ecf0 fffff806`8d86ef99     : ffffb30e`4b2fa000 fffff806`76252092 ffffffff`ffffffff fffff806`7632e05d : WinSetupMon!HandleOperation+0x540
ffffd502`bae4eec0 fffff806`73217034     : 00000000`00000001 ffffb30e`4d9519a0 00000000`00000020 ffffd502`bae4efc9 : WinSetupMon!WinSetupMonPreSetInformation+0x59
ffffd502`bae4ef20 fffff806`73216ae6     : ffffd502`bae4f110 ffffb30e`29602406 ffffb30e`4fe66e00 00000000`00000000 : FLTMGR!FltpPerformPreCallbacksWorker+0x374
ffffd502`bae4f030 fffff806`73215b72     : ffffd502`bae50000 ffffd502`bae49000 00000000`00000000 ffffd502`bae4f120 : FLTMGR!FltpPassThroughInternal+0xc6
ffffd502`bae4f080 fffff806`732158fb     : 00000000`00000004 00000000`00000000 ffffd502`00000001 ffffb30e`51c72c20 : FLTMGR!FltpPassThrough+0x1c2
ffffd502`bae4f0f0 fffff806`76253be5     : 00000000`00000000 00000000`00000001 00000000`00000608 fffff806`00000000 : FLTMGR!FltpDispatch+0x8b
ffffd502`bae4f150 fffff806`7623f869     : ffffffff`ffffffff 00000000`007b3168 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x55
ffffd502`bae4f190 fffff806`762400da     : 00000000`00000004 00000000`00000040 ffffd502`bae4f420 ffffb30e`42536f49 : nt!IopCallDriverReference+0xf9
ffffd502`bae4f200 fffff806`76429e75     : 00000000`000003a8 00000000`2a66fc78 00000000`2a66fc70 00000000`00000004 : nt!NtSetInformationFile+0x52a
ffffd502`bae4f330 00007ffe`550c4394     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000000`2a66fc38 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`550c4394


SYMBOL_NAME:  WinSetupMon!HandleOperation+540

MODULE_NAME: WinSetupMon

IMAGE_NAME:  WinSetupMon.sys

IMAGE_VERSION:  10.0.22000.5

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  540

FAILURE_BUCKET_ID:  0x4_WinSetupMon!HandleOperation

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3bbebac1-3bd8-8305-09ab-79aea9f2838a}

Followup:     MachineOwner
---------

I tried the list of commands but it's still disabled:

REAGENTC.EXE: The Windows RE image was not found

EDIT: I successfully enabled the recovery option

OK, if the upgrade ever completes, it may repair that problem. Since I have not found anything other than the dump file indications, it may work if that problem is taken care of.  Otherwise, we will try to find the location of the Winre.wim file which should be in the Recovery Tools partition as indicated in my listing.  This command would be used to do that so check out the help file for it.

REAGENTC.EXE /setreimage /?

C:\Windows\System32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

Windows RE status: Enabled
Windows RE location: \\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE
Boot Configuration Data (BCD) identifier: a9bffc69-f347-11ec-844f-d45d64569331
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0

In addition to the dump file, you seem to not have your recovery options configured.  If you want to check, open an admin command prompt and type the command below.  If it comes back as disabled, enter the two commands below that and check again.

reagentc /info

reagentc /disable

reagentc /enable

If it still shows as disabled, we may need to try to locate the Winre.wim file and set a path to is for that system.  This may not be causing the upgrade failure but still needs to be repaired.  If you feel any of this might be related to your Backup software, then please advise.

That is good. 

It appears the cbservice.exe is related to the OneDrive Backup process.  I am currently comparing what my log shows regarding this situation.  I do not have OneDrive configured to be used as a recovery source.