[SOLVED] Windows update corruptions

Alright, SFC returned a clean log (only a few repairs were made). Let's see if it's the same for DISM.
 
DISM had to be twice due to services needing to be started as i mentioned in notes i uploaded to you along with the DISM log file from the second attempt, the only log file i succeeded at as the first time
i mistakenly copied the cbs log of course not meaning to. In any event it failed regardless, once we resolve this issue i would like to pursue the issue with the install.wim mount for other reasons.

This time there was a connection to the provider store it seems, i am not certain if that is a new development.

Look forward to next instructions the link to the file is

https://www.dropbox.com/s/rzt25unbd4xnil5/DISM 2ND TRY.zip?dl=0
 
This is what DISM returned:
Code: 
(p)	CSI Payload Corrupt	(Fixed)	x86_microsoft-windows-t..-collaboration-core_31bf3856ad364e35_6.2.9200.16384_none_b7ba023dc7917ceb\rdpcore.dll
(p)	CSI Payload Corrupt	(Fixed)	msil_system.identitymodel_b77a5c561934e089_6.2.9200.16384_none_285b0383f3e6b112\System.IdentityModel.dll
(p)	CSI Payload Corrupt	(Fixed)	amd64_netfx35linq-system.data.services.client_31bf3856ad364e35_6.2.9200.16384_none_26e3adddcb0bda52\System.Data.Services.Client.dll
(p)	CSI Payload Corrupt	(Fixed)	msil_system.web.dynamicdata_31bf3856ad364e35_6.2.9200.16384_none_9d7304f75c3c5a09\System.Web.DynamicData.dll
(p)	CSI Payload Corrupt	(Fixed)	msil_microsoft.build.framework_b03f5f7f11d50a3a_3.5.9200.16384_none_17602a7514e82135\Microsoft.Build.Framework.dll
Therefore, it succeeded but still return a 0x800f081f message. Let's run it again to see what it'll tell us this time.

EndqYRa.png
DISM - Fixing Component Store Corruption
Follow the instructions below to run a DISM operation on your system.
  • On Windows 8, drag your cursor in the bottom-left corner, and right-click on the metro menu preview, then select Command Prompt (Admin);
  • On Windows 8.1, right click on the Windows logo in the bottom-left corner and select Command Prompt (Admin);
  • Enter the command below and press on Enter;
    Code: 
    DISM /Online /Cleanup-Image /RestoreHealth
  • Let the scan run until the end (100%). Depending on your system, it can take some time;
  • Copy the C:\Windows\Logs\DISM folder and C:\Windows\Logs\CBS\CBS.log file on your Desktop, then right-click on it, go to Send to... and select Compressed .zip archive;
  • Upload the file on Dropbox, Google Drive or OneDrive and post the download URL for it here;
Note: Please note that the CBS.log is volatile, which means that if you don't upload it after the DISM scan is completed, it won't contains the information from the scan anymore. So archive it and upload it as soon as you can.
 
It failed twice, I tried to run the restore health command alone at first without starting up both remote procedure call services and it failed due to remote procedure call failed. I then started both services for RPC and restarted the computer, again had to restart the second RPC service and ran DISM again but this time first I started the component store cleanup before running restore health command the latter failed again due to remote procedure call failed. During the restart Windows upadate kicked in and for what is surely the 30th time since September security update KB3069114 had failed. I have put the latter logs with two other info files in the zip file, the dropbox link is

https://www.dropbox.com/s/42pkso85hdjjkbm/CBS AND DISM LOGS.zip?dl=0
 
I don't see any traces of a DISM scan in your logs. Before we do another DISM scan, let's take care of that RPC service not working properly.

zImGw67.png
Windows Repair All-In-One
NOTE: Before following to step below, please disable your Antivirus software or any other real-time security software that you have enabled.
  • Boot in Safe Mode with Networking;
  • Download the portable version of Windows Repair All-In-One;
  • Move the file (archive) on your Desktop, and extract it there;
  • Go in the tweaking.com_windows_repair_aio folder, then Tweaking.com - Windows Repair folder, right-click on Repair_Windows.exe and select Run as Administrator;
  • From there, click on the Next button until you are presented with an Open Repairs button and click on it;
  • Let the Registry back up complete, and move on to the check-list window;
  • Click on the Unselect All button at the bottom, then check the following items:
    • Reset Service Permissions;
    • Repair Important Windows Services;
    • Set Windows Services To Default Startup;
  • Once done, click on the Start Repairs button and let the scan execute;
  • If you are being prompted with a Security Warning, allow it to go through;
  • Once the repair is complete, it'll ask you to restart your computer, please do it;
 
