It's a base62 encoder that takes multiple integers as input. Probably a bit-length prefixed encoding. I am assuming it just pads an extra junk integer to re-roll the encoded number.
What the hell, man. This happens on every Windows 10 device that's left off for long periods of time. Stop blaming users for what's shitty programming/design.
Just booted up my laptop. CompatTelRunner is spinning two processes, one UpdateSoftwareInventory and one DoScheduledTelemetryRun. Meanwhile Edge and OneDrive have updated. I'm 10 minutes in. Spinning 100% CPU. Wuauserv and BITS are peeking in the background while telemetry is hogging everything.
Nope. It can do this for days if you leave the laptop off long enough. And then the CPU usage will suddenly drop to 0% when it's done. It's not even updating, it's Windows Store / universal app shenanigans.
You're assuming it's actually doing something important. I'm assuming there's a bug in Windows. Which is more likely?
I shouldn't need to run my laptop for days at 100% to please some Windows Store optimization service, just because I haven't booted it up for a month. I have a desktop, the laptop is for emergencies. But it's useless because Windows insists on emptying the battery when I need it.
I have this issue on my older laptops with Windows 10 that I rarely use. The culprit is some Windows Store "optimization" process (wsappx). It'll run for days at 100% if you don't boot Windows for long enough. I hear the exact same from friends. It's clearly a blatant bug that's been going on for years now, and Microsoft doesn't give a shit.