andybn1
New Member
- Joined
- Jan 6, 2024
- Messages
- 3
- Thread Author
- #1
One day i tried to start my pc and got the blue screen with the code: 0xc00000e and following an tutorial i formated the 100mb boot partition and rebuild it with the command
bcdboot c:\windows /l en-us /s z: /f UEFI
My windows booted fine after that but thinks whare not right. The first thing i've notice was that my sleep and hibernate whare missing from the power dropdown in the start menu and when i tried to check the power options in control panel i saw this error: Your power plan information isn't available.
After this i've tried windows updates and realizes that the updates are failing every time.
Now i'm thinking there's something wrong with the recovery partition and i've run
reagentc /info
output: REAGENTC.EXE: A target Windows installation must be specified.
Wird Next i've tried enabling reagentc
reagentc /enable
output:
Enables the local copy of the Windows Recovery Environment (Windows RE).
This command can be used from the running operating system without additional
parameters, or from the Windows Preinstallation Environment (Windows PE) using
the optional /osguid parameter.
How can i be in Windows Preinstallation Environment? confused i've runned bcdedit
output:
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.efi
description Windows PreInstallation Environment
locale en-us
inherit {bootloadersettings}
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
nx OptOut
winpe Yes
as you can see it reports that my windows installation is in Preinstallation Environment which explains all the problems i'm having.
I've tried rebuilding the BCD store servil times without any change. One thing i need to mention is that when i run the command bootrec /fixboot i get the error: element not found.
I'm tiring to fix this for a mount now and i'm stuck. Any help whit be greatly appreciated
bcdboot c:\windows /l en-us /s z: /f UEFI
My windows booted fine after that but thinks whare not right. The first thing i've notice was that my sleep and hibernate whare missing from the power dropdown in the start menu and when i tried to check the power options in control panel i saw this error: Your power plan information isn't available.
After this i've tried windows updates and realizes that the updates are failing every time.
Now i'm thinking there's something wrong with the recovery partition and i've run
reagentc /info
output: REAGENTC.EXE: A target Windows installation must be specified.
Wird Next i've tried enabling reagentc
reagentc /enable
output:
Enables the local copy of the Windows Recovery Environment (Windows RE).
This command can be used from the running operating system without additional
parameters, or from the Windows Preinstallation Environment (Windows PE) using
the optional /osguid parameter.
How can i be in Windows Preinstallation Environment? confused i've runned bcdedit
output:
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.efi
description Windows PreInstallation Environment
locale en-us
inherit {bootloadersettings}
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
nx OptOut
winpe Yes
as you can see it reports that my windows installation is in Preinstallation Environment which explains all the problems i'm having.
I've tried rebuilding the BCD store servil times without any change. One thing i need to mention is that when i run the command bootrec /fixboot i get the error: element not found.
I'm tiring to fix this for a mount now and i'm stuck. Any help whit be greatly appreciated
- Joined
- Mar 14, 2023
- Messages
- 44,742
It seems like you are encountering several issues with your Windows installation after rebuilding the BCD store. Let's try to address each problem step-by-step:
1. Missing sleep and hibernate options:
This issue might be related to the power plan settings on your system. Try the following steps:
- Open the Control Panel and navigate to "Power Options."
- Click on "Change plan settings" for your currently selected power plan.
- Next, click on "Change advanced power settings."
- Expand the "Sleep" and "Hibernate" options, and make sure they are enabled and set according to your preferences.
- Click "Apply" and then "OK" to save the changes.
Check if the sleep and hibernate options are now available in the power dropdown menu.
2. Windows Update failures:
Rebuilding the BCD store should not directly affect Windows Update. However, let's ensure all required services are running properly:
- Press "Win + R" to open the Run dialog box.
- Type "services.msc" and press Enter to open the Services window.
- Locate and verify the following services are running:
- Windows Update Service
- BITS (Background Intelligent Transfer Service)
- Cryptographic Services
- If any of these services are not running, right-click on the service, select "Properties," set the startup type to "Automatic," and click "Start" to enable it.
- Reboot your computer and then try running Windows Update again.
3. Recovery partition and Windows RE:
It appears that the command "reagentc /info" is not providing the expected output. To check the status of your recovery environment, you can use the following command instead:
- Open Command Prompt as Administrator.
- Enter the command: "reagentc /info /target c:\Windows"
- This will display the information about your recovery environment, specifically for your Windows installation on the C: drive.
- If the information is not available or shows an error, it might indicate an issue with the recovery environment on your system.
4. Windows Preinstallation Environment (WinPE) showing as the current boot loader:
This is likely causing the confusion about why your Windows installation is in the Preinstallation Environment.
- Open Command Prompt as Administrator.
- Enter the command: "bcdedit /default {current}"
- This sets the default boot loader to {current}, which should point to your Windows installation.
- Restart your computer and check if Windows boots properly.
5. "Element not found" error when running "bootrec /fixboot":
This error can occur if the required boot files are missing or corrupted.
- Open Command Prompt as Administrator.
- Run the following commands one by one:
- "bootrec /fixmbr" (this repairs the Master Boot Record)
- "bootrec /fixboot" (this repairs the boot sector)
- "bootrec /rebuildbcd" (this scans for Windows installations and allows you to add them to the boot configuration)
- Restart your computer and check if the issue persists.
If these steps do not resolve your problems, it may be necessary to consider performing a repair installation or a clean installation of Windows 11. Before proceeding with any major changes, ensure that you have a backup of your important files to avoid data loss.
1. Missing sleep and hibernate options:
This issue might be related to the power plan settings on your system. Try the following steps:
- Open the Control Panel and navigate to "Power Options."
- Click on "Change plan settings" for your currently selected power plan.
- Next, click on "Change advanced power settings."
- Expand the "Sleep" and "Hibernate" options, and make sure they are enabled and set according to your preferences.
- Click "Apply" and then "OK" to save the changes.
Check if the sleep and hibernate options are now available in the power dropdown menu.
2. Windows Update failures:
Rebuilding the BCD store should not directly affect Windows Update. However, let's ensure all required services are running properly:
- Press "Win + R" to open the Run dialog box.
- Type "services.msc" and press Enter to open the Services window.
- Locate and verify the following services are running:
- Windows Update Service
- BITS (Background Intelligent Transfer Service)
- Cryptographic Services
- If any of these services are not running, right-click on the service, select "Properties," set the startup type to "Automatic," and click "Start" to enable it.
- Reboot your computer and then try running Windows Update again.
3. Recovery partition and Windows RE:
It appears that the command "reagentc /info" is not providing the expected output. To check the status of your recovery environment, you can use the following command instead:
- Open Command Prompt as Administrator.
- Enter the command: "reagentc /info /target c:\Windows"
- This will display the information about your recovery environment, specifically for your Windows installation on the C: drive.
- If the information is not available or shows an error, it might indicate an issue with the recovery environment on your system.
4. Windows Preinstallation Environment (WinPE) showing as the current boot loader:
This is likely causing the confusion about why your Windows installation is in the Preinstallation Environment.
- Open Command Prompt as Administrator.
- Enter the command: "bcdedit /default {current}"
- This sets the default boot loader to {current}, which should point to your Windows installation.
- Restart your computer and check if Windows boots properly.
5. "Element not found" error when running "bootrec /fixboot":
This error can occur if the required boot files are missing or corrupted.
- Open Command Prompt as Administrator.
- Run the following commands one by one:
- "bootrec /fixmbr" (this repairs the Master Boot Record)
- "bootrec /fixboot" (this repairs the boot sector)
- "bootrec /rebuildbcd" (this scans for Windows installations and allows you to add them to the boot configuration)
- Restart your computer and check if the issue persists.
If these steps do not resolve your problems, it may be necessary to consider performing a repair installation or a clean installation of Windows 11. Before proceeding with any major changes, ensure that you have a backup of your important files to avoid data loss.
andybn1
New Member
- Joined
- Jan 6, 2024
- Messages
- 3
- Thread Author
- #3
bcdedit /default {current}It seems like you are encountering several issues with your Windows installation after rebuilding the BCD store. Let's try to address each problem step-by-step:
1. Missing sleep and hibernate options:
This issue might be related to the power plan settings on your system. Try the following steps:
- Open the Control Panel and navigate to "Power Options."
- Click on "Change plan settings" for your currently selected power plan.
- Next, click on "Change advanced power settings."
- Expand the "Sleep" and "Hibernate" options, and make sure they are enabled and set according to your preferences.
- Click "Apply" and then "OK" to save the changes.
Check if the sleep and hibernate options are now available in the power dropdown menu.
2. Windows Update failures:
Rebuilding the BCD store should not directly affect Windows Update. However, let's ensure all required services are running properly:
- Press "Win + R" to open the Run dialog box.
- Type "services.msc" and press Enter to open the Services window.
- Locate and verify the following services are running:
- Windows Update Service
- BITS (Background Intelligent Transfer Service)
- Cryptographic Services
- If any of these services are not running, right-click on the service, select "Properties," set the startup type to "Automatic," and click "Start" to enable it.
- Reboot your computer and then try running Windows Update again.
3. Recovery partition and Windows RE:
It appears that the command "reagentc /info" is not providing the expected output. To check the status of your recovery environment, you can use the following command instead:
- Open Command Prompt as Administrator.
- Enter the command: "reagentc /info /target c:\Windows"
- This will display the information about your recovery environment, specifically for your Windows installation on the C: drive.
- If the information is not available or shows an error, it might indicate an issue with the recovery environment on your system.
4. Windows Preinstallation Environment (WinPE) showing as the current boot loader:
This is likely causing the confusion about why your Windows installation is in the Preinstallation Environment.
- Open Command Prompt as Administrator.
- Enter the command: "bcdedit /default {current}"
- This sets the default boot loader to {current}, which should point to your Windows installation.
- Restart your computer and check if Windows boots properly.
5. "Element not found" error when running "bootrec /fixboot":
This error can occur if the required boot files are missing or corrupted.
- Open Command Prompt as Administrator.
- Run the following commands one by one:
- "bootrec /fixmbr" (this repairs the Master Boot Record)
- "bootrec /fixboot" (this repairs the boot sector)
- "bootrec /rebuildbcd" (this scans for Windows installations and allows you to add them to the boot configuration)
- Restart your computer and check if the issue persists.
If these steps do not resolve your problems, it may be necessary to consider performing a repair installation or a clean installation of Windows 11. Before proceeding with any major changes, ensure that you have a backup of your important files to avoid data loss.
The default entry is not valid as specified.
Run "bcdedit /?" for command line assistance.
The parameter is incorrect.
- Joined
- May 22, 2012
- Messages
- 4,431
andybn1
New Member
- Joined
- Jan 6, 2024
- Messages
- 3
- Thread Author
- #5
This was the solution Redirecting
Chrisjordan33
New Member
- Joined
- Jan 11, 2024
- Messages
- 1
If Windows 11 is incorrectly detecting that it's in a preinstallation state after rebuilding the BCD (Boot Configuration Data) store, there could be a few reasons for this issue. Here are some steps you can try to resolve the problem:
- Check Boot Configuration Data (BCD):
- Open the Command Prompt as an administrator.
- Type the following command and press Enter:
Copy code.
bcdedit - Check the information displayed and ensure that the values are correct, especially the device and osdevice entries.
- Repair BCD:
- Open the Command Prompt as an administrator.
- Type the following commands and press Enter after each:
bashCopy code
bootrec /scanos
bootrec /rebuildbcd
- Check for Windows Updates:
- Make sure your Windows 11 installation is up-to-date by checking for and installing any available updates.
- Perform a System File Check (SFC) and Deployment Image Service and Management Tool (DISM) scan:
- Check Disk for Errors:
- Open the Command Prompt as an administrator.
- Run the following command:
bashCopy code
chkdsk /f - Restart your computer and let the check disk process complete.
- Perform a Repair Install:
- If the issue persists, consider performing a repair install of Windows 11. This option allows you to reinstall Windows without losing your files and applications.
- Joined
- May 22, 2012
- Messages
- 4,431
- Joined
- Mar 14, 2023
- Messages
- 44,742
Thank you for sharing this additional information about the bcdedit error. Based on this, it looks like your rebuilt BCD store is improperly set up, and the
{current}
entry is either missing or misconfigured. Let’s go deeper into solving this issue step by step:1. Diagnose the Current BCD Configuration
The error “The default entry is not valid
” indicates that {current}
may not exist or isn't pointing to the correct installation. You’ll need to first confirm what entries exist in the BCD.Steps:
- Open Command Prompt as Administrator.
- Run:
Code:cmd bcdedit /enum all
- Carefully review the output:
- Look for the correct Windows Boot Loader entry. It should:
- Reference the valid Windows installation directory (e.g.,
C:\Windows
). - Have an identifier, like
{current}
,{default}
, or a GUID in the form{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
.
- Reference the valid Windows installation directory (e.g.,
- If you don't see a valid entry, it means the BCD isn't properly pointing to a Windows installation, requiring manual configuration.
- Look for the correct Windows Boot Loader entry. It should:
2. Fix the BCD Configuration
Scenario 1: If {Current} is Missing
If{current}
doesn’t exist, create and configure it properly.- Identify the volume where Windows is installed:
- Run:
Code:cmd diskpart
- In DiskPart, run:
Code:cmd list vol
- Note the drive letter of the partition where Windows is installed (usually it's
C:
).
- Run:
- Create a new boot loader entry:
- Run:
Code:cmd bcdedit /set {default} osdevice partition=C: bcdedit /set {default} device partition=C: bcdedit /set {default} path \Windows\system32\winload.efi bcdedit /set {default} description "Windows 11" bcdedit /set {bootmgr} displayorder {default} bcdedit /default {default}
- Replace
partition=C:
with the correct drive letter for your Windows installation, if different (C:
is assumed here).
- Run:
- Reboot and test! This should create and set
{default}
(equivalent to{current}
).
3. Address the “Preinstallation Environment” Issue
If Windows still thinks it’s in the Preinstallation Environment (WinPE), you may need to refresh the Recovery Environment (RE) linkage.Steps:
- Check Windows RE status:
Code:cmd reagentc /info
- If it says
Disabled
, move to the next step to re-enable it.
- If it says
- Re-enable the Recovery Environment:
Code:cmd reagentc /enable
- Restart and check status again. The PC should boot into the Windows OS, not WinPE, assuming the BCD is corrected.
4. Fix the "bootrec /fixboot" Error
The infamous"Element not found"
error when running bootrec /fixboot
can happen if the EFI partition is not properly mounted or recognized. Let’s fix that next.Steps:
- Manually mount the EFI Partition:
- Open Command Prompt as Administrator and run:
Code:cmd diskpart
- In DiskPart:
Code:cmd list disk select disk [number] # Choose the disk with the EFI partition list partition select partition [number] # Choose the EFI partition (usually a 100MB FAT32 partition) assign letter=W
W
to the EFI partition for easier access.)
- Open Command Prompt as Administrator and run:
- Recreate Boot Files:
- Exit DiskPart by typing
exit
. - Then run the following commands to repair boot files:
Code:cmd cd /d W:\EFI\Microsoft\Boot\ bootrec /fixboot bcdboot C:\Windows /s W: /f UEFI
- Replace
C:\Windows
with the appropriate drive letter if Windows is installed on a different partition.
- Replace
- Exit DiskPart by typing
- Reboot and verify the fix.
5. Regenerate the Boot Manager
If things are still not booting up correctly, you can rebuild the entire BCD store as a last resort.Steps:
- Erase the Existing BCD (Be Careful!):
Code:cmd bcdedit /export C:\BCD_Backup attrib -r -s -h C:\boot\bcd del C:\boot\bcd
- Rebuild the BCD Store:
Code:cmd bootrec /rebuildbcd
- When prompted, type
Y
to add the detected Windows installation to the boot loader.
- When prompted, type
- Verify and Restart.
Backup Plan: Perform an In-Place Upgrade Repair
If all BCD fixes fail and your Windows keeps thinking it’s in preinstallation mode, consider an in-place upgrade repair:- Use the Windows 11 installation media.
- Choose Upgrade > Keep my files and apps to refresh the installation without losing data.
Final Check
Let me know:- Did the
/enum all
command show valid entries? - Were you able to set the
{default}
or fix the EFI partition?