New-Object : The term New-Object is not recognized as the name of a cmdlet

Question

I want to configure high trusted app for app dev in SharePoint, and to do so, i need first to insert some commands in the powershell editor like :

$publicCertPath = "C:\Certs\HighTrustSampleCert.cer" 
$certificate = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2($publicCertPath)

I am using windows PowerShell on Windows Server 2012 R2 which includes Windows PowerShell 4 that includes by default the new-object cmd-let... I don't understand though, why doesn't my operating system recognize that command ... I don't stop having the following error : New-Object : The term 'New-Object' is not recognized as the name of a cmdlet.

When i open powerShell i get this :

*select :

The term 'Select-Object' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\CONFIG\POWERSHELL\Registration\SharePoint.ps1:1 char:16 + $ver = $host | select version + ~~~~~~ + CategoryInfo : ObjectNotFound: (Select-Object:String) [], Comma ndNotFoundException + FullyQualifiedErrorId : CommandNotFoundException Set-location : The term 'Set-location' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again At C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\CONFIG\POWERSHELL\Registration\SharePoint.ps1:4 char:1 + Set-location $home + ~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (Set-location:String) [], Comman dNotFoundException + FullyQualifiedErrorId : CommandNotFoundException*

I thought that was normal until today... does it have any relation with the error? And here is the hole (new-object) exception stack:

New-Object : The term 'New-Object' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:16 + $certificate = New-Object System.Security.Cryptography.X509Certificates.X509Cert ... + ~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (New-Object:String) [], CommandN otFoundException + FullyQualifiedErrorId : CommandNotFoundException

ps: i want to mention that when i used enter-psSession and worked remotely, the command new-object was recognized but sharepoint commands (like Get-SPAuthenticationRealm) were no more recognized ... And it's like there is a problem related to the operating system.

Waldenburg

You've tried Get-Command and/or Get-Help to see whether it's recognized, right. Very strange to get that error, should be available by default. – Bichromate

The New-Object cmdlet is available since PowerShell 1.0. It's also exported by the Microsoft.PowerShell.Utility module, so if you don't have that loaded in your PowerShell session, that could trigger an error like that. Does the result list of Get-Module contain this module? – Under

Are you connecting to a remote endpoint using enter-pssession? Sounds liked something that would occur with a constrained PowerShell endpoint. – Prelate

Please give the exact exception stack. – Tabloid

@Bichromate No, it does not recognize it. – Waldenburg

@PeterK, can you explain more please? – Waldenburg

@boeprox, i tried first with remote session and used enter-pssession, it does not work, then i switched to work directly on the sever machine and it does not work either. – Waldenburg

@Tabloid i edited the post to include the hole stakc – Waldenburg

@KarouiHaythem: Yes, of course. PowerShell is modularized. Certain cmdlets like New-Object are only available if the module that implements them is loaded. New-Object, in particular is provided by the Microsoft.PowerShell.Utility module. You can verify if this module is loaded in your session by running the Get-Module cmdlet. This will give you the list of loaded modules and Microsoft.PowerShell.Utility should be in the list. This should confirm if you have New-Object available at all. – Under

@Under seems like i have serious problem... Get-Module get me blank ... nothing is loaded seems, what should i do ? – Waldenburg

Run Get-Module -ListAvailable' to get the list of PowerShell modules available for loading. This should include Microsoft.PowerShell.Utility. If it's in the list, you can just run Import-Module Microsoft.PowerShell.Utility` to load it. By the way this module is among the Core Modules of PowerShell so the default session should include them. If this is a just a regular PowerShell session, you may want to try repairing your PowerShell installation. – Under

@Under i tried already to uninstall - reinstall powershell feature i got an error while unistalling it... :/ – Waldenburg

@KarouiHaythem: It sounds like your PowerShell installation is corrupted. What was the error you got? – Under

@Under i finally fixed it i went to powerShell installation files on another server and copied the files inside the c:\ProgramFiles\WindowsPowerShell so it recognizes now the commands... thank you peter for you assistance and patience... you can post your comment as answer and i will mark it aswell. – Waldenburg

@KarouiHaythem: Thank you. I'm not sure if I deserve the credit as you did the work, but I've posted my answer anyway for future reference. You may want to add the way you have fixed the problem eventually. Thanks. – Under

Answer 1

It appears that your PowerShell installation is corrupted and needs to be repaired. The New-Object cmdlet is exported by the Microsoft.PowerShell.Utility module, which is one of the Core PowerShell modules and should be imported by default on all PowerShell installations.

Under

Answer 2

This can be because the Registry key entry for PSModulesPath is not pre-filled with the default PowerShell Modules path.

$PSModulePath = Get-ItemProperty -Path "HKLM:SYSTEM\CurrentControlSet\Control\Session Manager\Environment" -Name "PSModulePath"

$newPSModulePath = $PSModulePath.PSModulePath + ";C:\Windows\System32\WindowsPowerShell\v1.0\Modules"

Set-ItemProperty -Path "HKLM:SYSTEM\CurrentControlSet\Control\Session Manager\Environment" -Name "PSModulePath" -value $newPSModulePath

Whiten

Answer 3

Nothing verified here, but I am advancing the hypothesis that Powershell has run into a runtime error that caused it to corrupt its process.

Blowbyblow

have you read the comments? The problem was in the installation and peter helped me figurin' it out... i don't see any reason for doubt – Waldenburg