Situation:
I was attempting to make a game work, but got an error saying api-ms-win-crt-runtime-l1-1-0.dll is missing. According to various sources, this should be fixed by running the Visual C++ update shipped with the game. I tried running the update, and it seemed to stop doing anything after a while. Cancelling the update gave me a log where it shows that it tries to install KB2999226 two times and then just stops doing anything on the third run. I figured I'd download the update straight from the microsoft site and run it from there, which also fails to do anything (it "searches for updates" forever). I instead decided to use admin cmd to extract the update using wusa.exe and then tried to add the package with DISM.exe. At this point, I was told the configuration registry database is corrupt. I then tried "SFC /SCANNOW" which claimed to have fixed something.
After the SFC /SCANNOW, the DISM.exe response is unchanged, and double-clicking the .msu (which previously looped forever) now runs but tells me it failed. I tried rerunning SFC /SCANNOW on the off chance and was told all is well.
I ran the SFCFix tool:
AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.
I was attempting to make a game work, but got an error saying api-ms-win-crt-runtime-l1-1-0.dll is missing. According to various sources, this should be fixed by running the Visual C++ update shipped with the game. I tried running the update, and it seemed to stop doing anything after a while. Cancelling the update gave me a log where it shows that it tries to install KB2999226 two times and then just stops doing anything on the third run. I figured I'd download the update straight from the microsoft site and run it from there, which also fails to do anything (it "searches for updates" forever). I instead decided to use admin cmd to extract the update using wusa.exe and then tried to add the package with DISM.exe. At this point, I was told the configuration registry database is corrupt. I then tried "SFC /SCANNOW" which claimed to have fixed something.
After the SFC /SCANNOW, the DISM.exe response is unchanged, and double-clicking the .msu (which previously looped forever) now runs but tells me it failed. I tried rerunning SFC /SCANNOW on the off chance and was told all is well.
I ran the SFCFix tool:
AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.