oaktrees
asked on
Trapped in UEFI Boot - A Potential Solution
Win 7, 64 system. Was upgrading from Norton Ghost 15 to Symantec System Recovery - basically Ghost 16.
During the creation of the recovery disk I somehow got a UEFI / EFI partition on my system drive.
Even though the BIOS says "Legacy", the system is booting through the UEFI. Restarting opens a "Windows Boot Manager" each time: white text on black screen. Asks me if I want to Load Windows 7. Counts down from 7 then loads.
The BIOS Boot Sequence shows Legacy, not UEFI. I tried changing from Legacy to UEFI then back to Legacy. Still get the same Windows Boot Manager screen at restart.
Open Disk Manager I can see an EFI partition - 300 Mb.
If I go to C:\Windows\Panther\setupac
2015-01-29 00:15:03, Info IBS Callback_BootEnvironmentDe
2015-01-29 00:15:03, Info IBS Callback_BootEnvironmentDe
So, seems that UEFI is the way this computer will boot.
Only solution I've found so far was here: http://www.tomshardware.com/forum/33472-63-win7-boot-loader-issues
"...delete the SRD directory and reboot. Since the directory doesn't exist anymore, I was able to select Windows 7 from the boot loader and boot right into windows like normal."
I'm confused. First, I don't know how to delete the SRD directory. More significantly, when I look up the SRD Directory that's the...System Root Directory. Seems like a pretty crucial thing to "delete'. How do you all see it? Do you agree with this strategy?
Or, should I just clean away the UEI partition via this strategy:http://www.howtogeek.com/215349/how-to-remove-an-efi-system-partition-or-gpt-protective-partition-from-a-drive-in-windows/
Seems like the first route, deleting the SRD, if that's one of those self-creating directories, like in Outlook -if there's no data file / null it auto generates - then I can see the logic. And, the suggestion seems to have come FROM Symantec. So, seems trustworthy. But, I am in the dark about what deleting the SRD would cause, or how to do it.
The second route - just eliminating the partition, looks less likely to induce the BSOD.
How do you all see it?
Thanks!!
OT
(Currently downloading Clonezilla :D )
During the creation of the recovery disk I somehow got a UEFI / EFI partition on my system drive.
Even though the BIOS says "Legacy", the system is booting through the UEFI. Restarting opens a "Windows Boot Manager" each time: white text on black screen. Asks me if I want to Load Windows 7. Counts down from 7 then loads.
The BIOS Boot Sequence shows Legacy, not UEFI. I tried changing from Legacy to UEFI then back to Legacy. Still get the same Windows Boot Manager screen at restart.
Open Disk Manager I can see an EFI partition - 300 Mb.
If I go to C:\Windows\Panther\setupac
2015-01-29 00:15:03, Info IBS Callback_BootEnvironmentDe
2015-01-29 00:15:03, Info IBS Callback_BootEnvironmentDe
So, seems that UEFI is the way this computer will boot.
Only solution I've found so far was here: http://www.tomshardware.com/forum/33472-63-win7-boot-loader-issues
"...delete the SRD directory and reboot. Since the directory doesn't exist anymore, I was able to select Windows 7 from the boot loader and boot right into windows like normal."
I'm confused. First, I don't know how to delete the SRD directory. More significantly, when I look up the SRD Directory that's the...System Root Directory. Seems like a pretty crucial thing to "delete'. How do you all see it? Do you agree with this strategy?
Or, should I just clean away the UEI partition via this strategy:http://www.howtogeek.com/215349/how-to-remove-an-efi-system-partition-or-gpt-protective-partition-from-a-drive-in-windows/
Seems like the first route, deleting the SRD, if that's one of those self-creating directories, like in Outlook -if there's no data file / null it auto generates - then I can see the logic. And, the suggestion seems to have come FROM Symantec. So, seems trustworthy. But, I am in the dark about what deleting the SRD would cause, or how to do it.
The second route - just eliminating the partition, looks less likely to induce the BSOD.
How do you all see it?
Thanks!!
OT
(Currently downloading Clonezilla :D )
ASKER
IN THE BIOS UNDER SECURITY IS THERE A SECURE BOOT,
No
CHANGE THAT FROM IT'S CURRENT SETTING: ENABLED OR DISABLED, TO THE OPPOSITE CHOICE.
THERE MAY ALSO BE AN OPTION TO SET SECURE BOOT TO SETUP MODE THAT YOU CAN TRY.
Nope
ALSO IN THE BIOS UNDER STARTUP , DO YOU HAVE A CSM , COMPATIBILITY SUPPORT MODULE?
No
CHANGE THAT FROM IT'S CURRENT SETTING: ENABLED OR DISABLED, TO THE OPPOSITE CHOICE.
What do you think?
Delete SRD File is a no go?
What about that UEI partition and trying to get rid of it?
No
CHANGE THAT FROM IT'S CURRENT SETTING: ENABLED OR DISABLED, TO THE OPPOSITE CHOICE.
THERE MAY ALSO BE AN OPTION TO SET SECURE BOOT TO SETUP MODE THAT YOU CAN TRY.
Nope
ALSO IN THE BIOS UNDER STARTUP , DO YOU HAVE A CSM , COMPATIBILITY SUPPORT MODULE?
No
CHANGE THAT FROM IT'S CURRENT SETTING: ENABLED OR DISABLED, TO THE OPPOSITE CHOICE.
What do you think?
Delete SRD File is a no go?
What about that UEI partition and trying to get rid of it?
ASKER
Ps - all capped your replies just so it'd be easier to read. :)
What is the Computer Brand , Model and Type?
You indicated you were downloading Clonezilla ,
so you are going to make a backup of the drive with it, before making any changes?
Restarting opens a "Windows Boot Manager" each time: white text on black screen. Asks me if I want to Load Windows 7. Counts down from 7 then loads.
So does the above mean Windows 7 does load, but has to be chosen from Windows Boot Manager, To do so?
Do you have a Windows 7 64 Boot CD?
You indicated you were downloading Clonezilla ,
so you are going to make a backup of the drive with it, before making any changes?
Restarting opens a "Windows Boot Manager" each time: white text on black screen. Asks me if I want to Load Windows 7. Counts down from 7 then loads.
So does the above mean Windows 7 does load, but has to be chosen from Windows Boot Manager, To do so?
Do you have a Windows 7 64 Boot CD?
ASKER
MODEL
Acer E5-572
CLONEZILLA
Correct. Was going to make a backup before we did anything.
SO DOES THE ABOVE MEAN WINDOWS 7 DOES LOAD, BUT HAS TO BE CHOSEN?
Does not need to be chosen. Chooses itself - asks me and says: in 10 second will happen automatically. Counts down - sort of like Safe Mode - then loads itself.
DO YOU HAVE A WINDOWS 7 64 BOOT CD?
I have the one I had always used with the previous iteration of Ghost.
Acer E5-572
CLONEZILLA
Correct. Was going to make a backup before we did anything.
SO DOES THE ABOVE MEAN WINDOWS 7 DOES LOAD, BUT HAS TO BE CHOSEN?
Does not need to be chosen. Chooses itself - asks me and says: in 10 second will happen automatically. Counts down - sort of like Safe Mode - then loads itself.
DO YOU HAVE A WINDOWS 7 64 BOOT CD?
I have the one I had always used with the previous iteration of Ghost.
Ok, Then No need to do anything with partitions, just the Boot.ini Settings.
When in Windows 7.
Open up the command prompt as an Elevated Administrator.
Type : bcdedit
It will show the current Boot Loader Settings.
Type: bcdedit /timeout 0
Exit then Restart and should now boot directly into Windows 7
When in Windows 7.
Open up the command prompt as an Elevated Administrator.
Type : bcdedit
It will show the current Boot Loader Settings.
Type: bcdedit /timeout 0
Exit then Restart and should now boot directly into Windows 7
ASKER
Should I wait to run Clonezilla backup ? (It's 1tb - will take a few hours.) Plus, need to install Clonezilla and figure it out.
Ran only the Elevated command already. Can see the timeout value now is 10. What do you think? Run the edit before the backup?
Also, do you think this will alter Ghost's ability to function on this machine? I mean: Are we doing an end run on Ghost that will be permanent?
Ran only the Elevated command already. Can see the timeout value now is 10. What do you think? Run the edit before the backup?
Also, do you think this will alter Ghost's ability to function on this machine? I mean: Are we doing an end run on Ghost that will be permanent?
ASKER
Confused also about this entry from C:\Windows\Panther\setupac
2015-01-29 00:15:03, Info IBS Callback_BootEnvironmentDe
Looks like if we set the timeout value to 0 via bcdedit then we'll be able to skip the EFI boot sequence. Am I right? But, are we fixing the problem? Or just working around it?
Here is what the developer is suggesting.
1. Remove / Rename the C:\bootmgr file
2. Remove / Rename the C:\boot folder
3. Remove / Rename the C:\Srd folder
4. Reboot the system. It should boot to the normal Windows Splash Screen
https://www.veritas.com/support/en_US/article.TECH67808
I want to get rid of that UEFI boot sector. But, seems like taking step 1 ~ 4 above would wreck the system as these are critical system files? Can they be just deleted / renamed without causing permanent damage?
Developer is not giving any direction on this question. Need your advice: change time out alone via bcdedit: permanent work around? Or, 1 ~ 4 above: safely get rid of the UEFI.
This second strategy is also referenced here: http://www.tomshardware.com/forum/33472-63-win7-boot-loader-issues
"...delete the SRD directory and reboot. Since the directory doesn't exist anymore, I was able to select Windows 7 from the boot loader and boot right into windows like normal."
Put another way: do you think renaming / deleting the files above will result in getting rid of the UEFI, and is it system-safe?
How do you see it?
Thanks!!
OT
2015-01-29 00:15:03, Info IBS Callback_BootEnvironmentDe
Looks like if we set the timeout value to 0 via bcdedit then we'll be able to skip the EFI boot sequence. Am I right? But, are we fixing the problem? Or just working around it?
Here is what the developer is suggesting.
1. Remove / Rename the C:\bootmgr file
2. Remove / Rename the C:\boot folder
3. Remove / Rename the C:\Srd folder
4. Reboot the system. It should boot to the normal Windows Splash Screen
https://www.veritas.com/support/en_US/article.TECH67808
I want to get rid of that UEFI boot sector. But, seems like taking step 1 ~ 4 above would wreck the system as these are critical system files? Can they be just deleted / renamed without causing permanent damage?
Developer is not giving any direction on this question. Need your advice: change time out alone via bcdedit: permanent work around? Or, 1 ~ 4 above: safely get rid of the UEFI.
This second strategy is also referenced here: http://www.tomshardware.com/forum/33472-63-win7-boot-loader-issues
"...delete the SRD directory and reboot. Since the directory doesn't exist anymore, I was able to select Windows 7 from the boot loader and boot right into windows like normal."
Put another way: do you think renaming / deleting the files above will result in getting rid of the UEFI, and is it system-safe?
How do you see it?
Thanks!!
OT
Yes, Setting it to Zero will skip the Windows Boot Manager.
But, As far as getting rid of the UEFI if it's only 400 MB in size, I would just leave it be.
If you want to continue to proceed in deleting it then I would recommend creating a System Restore Disk and Recovery Disk by running the tools provided by Microsoft.
Just Type Restore in the Search Windows and Press Enter.
In upper left of the screen that comes up you will see : Create a System Image and Create a System Repair Disc.
The System Repair Disc can be used to use the System Image created to get Windows back up and running if a problem arises from deleting the UEFI .
But, As far as getting rid of the UEFI if it's only 400 MB in size, I would just leave it be.
If you want to continue to proceed in deleting it then I would recommend creating a System Restore Disk and Recovery Disk by running the tools provided by Microsoft.
Just Type Restore in the Search Windows and Press Enter.
In upper left of the screen that comes up you will see : Create a System Image and Create a System Repair Disc.
The System Repair Disc can be used to use the System Image created to get Windows back up and running if a problem arises from deleting the UEFI .
ASKER
But, if we set the timeout value to 0 via bcdedit, how do we get out of this:
IBS Callback_BootEnvironmentDe
Seems like this value will remain EFI after setting the timeout value to zero?
I think that this "suppressed" EFI environment will pop up somewhere later and cause system trouble. How do you see it?
I want to know how to flat out get rid of it safely.
IBS Callback_BootEnvironmentDe
Seems like this value will remain EFI after setting the timeout value to zero?
I think that this "suppressed" EFI environment will pop up somewhere later and cause system trouble. How do you see it?
I want to know how to flat out get rid of it safely.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks!
Change that from it's current setting: Enabled or Disabled, to the opposite choice.
There may also be an option to set Secure boot to setup mode that you can try.
Also in the Bios under Startup , Do you have a CSM , Compatibility Support Module?
Change that from it's current setting: Enabled or Disabled, to the opposite choice.