-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
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
NVRAM Boot Entries Are Shown As Shell Tools #184
Comments
I've added a dummy Here are the logs. |
Thanks for the report and input. |
This item was addressed by Commit 00dcb08. Current RefindPlus Release: v0.14.1.AA. Note Alternatively, the issue can be worked around pending the next release by setting the Thank you for taking the time to report a problem with RefindPlus. |
This thread is being locked. Please use the Discussions Feature for follow-on discussion or raise a new issue if appropriate. |
RefindPlus Version
v0.14.1.AA Release
Device Type
UEFI PC
Problem Description
My tool row is filled with many shell icons, corresponding to the various entries I have in nvram (like local HD, usb, optical, or OS boot entries).
My config contains
showtools shell
Problem Point
Before starting a loader or tool
Affected Items
One or More Tools (Second Row Items)
Debug Log
Debug logs are on the way, but I've been browsing scan.c and found 2 suspicious things. I don't know if that could help.
First, ScanForTools, case TAG_SHELL always calls ScanFirmwareDefined(), even if a shell has already been found. Maybe that's intended, I don't know, but I found it strange to search the firmware if we've already found the tool.
Second, in ScanFirmwareDefined(), if DontScanFirmware is empty, then every nvram entries are scanned and added, regardless of MatchThis (which, in this case, should contain L"shell"). I think that's why all the firmware entries become uefi shells in my toolbar.
Additional Context
No response
The text was updated successfully, but these errors were encountered: