Is anyone else having problems with the MS ActiveDirectory cmdlets in PowerShell 4.0?  Running the following command on a domain-joined Windows 8 RTM device:

get-aduser myusername -properties *

...returns all available properties of user myusername, as expected.  However, on a domain-joined Windows 8.1 preview machine with the Windows 8.1 RSAT installed, the same command returns the following error:

get-aduser : One or more properties are invalid.
Parameter name: msDS-AssignedAuthNPolicy
At line:1 char:1
+ get-aduser myusername -properties *
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (myusername:ADUser) [Get-ADUser], ArgumentException
    + FullyQualifiedErrorId : ActiveDirectoryCmdlet:System.ArgumentException,Microsoft.ActiveDirectory.Management.Comm
   ands.GetADUser

The cmdlet works correctly if I specify the properties rather than using the wildcard.  Get-AdComputer is doing exactly the same thing.

I should note that I just noticed this behavior this morning. I was using these cmdlets on my Win 8.1 machine last week, and the only change I can think of is that I installed the latest batch of updates on Friday.  Has anyone else seen this behavior?

I'm having this exact issue.

I have a couple of extremely basic scripts that use -properties * and neither work.

Hoping someone can find a fix.