[SOLVED] Unable to update Windows Update itself and other problems.

Rantsoft · May 18, 2015

Hello,

I'm using a Pavilion g6 g6-2292nr laptop with Windows 8, and while I've had a few problems in the past getting updates to install, Windows Update states that it the updater itself needs to update, which it fails at doing. It returns an error code of 800703F1, and using the troubleshooter option claims that it's fixed some problems, but trying to run the updater again only results in bringing up the same or a similar error code. Repeating those steps just seems to give me the same set of error codes over and over. I can't run sfc in command prompt without getting error 11, I can't use DISM because I get a message that I need a 64-bit version, and I'm not even able to refresh my PC through the PC Settings. I'm pretty much at a loss of what to do. :huh:

Below are the files requested from the posting instructions thread. Can't seem to use the file attachment system here, so I've uploaded both files to Dropbox. Any help would be appreciated.

https://www.dropbox.com/s/vsv18ne67c8ng09/SFCFix.txt?dl=0
https://www.dropbox.com/s/y5xdowww62kkg5z/CBS.zip?dl=0

BrianDrab · May 21, 2015

Hi and welcome to Sysnative. You have some interesting errors.

Code:

2015-05-18 13:15:44, Error                 CSI    00000011@2015/5/18:17:15:44.770 (F) base\wcp\componentstore\com\store.cpp(4878): Error NTSTATUS_FROM_WIN32(1009) originated in function Windows::COM::CComponentStore::MountSMISchemaHive expression: MountSMISchemaHive
2015-05-18 13:16:17, Error                 CBS    Exec: Failed to commit CSI transaction to execute changes. [HRESULT = 0x800703f1 - ERROR_BADDB]

Before we start looking at potentially fixing these I would like you to do a disk check. Please do the following.

ChkDsk
1. Point your mouse to the lower left of your computer screen and click on the Start screen. Type cmd on the Start Screen.
2. Once the Command Prompt program is found, right-click on it with your mouse and select Run as administrator.
3. Answer Yes when asked to allow.
4. You should now have a black window open that you can type in to.
5. Please type chkdsk and then press enter.
6. Let it complete please.
7. Download ListChkdskResult.exe by SleepyDude and save it on your desktop.
8. Right-click this file and select Run as administrator (Allow if prompted)and a text file will open (and also be saved on the desktop as ListChkdskResult.txt).
Please copy the contents of this file and paste into your next post

Rantsoft · May 22, 2015

Hi, thanks for the response. Here are the contents of the txt file:

Code:

ListChkdskResult by SleepyDude v0.1.7 Beta | 21-09-2013

------< Log generate on 5/22/2015 7:57:31 PM >------
Category: 0
Computer Name: T
Event Code: 26213
Record Number: 172872
Source Name: Chkdsk
Time Written: 05-22-2015 @ 22:56:50
Event Type: Information
User: 
Message: Chkdsk was executed in read-only mode.  A volume snapshot was not used. Extra errors and warnings may be reported as the volume may have changed during the chkdsk run.  


Checking file system on C:
The type of the file system is NTFS.
The volume is in use by another process. Chkdsk
might report errors when no corruption is present.


WARNING!  F parameter not specified.
Running CHKDSK in read-only mode.


CHKDSK is verifying files (stage 1 of 3)...
  441856 file records processed.                                         


File verification completed.
  5690 large file records processed.                                   


  0 bad file records processed.                                     




CHKDSK is verifying indexes (stage 2 of 3)...
Index entry CHKDSK.EXE-13847046.pf of index $I30 in file 0x1967 points to unused file 0x339c2.


Index entry CHKDSK.EXE-13847046.pf in index $I30 of file 6503 is incorrect.
The file reference 0x894000000019faf of index entry f_00eb6a of index $I30
with parent 0x294e6 is not the same as 0x879000000019faf.


Index entry f_00eb6a in index $I30 of file 169190 is incorrect.
Index entry htt8E35.tmp of index $I30 in file 0x3e6ef points to unused file 0x1c466.


Index entry htt8E35.tmp in index $I30 of file 255727 is incorrect.
Index entry htt91DE.tmp of index $I30 in file 0x3e6ef points to unused file 0x1c7f8.
Index entry htt91DE.tmp in index $I30 of file 255727 is incorrect.
Index entry #sKKuZumucej&k07.tmp.dat of index $I30 in file 0x50fb5 points to unused file 0x3814e.


