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.
Hi, jm. Just letting you know you're not alone with this. I get this:
Referring to Brink's tutorial on SFC (SFC Command - Run in Windows 10), 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.Hi, jm. Just letting you know you're not alone with this. I get this:
Referring to Brink's tutorial on SFC (SFC Command - Run in Windows 10), 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.
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).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.
Let's see if others have the same issue with this build.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).
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.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.
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 -
Recent poster in that thread reports MS saying they'll update on issue.
