Of the 5 options I tried 1 to 4. 3 of the 4 worked. Thx. The one that did not work was notebook opened as administrator and then file open setupact. Using edit find detectedor bootor environment each displayed cannot find respectively. Does a panther command need to be run again or does something need to be un-hidden?

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Hi Brink,
This computer last had a clean install using a bootable windows 10 iso.
Using administrative notepad for file search setupact.log there was only one result.
Using file explorer search for setupact.log there were 8 results.
These are the results after renaming and saving to the desktop: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
Using file explorer search for C:\Windows\Panther there were 19 results
These are the 19 results: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
The 8 results using search for setupact.log were pasted to the desk top renaming them 1 to 8.
Of the 8 results only one of them was useful as it had the find Detected boot environment which displayed EFI.
So it worked!
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
Through the process I had only searched for boot to create the most find results.
Once I found results I added the detected and it no longer produced the result.
In the process I learned that when using find the entry of the words must be in order and the exact spelling must be used. For example detected environment produced no resultsboot detected produced no resultsand detect boot environment produced no results. Only the 7th setupact.log had a result and only if find was used exactly as detected boot environment.

This was the computer windows upgrade history:
There were two windows 10 version 1607 clean installs in March 2017. In April 2017 there was a failed to upgrade to windows 1703.
C:\$Windows.~BT\Sources\Panther was used to generate log files to troubleshoot the upgrade failure.
Analysis of the logs led to the report that the upgrade was seeking more free space than what was available in the EFI partition.
The size of the partition was ok for the upgrade. It was the free space within the partition that was insufficient. Within this partition were files for foreign languagefontand UEFI diagnostics. It was unclear how to remove items from this partition. HP suggested using command line but they did not provide information on how they planned to remove the downloaded HP UEFI diagnostics (not available to uninstall via control panel).
It was repaired using the information in this link (explorer.exe): https://support.microsoft.com/en-us/...ing-windows-10
Was there an easy method using command line to uninstall the UEFI diagnostics folder? Using diskpart?
Or was there an easy method using command line to uninstall the Microsoft language folders or font files?
Backup files are highly recommended. If files were not backed up which method is considered safer explorer.exe or command line? Another option was to leave the contents of the EFI partition but enlarge its size. It was unclear whether this would place the nearby files at risk. It remains a learning experience for me as I need more experience in these areas.

Great to hear that people like Brink does exist. So many options. I think there is always a knowledge gap between MS development team and MS support team. Many MS articles don't give clear cut ideasjust try try try. They also don't know so many options. I'm using your another KB from your website. Immediately register to compliment you. Thanks a lot!