![]() WhyNotWin11 is going to fail other checks in WinPE since it's detecting the RAM disk as the boot disk which will fail Disk Partition Type and Storage Available, but that's ok because I know that our actual internal drives will be large enough and I will be formatting them correctly in code. TPM is easy enough to check on my own without using WhyNotWin11, but since the CPU check is more complicated, using WhyNotWin11 would be handy. Or if its possible to determine that the drivers aren't installed so the check can't be performed to skip it promptly (that would be even better and faster).įor my usage in WinPE, I am really only wanting to confirm UEFI, CPU, RAM, and TPM. I'm thinking it would be useful to add some timeout to this check to give up after some reasonable time (and go ahead and create the export with an "Unknown" value in this field or something so the other fields can be checked). If I check TaskMgr, I can see my multiple WhyNotWin11 executable attempts still running with no exports created after multiple minutes. I am assuming that this may be because the process is hanging in the background waiting to be able to determine the "DirectX + WDDM2" status. When I try to do a silent export, nothing ever gets created. That it continues to show "Checking…" for this row in the GUI is not that bad, but I am wanting to run this silently with an export and analyze the export with no user intervention to determine if Windows 11 can be installed. I'm assuming this is because there are no graphics drivers installed yet. WhyNotWin11 appears to run fine in WinPE, but is not able to determine "DirectX + WDDM2". Once Windows 11 is released, I would like to be able to run WhyNotWin11 in WinPE during our refurbishment process to determine if a computer should get the Windows 11 WIM image or the Windows 10 WIM image installed onto it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |