Windows 10: SFC Fails within Recovery Enviroment

I started getting the dreaded startup repair loop, and am unable too boot in Win 10 Insider build 16199. I have a multiboot, with Win 7, which works fine.
I went to the command line within WinRE and ran chkdsk on the Win 10 partition, which found no errors. I then ran SFC /SCANNOW. First step ran fine. It then ends with the message "Windows resource protection could not perform the requested operation." Then back to the command line. Any ideas? Many thanks for the help.

Jon

:)

 

automatic startup repair failed

how to reset PC from the Recovery Enviroment?

 

My asus transformer says cant find recovery enviroment when I try to restore orig factory settings what can I do

my asus book says cant find recovery enviroment haw can I fix this?

 

Yes, you'll get that if you just type SFC /SCANNOW. Without any options you're trying to run it on the online system (currently WinRE) not on your installed Windows - that's an offline system at present.

From the recovery environment command prompt you need to use SFC's /OFFWINDIR option (and perhaps /OFFBOOTDIR) to tell it the system you want it to check. If from the WinRE command prompt your Windows system appear to be on the D: drive and installed in the \Windows folder then the command is:

SFC /SCANNOW /OFFWINDIR=D:\WINDOWS

I`d be careful with the /OFFBOOTDIR option as you have a dual boot system, I`m not sure what the effect could be. I don`t have a dual-boot system to test it on. On a single-boot system this runs successfully:

SFC /SCANNOW /OFFBOOTDIR=D:\ /OFFWINDIR=D:\WINDOWS

Code: /OFFBOOTDIR For offline repair specify the location of the offline boot directory /OFFWINDIR For offline repair specify the location of the offline windows directory[/quote] Type SFC /? for the full Help

Edit: There's more on using SFC at boot in Options One and Two here...

Run SFC Command in Windows 10

...and on using it with dual-boot systems in Method Two here:

SevenForums - SFC /SCANNOW : Run in Command Prompt at Boot

 

Bree, thank you for your response. I will try your advice and let you know the results.

 

I finally got around to running SFC from WinRE with the additional parms pointing to the Win10 partition. After completing the message was it found corrupted files, but was unable to to repair all of them. Logging not available in offline mode. Any ideas are greatly appreciated. Thanks.

 

Good. Now try sfc again. From the tutorial...

 

Bree, I'll check it out. One of the perks of retirement is time isn't much of factor Many thanks for the heads up.

 

Ok, I created a WinPE Khly (sp) boot USB drive. Neither SFC or DISM will run. Are they not supported in that environment? Also, I got past the automatic repair loop by using Macrim to repair the MBR. Now I'm now getting an error about a Malwarebytes driver corruption. It happens both regular and safe boot. Is there any way to uninstall an app without booting the Win10 partition? Thanks for any advice.
Jon

 

You'd have to ask @Kyhi that. The usual way to boot to a command prompt would be to boot from Windows 10 install media (not sure how you'd make that for your Insider build 16199) or a Recovery Drive USB (Control Panel\All Control Panel Items\Recovery > Create a recovery drive).

 

I have an ISO for 16193. If I burn that to USB, I should be able too use that, right? Thanks.
Jon

 

Not being an Insider I can't say, but it sounds like it's worth a try.

 

Thanks Bree, I'll give a try. What's the worst that can happen? Ouch!!!
Jon

 

Well, I never saw the iceberg. I sank this morning while working in bootice. I'm now sitting at the grub rescue > waiting to issue commands to boot Ubuntu so I can reinstall GRUB. The Windows side isn't any better. It boots to an error about missing winload.exe. I'll tackle that after I fix the first debacle. Mom always said I should be a doctor.

 

Ouch!

Sorry, I don't do Ubuntu, but others do, hopefully they'll join this thread...