ok, the corruption of files is happening again using cat in powershell, windows 11.
This is one of the OP links:
safe cat safe://hygoygycc11b4pmrcb97ro6ro3wxh3cfrgi7ctbiwyya8mkktq1j35ysmzh > 6.jpg
It retrieves a file that doesn’t open, and looking at it in hex it has the same characteristics as the previous corrupted files, i.e additional 00 characters:
Same command, in a VM running ubuntu, on the same machine, retrieves a valid jpg.
HEX of the valid files looks like this:
let me know if there’s any additional tests I can run or logs I can check