Index entry #sKKuZumucej&k07.tmp.dat in index $I30 of file 331701 is incorrect.
  569906 index entries processed.                                        


Index verification completed.


Errors found.  CHKDSK cannot continue in read-only mode.


-----------------------------------------------------------------------
Category: 0
Computer Name: T
Event Code: 26213
Record Number: 171749
Source Name: Chkdsk
Time Written: 05-18-2015 @ 01:28:51
Event Type: Information
User: 
Message: Chkdsk was executed in read-only mode.  A volume snapshot was not used. Extra errors and warnings may be reported as the volume may have changed during the chkdsk run.  


Checking file system on C:
The type of the file system is NTFS.
The volume is in use by another process. Chkdsk
might report errors when no corruption is present.


WARNING!  F parameter not specified.
Running CHKDSK in read-only mode.


CHKDSK is verifying files (stage 1 of 3)...
  441856 file records processed.                                         


File verification completed.
  5684 large file records processed.                                   


  0 bad file records processed.                                     




CHKDSK is verifying indexes (stage 2 of 3)...
Index entry CHKDSK.EXE-13847046.pf of index $I30 in file 0x1967 points to unused file 0x4e9b8.


Index entry CHKDSK.EXE-13847046.pf in index $I30 of file 6503 is incorrect.
Index entry CMD.EXE-2EB3E6E2.pf of index $I30 in file 0x1967 points to unused file 0x4e9b2.
Index entry CMD.EXE-2EB3E6E2.pf in index $I30 of file 6503 is incorrect.
  569782 index entries processed.                                        


Index verification completed.


Errors found.  CHKDSK cannot continue in read-only mode.


-----------------------------------------------------------------------

BrianDrab · May 22, 2015

Thank you. There are errors on your disk that we need to correct. Please do the following. Ensure you have time to allow it to complete. It could take a couple hours but usually finishes faster.

ChkDsk
1. Point your mouse to the lower left of your computer screen and click on the Start screen. Type cmd on the Start Screen.
2. Once the Command Prompt program is found, right-click on it with your mouse and select Run as administrator.
3. Answer Yes when asked to allow.
4. You should now have a black window open that you can type in to.
5. Please type chkdsk /R and then press enter. Note: There is a space before the / slash. You will be prompted to reboot in order to run this. Please do.
6. Let it complete please.
7. Download ListChkdskResult.exe by SleepyDude and save it on your desktop.
8. Right-click this file and select Run as administrator (Allow if prompted)and a text file will open (and also be saved on the desktop as ListChkdskResult.txt).
Please copy the contents of this file and paste into your next post

Rantsoft · May 23, 2015

All right. It took a little over 4 hours to complete, but here's the new txt file.

Code:

ListChkdskResult by SleepyDude v0.1.7 Beta | 21-09-2013

------< Log generate on 5/23/2015 12:36:20 AM >------
Category: 0
Computer Name: T
Event Code: 1001
Record Number: 172897
Source Name: Microsoft-Windows-Wininit
Time Written: 05-23-2015 @ 04:32:11
Event Type: Information
User: 
Message: 


Checking file system on C:
The type of the file system is NTFS.


A disk check has been scheduled.
Windows will now check the disk.                         


CHKDSK is verifying files (stage 1 of 5)...
  441856 file records processed.                                         


File verification completed.
  5693 large file records processed.                                   


  0 bad file records processed.                                     




CHKDSK is verifying indexes (stage 2 of 5)...
  569904 index entries processed.                                        


Index verification completed.
  0 unindexed files scanned.                                        


  0 unindexed files recovered.                                      




CHKDSK is verifying security descriptors (stage 3 of 5)...
CHKDSK is compacting the security descriptor stream
Cleaning up 6050 unused security descriptors.
  64025 data files processed.                                           


CHKDSK is verifying Usn Journal...
  4540656 USN bytes processed.                                            


Usn Journal verification completed.


