Can't Boot Into default Windows Partition

NavyLCDR · 22 Mar 2021

zebal said:

After which OS should be recovery partition put then? do you need 2 RE for each like in screenshot from OP?

I normally disable the recovery environment using "reagentc /disable". Then delete the recovery partition. Then re-enable the recovery environment with "reagentc /enable". This puts the recovery environment files in a hidden Recovery folder right on C: drive. My multi-OS disk will have an EFI System partition, MSR partition, followed by the partitions containing the OSes. No recovery partitions.

Megahertz · 22 Mar 2021

NavyLCDR said:

I normally disable the recovery environment using "reagentc /disable". Then delete the recovery partition. Then re-enable the recovery environment with "reagentc /enable". This puts the recovery environment files in a hidden Recovery folder right on C: drive. My multi-OS disk will have an EFI System partition, MSR partition, followed by the partitions containing the OSes. No recovery partitions.

NavyLCDR, on previous Windows versions (7 for sure) Recovery folder was under C:\Windows.
Do you know why did M$ moved it to a dedicated partition on Win 10?

NavyLCDR · 22 Mar 2021

Megahertz said:

NavyLCDR, on previous Windows versions (7 for sure) Recovery folder was under C:\Windows.
Do you know why did M$ moved it to a dedicated partition on Win 10?

No clue. Although, maybe, it has something to do with more partitions being available with GPT disks than MBR disks. And it's even more confusing because when you disable the recovery environment, Windows 10 "stores" the files in C:\Windows\Recovery (I think). But then when you re-enable the recovery environment it moves it to C:\Recovery. Here's the transcript of deleting a Recovery partition:

Code:

Microsoft Windows [Version 10.0.19043.867]
(c) 2020 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Enabled
    Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
    Boot Configuration Data (BCD) identifier: f589e185-630f-11eb-9197-3413e83d466c
    Recovery image location:
    Recovery image index:      0
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.


C:\WINDOWS\system32>diskpart

Microsoft DiskPart version 10.0.19041.610

Copyright (C) Microsoft Corporation.
On computer: JOHN-LAPTOP

DISKPART> lis dis

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          476 GB  1024 KB        *
  Disk 1    Online          476 GB  2048 KB        *

DISKPART> select dis 0

Disk 0 is now the selected disk.

DISKPART> lis par

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    System             100 MB  1024 KB
  Partition 2    Reserved            16 MB   101 MB
  Partition 3    Primary            412 GB   117 MB
  Partition 4    Recovery           552 MB   412 GB
  Partition 5    Primary             64 GB   412 GB

DISKPART> exit

Leaving DiskPart...

C:\WINDOWS\system32>reagentc /disable
REAGENTC.EXE: Operation Successful.


C:\WINDOWS\system32>diskpart

Microsoft DiskPart version 10.0.19041.610

Copyright (C) Microsoft Corporation.
On computer: JOHN-LAPTOP

DISKPART> sel dis 0

Disk 0 is now the selected disk.

DISKPART> lis par

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    System             100 MB  1024 KB
  Partition 2    Reserved            16 MB   101 MB
  Partition 3    Primary            412 GB   117 MB
  Partition 4    Recovery           552 MB   412 GB
  Partition 5    Primary             64 GB   412 GB

DISKPART> sel par 4

Partition 4 is now the selected partition.

DISKPART> del par override

DiskPart successfully deleted the selected partition.

DISKPART> exit

Leaving DiskPart...

C:\WINDOWS\system32>reagentc /enable
REAGENTC.EXE: Operation Successful.


C:\WINDOWS\system32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Enabled
    Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition3\Recovery\WindowsRE
    Boot Configuration Data (BCD) identifier: f589e18b-630f-11eb-9197-3413e83d466c
    Recovery image location:
    Recovery image index:      0
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.

Brentg · 22 Mar 2021

FreeBooter said:

Which partition is the second Windows OS installed on i only see one Boot partition.

Volume = F

- - - Updated - - -

zebal said:

I don't know if this is the problem but you seem to have 2 RE partitions, which one should Windows use?
Can you boot into RE? (blue screen Recovery Environment)

