Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get-BiosType not available #12443

Closed
superbonaci opened this issue Apr 23, 2020 · 7 comments
Closed

Get-BiosType not available #12443

superbonaci opened this issue Apr 23, 2020 · 7 comments
Labels
Issue-Question ideally support can be provided via other mechanisms, but sometimes folks do open an issue to get a Resolution-External The issue is caused by external component(s).

Comments

@superbonaci
Copy link

Using PowerShell 7.0.0. My script doesn't work because a command is missing:

PS C:\> Get-BiosType
Get-BiosType: The term 'Get-BiosType' 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.
@superbonaci superbonaci added the Issue-Question ideally support can be provided via other mechanisms, but sometimes folks do open an issue to get a label Apr 23, 2020
@SeeminglyScience
Copy link
Collaborator

I don't have that command in PS7 or Windows PowerShell. Can you post the output of Get-Command Get-BiosType from Windows PowerShell?

@p0W3RH311
Copy link

p0W3RH311 commented Apr 23, 2020

PS C:\> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.0.0
PSEdition                      Core
GitCommitId                    7.0.0
OS                             Microsoft Windows 6.3.9600
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

PS C:\> get-biostype
get-biostype: The term 'get-biostype' 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.


PS C:\> &  "$env:windir\system32\WindowsPowerShell\v1.0\powershell.exe" -c 'echo $psversiontable;
get-BiosType'

Name                           Value
----                           -----
PSVersion                      5.1.14409.1018
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14409.1018
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

get-BiosType : Le terme «get-BiosType» n'est pas reconnu comme nom d'applet de commande,
fonction, fichier de script ou programme exécutable. Vérifiez l'orthographe du nom, ou si un
chemin d'accès existe, vérifiez que le chemin d'accès est correct et réessayez.
Au caractère Ligne:1 : 23
+ echo $psversiontable; get-BiosType
+                       ~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (get-BiosType:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException



PS C:\>

@superbonaci
Copy link
Author

PS C:\> Get-Command Get-BiosType
Get-Command: The term 'Get-BiosType' 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.

@SeeminglyScience
Copy link
Collaborator

@superbonaci So you don't have the command in Windows PowerShell either? You may want to reach out to the script author to see where to get the command. Either way it's not a command provided by PowerShell so there's not much this repo can do.

@superbonaci
Copy link
Author

superbonaci commented Apr 23, 2020

It's used in this script:
https://github.com/PowerShellCrack/OSDBIOSPrerequisitesTool/blob/master/OSD-BIOSPrerequisitesTool.ps1

GitHub
Contribute to PowerShellCrack/OSDBIOSPrerequisitesTool development by creating an account on GitHub.

@SeeminglyScience
Copy link
Collaborator

@superbonaci gotcha, so what you want to do is file an issue on that repo so they can determine if someone is actually incompatible or if it's a script problem.

@iSazonov iSazonov added the Resolution-External The issue is caused by external component(s). label Apr 24, 2020
@ghost
Copy link

ghost commented Apr 25, 2020

This issue has been marked as external and has not had any activity for 1 day. It has been be closed for housekeeping purposes.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Question ideally support can be provided via other mechanisms, but sometimes folks do open an issue to get a Resolution-External The issue is caused by external component(s).
Projects
None yet
Development

No branches or pull requests

4 participants