WMI Problems in Windows PE 10240 that does not exist in PE 10074
hi!
finally got link windows 10 adk build 10240. great!
my problems stack overflow errors after executing "powershell" or own c# code disapeared to! great too!
but...
i have trouble getting wmi information while running this new pe boot wim provided 10240.
i switched new 10240 boot.wim , injected same winpe_ocs modules dism (also new 10240 version).
for example, cannot information root\cimv2 win32_diskpartition or win32_diskdrivetodiskpartition. while many others running fine!
i cannot value win32_operatingsystem property osarchitecture (other properties ar set!)
the strange thing: these queries worked flawless boot.wim 10074.
i happy, they are working again 10074, because wmi queries broken pe windows 8.1. had use , modify boot.wim dvd images not have issues.
i not happy see, problems returned 10240 boot.wim, honest, nice if fixed, not have use dvd boot.wim again our installation environment.
you can try out. use wmic in pe 10074 , in 10240
10074: wmic os returns property osarchitecture value 64-bit or 32-bit depending on pe bitness.
wmic partition returns a list of disk partitions found
10240: wmic os returns many properties values, property osarchitecture empty
wmic partition returns nothing - empty list
so, can please fix can use "official" boot.wim´s again?
thank help.
tom
hi tom,
where did windows adk build 10240?
based on test on lab machine, official download resource below not applied windows 10 build 10240.
download kits , tools windows 10
https://msdn.microsoft.com/en-us/windows/hardware/dn913721.aspx
thus suggest wait shortly rtm release, afterwards new windows adk release.
please remember mark replies answers if help, , unmark answers if provide no help. if have feedback technet support, contact tnmff@microsoft.com.
Windows 10 Insider Preview > Windows 10 Insider Preview Setup and Installation
WMI (Windows Management Instrumentation) issues in Windows PE 10240 may occur due to changes or limitations in the newer version compared to PE 10074. These issues can arise from missing or incompatible WMI components, or changes in system architecture. To resolve it, you may need to troubleshoot WMI services, ensure the correct version of WMI is installed, or look for any specific patches or updates from Microsoft. For more, check out: Golangci-Lint.
ReplyDelete