yesterday my windows 10 PC went trough a update, after it it worked normally, during the night I was compiling resources for a Linux OS in Virtual Box and after 1 hour or so I had a blue screen of death.
Windows tries to make automatic repairs, runs a diagnostic and opens the windows recovery environment. When trying to open saved checkpoints windows shows 3 restore checkpoints and if selected to show more it shows one more, but when trying to login on any of those checkpoints the process is interrupted saying that the system was not able to restore to that point.
Automatic repair option in the recovery environment doesn’t seem to do anything that the initialisation automatic repair doesn’t try to do and returns to the recovery environment.
Opening the cmd from the recovery environment and trying to run sfc /scannow returns :"Windows Resource Protection could not perform the required operation", then I tried using chkdsk on both my main ssd and additional hard drive, it seemed as if the ssd were Windows is installed had some problems that chkdsk appears to have solved since calling it again does not return those same messages, among them it appears that there was free space in the disk that seemed to having been interpreted as occupied space.
Although after running chkdsk and reinitiating the computer I still run in the same problems as before. sfc /scannow still gives that same message.
Then I tried to run Bootrec /fixMbr, which seemed to be sucessful but then Bootrec /fixboot gives me a acess denied reply, in this moment it seems to me as if the cmd in recovery mode is not running as administrator which could explain why sfc /scannow does not work and neither Bootrec /fixboot also doesn’t.
Also when opening C:\Windows\System32\Logfiles\Srt\SrtTrail.txt the closest thing that looked like a error was in:
"Name: Check for installed LCU
Result: Completed successfully. Error code = 0xc1 "
But the file ends with "Startup Repair has tried several times but still cannot determine the cause of the problem."
Even in the beginning when I tried to recover the system maintaining only my files it also did not work it appeared 1% and gave a message about undoing what it had done and that it was not possible to recover the system.
What I find strange is that I can access all my files trough the windows recovery environment cmd, which does not seem to imply large scale memory corruption, I think that if I could get sfc /scannow running all would be fixed.
EDIT: I just tried to run sfc /scannow from C:\Windows\System32 instead of from X:\Windows\System32 and got "This version of C:\Windows\System32\sfc.exe is not compatible with the version of Windows being executed. Verify the informations of the system of the computer and contact the supplier of the software." Doesn’t that mean that the problem is in the windows update since X: and C: have different and incompatible versions of sfc?
NEW EDIT: I have also tried to run sfc /verifyonly this results in "The Windows Resource Protection found integrity violations. For online repairs, the details are included in the CBS log file localized in windir\Logs\CBS\CBS.log so I decided to open the CBS.log in C:\Windows\Logs\CBS\CBS.log but the last entry was of yesterday and it appears to be from the update with TrustedInstaller, TiWorker and other such calls, the file ending with Ending TrustedInstaller finalization at 11:13:59 which is strange since I remember the update taking place at around 02:25:16 which is in fact were the previous set of entries begin in CBS.log , but no entry appears to be from the just run sfc /verifyonly.
NEW NEW UPDATE: After searching for verifiable evidence that there is something wrong with my SSD and/or HD, since that appears to be a "common place" with what regards to what the problem is with my computer, the following is a image of the cmd of the Windows Recovery Environment after using commands to get the SMART status of both drives (the part before that was I running chkdsk on my drives again, it is in Portuguese because my system is in Portuguese, but the result of SMART is in English anyway.).
Update Update: so after losing time with silly considerations for ssd failing, which it is not, It appears that I have randomly tripped on the actual problem, it seems that my BCD file is either corrupted or has some other problem, when invoking "bcdboot C:\Windows /s N: /f ALL" I get the following error: "BFSVC error:could not open the BCD template store. Status = [c000015c]" when going to C:\Windows\System32\config there is a BCD-template that supposedly is used to recreate the BCD template in the Boot directory, going to such a directory that is a unnamed occult FAT32 partition that I have named N: and going to N:\EFI\Microsoft\Boot there is a BCD file there, I have saved the old BCD as BCD.bak and tried to create a new BCD, with BCDBOOT but still got the same error, although a new BCD was present at the N:\EFI\Microsoft\Boot folder, it still doesn’t work, so I think that the BCD-template was corrupted and is creating bad BCD in the boot directory, is there a way to repair this BCD-template file without a Windows install CD? And if it can be done only with a install CD what are the exact steps that one should take, and will this erase all my files or make all installed programs stop working?
