Conflicting check values should be better displayed.
ErikBrown2 opened this issue · comments
Describe the bug
A clear and concise description of what the bug is.
Version 2.5.0.0 reports that secureboot is disabled/not detected while msinfo32 reports that it is enabled.
To Reproduce
Steps to reproduce the behavior:
- Run WhyNotWin11 and see it reporting that secureboot is disabled/not detected. Then run msinfo32 and see that secureboot state is reported as being on.
Expected behavior
A clear and concise description of what you expected to happen.
That WhyNotWin11 reports the secureboot status correctly
Screenshots
If applicable, add screenshots to help explain your problem.
Msinfo32 shows the following:
Desktop (please complete the following information):
- OS: [e.g. iOS]Win10
- Version [e.g. 2.3.0.0]
21H2 build 19044.1806
Additional context
Add any other context about the problem here.
Please check Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators\NI22H2 value RedReason and let me know what is listed.
Ah, you were in the discord earlier. Yep, in progress