[SOLVED] Game installation - found issues in SFC - Win7

B

billp

Contributor
Joined
Mar 17, 2018
Posts
129
I installed a game (Fallout76) but it won't start. I contacted Bethesda support and they have been walking me through some steps.

They did the usual "please run chkdsk", etc. One of the steps was to run SFC /SCANNOW. I have run this before with no issues, but
interestingly it found problems. As the issue I'm having with the game is internet connectivity, I do not think the issues found are
related, but folks here at Sysnative have been great in the past helping me diagnose issues.

Granted, this is an old O/S, but the machine has been a good workhorse and runs every day. Never had any significant issues, so
I'm reaching out for help on the off chance that the SFC issues can be fixed and I can see if that made any difference.

I went through the steps on the Windows Update Forum Posting Instructions and am attaching the ZIP of the CBS log file.

Thanks!
 

Attachments

Hello,

Follow the instructions below please.

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
  • Download
    myjIXnC.png
    SFCFix and move the executable to your desktop.
  • Download the attachment SFCFix.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Open the file, then copy and paste its content in your next reply.

Step 2:
Restart the machine.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails attach the file cbs.log to your next reply.
 

Attachments

Great. Please attach the file cbs.log again. I'd like to check something else.
 
An update is missing, preventing another update to install successful.
Please do following.

Install Update with DISM
  1. Download the update MSU here: http://download.windowsupdate.com/c..._92202202c3dee2f713f67adf6622851b998c6780.msu
  2. Copy the MSU file to a convenient location (such as C:\temp).
  3. Click on the Start button and in the search box, type Command Prompt
  4. When you see Command Prompt on the list, right-click on it and select Run as administrator
  5. When command prompt opens, copy and paste the following commands into it, press enter after each

    cd C:\temp
    replace C:\temp with your path if different

    expand windows6.1-kb4555449-x64_92202202c3dee2f713f67adf6622851b998c6780.msu -f:* C:\temp

    DISM.exe /Online /Add-Package /PackagePath:C:\temp\windows6.1-kb4555449-x64.cab

  6. You should receive the message:
    The operation completed successfully.
    Make sure to allow the computer to restart if prompted.
  7. If you receive any other message:
    Post a screenshot of the Commandprompt window.
    Zip and attach the file C:\Windows\Logs\CBS\CBS.log
 
I did the steps you specified and got a "The operation completed successfully." message
 
Great. Is the issue with the game Fallout76 solved ?
 
Sadly, no. It's a connectivity thing that Bethesda is being tight-lipped about (based on my experience and from others with
the same issue posting in various forums). The error code is shown, which obviously the software came across an issue and
displayed this specific code, but all of their "debugging" is in the general form of "try turning it off & on again" instead of saying
"oh, that code happens when we see _______". Like a doctor starting at your toes when you have a cut on your forehead.
No, treat the obvious thing first, please. But they won't. <shrug>

Some of their debugging steps are valid & necessary which is why I ran SFC at their request. Asking for help here with the
CBS.log is just me being worrisome that "something isn't quite right" because I'm used to SFC returning "everything's OK".
While I had hopes it might fix the game problem, I didn't think it would. But leaves me with a cleaner machine, so thanks!

The SysNative folks helped me out a few years back with a strange issue on another machine, so I know you folks know how
to read a CBS.log and recommend a fix, and I remain grateful for your efforts.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top