Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Win8 to 8.1 update questions


  • Please log in to reply
33 replies to this topic

#1 kelkay

kelkay

  • Members
  • 298 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:05:23 AM

Posted 11 December 2015 - 02:42 AM

I had Win8, then updated to Win8.1 via the store, because of a forced update.  I wasn't happy as it messed up the computer.  Well with my computer new, it was in warranty so the tech helped me.  It took quite a while to get the issues ironed out.  It ran great for a good long while.  Then I changed my Microsoft password, and even though online it showed fine, it never took it on the computer.  I did not know that, and restarted it a day or so later.  So I then was locked out of my administrator account because of it, and had to use my guest account.  So I finally got up the nerve to start from scratch.  The 8.1 had been backed up, and the flash drive files did not work.  I had to go all the way back to Win8.  I was going to be fine there, but now I hear they are going to stop giving updates after the first week or so of Jan 2016.  I am livid. 

 

Now I have 3 updates that won't go.  Can I still update to 8.1 like that with an iso?  Or am I going to have to correct that, before trying the 8.1 update?  After that it will be bugging me about going to Win10.  I don't want to go to the Win10 because of privacy issues.  I guess I will have to eventually.  I would rather go back to Win7 and be done with it.  But you can't even buy it anymore.  At least it ran with no major issues.  I don't want to do this major step until after the holidays are over...I need my computer, and don't have a smart phone.  This is the only computer I have.  Microsoft hasn't made me a happy customer in quite a while now.  They seem to know it, but they don't care what people think.  I don't want to jump through a bunch of hoops, I just want a normal computer to run the way it should.  You think by now they would a way to download any missing or corrupt files by now too.  I guess that is too much to ask.  If anyone can help me out on the question in red, I'd be very grateful.



BC AdBot (Login to Remove)

 


#2 cmptrgy

cmptrgy

  • Members
  • 1,690 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Massachusetts
  • Local time:06:23 AM

Posted 11 December 2015 - 04:29 AM

"Then I changed my Microsoft password, and even though online it showed fine, it never took it on the computer. "

--- Please verify the this issue while you are on Windows 8. 

 

"I had to go all the way back to Win8."

--- Make sure it's running well so you can move on to 8.1 (I'm recommending you move on to 8.1)

--- Create a system image backup using a 3rd party program onto an external drive: myself I use Macrium Reflect Free.

--- Create MR's bootable rescue media onto disc: I used a DVD-RW

 

Once you move onto 8.1, and you have it running well, create a "pristine" system image backup using your 3rd party program.

--- This way if you run into further issues you will be able to restore it without having to return to 8.

--- On the weekend before Patch Tuesday, I have a monthly maintenance plan and then I create system image backups: in my case I only keep only two system backups at a time

 

Now I have 3 updates that won't go.  Can I still update to 8.1 like that with an iso?  Or am I going to have to correct that, before trying the 8.1 update? 

--- The experts can help you much more than I can on that.

--- But please continue to create system image backups with a schedule that suits you 

 

"After that it will be bugging me about going to Win10.  I don't want to go to the Win10 because of privacy issues.  I guess I will have to eventually." You can bring up that discussion once you have 8.1 up & running 

 

"I would rather go back to Win7 and be done with it." Do you mean you'd like to do that on this computer?



#3 kelkay

kelkay
  • Topic Starter

  • Members
  • 298 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:05:23 AM

Posted 11 December 2015 - 10:32 AM

"I had to go all the way back to Win8."

--- Make sure it's running well so you can move on to 8.1 (I'm recommending you move on to 8.1)

--- Create a system image backup using a 3rd party program onto an external drive: myself I use Macrium Reflect Free.

--- Create MR's bootable rescue media onto disc: I used a DVD-RW

I have a backup image on 8 now.  (I had one for 8.1, but as I said, it failed, which stunk...it was from the computer manufacturer software) I use Macrium Reflect, and I have a couple of images to go back to on Win8 if necessary. 

 

Once you move onto 8.1, and you have it running well, create a "pristine" system image backup using your 3rd party program.

--- This way if you run into further issues you will be able to restore it without having to return to 8.

--- On the weekend before Patch Tuesday, I have a monthly maintenance plan and then I create system image backups: in my case I only keep only two system backups at a time

That is a good idea.  I usually don't do them as frequently, but will have to try to increase that to once a month or so too.

 

Now I have 3 updates that won't go.  Can I still update to 8.1 like that with an iso?  Or am I going to have to correct that, before trying the 8.1 update? 

--- The experts can help you much more than I can on that.

--- But please continue to create system image backups with a schedule that suits you 

okay :thumbup2:

 