CHKDSK is verifying file data (stage 4 of 5)...
Windows replaced bad clusters in file 76588
of name \Windows\System32\DRIVER~1\FILERE~1\PRNCAC~3.INF\Amd64\CNBJ2530.DPB.
Windows replaced bad clusters in file 87463
of name \Windows\WinSxS\AM7F7F~1.163\tctree.dat.
Windows replaced bad clusters in file 273273
of name \Windows\WinSxS\Backup\x86_microsoft-windows-a..on-authui-component_31bf3856ad364e35_6.2.9200.16604_none_d9d8dbd8e0fd96b7_authui.dll_05ff9fd2.
  441840 files processed.                                                


File data verification completed.


CHKDSK is verifying free space (stage 5 of 5)...
  208095377 free clusters processed.                                        


Free space verification is complete.
CHKDSK discovered free space marked as allocated in the volume bitmap.


Windows has made corrections to the file system.
No further action is required.


 949365759 KB total disk space.
 116288572 KB in 324873 files.
    152212 KB in 64028 indexes.
         0 KB in bad sectors.
    543463 KB in use by the system.
     65536 KB occupied by the log file.
 832381512 KB available on disk.


      4096 bytes in each allocation unit.
 237341439 total allocation units on disk.
 208095378 allocation units available on disk.


Internal Info:
00 be 06 00 2f ef 05 00 b4 39 08 00 00 00 00 00  ..../....9......
72 1b 00 00 54 00 00 00 00 00 00 00 00 00 00 00  r...T...........
00 00 6f e1 91 00 00 00 04 00 00 00 00 00 00 00  ..o.............


Windows has finished checking your disk.
Please wait while your computer restarts.


-----------------------------------------------------------------------
Category: 0
Computer Name: T
Event Code: 26213
Record Number: 172872
Source Name: Chkdsk
Time Written: 05-22-2015 @ 22:56:50
Event Type: Information
User: 
Message: Chkdsk was executed in read-only mode.  A volume snapshot was not used. Extra errors and warnings may be reported as the volume may have changed during the chkdsk run.  


Checking file system on C:
The type of the file system is NTFS.
The volume is in use by another process. Chkdsk
might report errors when no corruption is present.


WARNING!  F parameter not specified.
Running CHKDSK in read-only mode.


CHKDSK is verifying files (stage 1 of 3)...
  441856 file records processed.                                         


File verification completed.
  5690 large file records processed.                                   


  0 bad file records processed.                                     




CHKDSK is verifying indexes (stage 2 of 3)...
Index entry CHKDSK.EXE-13847046.pf of index $I30 in file 0x1967 points to unused file 0x339c2.


Index entry CHKDSK.EXE-13847046.pf in index $I30 of file 6503 is incorrect.
The file reference 0x894000000019faf of index entry f_00eb6a of index $I30
with parent 0x294e6 is not the same as 0x879000000019faf.


Index entry f_00eb6a in index $I30 of file 169190 is incorrect.
Index entry htt8E35.tmp of index $I30 in file 0x3e6ef points to unused file 0x1c466.


Index entry htt8E35.tmp in index $I30 of file 255727 is incorrect.
Index entry htt91DE.tmp of index $I30 in file 0x3e6ef points to unused file 0x1c7f8.
Index entry htt91DE.tmp in index $I30 of file 255727 is incorrect.
Index entry #sKKuZumucej&k07.tmp.dat of index $I30 in file 0x50fb5 points to unused file 0x3814e.


Index entry #sKKuZumucej&k07.tmp.dat in index $I30 of file 331701 is incorrect.
  569906 index entries processed.                                        


Index verification completed.


Errors found.  CHKDSK cannot continue in read-only mode.


-----------------------------------------------------------------------
Category: 0
Computer Name: T
Event Code: 26213
Record Number: 171749
Source Name: Chkdsk
Time Written: 05-18-2015 @ 01:28:51
Event Type: Information
User: 
Message: Chkdsk was executed in read-only mode.  A volume snapshot was not used. Extra errors and warnings may be reported as the volume may have changed during the chkdsk run.  


Checking file system on C:
The type of the file system is NTFS.
The volume is in use by another process. Chkdsk
might report errors when no corruption is present.


WARNING!  F parameter not specified.
Running CHKDSK in read-only mode.


CHKDSK is verifying files (stage 1 of 3)...
  441856 file records processed.                                         


