should pendmoves (and movefile) be updated to comply to the "new" syntax of PendingFileRenameOperations?

Question

It appears that at least in Win10, the PendingFileRenameOperations registry value is now being populated using a slightly different syntax, which prepends "*1" or "*2" to the usual renaming/deleting patterns.

Can at least pendmoves be updated to take this into account? (It does appear that the previous syntax in still functional, so movefile might not need to be updated.)

Example contents of the PendingFileRenameOperations value:

*1??\C:\Program Files (x86)\Microsoft\Edge\Temp\scoped_dir2540_1132862623\old_msedge.exe *1??\C:\Program Files (x86)\Microsoft\Edge\Temp\scoped_dir2540_1132862623 *1??\C:\Program Files (x86)\Microsoft\Edge\Temp *2??\C:\Users\Nuno\AppData\Local\Temp\iu-14D2N.tmp_unins.tmp *1??\C:\Users\Nuno\AppData\Local\Temp\iu-14D2N.tmp *1??\C:\Program Files\Microsoft OneDrive\Update\OneDriveSetup.exe *2??\C:\Program Files\Microsoft OneDrive\StandaloneUpdater\OneDriveSetup.exe