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

Select Storage Commands Don't Work in WinPE #7429

Closed
Chirishman opened this issue Aug 1, 2018 · 5 comments
Closed

Select Storage Commands Don't Work in WinPE #7429

Chirishman opened this issue Aug 1, 2018 · 5 comments
Labels
Issue-Question ideally support can be provided via other mechanisms, but sometimes folks do open an issue to get a Resolution-Answered The question is answered.

Comments

@Chirishman
Copy link

Bug Age: 5 Years

Steps to reproduce

Follow this

Attempt to use:

Clear-Disk
Format-Volume

Expected behavior

Clears and or formats the disk in question

Actual behavior

Unspecified Error 0x80004005

Environment data

Name                           Value
----                           -----
PSVersion                      5.1.17134.1
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17134.1
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
@Chirishman
Copy link
Author

Anybody? Bueller?

This problem has been open since 2013 guys, please at least triage it and label it as an issue so I know someone's read this...

@daxian-dbw @TravisEz13 @adityapatwardhan @iSazonov @anmenaga

@TravisEz13 TravisEz13 added the Issue-Question ideally support can be provided via other mechanisms, but sometimes folks do open an issue to get a label Feb 20, 2019
@TravisEz13
Copy link
Member

Please follow the instructions in the Issue template for Windows PowerShell issues:
https://github.com/PowerShell/PowerShell/blob/master/.github/ISSUE_TEMPLATE/Windows_PowerShell.md

@TravisEz13 TravisEz13 added the Resolution-Answered The question is answered. label Feb 20, 2019
@Chirishman
Copy link
Author

@BrucePay sorry to bug you but when we talked about issue #6616 last year (which I had originally raised on UserVoice all the way back in 2016) you told me that I should raise issues here because Uservoice is pretty much useless for getting bug reports seen.

Can I get some guidance here? Because in fact still no one has responded to or triaged the UserVoice version of that bug report from 2016.

Sorry, I know this isn't an interesting engine problem like the Hashtable one, but it is one that was discussed during the OS Deployments using WinPE + PowerShell and WindowsImageTools panel by David Jones at last year's PowerShell Summit and there doesn't seem to be any official acknowledgement that this issue exists.

@TravisEz13
Copy link
Member

cc @SteveL-MSFT

@SteveL-MSFT
Copy link
Member

@Chirishman Those cmdlets are in the Storage module which is not owned by the PowerShell team. You should open the issue here: https://windowsserver.uservoice.com/forums/295056-storage

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-Answered The question is answered.
Projects
None yet
Development

No branches or pull requests

3 participants