File verification completed.
  5684 large file records processed.                                   


  0 bad file records processed.                                     




CHKDSK is verifying indexes (stage 2 of 3)...
Index entry CHKDSK.EXE-13847046.pf of index $I30 in file 0x1967 points to unused file 0x4e9b8.


Index entry CHKDSK.EXE-13847046.pf in index $I30 of file 6503 is incorrect.
Index entry CMD.EXE-2EB3E6E2.pf of index $I30 in file 0x1967 points to unused file 0x4e9b2.
Index entry CMD.EXE-2EB3E6E2.pf in index $I30 of file 6503 is incorrect.
  569782 index entries processed.                                        


Index verification completed.


Errors found.  CHKDSK cannot continue in read-only mode.


-----------------------------------------------------------------------

BrianDrab · May 23, 2015

I know you have tried this before but I need to establish a baseline after chkdsk was run. Please do the following.

DISM /RestoreHealth Scan
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.

Point your mouse down to the bottom left corner of your screen until the Start Screen icon appears. Right-click on the Start Screen icon and select Command Prompt (Admin)
When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
Dism /Online /Cleanup-Image /RestoreHealth
When DISM finishes scanning your component store, zip up and attach your CBS log to your next post:
C:\Windows\Logs\CBS\CBS.log

Note: If you get an error when attempting this command please provide the EXACT error message. Thank you.

Rantsoft · May 24, 2015

All right, so I tried that, and I received the same error that I had before. Here's a screenshot for reference:

BrianDrab · May 24, 2015

The screen shot was helpful. I can see that you are running the 32-bit version from the title bar. Please do the following.

1. Bring up the command-prompt like you did previously.
2. Then type start c:\windows\system32\cmd.exe
3. A new command-prompt window will open. In the title bar of the new window that opens you will see Administrator: c:\windows\system32\cmd.exe
4. Now please run DISM and provide the log.

Thanks.

Rantsoft · May 24, 2015

Seems like I'm still getting the same result as before. Here's a screenshot of both Command Prompt windows for reference.

BrianDrab · May 24, 2015

Get both Command Prompt windows open like you just did previously. Then open up Task Manager. You can hit CTRL-SHIFT-ESC to do this. Find the Windows Command Processor Apps and see if it looks like follows. Notice one has 32 bit in parenthesis and the other doesn't. Does yours look like this?

Rantsoft · May 25, 2015

Huh. It seems that both of mine are the 32 bit version of Command Prompt. I'm going to assume that's the problem, but I'm not quite sure how to get the 64 bit version of it running. Any ideas?

BrianDrab · May 25, 2015

I have a few ideas. Let's first establish if the file exists on your machine anywhere.

Step#1 - SFCFix Script - FileScan
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.

Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
Download the file below, SFCScript.txt, and save this to your Desktop.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
Drag the file SFCScript.txt onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please

Rantsoft · May 25, 2015

Okay, here are the contents of the txt file.

Code:

SFCFix version 2.4.3.0 by niemiro.Start time: 2015-05-25 17:49:49.887
Microsoft Windows 8  - amd64
Using .txt script file at C:\Users\TotallyTim\Desktop\SFCScript.txt [0]








FileScan::
[0: 2] C:\Windows\WinSxS\amd64_microsoft-windows-wrp-integrity-client_31bf3856ad364e35_6.2.9200.16384_none_840874a1750a67bc\sfc.exe
File is untraceable.
 Found: P9u/JCCh+teoZb898qdMceW808MwHtYl6GmEPlU3QBc=
 Found: 6.2.9200.16384
Trace not available.


 [C:\Windows\System32\sfc.exe]




[1: 2] C:\Windows\WinSxS\x86_microsoft-windows-wrp-integrity-client_31bf3856ad364e35_6.2.9200.16384_none_27e9d91dbcacf686\sfc.exe
File is untraceable.
 Found: 74lhSXQSfFmtiHbb3AHqDMRUuws8eVDupTGNdkXMQso=
 Found: 6.2.9200.16384
Trace not available.


 [C:\Windows\SysWOW64\sfc.exe]
FileScan:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.3.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2015-05-25 17:49:53.041
Script hash: 6NLaV6gNkgfFggf7kelHoUdqOp0mr14HF5o+68ULcR0=
----------------------EOF-----------------------