"After that it will be bugging me about going to Win10.  I don't want to go to the Win10 because of privacy issues.  I guess I will have to eventually." You can bring up that discussion once you have 8.1 up & running 

 

"I would rather go back to Win7 and be done with it." Do you mean you'd like to do that on this computer?

 I wish I could, but I cannot.  I bought this new as a Win8 computer.  It took the manufacturer tech and I, 2-3 days to get the computer straight, after the forced Win8.1 update.  That is why I am in panic mode thinking of doing it this time, and by myself.  It totally messed up my computer, firewall, av, video driver install kept failing, you name it, it was a big fat steaming mess.  That is when Microsoft started on the decline, as far as my loyalty to them was concerned.  Now I hear they are still doing some forced updates, which is crazy.  If it went smoothly great, but sometimes it is just a nightmare, like what happened to me. 



#4 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,714 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:03:23 AM

Posted 11 December 2015 - 10:57 AM

Microsoft will end update for Window 8 in January 2016, not for Windows 8.1.  


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#5 kelkay

kelkay
  • Topic Starter

  • Members
  • 298 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:05:23 AM

Posted 11 December 2015 - 11:11 AM

Yes, thank you.  I couldn't remember if it was the 6th or the 8th.  I knew they would still do updates for 8.1, but not 8.  I wasn't happy about that, when I found out they were going to stop updating Win8.  This computer is almost 3 years old.  I did good to buy this one.  I liked 8, and after 8.1 got straightened out, I liked it too.  But the problems that I did have were major with a capital M. 



#6 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,714 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:03:23 AM

Posted 11 December 2015 - 11:27 AM

Have you tried to manually download the updates?

 

What are the updates that won't load?


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#7 kelkay

kelkay
  • Topic Starter

  • Members
  • 298 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:05:23 AM

Posted 11 December 2015 - 01:43 PM

I did try to manually do updates in the past, with no luck.  I think it is because I had corrupted files, that could not be fixed.  Last night I decided to try again, to do

DISM.exe /Online /Cleanup-image /Scanhealth and this time it said the component store is repairable, which was a sigh of relief.  Before it said it was not.  Then I tried to run

DISM.exe /Online /Cleanup-image /Restorehealth  I started that one late last night.  It is still running now, several hours later.  I think it may be stuck, but I am afraid to close it.  It shows 40%, and the cursor is still blinking.  I am hoping that once I hopefully get it repaired, that it will allow me to get the updates to update successfully.  The first one I had trouble with was KB2920189.  That was the only one for a while.  Then about two updates times ago, 3 more popped up, that would not update successfully.  They were KB3033983, then later KB3100773, and last was 3097877. 

 

Last night I had about 10 updates to show up.  Only these show as not being updated, and of  course as usual, I repeatedly tried.  KB3104002, KB2920189, KB3109094.  I did try to manually update KB2920189 in the past.  The newest two to not install in this paragraph, I have not tried to manually install.  I thought I would give the DISM restore health deal a chance first. 

 

Update: The DISM restore health program is still running.  It has been over 12 hours now.  Something tells me my chances of it working successfully are about 1% or so now, if that.  Make that over 15 hours now.  This doesn't sound promising at all.


Edited by kelkay, 11 December 2015 - 06:12 PM.


#8 kelkay

kelkay
  • Topic Starter

  • Members
  • 298 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:05:23 AM

Posted 11 December 2015 - 11:28 PM

Well it is over 20 hours, I think it is messed up.  If I close it, will it cause a problem?  Or should I let it go longer, hoping it will clear things up?

 

I was able to look up the last of the logs from DISM.  It looks like it may have stopped.  Since I haven't heard anything here, I guess I will stay connected, and see what happens.  I have no message on the command prompt that it finished, or failed. 

================================================================

 

