Windows 10: SFC and DISM will not run on build 14279

Just installed the Insider upgrade to 14279.rs1-release_160229-1700 today. Tried to run SFC/ scannow from CMD prompt (admin) and it won't run. Also tried to run DISM restore health and it would not run. Used CMD prompt (admin) and KYHI Image utilities both failed. maybe it's the water here in TEXAS.

:)

 

should I run SFC and DISM or not?

I got into administrator command prompt.

I ran chkdsk c: /f no problems.

I ran sfc /scannow

It ran through verification but then said windows resource protection could not perform the requested operation

I have windows 10 version 1607. It did some updates today.

So what does that mean?

I also ran:

Dism /online /cleanup-image /restorehealth

I got / online id not available in the pe version

Cleanup-image is unknown

Restore health is unknown.

This system was originally 8.0 then updated to 8.1 then updated to 10. If I have to run a reset will it be able to reset with Windows 10?

There were no specific changes. It was just getting worse over a period of time while I was waiting for the creators update to become available.

 

should I run SFC and DISM or not?

If your system is "messed up" and you don't know where to begin to fix it, the smart thing to do is either (1) show the computer to a professional; or (2) backup your personal files and do a clean install.

The thing not to do is to keep trying whatever you can think of in the hope of hitting on something that will work. That's a waste of time, in my view, and could make things worse.

For the future, the best thing to do is to backup your computer every day, so when it does get messed up - something at which I am expert - all you have to do is restore a backup made before the trouble started.

 

Hi, jm. Just letting you know you're not alone with this. I get this:



Referring to Brink's tutorial on SFC (https://www.tenforums.com/tutorials/2...dows-10-a.html), I followed the tip on Windows Modules Installer service and saw it already in Manual, not running before SFC scannow attempt, and then running after the attempt.

Post back if you find anything out on this or I will do the same.

 

My Windows Modules is set to manual. I even turned it OFF and then ran SFC /scannow from Cmd. prompt (admin) it failed with the same message you received. I am also having a problem with the DISM restoreHealth command.

 

OK. I haven't tried DISM yet but wouldn't be surprised if I have same result as you. Looking at your system specs, I don't see much in common between you and I except 16GB RAM, the fact that we use SSDs, use Windows Defender, and that we are multi-booting (I have dual boot of Win10-RTM and Win10IP).

 

Let's see if others have the same issue with this build.

 

SFC not working for me either:

 

I tried several variations of DISM including using /source options several ways, including copying install.wim (made from ESDtoISO script from Kari) directly into c:\ and referencing it there and NO GO for any DISM /RestoreHealth for me. I did however, get DISM /Online /Cleanup-Image /Scanhealth to work and it reported "The component store is repairable." - indicating something is up. Unless something is wrong with the install.wim decrypted from the 14279 install.esd, don't understand why DISM with /source wouldn't work.

If I don't get time tonight, I will try in the morning, with the install.esd - need to retrieve it from a Macrium image first.

 

I tried using a mounted DVD (made using the esd to iso tool), which didn't work and then copied the install.wim to the desktop and mounted it there. That didn't work either, "source files could not be found" both times. However the /scanhealth appeared to work both times.

 

Same result as me then. I just now got done retrieving the unconverted install.esd from the image I made prior to update and restart - getting same "source files could not be found" message whether I place install.esd in c:\ or on the desktop. Didn't necessarily expect install.esd to work but neither location nor mounting of the wim based iso and pointing at install.wim in \sources works.

Oh well... no problem for me per se but has me curious - will report to feedback and check next build.

 

Parallel thread regarding SFC on IP build 14279: 14279-Win Resource Protection Couldn't Start Repair Service

A thread over at MS Insider forum on this also - http://answers.microsoft.com/en-us/i...d453123?auth=1

Recent poster in that thread reports MS saying they'll update on issue.

 

I have posted elsewhere but I can concur I have same issue on build 14279, seems poor microsoft didn't pick up on this

 

I found the reason why it cant start (Well 4 me anyways) *Wink


For some reason the wrpint.dll was missing from my "%SystemRoot%\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14279.1000_none_25a158fc7f85c69d"


I found a copy in
"%SystemRoot%\winsxs\amd64_microsoft-windows-servicingstack-onecore_31bf3856ad364e35_10.0.14279.1000_none_5a92ee0dd788e433"




Now it's more than likely that the names are different but I am pretty sure the names would be pretty close depending on machine architecture that is, for X86 going off a hunch here but I would look in.




"%SystemRoot%\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14279.1000_none_c982bd78c7285567"


To see if its there, if not take a wander over to..


"%SystemRoot%\winsxs\x86_microsoft-windows-servicingstack-onecore_31bf3856ad364e35_10.0.14279.1000_none_fe74528a1f2b72fd"



Copy the wrpint.dll And wack it in the appropriate folder. Also you will need to grant ownership from System to Administrators to copy the file in the Tiworker directory.


If unsure of the correct locations just delete or move CBS.LOG from Windows\Logs\CBS run SFC /SCANNOW and open the log file and it will tell you the right location or the location its trying to find the file in.

I will also state the the X64 Version of the file is about 65.5Kb & the X86 Version is about 55Kb


Hope this helps Good Day *Smile

 

Thanks, Darknetz, and welcome to TenForums.*Smile. That seems to have worked OK for me. Not sure if this was just a miss/sloppiness in this build or something more significant on MS's side. Have to run to work, so couldn't wade through enough of the driver updater chaff hits in Google to find out what wrpint.dll is for other than something to do with integrity checking.