Please give me one extra day on this one, I have one computer in the shop, one new computer due here Wednesday so I don't lose all access and a way to communicate with you should something go wrong which it seems there is the potential for however minimal. In other words after I receive the new rig on Wednesday I will perform the operation promptly in hopes that we can clear up this problem. Thanks for your patience.
 
All good no worries. You can take all the time you need :)
 
My apologies for the waiting, alright then I ran the repair tool exactly as you requested and did nothing else though I suspect you may next want to retry the dism restorehealth action, that said I await your next instruction, I noticed the repair component store option, i take it you haven't determined it's broken. til next instruction then...
 
Let's see what DISM have to say, yes.

EndqYRa.png
DISM - Fixing Component Store Corruption
Follow the instructions below to run a DISM operation on your system.
  • On Windows 8, drag your cursor in the bottom-left corner, and right-click on the metro menu preview, then select Command Prompt (Admin);
  • On Windows 8.1, right click on the Windows logo in the bottom-left corner and select Command Prompt (Admin);
  • Enter the command below and press on Enter;
    Code: 
    DISM /Online /Cleanup-Image /RestoreHealth
  • Let the scan run until the end (100%). Depending on your system, it can take some time;
  • Copy the C:\Windows\Logs\DISM folder and C:\Windows\Logs\CBS\CBS.log file on your Desktop, then right-click on it, go to Send to... and select Compressed .zip archive;
  • Upload the file on Dropbox, Google Drive or OneDrive and post the download URL for it here;
Note: Please note that the CBS.log is volatile, which means that if you don't upload it after the DISM scan is completed, it won't contains the information from the scan anymore. So archive it and upload it as soon as you can.
 
Follow the instructions below please.

myjIXnC.png
SFCFix - Fix Time

WARNING! The following fix is specific to the user's system in this thread. No one else should follow the instructions below to apply that fix, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly.

Follow the instructions below to download and execute a SFCFix fix, and provide the log.
  • Download SFCFix and move the executable on your Desktop;
  • On your Desktop, right-click and select New, then Text Document. Give it the name SFCFixScript (it should be a .txt) extension;
  • Open the SFCFixScript.txt file you just created, and copy/paste the following in it;
    Code: 
    Trace::
amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_fdce12188b615b12
amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.20531_none_fe58af2da47e1433
  • Save any work you have open, and close every programs;
  • Drag the SFCFixScript.txt 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;
 
Done, below the content you requested from SFCFix.txt

SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-10-12 17:44:18.738
Microsoft Windows 8 - amd64
Using .txt script file at C:\Users\Terry\Desktop\SFCFixSript.txt [0]




Trace::
Failed to trace component amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_fdce12188b615b12 with return code -2.

Failed to trace component amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.20531_none_fe58af2da47e1433 with return code -2.
Trace:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2015-10-12 17:44:19.014
Script hash: 14yL3BN0NXjaYDrL4V9bhQ+zdA4W+G+8YwH419DY7y8=
----------------------EOF-----------------------
 
I take it you're away from the forum or busy with otherd clients, no worries. I tried something else after I found a directive to start the windows update service before running dism restorehealth so I attempted to start it as you can see below upon which it already had been so that was not it, then i started component cleanup then i ran the restorehealth command which failed said as you can see below which is somewhat different from what we have seen before if only slightly, the exception is that this time there is a direct reference to the fact that the component store is broken beyond repair, if that is the case I noted before that the windows repair tool you sent me has the option to fix the component store, is there any benefit to making that attempt and if so would you please provide instructions for doing so, I don't want to do without your input and guidance. I have uploaded the zip file with dism and cbs files as well as the cpadmin content which I will also post here. I am more worried than ever that this is what trashed my Asus computer still in the shop, I am extremely hesitant to try and do a recovery as this I fear is what rendered the recovery environment on the Asus dysfuntional, it seems to me that what's wrong here has some effect on the "RE"