2015-12-12 01:12:08, Info                  DISM   DISM Provider Store: PID=4940 TID=3832 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-12-12 01:12:08, Info                  DISM   DISM Provider Store: PID=4940 TID=3832 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-12-12 01:12:08, Info                  DISM   DISM Provider Store: PID=4940 TID=3832 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-12-12 01:12:08, Info                  DISM   DISM Provider Store: PID=4940 TID=3832 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-12-12 01:12:08, Info                  DISM   DISM Provider Store: PID=4940 TID=3832 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2015-12-12 01:12:08, Info                  DISM   DISM Provider Store: PID=4940 TID=3832 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2015-12-12 01:12:08, Info                  DISM   DISM Provider Store: PID=4940 TID=3832 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2015-12-12 01:12:08, Info                  DISM   DISM Provider Store: PID=4940 TID=3832 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2015-12-12 01:12:08, Info                  DISM   DISM Provider Store: PID=3140 TID=4444 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-12-12 01:12:08, Info                  DISM   DISM Provider Store: PID=3140 TID=4444 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2015-12-12 01:12:08, Info                  DISM   DISM Provider Store: PID=3140 TID=4444 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2015-12-12 01:12:08, Info                  DISM   DISM Provider Store: PID=3140 TID=4444 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
2015-12-12 01:12:08, Info                  DISM   DISM Provider Store: PID=3140 TID=4444 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
2015-12-12 01:12:08, Info                  DISM   DISM Provider Store: PID=3140 TID=4444 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2015-12-12 01:12:08, Info                  DISM   DISM Provider Store: PID=3140 TID=4444 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2015-12-12 01:12:09, Info                  DISM   API: PID=3140 TID=4444 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2015-12-12 01:12:09, Info                  DISM   API: PID=3140 TID=2388 Leave DismCloseSessionInternal - DismCloseSessionInternal
2015-12-12 01:12:09, Info                  DISM   API: PID=3140 TID=2388 Enter DismShutdownInternal - DismShutdownInternal
2015-12-12 01:12:09, Info                  DISM   API: PID=3140 TID=2388 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
2015-12-12 01:12:09, Info                  DISM   API: PID=3140 TID=2388 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
2015-12-12 01:12:09, Info                  DISM   API: PID=3140 TID=4428 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2015-12-12 01:12:09, Info                  DISM   API: PID=3140 TID=2388 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2015-12-12 01:12:09, Info                  DISM   API: PID=3140 TID=4428 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2015-12-12 01:12:09, Info                  DISM   API: PID=3140 TID=4428 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
2015-12-12 01:12:09, Info                  DISM   API: PID=3140 TID=4428 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2015-12-12 01:12:09, Info                  DISM   PID=3140 TID=4428 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
2015-12-12 01:12:09, Info                  DISM   PID=3140 TID=4428 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
2015-12-12 01:12:09, Info                  DISM   PID=3140 TID=4428 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
2015-12-12 01:12:10, Info                  DISM   API: PID=3140 TID=4428 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2015-12-12 01:12:10, Info                  DISM   API: PID=3140 TID=2388 Deleted g_internalDismSession - DismShutdownInternal
2015-12-12 01:12:10, Info                  DISM   API: PID=3140 TID=2388 Shutdown SessionTable - DismShutdownInternal
2015-12-12 01:12:10, Info                  DISM   API: PID=3140 TID=2388 Leave DismShutdownInternal - DismShutdownInternal
2015-12-12 01:12:10, Info                  DISM   API: PID=3140 TID=2388 DismApi.dll:                                          - DismShutdownInternal
2015-12-12 01:12:10, Info                  DISM   API: PID=3140 TID=2388 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
2015-12-12 01:12:10, Info                  DISM   API: PID=3140 TID=2388 DismApi.dll:                                          - DismShutdownInternal
 


Edited by kelkay, 12 December 2015 - 03:30 AM.


#9 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,714 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:03:23 AM

Posted 12 December 2015 - 10:00 AM

Is the log you posted from the latest DISM?


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#10 kelkay

kelkay
  • Topic Starter

  • Members
  • 298 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:05:23 AM

Posted 12 December 2015 - 11:53 AM

Yes.  I closed it after it didn't do anything for an hour or more after that last log.



#11 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,714 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:03:23 AM

Posted 12 December 2015 - 12:01 PM

Please run the sfc /scannow again and post the new log.  The logs are date and time stamped.


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#12 kelkay

kelkay
  • Topic Starter

  • Members
  • 298 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:05:23 AM

Posted 12 December 2015 - 12:43 PM

  It took a while before I could figure out how to get it. (access denied to read) It said it found corrupt files but it was unable to fix some of them.

 

2015-12-12 01:12:08, Info DISM DISM Provider Store: PID=4940 TID=3832 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

2015-12-12 01:12:08, Info DISM DISM Provider Store: PID=4940 TID=3832 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

2015-12-12 01:12:08, Info DISM DISM Provider Store: PID=4940 TID=3832 Found the PE Provider. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

2015-12-12 01:12:08, Info DISM DISM Provider Store: PID=4940 TID=3832 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider

2015-12-12 01:12:08, Info DISM DISM Provider Store: PID=4940 TID=3832 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider

2015-12-12 01:12:08, Info DISM DISM Provider Store: PID=4940 TID=3832 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider

2015-12-12 01:12:08, Info DISM DISM Provider Store: PID=4940 TID=3832 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider

2015-12-12 01:12:08, Info DISM DISM Provider Store: PID=4940 TID=3832 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

2015-12-12 01:12:08, Info DISM DISM Provider Store: PID=3140 TID=4444 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

2015-12-12 01:12:08, Info DISM DISM Provider Store: PID=3140 TID=4444 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider

2015-12-12 01:12:08, Info DISM DISM Provider Store: PID=3140 TID=4444 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider

2015-12-12 01:12:08, Info DISM DISM Provider Store: PID=3140 TID=4444 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider

2015-12-12 01:12:08, Info DISM DISM Provider Store: PID=3140 TID=4444 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider

2015-12-12 01:12:08, Info DISM DISM Provider Store: PID=3140 TID=4444 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider

2015-12-12 01:12:08, Info DISM DISM Provider Store: PID=3140 TID=4444 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

2015-12-12 01:12:09, Info DISM API: PID=3140 TID=4444 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub

2015-12-12 01:12:09, Info DISM API: PID=3140 TID=2388 Leave DismCloseSessionInternal - DismCloseSessionInternal

2015-12-12 01:12:09, Info DISM API: PID=3140 TID=2388 Enter DismShutdownInternal - DismShutdownInternal

2015-12-12 01:12:09, Info DISM API: PID=3140 TID=2388 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession

2015-12-12 01:12:09, Info DISM API: PID=3140 TID=2388 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession

2015-12-12 01:12:09, Info DISM API: PID=3140 TID=4428 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop

2015-12-12 01:12:09, Info DISM API: PID=3140 TID=2388 Successfully enqueued command object - CCommandThread::EnqueueCommandObject

2015-12-12 01:12:09, Info DISM API: PID=3140 TID=4428 Successfully dequeued command object - CCommandThread::DequeueCommandObject

2015-12-12 01:12:09, Info DISM API: PID=3140 TID=4428 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop

2015-12-12 01:12:09, Info DISM API: PID=3140 TID=4428 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop

2015-12-12 01:12:09, Info DISM PID=3140 TID=4428 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct

2015-12-12 01:12:09, Info DISM PID=3140 TID=4428 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir

2015-12-12 01:12:09, Info DISM PID=3140 TID=4428 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct

2015-12-12 01:12:10, Info DISM API: PID=3140 TID=4428 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub

2015-12-12 01:12:10, Info DISM API: PID=3140 TID=2388 Deleted g_internalDismSession - DismShutdownInternal

2015-12-12 01:12:10, Info DISM API: PID=3140 TID=2388 Shutdown SessionTable - DismShutdownInternal

2015-12-12 01:12:10, Info DISM API: PID=3140 TID=2388 Leave DismShutdownInternal - DismShutdownInternal

2015-12-12 01:12:10, Info DISM API: PID=3140 TID=2388 DismApi.dll: - DismShutdownInternal

2015-12-12 01:12:10, Info DISM API: PID=3140 TID=2388 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal

2015-12-12 01:12:10, Info DISM API: PID=3140 TID=2388 DismApi.dll: - DismShutdownInternal


Edited by kelkay, 12 December 2015 - 12:46 PM.


#13 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,714 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:03:23 AM

Posted 12 December 2015 - 12:50 PM

That is the DISM log.  You need to run sfc /scannow from the command prompt.

 

Please run sfc /scannow
 
The sfc /scannow command scans all protected system files and replaces corrupted and incorrect versions with correct Microsoft versions.
 
To run sfc /scannow in Windows 8 you will need to open the Elevated Command Prompt.  The easiest way to do this is to press the Windows key windowskey_zps092d5c75.png and the X key at the same time.   A menu will open with the option Command Prompt (Admin), click/tap on this.
 
You will see a window similar to the one below.
 
command%20prompt%20w8_zpsxjmewau9.png
 
When the Elevated Command Prompt opens copy and paste in sfc /scannow, then press Enter.
 
This will take a while,  have patience and allow it finish.  Stopping this scan could damage files.  
 
When the scan is finished please post the log of this scan.
 
To find sfc /scannow log, reopen the Elevated Command Prompt using the Windows key windowskey_zps092d5c75.png and the X key method outlined in the instructions above. 
 
When the Elevated Command Prompt opens copy and paste the following in the Command Prompt, then press Enter.  
 
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >"%userprofile%\Desktop\sfcdetails.txt"
 
This will place a new icon on the desktop titled sfcdetails.  Click/tap on this to open the log, copy and paste it in your topic.

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#14 kelkay

kelkay
  • Topic Starter

  • Members
  • 298 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:05:23 AM

Posted 12 December 2015 - 12:59 PM

I did do that sfc /scannow.  I put in your command, and it did save to my desktop.  Thank you.  It is attached.

Attached Files



#15 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,714 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:03:23 AM

Posted 12 December 2015 - 01:30 PM

I will not download anything to my computer unless I know exactly what it contains.

 

You need to post the log in your topic.  If it is too large to post break it down into sections and post those.


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users