After Repair: Can Shutdown/Boot but Not Restart/Boot

Hello all,

In attempting to fix this problem:
Encountering "Element not found" on File History Cleanup

I used this solution:
Repair Install Windows 10 with an In-place Upgrade

And it worked! The repair fixed that particular issue and I now have a working-as-expected File History (at least as far as that problem is concerned).

However, now I have a new problem.

When I reboot the machine, the machine restarts twice and then on the 3rd time results in the following screen:



Upon hitting Enter, it continues as desired and Windows boots.

Note that I have tried Startup Repair and it still results in this issue. Also note that I have tried Macrium's Fix Boot Problems as discussed here:
v5: How to fix Windows boot problems (Restore, Windows PE)

And it did not address the issue.

The weird thing is that if I shut down the computer and turn it back on, it boots like a charm. It's only when I do a restart that I run into this problem.

Any suggestions/hints towards fixing this issue would be appreciated.

- - - Updated - - -

I'm wondering... should I Repair again?

Thank you for your reply, @zbook! I am going to paste what I find here. Note that I have redacted the username for security purposes.

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell Installing PowerShell - PowerShell | Microsoft Docs

PS 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.
PS C:\WINDOWS\system32> dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.329

Image Version: 10.0.19041.330

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.
PS C:\WINDOWS\system32> dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.329

Image Version: 10.0.19041.330

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
PS 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.
PS C:\WINDOWS\system32> chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
504320 file records processed.
File verification completed.
Phase duration (File record verification): 2.18 seconds.
6991 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.25 milliseconds.

Stage 2: Examining file name linkage ...
204 reparse records processed.
611426 index entries processed.
Index verification completed.
Phase duration (Index verification): 5.73 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 274.17 milliseconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.81 milliseconds.
204 reparse records processed.
Phase duration (Reparse point and Object ID verification): 3.18 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 50.04 milliseconds.
53554 data files processed.
Phase duration (Data attribute verification): 0.27 milliseconds.
CHKDSK is verifying Usn Journal...
34542056 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 39.63 milliseconds.

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

487023699 KB total disk space.
84672188 KB in 159865 files.
132160 KB in 53555 indexes.
0 KB in bad sectors.
626291 KB in use by the system.
65536 KB occupied by the log file.
401593060 KB available on disk.

4096 bytes in each allocation unit.
121755924 total allocation units on disk.
100398265 allocation units available on disk.
Total duration: 8.29 seconds (8290 ms).
PS C:\WINDOWS\system32> get-computerrestorepoint
PS C:\WINDOWS\system32> get-computerrestorepoint -laststatus
The last attempt to restore the computer failed.
PS C:\WINDOWS\system32> get-localuser

Name Enabled Description
---- ------- -----------
Administrator False Built-in account for administering the computer/domain
DefaultAccount False A user account managed by the system.
----- True
Guest False Built-in account for guest access to the computer/domain
WDAGUtilityAccount False A user account managed and used by the system for Windows Defender Application Guard scen...

Also note that my install drive is Disk 1 and not Disk 0:



I will look into installing the other two applications. I am hesitant on installing any applications on this machine unless absolutely necessary and can confirm a clean install/uninstall. I am also hoping the above can assist towards diagnosing as well.

While I do so, are you able to comment on why this seems to happen on a restart and not a shutdown?

Thank you for any continued assistance!

Open administrative command prompt and copy and paste: (all at one time)

Code:

bcdedit /enum all
reagentc /info
diskpart
lis dis
lis vol
sel dis 0
det dis
sel par 1
det par
sel par 2
det par
sel par 3
det par
sel par 4
det par
sel par 5
det par
sel par 6
det par
sel par 7
det par
sel dis 1
det dis
sel par 1
det par
sel par 2
det par
sel par 3
det par
sel par 4
det par
sel par 5
det par
sel par 6
det par
sel par 7
det par

When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread


Please post an image of disk management including the upper portion (expand columns)


This command and result were not yet displayed:
10) powercfg -h off

Whoops! Sorry about that @zbook, here you go:

Code:

PS C:\WINDOWS\system32> powercfg -h off
PS C:\WINDOWS\system32> bcdedit /enum all

Firmware Boot Manager
---------------------
identifier              {fwbootmgr}
displayorder            {bootmgr}
timeout                 1

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}
resumeobject            {ed16a0a0-b6aa-11ea-b510-309c23e0f9ea}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \WINDOWS\system32\winload.efi
description             Windows 10
locale                  en-us
inherit                 {bootloadersettings}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {ed16a0a0-b6aa-11ea-b510-309c23e0f9ea}
nx                      OptIn
bootmenupolicy          Standard

Resume from Hibernate
---------------------
identifier              {ed16a0a0-b6aa-11ea-b510-309c23e0f9ea}
device                  partition=C:
path                    \WINDOWS\system32\winresume.efi
description             Windows Resume Application
locale                  en-us
inherit                 {resumeloadersettings}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
filedevice              partition=C:
filepath                \hiberfil.sys
bootmenupolicy          Standard
debugoptionenabled      No

Windows Memory Tester
---------------------
identifier              {memdiag}
device                  partition=\Device\HarddiskVolume1
path                    \EFI\Microsoft\Boot\memtest.efi
description             Windows Memory Diagnostic
locale                  en-us
inherit                 {globalsettings}
badmemoryaccess         Yes

EMS Settings
------------
identifier              {emssettings}
bootems                 No

Debugger Settings
-----------------
identifier              {dbgsettings}
debugtype               Local

RAM Defects
-----------
identifier              {badmemory}

Global Settings
---------------
identifier              {globalsettings}
inherit                 {dbgsettings}
                        {emssettings}
                        {badmemory}

Boot Loader Settings
--------------------
identifier              {bootloadersettings}
inherit                 {globalsettings}
                        {hypervisorsettings}

Hypervisor Settings
-------------------
identifier              {hypervisorsettings}
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200

Resume Loader Settings
----------------------
identifier              {resumeloadersettings}
inherit                 {globalsettings}
PS C:\WINDOWS\system32> reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Disabled
    Windows RE location:
    Boot Configuration Data (BCD) identifier: a5fc395c-b677-11ea-b3ec-a9a561807678
    Recovery image location:
    Recovery image index:      0
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.

If I am not mistaken, the diskpart should provide the same information as the disk management. Please let me know if you still require the screenshot.

As for the above, it seems WinRE is disabled? Could that be a part of the problem?

Had you performed an in place upgrade repair from 1909 to 2004 or 2004 to 2004?
Had you performed a clean install?
What are the status of the important files?
a) backup image
b) files backed up to another drive or the cloud
c) no image or file backup > need to save files
d) no image or file backup > don't need to save files


Open administrative command prompt and type or copy and paste:
reagentc /enable
net user test /add


display results

reboot

Log on with the new user named test.
reboot

Report into the thread whether the boot has changed or remains the same.

Alright I think we're getting warmer here:

Code:

PS C:\WINDOWS\system32> reagentc /enable
REAGENTC.EXE: Unable to update Boot Configuration Data.

PS C:\WINDOWS\system32> net user test /add
The command completed successfully.

Looks like there's a problem with BCD? Since there seems to be a problem here I will wait for your next instruction/suggestion.

As for the upgrade, yes I did a 1909 -> 2004 in place upgrade, followed by a 2004 Repair as denoted in my first post above.

- - - Updated - - -

Ah apologies, to answer your question about backups I do have an image backup that I make weekly with Windows Backup.

Please post the results that were requested earlier.

It's 3:25 AM here.

Post the results for:
the diskpart commands
disk management


How come you did not post these earlier?

Ah apologies @zbook I did post them but took them down as posting my entire diskpart inventory is a bit sensitive information I do not want floating out on the internet. Hope that makes sense. I also saw that there is a private message function and figured I would send them to you if needed. Should I send you a private message?

I, too, also have questions that I have asked you that have gone unanswered, btw. :)

The EFI partition can be rebuilt.

With missing or disappearing data it can't be done now.

If anyone is to provide help they need to know partitions / volumes.
This info can be deleted at the completion of troubleshooting.
Deleting while troubleshooting consumes time having to request it again and again.