Windows 8.1 failed to boot after an automatic update

[DRQ]

Hi,
I have a machine that hasn't always been well behaved but after a recent automatic update it wouldn't boot and automatic repair couldn't fix it. I've tried a few things and sfcfix.exe told me I would need help, so here I am!

I managed to get it working using an installation flash and, at the command prompt typing:
dism.exe /image:C:\ /cleanup-image /revertpendingactions

After going through this a couple of times I've hidden the following update and the machine boots.
2021-07 Security Monthly Quality Rollup for Windows 8.1 for x86-based Systems (KB5004298) - 348.1 MB Published on 13/07/2021


I tried:
sfc /scannow
but I appear to have lost my notes as to what that said.
I tried:
DISM /Online /Cleanup-Image /CheckHealth
which said it was fixable, as did:
DISM /Online /Cleanup-Image /ScanHealth

but when I tried
DISM /Online /Cleanup-Image /RestoreHealth
it said it couldn't find source files
I did also try it with a reference to a mounted ISO file but, sorry, again I've lost those notes.
I think it said something like no action had been taken


That's when I found sysnative.com so I tried sfcfix.exe. I've run that a couple of times and here is the latest log file:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2021-07-18 11:21:36.181
Microsoft Windows 8.1 Update 3 - x86
Not using a script file.




AutoAnalysis::
WARNING: Performed DISM repair due to manifest damage on component "x86_162ef6a3b7ffa3b66bd95f6f767f3109_b03f5f7f11d50a3a_4.0.9680.17244_none_c4b2ef5a3d008d66". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_23c44d3a14939a558d90c43e90395cda_b03f5f7f11d50a3a_4.0.9680.17299_none_5106d62e8d4f3da7". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_4ff1911320fa1386279eea2c24864bde_b03f5f7f11d50a3a_4.0.9680.17244_none_680a125e36d8b2e1". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_76490b0ef39476773fef2e2db07f6284_b03f5f7f11d50a3a_4.0.9680.17299_none_95f35bf08d79e1d0". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_7dfbb2c4b7569a6ca804737b0532f8c6_31bf3856ad364e35_4.0.9680.17299_none_6eb0b10187fc37da". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_9bdd32389dc893488da16640faa97382_b03f5f7f11d50a3a_4.0.9680.17299_none_fcf11265cd1ce9c6". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_a9d97d4b634f7b3603a7af1272903c34_31bf3856ad364e35_4.0.9680.17244_none_4bbc771ffd3d2b57". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_b2f81fb3a478152600d95a6326a38620_b03f5f7f11d50a3a_4.0.9680.17244_none_56a608f087306c8c". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_fcae06da1f518aeaf78a4b9e821578fe_b03f5f7f11d50a3a_4.0.9680.17299_none_96e0af1236b8ebb2". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_fdac013f888f8be948d71aa1ccfd96b3_31bf3856ad364e35_4.0.9680.17244_none_50fd618d45e89e3b". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_3b0c6856e57322af51bf4aab6c92e357_b03f5f7f11d50a3a_4.0.9680.17244_none_95f61a358f6d2b1c". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_59f7c3e2ec3a1327c5cbebb2a3719ea0_b03f5f7f11d50a3a_4.0.9680.17299_none_6c267935e6df5d88". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_971a50c3da8ae9ff13781bc887d7ba0a_31bf3856ad364e35_4.0.9680.17244_none_5ae3896c0710ed0a". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_df38ce7404e6cd0ef3c33563acc2bd53_b77a5c561934e089_4.0.9680.17244_none_9423418919060e42". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_00857d7ecc356bb312e194a167cc0f9d_31bf3856ad364e35_4.0.9680.17244_none_7ef8cfb2936e921d". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_28244c147edbae745d833a6ec69d7d1e_b03f5f7f11d50a3a_4.0.9680.17244_none_b790f42067282cdf". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_48ff9c658348a18226c289761bf6713b_31bf3856ad364e35_4.0.9680.17244_none_0e09d5eadd8e9e23". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_790d2e5e3bf8b05e5ab98eb10c11fa18_31bf3856ad364e35_4.0.9680.17299_none_60ea423398db7798". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_83c081f0a321504212c6b3d7bc091e1a_b03f5f7f11d50a3a_4.0.9680.17299_none_3a39465e40a1b6b7". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_a020adc08e24573fe93fd94775b16078_b03f5f7f11d50a3a_4.0.9680.17244_none_20d67a4d46be69aa". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_6dfc33dc5f623d1b9e2a0d1b7cfed8ba_b77a5c561934e089_4.0.9680.17244_none_0c267f7d8e97d33b". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_a141de8901b6fc8667d06bffa03752d6_b77a5c561934e089_4.0.9680.17299_none_f53ecde39a348986". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_8005a7fbb35eda357d11831a712348d4_b77a5c561934e089_4.0.9680.17299_none_a19a683a2719e292". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_b5dc64f4072395b9d17ef59c97c5eb62_b03f5f7f11d50a3a_4.0.9680.17299_none_dcab4022845c26ae". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_c46cbe1275cb88fcc0b3af45a3912603_b03f5f7f11d50a3a_4.0.9680.17244_none_21a82345b0ca23d5". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_e878c23a62c988c7a26223ef488496ca_b03f5f7f11d50a3a_4.0.9680.17244_none_a6377bc7e71601c5". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_f6332c4328f001d557e1b53e01448bc5_b77a5c561934e089_4.0.9680.17244_none_6efe5b69644be274". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_07f09e72034a94e438b19f1c1697440f_b03f5f7f11d50a3a_4.0.9680.17244_none_d62c77fc74b6b5b0". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_69a0cb79e013bacae0a4b830a85ba266_31bf3856ad364e35_4.0.9680.17244_none_7bb26a37cf690e67". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_b144c99494570c3999dca434e22a1366_b77a5c561934e089_4.0.9680.17244_none_3b670a2ed97d09b1". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "x86_2619d3f22122edec4e0e82bb3e888f73_b03f5f7f11d50a3a_4.0.9680.17244_none_138467182b30191b". See CBS logfile for more details.




SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
   CBS & SFC total detected corruption count:     124
   CBS & SFC total unimportant corruption count:  0
   CBS & SFC total fixed corruption count:        0
   SURT total detected corruption count:          0
   SURT total unimportant corruption count:       0
   SURT total fixed corruption count:             0
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2021-07-18 12:04:28.706
----------------------EOF-----------------------

All the log files gave the same warnings, but the very first one I had some slightly different comments, including

Failed to generate a complete zip file. Upload aborted.

, but I guess that's not so important.



Some computer information:
Medion Akoya s5610
Microsoft Windows 8.1 Pro with Media Center
6.3.9600 Build 9600
32-bit

I zipped up the CBS folder and it's on OneDrive at:
CBS folder zipped up
it's about 18 MB.

I've just looked at Windows Update and it was suggesting an update to Defender. I tried that to see if it would also make things fall over but it wouldn't install. Sorry, I did that after I'd grabbed the CBS log.

I think I've followed the guide on how to post an issue but I know I've not give the full details of the error message. I can re-run those if that would help.

Any help would be appreciated. The machine is not vital, but is useful and since it's working at the moment then I'd suggest that this is a relatively low priority, if you've got more desperate people out there looking for help then I will be happy to wait.

Regards,

Doug.

 

[PeterJ]

Hello and welcome,

Follow the instructions below please.

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 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.
  
  
• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Attach that file to your next reply.

 

[DRQ]

Hi,
I think I followed the instructions correctly...
Thanks for looking at this.
Regards,
DRQ

 

[PeterJ]

Well done.
Restart the computer.
Open an elevated command prompt.
Copy and paste the following commands into it, press enter after each.

sfc /scannow

Wait for this to finish before you continue

copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

This will create a file, cbs.txt on your Desktop. Zip this file and attach the zipped cbs.txt to your next post.

 

[DRQ]

And there should be 'cbs.zip' attached here.

 

[PeterJ]

It looks like all went well.
Check Windows Update and report the result.

 

[DRQ]

I shan't have a chance to do it today but will have a look tomorrow. BUt I'd like to check a couple of things, please.

I forgot to note it down but there was an error message from the sfc /scannow - sorry about that, I assumed it would be in the log but I'm confused by the apparent contradiction with your report that it looks to have gone well. I'm more thinking that I sent the wrong file rather than you're telling me something wrong!

With Windows Update, should I allow it to install the updates that caused the problem? I'd prevented these ones (can't remember how many, may only have been one) from installing for the time being since each time they installed it wouldn't boot.

I'd just like to make sure that I've understood correctly.

Thanks,

 

[PeterJ]

There was an error in the cbs.log but I think we can ignore that.

With Windows Update, should I allow it to install the updates that caused the problem?

You may provide a screenshot of the available important update first.

 

[DRQ]

There should be a couple of screenshots attached here. I don't know if I've properly captured the problematic update(s). The history shows that some of them have failed to install many, many times...

 

[PeterJ]

Try to install the update for "Microsoft Defender Antivirus" only.
If successful install the update for "Windows Malicious Software Removal Tool" only.

 

[DRQ]

Hi,
I selected only the update for Defender antivirus but that failed to install. Looking through the history that seems to have failed many times.
I have just restarted the computer and it seems to have done that OK, i.e. it's still booting.
I've not tried any other updates or anytihng else as yet.
Thanks (again) for your patience.

 

[PeterJ]

The dates in the second screenshot are puzzling, 2015, 2021 and 2024 !!
Check the system date and time.

 

[DRQ]

Maybe I need to wait until 2024 before the updates will install...

The system time and date is currently correct and set to automatic.

Both the main battery and the CMOS battery on this laptop are shot so if it gets disconnected from the mains power the system time and date are incorrrect until it manages to update itself. Although I don't know how it managed to come up with a future date.

 

[DRQ]

This laptop doesn't do much. It's connected to a television for Netflix, etc. and occasionally runs a 3D printer. It seems (to me) wasteful to go and get something else to just do those jobs.

 

[PeterJ]

FRST Scan:

1. Download the Farbar Recovery Scan Tool and save it to your Desktop:
   64-bit: Downloading Farbar Recovery Scan Tool
   Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.
   
2. Right-click to run the tool as administrator. When the tool opens click Yes to disclaimer.
3. Note: Ensure that the Addition.txt check box is checked at the bottom of the form within the Optional Scan area.
4. Press the Scan button.
5. Please wait for the tool to finish. It will produce two logfiles called FRST.txt and Addition.txt in the same directory the tool is run from (which should be the desktop)
6. Post the logfiles FRST.txt and Addition.txt as attachment in your next reply.

 

[DRQ]

The laptop is 32 bit so I used that version of FRST.

'Addition.txt' was selected as default, but various other options weren't. If you'd like me to re-run with those enabled then I can do that.

The log files should be attached here.

 

[PeterJ]

The laptop is 32 bit so I used that version of FRST.

Sorry for pointing to the x64 version. The scan was done correctly.


You have Avast installed. Windows Defender is therefore switched off and that might be the cause Windows Defender updates not installed successfully.

Step 1: Update Java
Open this web page to download the latest version. Click 'Free Java Download' and then 'Agree and Start Free Download'.
Download the installer jxpiinstall.exe and run it.
Click Install and then Install>.
Warning: You may get a choice to install additional software and/or allow to change your browser settings. Uncheck all that!
If you get a pop-up saying "Out-of-date Java versions detected.", click Uninstall>. This will remove the outdated Java versions.

Step 2:
Mozilla Firefox 43.0.1 (x86 en-GB) is an old version. Please update if you use this to browse the internet.
Uninstall Spybot - Search & Destroy. It's an old version. You may install the latest version when we are done in this thread.

Step 3:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.

1. Download the attachment fixlist.txt and save it to your desktop.
2. Right-click on FRST.exe and select "Run as administrator".
3. Press the Fix button.
4. The tool will now process fixlist.txt.
5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
7. Post the logfile Fixlog.txt as attachment in your next reply.

 

[DRQ]

Well, that didn't go quite as expected.

step 1- The Java download page didn't have a 'free download' link nor could I find any link to the 'jxpiinstall.exe' file you mentioned, but I think they may have updated the page and I have downloaded and run the installer. It di dremove an old version of Java in that process.

step 2 - Used the Firefox -> Help -> About -> Check for updates to install latest version of that and uninstalled S&D.

step 3 - when I ran 'FRST.exe' (right-click and run as administrator) it reported that it had updated successfully. Then it wouldn't work, giving the "Windows cannot access the specified device..." error message ('cannotaccess.png'), I think that was after I tried clicking on "Fix" rather than right away. I tried restarting the computer and then it gave that error message as soon as I tried to run it. I found the previous version and put that back on the desktop. I ran that and clicked on Fix and it seeemed to be doing something. I then went to grab a coffee. When I came back there was the normal desktop on the screen and no sign of the tool. And no sign of of a logfile and the 'FRST.exe' file had also vanished from the desktop. I did a search for 'Fixlog.txt' and nothing was found. I just tried copying 'FRST.exe' on to the desktop, thinking about running it again so I coud see any messages and it now won't let me, saying that access is denied ('access_denied.PNG', 'no_progress.PNG', 'access_denied_2.PNG').

So... I now don't have write access to the desktop?

 

[PeterJ]

Disable the realtime-protection of Avast.
Perform step 3 in my previous message again and report the result.

 

[DRQ]

That was a bit more straightforward. I could copy the 'FRST.exe' to the desktop this time - I don't understand how that works... Computers are confusing.

The 'fixlog.txt' should be attached here.