Windows 8 will not update

S

sinyc

New member
Joined
Oct 25, 2014
Posts
4
Location
Las Vegas, Nv
My computer has had a string of crashes and finally would not start yesterday. I tried what I could and then just did a complete wipe and tried reinstalling Windows 8 pro. Initial updates were done and then it got to a point where windows update would not work and I started getting blue crash screens again. All attempts to fix via my installation disk have not worked. I cant update to Windows 8.1 either.
Further attempts at windows update give error 8007246. Trying to fix via the troubleshooter, it says fixed and future attempts give the same error.
I ran SFCFix and below is the result...

Welcome to SFCFix by niemiro and sysnative.com.


Checking for updates . . .
No new update is available at this time.


Processing directive 1 of 1 (AutoAnalysis::)
Beginning flash scan of Windows Update registry.Checking store directories . . .


Checking CBS.log . . .
Checking CBS.persist.log . . .
Checking CheckSUR.log . . .
Checking CheckSUR.persist.log . . .


Attempting repair . . .
Stage 1
Stage 2
Stage 3


Due to the nature of your corruptions, scan times have been extended by
approximately 15-20 minutes. Please be patient and allow the operation to
complete.




Deployment Image Servicing and Management tool
Version: 6.2.9200.16384


Image Version: 6.2.9200.16384


[==========================100.0%==========================]


Error: 582


An illegal character was encountered. For a multi-byte character set this includ
es a lead byte without a succeeding trail byte. For the Unicode character set th
is includes the characters 0xFFFF and 0xFFFE.


The DISM log file can be found at C:\Windows\Logs\DISM\dism.log


...Please help.
 
Hello and welcome to the forum.

Is there a file called SFCFix.txt on desktop? if so can you please attach it to this post.

SFC /SCANNOW
  1. Right click on the
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on Command prompt (Admin) => Press Yes on the prompt
  3. Inside the Command Prompt windows copy and paste the following command SFC /SCANNOW
  4. Please wait for this to Finish before continuing with rest of the steps.
Convert CBS.log to CBS.txt
  1. Right click on the
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on Run => Inside the run box copy and paste the following command:
    Code: 
    cmd /c copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  3. Press Enter
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please upload CBS.txt to this thread
Please Note:: if the file is too big to upload to you next post please upload via Dropbox or One Drive



As for the BSOD can you please follow the steps here:
https://www.sysnative.com/forums/bs...ons-windows-10-8-1-8-7-and-windows-vista.html

Then upload the required files to this post and I will get a BSOD analyst to come and take a look for you.

Alex
 
Thanks for responding. I am still getting BSOD interuptions every once in a while.
I don't have the SFCFix.txt file on my desktop and the cbs file is in the OneDrive file below.
https://onedrive.live.com/redir?resid=50433FBEA4A5227A!2573&authkey=!AOV2TtLGeGAtLKI&ithint=file,txt


Is there a file called SFCFix.txt on desktop? if so can you please attach it to this post.

SFC /SCANNOW
  1. Right click on the
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on Command prompt (Admin) => Press Yes on the prompt
  3. Inside the Command Prompt windows copy and paste the following command SFC /SCANNOW
  4. Please wait for this to Finish before continuing with rest of the steps.
Convert CBS.log to CBS.txt
  1. Right click on the
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on Run => Inside the run box copy and paste the following command:
    Code: 
    cmd /c copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  3. Press Enter
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please upload CBS.txt to this thread
Please Note:: if the file is too big to upload to you next post please upload via Dropbox or One Drive



As for the BSOD can you please follow the steps here:
https://www.sysnative.com/forums/bs...ons-windows-10-8-1-8-7-and-windows-vista.html

Then upload the required files to this post and I will get a BSOD analyst to come and take a look for you.

Alex[/QUOTE]
 
There are some strange errors appearing in your SFC log, ones that I have not seen before. I would like to take a look at the registry hive called COMPONENTS, please do the following:

SFCFix Collect COMPONENTS
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. On your Desktop, you should now see two files: SFCFix.exe and SFCFixScript.txt.
  4. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  5. SFCFix will now begin to upload your CBS logfiles to our server.
  6. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  7. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.


If all goes well, you should see that your logfiles have now been added to your thread.
 
Thanks for your help. I didn't understand the last part of item 7. But, here is the contents of the txt file:

SFCFix version 2.4.1.0 by niemiro.
Start time: 2014-10-27 17:23:05.695
Using .txt script file at C:\Users\Milton\Desktop\SFCFixScript.txt [0]








Collect:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2014-10-27 17:25:30.243
----------------------EOF-----------------------



Go The Power said:
There are some strange errors appearing in your SFC log, ones that I have not seen before. I would like to take a look at the registry hive called COMPONENTS, please do the following:

SFCFix Collect COMPONENTS
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. On your Desktop, you should now see two files: SFCFix.exe and SFCFixScript.txt.
  4. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  5. SFCFix will now begin to upload your CBS logfiles to our server.
  6. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  7. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.


If all goes well, you should see that your logfiles have now been added to your thread.
Click to expand...
 
Thank you that worked.

Below you can see some symbols in the string's, they are not meant to be there, these are known as bitflip's. It should be pretty straight forward to fix and I hope to have a fix for you within the next few days.

Code: 
Key:   HKEY_LOCAL_MACHINE\28173640\DerivedData\Components\amd64_microsoft-windows-registry-editor_31bf3856ad364e35_6.2.9200.16384_none_4cf85cc9659cdc8e
Value: identity
Data:  Microsoft-Windows-Registry-Editor, Culture=neutral, Version=6.2.9200.16384, PublicKeyToken=31bf3856ad364e35, ProcessorArch�tecture=amd64, versionScope=Non�xS

Key:   HKEY_LOCAL_MACHINE\28173640\DerivedData\Components\amd64_microsoft-windows-registryidle-agent_31bf3856ad364e35_6.2.9200.16384_nonå_7836e33372a0ef52
Value: identity
Data:  Microsoft-Windows-RegistryIdle-Agent, Culture=neutral, Version=6.2.9200.16384, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd6�, versionScope=NonSxS

Key:   HKEY_LOCAL_MACHINE\28173640\DerivedData\Components\amd64_microsoft-windows-reliability-adm_31bf3856ad364e35_6.2.9200.16384_none_bc440b90cb3dc094
Value: identity
Data:  Microsoft-Windows-Reliability-Adm, Culture=neutral, Versio�=6.2.92�0.16384, PublicKeyToken=31bf3856ad364e3�, ProcessorArchitecture=amd64, versionScope=NonSxS

Alex
 
Hello again,

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download SFCFixScript.txt that is attached to this post, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

try Windows updates again, if it fails please continue.


DISM Scan

  1. Right click on the
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on Command prompt (Admin) => Press Yes on the prompt
  3. Inside the Command Prompt windows copy and paste the following command DISM /Online /Cleanup-Image /RestoreHealth
  4. Please wait for this to Finish before continuing with rest of the steps.
Convert CBS.log to CBS.txt
  1. Right click on the
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on Run => Inside the run box copy and paste the following command:
    Code: 
    cmd /c copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  3. Press Enter
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please upload CBS.txt to this thread
Please Note:: if the file is too big to upload to you next post please upload via Dropbox or One Drive
 

Attachments

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