It is slow to display context menu when store app trail version expire

Question

We follow this link to create the context menu for supported files,
https://learn.microsoft.com/en-us/windows/apps/desktop/modernize/desktop-to-uwp-extensions#context-menu

This is defination in Package.appxmanifest
</uap3:Extension>
<com:Extension Category="windows.comServer">
<com:ComServer>
<com:SurrogateServer DisplayName="Context menu verb handler">
<com:Class Id="1476525B-BBC2-4D04-B175-7E7D72F3DFF8" Path="QuickContextMenu.dll" ThreadingModel="STA"/>
</com:SurrogateServer>
</com:ComServer>
</com:Extension>
<desktop4:Extension Category="windows.fileExplorerContextMenus">
<desktop4:FileExplorerContextMenus>
<desktop5:ItemType Type=".mp3">
<desktop5:Verb Id="Command" Clsid="1476525B-BBC2-4D04-B175-7E7D72F3DFF8" />
</desktop5:ItemType>
<desktop5:ItemType Type=".wma">
<desktop5:Verb Id="Command" Clsid="1476525B-BBC2-4D04-B175-7E7D72F3DFF8" />
</desktop5:ItemType>

And this is project target

And this is system

We upload the app to Microsoft store and set 7 days trail. There is no problem if in trial period.
But when trial expire and we right click the supported file, for example it is slow to display context menu when i select mp3 file, and will slow again when i select mp3 file twice, even we restart the computer. It is slow every time when we right click the file. Please see attached video.

We can accept not display the context menu when expire, but can’t accept if it is slow.

We can see the event log in system. Unable to start because the expire, but need much time.

Unable to start a DCOM Server: {1476525B-BBC2-4D04-B175-7E7D72F3DFF8} as Unavailable/Unavailable. The error:
"2151645194"
Happened while starting this command:
"C:\WINDOWS\system32\DllHost.exe" /Processid:{1476525B-BBC2-4D04-B175-7E7D72F3DFF8}

So we want to know how to improve? I think below solution is acceptable

1. remove the context menu when expire
2. quick to return if unable to start DCOM server
3. not add context menu in trial verion and add context menu after user purchase the product. (Include configure in Store or create two installer)