We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
First thank you for this awesome tool. It runs fine on Windows PE without any optional component (WMI, .NET, etc).
I have found a minor issue. lsblk.exe -d (X: is Windows PE's ramdrive):
lsblk.exe -d
X:
Volumes: * \\?\Volume{b05dfcb2-e35d-49d8-96ef-9c144eb2ddf5}\ \GLOBAL??\Volume{b05dfcb2-e35d-49d8-96ef-9c144eb2ddf5} Extent: disk=0 start=1048576 len=524288000 n=1 d=PhysicalDrive0 f=FAT32 p= * \\?\Volume{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}\ \GLOBAL??\Volume{d9b257fc-684e-4dcb-ab79-03cfa2f6b750} Extent: disk=-1 start=0 len=3161088 Mounts: - X:\ n=2 d=PhysicalDrive-1 f=NTFS p=X:\ * \\?\Volume{4405fc50-9dd2-11ee-a527-806e6f6e6963}\ \GLOBAL??\Volume{4405fc50-9dd2-11ee-a527-806e6f6e6963} Error: Unable to get volume extents, NTSTATUS=0xC0000010 [0x00000015] The device is not ready. Mounts: 0: disk=PhysicalDrive0 start=1048576 len=524288000 fs=FAT32 paths= 1: disk=PhysicalDrive-1 start=0 len=3161088 fs=NTFS paths=X:\ lsblk for Windows v1.2, Copyright (c) 2021 Google LLC NAME HCTL SIZE ST TR RM RO TYPE DESCRIPTION Disks: \\.\PhysicalDrive0 PhysicalDrive0 0:0:0:0 56G 1 1 0 0 SATA OCZ-AGILITY3 L Partition 1 500M GPT [System] {C12A7328-F81F-11D2-BA4B-00A0C93EC93B} FAT32 L Partition 2 55G GPT {0FC63DAF-8483-4772-8E79-3D69D8477DE4} FAT32
Partition 2 is "Linux filesystem" (type 0fc63daf-8483-4772-8e79-3d69d8477de4) with a Btrfs filesystem.
0fc63daf-8483-4772-8e79-3d69d8477de4
The text was updated successfully, but these errors were encountered:
(latest WinPE, version 10.0.25398.1)
Sorry, something went wrong.
No branches or pull requests
First thank you for this awesome tool. It runs fine on Windows PE without any optional component (WMI, .NET, etc).
I have found a minor issue.
lsblk.exe -d
(X:
is Windows PE's ramdrive):Partition 2 is "Linux filesystem" (type
0fc63daf-8483-4772-8e79-3d69d8477de4
) with a Btrfs filesystem.The text was updated successfully, but these errors were encountered: