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

Windows 10 another SFC /Scannow DISM /RestoreHealth fix needed


  • Please log in to reply
6 replies to this topic

#1 Paulie Urethane

Paulie Urethane

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:11:29 PM

Posted 09 August 2015 - 01:31 AM

Hi, After the third try, I was trying to run down a forced Win10 update error while updating the drivers for my HP printer.

HP driver update for HP LaserJet 400 M401 PCL 6 - Error 0x80240017
 

Found via Google try; /SFC /scannow and the DISM /RestoreHealth which gave me errors very similar to this post http://www.bleepingcomputer.com/forums/t/585031/dismexe-restorehealth-produces-error-0x800f081f/

 

I followed each of the steps taken by Big Benny and I'm coming up with the same errors. Could someone much more talented (ie: knows what the heck he/she's doing) than I help here?

 

Attached are my logs;

 

Thank you in advance,

Paulie

Attached Files

  • Attached File  CBS.log   2.9MB   3 downloads
  • Attached File  dism.log   38.22KB   3 downloads


BC AdBot (Login to Remove)

 


#2 technonymous

technonymous

  • Members
  • 2,516 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:29 PM

Posted 09 August 2015 - 02:36 AM

I think the proper steps would be...

 

dism /online /cleanup-image /scanhealth

 

dism /online /cleanup-image /startcomponentcleanup

 

dism /online /clean-image /restorehealth



#3 Paulie Urethane

Paulie Urethane
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:11:29 PM

Posted 09 August 2015 - 04:19 AM

I think the proper steps would be...

 

dism /online /cleanup-image /scanhealth

 

dism /online /cleanup-image /startcomponentcleanup

 

dism /online /clean-image /restorehealth

 

Sorry, like I said in my OP; "I followed each of the steps taken by Big Benny". And I mean step-by-step. Did I miss something?



#4 Paulie Urethane

Paulie Urethane
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:11:29 PM

Posted 10 August 2015 - 03:24 AM

Okay, now I think I understand what technonymous was getting at; I ran the steps out of sequence? So in that case, I've reaccomplished them using his example.

 

Step 1:
C:\>sfc /SCANNOW

Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.


Step 2:
C:\>dism /online /cleanup-image /scanhealth

The component store is repairable.
The operation completed successfully.


Step 3:
C:\>dism /online /cleanup-image /startcomponentcleanup

The operation completed successfully.


Step 4:
C:\>dism /online /cleanup-image /Restorehealth

Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are
required to restore the feature. For more information on specifying a
source location, see http://go.microsoft.com/fwlink/?LinkId=243077

I went back into the Group Policy area and confirmed the system is supposed to contact the Windows Update Server. I had the firewall/anti-virus turned off and everything. Attached are the reaccomplished logs.
 

 

Attached Files



#5 technonymous

technonymous

  • Members
  • 2,516 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:29 PM

Posted 10 August 2015 - 11:03 PM

I read something about that error and a lot of .net frame work popped up. Download the .net 3.5 framework.

 

https://www.microsoft.com/en-us/download/details.aspx?id=21

 

Go to start type cmd and run in admin mode. Search if you have thse KB's and uninstall them. Then reinstall the .net 3.5 framework after a reboot of the system.

 

wmic qfe | find "KB2966826"
wmic qfe | find "KB2966827"
wmic qfe | find "KB2966828"

 

wusa /uninstall /kb:2966826 /quiet /norestart
wusa /uninstall /kb:2966827 /quiet /norestart
wusa /uninstall /kb:2966828 /quiet /norestart



#6 Paulie Urethane

Paulie Urethane
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:11:29 PM

Posted 11 August 2015 - 12:12 AM

Thank you technonymous for those tips but no joy for the wmic and wusa commands.

 

Seems like I don't have 3.5 .NET framework installed, it's not showing up in Windows Update utility or at least those particular KBs aren't on this system.

 

Are you suggesting that I should go ahead and install 3.5 .net frame work?



#7 technonymous

technonymous

  • Members
  • 2,516 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:29 PM

Posted 11 August 2015 - 05:59 PM

The 3.5 framework comes with Windows, but there is 4.5 out now and seems your .net framework is corrupt. You can check to see what you have installed. Go to control panel, uninstall programs, view installed updates. They are listed in there.

 

The best thing to do is download 3.5, 4.0, 4.5 and uninstall the old ones in safe boot and reinstall the ones you downloaded.

 

https://www.microsoft.com/en-us/download/details.aspx?id=21

http://www.microsoft.com/en-us/download/details.aspx?id=17851

http://www.microsoft.com/en-us/download/details.aspx?id=30653

 

To go into safe boot you go to start type msconfig. Select boot tab. Put a check in the safe boot and hit apply. Restart the system and go to control panel, uninstall programs, view installed and uninstall all the frameworks. Once done reinstall just 3.5 that you downloaded. Again, type msconfig under start and uncheck safe boot option and restart the system. If all goes well install 4.0 and then 4.5. Hopefully that will blow away the problem you're experiencing.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users