Windows 10: Reagentc disabled, and NO OPTIONS in ADVANCED Starup

Hello,

I've fairly fresh install of Windows 10 PRO. I wanted to go to Safe Mode to check a few things, but this is what popped up after holding SHIFT when clicking on Restart
Dropbox - W10.jpg

Quite a shocker to me.

Now, I've tried to solve it myself and got this far:

1. Reagentc is disabled
And Reagentc /enable does nothing. It says it finished sucessfully, but when Reagentc /info, I always get message that it is disabled.

2. SFC / Scannow completed sucessfully
But anyway, I downloaded the MS tool to do a repair renistall.
Did few steps, the tool downloaded necessary stuff and...

3. Windows 10 install tool said it could not detect, whether I got enough free space on the drive (WTF??)
To be clear, I have almost 300 GB of free space.


Otherwise, the system performs great.
Now, is there any option to fix it quickly and avoid any waste of time?

Thank you very much!
Jan.

:)

 

Windows and CMD- renaming a file in CMD

Steps I've done

Here what happens

• 
  turn on PC
  
• 
  start windows
  
• 
  get blue screen ( message NTFS file)
  
• 
  it reboots returns to diagnosing PC
  
• 
  Diagnose and repair fails
  
• 
  I move to advance options
  
• 
  will not reset windows , I click on CMD
  

things I've tried
commands:

reagentc /disable

reagentc /enable

*************************FAILED
not recognized
**********************************

Please advise

• 
  

 

Can't create a Windows 10 recovery drive. Some required files are missing.

Thank you very much. I had the same problem. when I typed reagentc /disbable, I see the message "already disabled". So I jumped to last step. Typed only reagentc /enabled and
Yip! . I think some version of windows 10 comes with this option disabled default. Thank you again.

 

To enter safe mode HP PCs - Windows Safe Mode (Windows 10, 8) | HP® Customer Support scroll down to "Entering Safe Mode from Windows 10" you'll find complete instructions to enter safe mode for your model of computer.

Google is your friend, googled "Pavillion dv7-6110 safe mode" first hit is the link posted above.
https://www.google.com/?gws_rd=ssl#q...6110+safe+mode

Good luck *Smile

 

I have already tried that, and as you can see from the screenshot, this is where the problem originates *Wink





Thanks,
Jan.

 

Sorry for my misunderstanding, just giving different things to try and must have overlooked that part *Redface

Have you tried options 2 and 3 from this tutorial? One of these should be able to boot in safe mode.

https://www.tenforums.com/tutorials/2...dows-10-a.html

Are you logged on as admin? I don't use safe mode much and I'm always logged on as admin anyway, so I'm not sure if the user needs to be logged on as an admin to boot into safe mode.

 

You will have to post a screenshot of disk management so we can see where the recovery partition is - or if there is one:
Disk Management - How to Post a Screenshot of - Windows 10 Tutorials

Also, the output from reagentc /info will help us too:

Code: Microsoft Windows [Version 10.0.14393] (c) 2016 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\partition1\Recovery\WindowsRE Boot Configuration Data (BCD) identifier: fcaab811-8717-11e6-843d-aa73efa5da58 Recovery image location: \\?\GLOBALROOT\device\harddisk1\partition3\Sources Recovery image index: 1 Custom image location: Custom image index: 0 REAGENTC.EXE: Operation Successful.[/quote]

 

Thanks for the replies. Tbh I haven't tried the 2nd a 3rd option to Safe mode boot yet, but will try as soon as I need it.

Here is the screenshot of the Disk management
(please note that the unallocated 46.58GB space is over-provisioning for the SSD disk).




And here is what reagentc /info reports
Code: Windows Recovery Environment (Windows RE) and system reset configuration Information: Windows RE status: Disabled Windows RE location: Boot Configuration Data (BCD) identifier: 8cfac78e-a660-11e6-94b0-bdb896bc3472 Recovery image location: Recovery image index: 0 Custom image location: Custom image index: 0 REAGENTC.EXE: Operation Successful.[/quote] Many thanks!

PS: The site might be showing I'm no Pavilion laptop (which is still true), but the problem is related to HP 6300 Microtower. Just in case this made a difference.

 

Looks like you need to run in a command prompt (admin):

reagentc /setreimage /path \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE
reagentc /enable

NOTE: there is a space between /path and \\

 

Done that... still not running *Sad

Code: Microsoft Windows [Version 10.0.14393](c) 2016 Microsoft Corporation. All rights reserved. C:\Windows\system32>reagentc /setreimage /path \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE Directory set to: \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE REAGENTC.EXE: Operation Successful. 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: Disabled Windows RE location: Boot Configuration Data (BCD) identifier: 8cfac78e-a660-11e6-94b0-bdb896bc3472 Recovery image location: Recovery image index: 0 Custom image location: Custom image index: 0 REAGENTC.EXE: Operation Successful.[/quote]

 

If you only have one Windows OS running then the 100MB EFI System partition on disk 1 should not be there. You'd need to delete this partition or better yet, temporarily disconnect disk 1 then reboot and try reagentc again.

 

I've been running for almost a month without Disk 1.
Connected it just yesterday to troubleshoot this... so, safe to say Disk 1 has nothing to do with it.

 

Update.
I have tried repair install with Disk 1 connected, but the installer still cannot tell how much free space I got... and stops there.

I cannot believe one of the biggest software companies, literally an inventor of PC segment cannot tell how much free space I got.

 

I would open a command prompt (admin) and run:

chkdsk C: /f

You'll have to restart the computer. Then after that is done, in command prompt (admin) run:

sfc /scannow

See if you have any errors that can be corrected. Seems like something has corrupted part of the drive.

 

Done that. No errors detected by CHKDISK nor SFC.