The error message as such is a bug in SQL Server. An assertion error is due to that in the program code there is an assertion check saying that "at this point, this condition is assumed to be true, and if it is not, we no longer know what we are doing, and we should get out of hear real quick, before we cause any more damage" and then they terminate your process.
Since you have the most recent CU of SQL Server 2022, the correct action would be to open a support case. This assume that you have some form of support contract.
I should make it clear that this is necessarily a bug in the meaning "this should work". The essence of the bug might just be that they should produce a normal error message without terminating the process.
If I am to make any guess, I would run this command:
fsutil fsinfo sectorinfo <volume pathname>
On the machine hosting the share, replacing the angle bracketed part with the drive for the share. If any number is > 4096, this may be the problem.
And, oh, if this is a share, shouldn't there be two backslashes in the beginning of the path?