Win 10 - Automatic Repair (fails) suddenly on boot

[field_studies]

Hi all,
Hope someone here with a similar experience can help. I've spent the morning reading forums, but haven't found a solution to my current issue.

I'm using a new (1 month old) Windows 10 pre-built tower. It arrived, I soon discovered, with a faulty motherboard. Once that was replaced it seemed to be working without issue ... until this morning ...

Now it boots straight into the Automatic Repair blue-screen. This fails. In the advanced options, I've tried to use Startup Repair, System Restore, Previous Version, and even Windows Reset, but none work (the first fails, the next two claim there are no previous points to revert to, and windows reset fails).

I've also tried to boot off of a Windows 10 media creation tool USB. That only seems to give me the option of a clean install of Windows or, by selecting the 'repair' option, puts me back into the startup repair bluescreen, with the same (non-working) options as earlier, minus Windows Reset.

I'm nearly resigned to taking it in to the store for repair, but as they can't look at it until tomorrow so figured I'd try to work at it a little more myself.

A couple other notes:
- I've run CHKDSK on my C: drive, and it turned up clean
- strangely, if I disconnect my C: drive, I get the same blue screen circuit detailed above; but if I disconnect either of my storage drives, I get just a black screen with "reboot and select proper boot device"
- I have accessed the boot log in my System32 folder. There are a few warming messages therein. If it would be helpful, I can post those.

If anyone has any ideas, I'd be very grateful!

 

[field_studies]

Just to update a little. I don't know if this is helpful info, but I looked into my C: window log folder. In the file DISMReportLogFile.txt I found the following error/warning messages (these all refer to my latest boot attempt [from Windows installation USB])

"[...] c:\Windows may not point to a valid Windows folder. - DISMOSServiceManager: : Final_OnConnect"

"Failed to load the provider: X:\windows\TEMP\92DA3[etc]\PEProvider.dll. - CDISMProviderStore : : Inter [...]"

"Failed to load the provider: X:\windows\SYSTEM32\Dism\MetaDeployProvider.dll. -CDISMProviderStore: :Internal_GetProvider [...]"

"[1524] [0x80070002] FIOReadFileIntoBuffer: (1381): The system cannot find the file specified."

 

[field_studies]

One last update:

I've now been able to run sfc /scannow and dism.exe /Image:C:\ /Cleanup-image /Restorehealth
though neither seemed to turn up anything or help.

 

[field_studies]

Oh wow ... after hours of working at this, I think it's (sort of) fixed.

I was poking around the Auto-Repair blue screen again, and tried the option "use another version of windows". There were two versions of Win 10 listed there-- "Windows 10" and "Windows 10 home". I selected the latter, and for the first time today Windows booted into what looked like an update-finish-up status screen and then into Windows.

Will see how stable this is.