New
#1231
I've been trying to perform sfc, dism, chkdsk... Though it's probably the OS that is damaged. I've been trying to get at the original windows 10 installation, to see if I can determine where the error (0x82f) is to be found. But that hasn't been possible. The SrtTrail.txt states that a recently maintained (? translating from Dutch, here) binary start-up element has been damaged (part of an update in progress, apparently).
I've entered the command you provided, but it also didn't work, gave me error 2.
I've used this PE to get into my PC stuck in boot loop in order to see if things are fixable. I've been able to get out all my files and media, so that's good. I haven't mounted any C:-drive image, though, just tried to access the installation that's on my hard drives to discover whether anything is fixable. But that's probably not the case...