Btw. you can't have 2 Windows OS'es on same drive I think. (unless I'm wrong ofc, never tried with GPT)

I have had 2 Windows OS'es on same drive for several months now. Now the default won't boot and the system boots directly to the RE environment where I choose the second OS and it opens and runs.

- - - Updated - - -

NavyLCDR said:

@Brentg,

We need to start with seeing the output of:

Code:

diskpart
select disk 0
list part

DISKPART> select disk 0

Disk 0 is now the selected disk.

DISKPART> list part

Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 System 100 MB 1024 KB
Partition 2 Reserved 16 MB 101 MB
Partition 3 Primary 393 GB 117 MB
Partition 4 Recovery 538 MB 393 GB
Partition 5 Primary 390 GB 393 GB
Partition 6 Recovery 1024 MB 930 GB

zbook · 22 Mar 2021

When available please update the progress with the steps in post #2.

Brentg · 23 Mar 2021

zbook said:

When available please update the progress with the steps in post #2.

###########################################################
# The following commands will be run in sequence. #
# They can take quite a while to run, be patient. #
###########################################################

sfc /scannow
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth
sfc /scannow

chkdsk /scan

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.746

Image Version: 10.0.19042.746

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.746

Image Version: 10.0.19042.746

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.
Volume label is Acer.

Stage 1: Examining basic file system structure ...
879376 file records processed.
File verification completed.
Phase duration (File record verification): 1.96 minutes.
6785 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.54 milliseconds.

Stage 2: Examining file name linkage ...
25520 reparse records processed.
1036294 index entries processed.
Index verification completed.
Phase duration (Index verification): 3.47 minutes.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 3.39 seconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 1.41 milliseconds.
25520 reparse records processed.
Phase duration (Reparse point and Object ID verification): 115.19 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 248.42 milliseconds.
78460 data files processed.
Phase duration (Data attribute verification): 1.26 milliseconds.
CHKDSK is verifying Usn Journal...
38945808 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 889.16 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

412302446 KB total disk space.
259360908 KB in 360209 files.
304984 KB in 78461 indexes.
0 KB in bad sectors.
996582 KB in use by the system.
65536 KB occupied by the log file.
151639972 KB available on disk.

4096 bytes in each allocation unit.
103075611 total allocation units on disk.
37909993 allocation units available on disk.
Total duration: 5.51 minutes (330941 ms).

C:\WINDOWS\system32>Echo off
###################################################################################
# How to capture batch file data and post in your thread in the BSOD forum #
# #
# Batch files and instructions for use in BSOD debugging[Part Two-Four] #
# #
# Press [V] to visit the above web page for detailed instructions. #
# Press [C] to close this window. #
###################################################################################

zbook · 23 Mar 2021

These are the links to run:
https://www.tenforums.com/attachment...ing-tuneup.bat

Please don't accidentally run:
Tuneup1.bat
Tuneup2.bat

Make sure it is: Tuneup.bat Batch files for use in BSOD debugging

Run:

DiskParInfo.bat
DiskParInfo.bat - Click here to go to the BSOD batch repository to download and run this batch file.

NavyLCDR · 23 Mar 2021

Brentg said:

DISKPART> select disk 0

Disk 0 is now the selected disk.

DISKPART> list part

Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 System 100 MB 1024 KB
Partition 2 Reserved 16 MB 101 MB
Partition 3 Primary 393 GB 117 MB
Partition 4 Recovery 538 MB 393 GB
Partition 5 Primary 390 GB 393 GB
Partition 6 Recovery 1024 MB 930 GB

The commands that you want to try first are:

Code:

diskpart
select disk 0
select part 1
assign letter=w
exit
bcdboot C:\Windows /s W: /f UEFI
exit

Reboot the computer, see if that fixes anything. If it boots into C: then run the command:

Code:

bcdboot F:\Windows /d /addlast

That will set up dual booting.

In your BIOS, make sure that CSM (or legacy BIOS) booting is disabled. You have to boot in UEFI mode. Make sure your disk 0 is the first disk in the boot priority list. If you have an option called Network Stack or PXE, disable those - that is booting from a network location.

Brentg · 23 Mar 2021

NavyLCDR said:

The commands that you want to try first are:

Code:

diskpart
select disk 0
select part 1
assign letter=w
exit
bcdboot C:\Windows /s W: /f UEFI
exit

Reboot the computer, see if that fixes anything. If it boots into C: then run the command:

Code:

bcdboot F:\Windows /d /addlast

That will set up dual booting.

In your BIOS, make sure that CSM (or legacy BIOS) booting is disabled. You have to boot in UEFI mode. Make sure your disk 0 is the first disk in the boot priority list. If you have an option called Network Stack or PXE, disable those - that is booting from a network location.

The command assign letter=w worked, but when I ran bcdboot C:\Windows /s W: /f UEFI I got the message that the boot files could not be copied.

zbook · 23 Mar 2021

Please indicate any problems running the bat files in post #17.
(manual commands can be posted)