[SOLVED] SFC not able to repair corrupt files

[dennisd301]

A few weeks ago, my Windows 10 pc bluescreened with the error code BAD_SYSTEM_CONFIG_INFO and upon rebooting repeatedly showed another, different bluescreen. I booted to an installation of Windows on a different drive and ran chkdsk targeting the original drive, which seemed to fix whatever was causing the bluescreen. Once I booted back to the affected installation of Windows, the welcome screen with date and time would show, but when I tried to get to the login screen with the password entry box, my username with a loading icon was shown for a split second and I was back to the welcome screen. Thinking that perhaps some Windows files were corrupt, I booted to the spare installation of Windows and ran dism and sfc /scannow targeting the affected Windows installation, both of which detected multiple corrupt files but were unable to repair them.

I have also attached the CBS folder from the affected Windows installation as CBS (2), and the log for DISM if it helps.

 

[dennisd301]

I eventually found a way to fix the problem. First, I found a way to open the command prompt at the welcome screen by changing the name of Magnify.exe to something different, changing cmd.exe to Magnify.exe, and then using the shortcut to open magnifier (Win + Plus key). Next, I ran an online scan with DISM and sfc /scannow followed by running SFCFix. After restarting, I was able to continue to the login screen with the password (in my case, a PIN) entry box, which showed the error "Something went wrong and your PIN isn't available (code: 0x80090010). Click to set up your PIN again." Setting up the PIN did not work, but I was still able to log in with my Microsoft account password. I then got to the desktop and tried to set up a PIN again, but the option to set up a PIN was unavailable in account settings even after logging out of all accounts other than my main one, so I went ahead and did an in-place install of Windows 10. After the reinstall, I was able to set my PIN and password, and have had no issues since.