E2B keeps showing wmic error on update even though it is in path.
I've been trying to update my USB stick but it always fails with the "cannot run wmic" error, even though I already followed the guide it links to.
Well wmic is a standard Windows command. Are you using a standard Windows 10 system?
Can you run wmic from the Windows command shell? e.g.
wmic /?
Type
path
A standard Windows will normally have C:\Windows\System32\Wbem somewhere in the path string displayed.
The WMI command-line (WMIC) utility is deprecated as of Windows 10, version 21H1, and as of the 21H1 semi-annual channel release of Windows Server.
It is remove so that e2b will can not install. Check C:\Windows\System32\Wbem you would see wmic.exe was not there
Hi, same problem. Tested on Windows 10 Enterprise x64 21H2 build 19044.1415
PATH set, wmic present and working. Tested like:
d:\wmic logicaldisk get caption,volumename,description,Size
->displayed all my drive mounts. I've found that the check
path | find /i "wbem">nul || set FAIL=1
is 0 (ok) when running from command line, but returns 1 (not found) when runned from script. Maybe script nesting problem?
So i commented out this check in those .cmd files
Easy2Boot_v2.10\_ISO\docs\E2B Utilities\E2B SUBMENU Maker.cmd
Easy2Boot_v2.10\_ISO\docs\E2B Utilities\Launcher\StartupCheck.cmd
Easy2Boot_v2.10\_ISO\docs\Make_E2B_USB_Drive\MAKE_E2B_USB_DRIVE.cmd
Easy2Boot_v2.10\_ISO\SUB_MENU_Maker.cmd
Easy2Boot_v2.10\UPDATE_E2B_DRIVE.CMD
crude, but works 4 now .)
Update: update drive is working for already prepared(old) usb drive. But when creating/partitioning new flash drive - script cannot find second partition.
find: ' 31 ': No such file or directory
Error: E2B Partition 2 not found!
it is created, but always as fixed size 31.5 KB and type FAT12 (plenty of free space after first partition. My target was first 114 GiB second 500 MiB or 1 Gib)
Update2:
Had to delete this small 2nd partition (windows disk management tool does not see it), create new 2nd partition as FAT32 and copy files from agFM_download_files.zip
then successfully tested boot in both BIOS and UEFI mode.
d:\wmic
???
wmic is part of all Windows full release versions and should be in the path (\windows\system32 usually).
If you are not running a full release then wmic wont work.
..as stated PATH set, wmic present and working. Tested like:
so calling wmic from any path/working directory. (PATH variable in system is working)
How did you set the path?
..just as you do in Windows. And rebooted, so it will not be a "cmd" session specific set PATH. .)
Is there a possibility MS change something, so whole WMI is crippled in some way?
Maybe development versions don't have full support for wmic.exe?
just tested latest beta Easy2Boot_v2.11d on the same machine and everything works out of the box. :7
V2.11 is released today and is latest