I tried to use PowerShell Core with the Get-DedupStatus and Get-DedupVolume.

First of all, in an unelevated shell it just shows "A general error has occured" without more specific message (like Windows PowerShell does, from this message it is possible to understand that we got an ACCESS DENIED error).

Now, in an elevated shell the table formatting is buggy. I.e. for Get-DedupStatus the columns "FreeSpace" and "SavedSpace" are just empty (while they are filled in Windows PowerShell), the same for Get-DedupVolume (columns SavedSpace and SavingsRate are empty) and Get-DedupSchedule (column "StartTime" is also empty).

This is not really deal-breaking, but seeing this type of bugs when Windows PowerShell nags to try out PowerShell Core makes me wondering if it is really ready for this...