dropbox link:

https://www.dropbox.com/s/hswqjuqvooek5sz/dism.zip?dl=0

start windows update diirective and cdadmin contents below

When it says the source files can't be downloaded that means it can't obtain the image from

Windows update.

Sometimes you can fix this by running the following command in an elevated command prompt.

Code:

net start wuauserv

If the code works it should say "The Windows update service is starting" then say " The Windows

update service started successfully" after that try running the DISM repair command again.

If none of this works then the system might be fixed by running a Refresh or Reset but that takes

you back to square one.

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\windows\system32>net start wuauserv
The requested service has already been started.

More help is available by typing NET HELPMSG 2182.

///////////////////////

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\windows\system32>net start wuauserv
The requested service has already been started.

More help is available by typing NET HELPMSG 2182.


C:\windows\system32>NET HELPMSG 2182

The requested service has already been started.



C:\windows\system32>Dism /Online /Cleanup-Image /StartComponentCleanup

Deployment Image Servicing and Management tool
Version: 6.2.9200.16384

Image Version: 6.2.9200.16384

[==========================100.0%==========================]
The operation completed successfully.

C:\windows\system32>Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 6.2.9200.16384

Image Version: 6.2.9200.16384

[==========================100.0%==========================]
The restore operation failed. Either the repair source was not found or the comp
onent store cannot be repaired.

Error: 0x800f081f

DISM failed. No operation was performed.
For more information, review the log file.

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

C:\windows\system32>
 
Sorry for the delay. From what I read in your last log, the two files that were originally corrupt at the beginning of the thread are now reported as corrupt again. I've been wondering though, did you ever attempt to upgrade to Windows 8.1?
 
Some six or seven months ago I did just that but it failed, I did so under duress what with all the complaints and problems I read about everywhere I turned on the net, then I learned that there were some preliminary files from Windows Update that need to be downloaded first some or four or five which I attempted but they failed. Anyway Windows Store had prompted the install another reason why I decided to let it try but it rolled back as you might well imagine, then months later I also read that it leaves behind a few files on your computer that can screw things up and no telling what it did not undo during the rollback so you suspect this may be the offender then ?
 
Well, I would like to see if the Windows 8.1 upgrade will succeed now that we fixed a few files on your system. Can you try to upgrade again via the Windows Store? If it doesn't work, we'll go back to fixing the two files reported as corrupt by DISM.
 
I was so horrified by my previous experience with 8.1 and the whole 8 thing in general and so pleased with the new Dell and Windows 10 that I upgraded the Toshiba to Windows 10 per your request, eventually I ran sfc /scannow which finished with no integrity violations, most applications survived the upgrade with few exceptions easily remedied. However one problem that began before the upgrade persist afterwards and not that familiar with the rules of the forum please advise if I need to start another thread that being before and after I am unable to copy folders of considerable size and small from my network drive to the recieving computer, in other words I cannot get folders or files or zip files from my network drive from one computer to the next. It is abysmally slow, so slow that 12mb says it needs 9-12 hours to transfer and then fails ultimately to transfer at all, a 5gb transfer says it needs more than a day and then fails in pretty short order to paste at all. What on earth is going on with this ? When I paste from the Dell to the network drive it is lightening fast but when I attempt to copy from the network drive to the Toshiba it fails everytime, I turned off ESET antivirus to no avail. I cannot find a way to disable large send or checksum offload in win 8 or 10 as this does not appear to be possible anymore, features no longer present, have you any idea what I might try to rectify this obnoxious thing. Please adivse and thanks for your help with the other thing behind us now.
 
Glad to see that upgrading to Windows 10 solved your Windows Update issues (that's how it works when you upgrade Windows version, since all the system files are replaced, the corruption dissapear). As for your other issue, I would post it in the Windows 10 section:

https://www.sysnative.com/forums/windows-10-a/

Since your issue here has been solved, I'll mark this thread as solved :)
 
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