Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Windows 8.1 Laptop acting very slow.


  • Please log in to reply

#31
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,012 posts
  • MVP

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.  


  • 0

Advertisements


#32
Pepsi_Man

Pepsi_Man

    Member

  • Topic Starter
  • Member
  • PipPip
  • 32 posts

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


  • 0

#33
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,012 posts
  • MVP

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?


  • 0

#34
Pepsi_Man

Pepsi_Man

    Member

  • Topic Starter
  • Member
  • PipPip
  • 32 posts

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.


  • 0

#35
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,012 posts
  • MVP

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


  • 0

#36
Pepsi_Man

Pepsi_Man

    Member

  • Topic Starter
  • Member
  • PipPip
  • 32 posts

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.


  • 0

#37
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,012 posts
  • MVP

Try this command from an admin Command Prompt:

dism.exe  /online  /cleanup-image  /scanhealth

Does it work?


  • 0

#38
Pepsi_Man

Pepsi_Man

    Member

  • Topic Starter
  • Member
  • PipPip
  • 32 posts

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


  • 0

#39
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,012 posts
  • MVP

Can you attach this log?

 

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


  • 0

#40
Pepsi_Man

Pepsi_Man

    Member

  • Topic Starter
  • Member
  • PipPip
  • 32 posts

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.

  • 0

Advertisements


#41
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,012 posts
  • MVP

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


  • 0

#42
Pepsi_Man

Pepsi_Man

    Member

  • Topic Starter
  • Member
  • PipPip
  • 32 posts

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


  • 0

#43
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,012 posts
  • MVP

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.


  • 0

#44
Pepsi_Man

Pepsi_Man

    Member

  • Topic Starter
  • Member
  • PipPip
  • 32 posts

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


  • 0

#45
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,012 posts
  • MVP

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:
 
 
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?

  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP