[RKinner]

OK.  Search for 

 

services.msc and click on it.

 

This should open up the Services Windows.  Find Background Intelligent Transfer Service and see if it is started.  If it is not started try starting it.  If it is started try stopping it.  

[Advertisements]

I have stopped it. Want me to run the fix or try something else?

[Pepsi_Man]

I have stopped it. Want me to run the fix or try something else?

[RKinner]

No problem stopping it this time so that's an improvement.  Start it back up and let's see if Windows Update is working:

 

Go to http://www.eightforu...indows-8-a.html

 

scroll down to where it says

 

Option 1

To Check for and Install Windows Updates in Control Panel

 

and see if you can get Windows updates to check for updates.  Does it find any?

[Pepsi_Man]

It has 3 updates for drivers and 6 just for Windows 8.1. If I check it; I can install it. That is what I got.

[RKinner]

I would let them install then see if dsim wants to work.

[Pepsi_Man]

I got a different error this time.

 

The restore operation failed. Either the repair source was not found or the component store cannot be repaired.

 

Error: 0x800f081f

 

DISM failed. No operation was performed.

[RKinner]

Try this command from an admin Command Prompt:

dism.exe  /online  /cleanup-image  /scanhealth

Does it work?

[Pepsi_Man]

It said the component store is repairable. The operation was successful.

[RKinner]

Can you attach this log?

 

C:\WINDOWS\Logs\DISM\dism.log

[Pepsi_Man]

I see a text file and a "dism.log.bak" should I attach the text file?

Edited by Pepsi_Man, 27 January 2016 - 05:33 PM.

[RKinner]

I assume the text file is the log so go ahead and attach it.

[Pepsi_Man]

I am sorry but it says the file is too big to upload.

[RKinner]

OK.  Sent you a PM with my email address.  Going to be off line for the next few hours.  Wife wants me to watch TV with her.

[Pepsi_Man]

Ok, cool! Sent it. I am going to study for little while.

[RKinner]

From the dism log we have:

 

 

(p) CSI Payload Corrupt amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\utc.app.json

(p) CSI Payload Corrupt amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\telemetry.ASM-WindowsDefault.json

 

Summary:

Operation: Detect only 

Operation result: 0x0

Last Successful Step: CSI store detection completes.

Total Detected Corruption: 2

CBS Manifest Corruption: 0

CBS Metadata Corruption: 0

CSI Manifest Corruption: 0

CSI Metadata Corruption: 0

CSI Payload Corruption: 2

Total Repaired Corruption: 0

CBS Manifest Repaired: 0

CSI Manifest Repaired: 0

CSI Payload Repaired: 0

CSI Store Metadata refreshed: True

 

We don't care about telemetry so we can ignore dsim and go on.  For what it is worth tho dsim is supposed to be the great fix there are a lot of people complaining about dism not working:  9 page thread here:

 

http://answers.micro...7d-298be85e7bc3

 

Let's run process explorer again as before:

 

(Vista or Win7 - right click and Run As Administrator).  

 

View, Select Column, check Verified Signer, OK

Options, Verify Image Signatures

 

 

Click twice on the CPU column header  to sort things by CPU usage with the big hitters at the top.  

 

Wait a full minute then:

 

File, Save As, Save.  Open the file Procexp.txt on your desktop and copy and paste the text to a reply.

 

 

How is it running now anyway?  Still slow?