BrianDrab · May 25, 2015

Good. Now let's do it one more time using a different script file.

Step#1 - SFCFix Script - FileScan
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.

Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
Download the file below, SFCScript.txt, and save this to your Desktop.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
Drag the file SFCScript.txt onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please

Rantsoft · May 25, 2015

All right.

Code:

SFCFix version 2.4.3.0 by niemiro.Start time: 2015-05-25 18:21:19.826
Microsoft Windows 8  - amd64
Using .txt script file at C:\Users\TotallyTim\Desktop\SFCScript.txt [1]








FileScan::
[0: 2] C:\Windows\System32\cmd.exe
File is untraceable.
 Found: hYpXZqLeVKaQiiyjDdWYN5C4xjYUpFUpJhOxKYdyI+k=
 Found: 6.2.9200.16384
Trace not available.


 [C:\Windows\WinSxS\amd64_microsoft-windows-commandprompt_31bf3856ad364e35_6.2.9200.16384_none_e3d66e21a420bf66\cmd.exe]




[1: 2] C:\Windows\WinSxS\wow64_microsoft-windows-commandprompt_31bf3856ad364e35_6.2.9200.16384_none_ee2b1873d8818161\cmd.exe
File is untraceable.
 Found: kQ1SExW4O7DYBerOrDyDFpqnkdHR5ktBcHfAGuIf62Y=
 Found: 6.2.9200.16384
Trace not available.


 [C:\Windows\SysWOW64\cmd.exe]




[2: 1] C:\HP\BIN\cmd.exe
File is untraceable.
 Found: hYpXZqLeVKaQiiyjDdWYN5C4xjYUpFUpJhOxKYdyI+k=
 Found: 6.2.9200.16384
Trace not available.
FileScan:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.3.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2015-05-25 18:21:22.166
Script hash: xwpWnzH+CdRqKiqeKknU0ixNSSN2Klan0fdNnNrHZMY=
----------------------EOF-----------------------

BrianDrab · May 25, 2015

OK, your system has the correct versions of both x64 and x86. Please do the following exactly as stated so we bypass all system shortcuts.

1. Click the File Explorer button on your taskbar.

2. On the left side of the screen, click the arrow next to the C: drive so it expands.

3. Locate the Windows folder and then click the arrow next to it to expand it.

4. Locate the System32 folder and click directly on that folder.
5. On the right pane window where the results are, scroll down until you find cmd

6. Right-click on this file and select Run as administrator. Answer Yes to the UAC prompt if it comes up.
7. Now open up the task manager and verify that you are running the 64-bit version of the command-prompt.

Let me know please.

Rantsoft · May 25, 2015

Yep, I believe that did the trick.

BrianDrab · May 25, 2015

Awesome. Let's do this now.

DISM /RestoreHealth Scan
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.

Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
Dism /Online /Cleanup-Image /RestoreHealth
When DISM finishes scanning your component store, zip up and attach your CBS log to your next post:
C:\Windows\Logs\CBS\CBS.log

Note: If you get an error when attempting this command please provide the EXACT error message. Thank you.

Rantsoft · May 25, 2015

All righty.

https://www.dropbox.com/s/y5xdowww62kkg5z/CBS.zip?dl=0

BrianDrab · May 25, 2015

Thanks. The only errors in the log are these.

Code:

2015-05-25 19:36:19, Error                 CBS    Failed to ask UI handler to terminate. [HRESULT = 0x800706ba - RPC_S_SERVER_UNAVAILABLE]
2015-05-25 19:36:20, Error                 CBS    Failed to ask UI handler to terminate. [HRESULT = 0x800706ba - RPC_S_SERVER_UNAVAILABLE]

So now that we have a way to get a proper command prompt, please run the following.

SFC
1. Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
sfc /scannow

2. Once it finishes (even if it errors out), copy and paste the following into the command-prompt window and press Enter.
copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

3. 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 your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.

[SOLVED] Unable to update Windows Update itself and other problems.

Member

Emeritus

Member

Emeritus

Member

Emeritus

Member

Emeritus

Member

Emeritus

Member

Emeritus

Attachments

Member

Emeritus

Attachments

Member

Emeritus

Member

Emeritus

Member

Emeritus