I have an ISO downloaded from Microsoft for Windows 8.1 that contains an "install.esd" file only, no "install.wim". The ISO file, Windows.ISO, can be mounted and examined (though there is a minor mount error); I also burned a DVD with the Media Creation Tool that appears identical to the ISO file as far as contents are concerned (makes sense...). I want to use that ISO/DVD to repair the Windows 8.1 Pro installation without destroying existing accounts/personal data/etc. I have a proper Product key, etc. Would a command like this work?: Code: Dism /Online /Cleanup-Image /RestoreHealth /Source:X:\sources\install.esd /LimitAccess Or, if not, how about a conversion using some tool to get the ESD file into a WIM file, then: Code: Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:C:\temp\install.wim:1 /LimitAccess I've been banging my head against this broken installation too long - causes Windows Update to repeatedly fail on the hidden installs of things like Microsoft.Reader, for example - so am anxious to get it right again. Any feedback thoroughly appreciated. [turns out the automated update to Windows 10 is failing as well for perhaps this and other reasons - clicking on the little GWX icon in the systray says "yer in the Q!" but then clicking on the three bar symbol in the upper left of that "Yer..." dialog says it's all Nvidia's fault...but that's another problem for another time - first to repair Windows 8.1...]
Use the following to give you a simplified view (of a few thousand less lines) without the need to scroll an exhausting log file. It puts the errors in a neat order for you on a few lines (depending on the amount of errors of course) to a txt file on your Desktop : Spoiler findstr /i /c:"[SR]" "%windir%\Logs\CBS\CBS.log" | findstr /i /v /c:"verify" > "%userprofile%\Desktop\sfc.txt"
Thanks for the fast response - I'll for sure give that a try. BTW, the following shows the ESD file being used as if it were a WIM file: Code: C:\>dism /Get-Wiminfo /WimFile:G:\sources\install.esd Deployment Image Servicing and Management tool Version: 6.3.9600.17031 Details for image : G:\sources\install.esd Index : 1 Name : Windows 8.1 Pro Description : Windows 8.1 Pro Size : 13,185,962,705 bytes The operation completed successfully. C:\>dism /Get-Wiminfo /WimFile:G:\sources\install.esd /index:1 Deployment Image Servicing and Management tool Version: 6.3.9600.17031 Details for image : G:\sources\install.esd Index : 1 Name : Windows 8.1 Pro Description : Windows 8.1 Pro Size : 13,185,962,705 bytes WIM Bootable : No Architecture : x64 Hal : acpiapic Version : 6.3.9600 ServicePack Build : 17415 ServicePack Level : 0 Edition : Professional Installation : Client ProductType : WinNT ProductSuite : Terminal Server System Root : WINDOWS Directories : 18805 Files : 104794 Created : 11/21/2014 - 1:07:26 PM Modified : 8/3/2015 - 1:04:28 PM Languages : en-US (Default) The operation completed successfully. C:\>
I have same issues last week, I tried to fix it like 25 times, I gave it up, I put clean install Win 10 and it's great no sfc errors. anymore. I used media creation tool USB loads on PC.
Would guess SFC showed errors . Is the path correctly pointing to ,the ESD file? Note, there are cases where the repair will fail, better check the CBS log for the actual error. Try the nice idea by eyecheck: Code: findstr /i /c:"[SR]" "%windir%\Logs\CBS\CBS.log" | findstr /i /v /c:"verify" > "%userprofile%\Desktop\sfc.txt" it will create sfc.txt on desktop. Post content here in [code][/code] tags.
Doesn't sound as a good explanation to me. Most of the files you see inside windows and System32 are just links to the winSXS real files. So there isn't too much to compare
To me it looks like a more general hickup in design. Murphy already discovered that there doesn't seem to exist any proper file check for the Setup and it might pass some errors. Similiar happend with early Preview builds where sfc was confused by new file compression and failed.
My idea is that somewhere the file hashes must be present, at least for the unsigned files, then, if something is corrupt the sfc thng should grab a sane copy of the file from the recovery or ask for the installation media, like XP did. Looks like the thing doesn't work that way, so yes, something wrong is present on the implementation.
OK, just though i might check the new CBS Parse implented in JATD after running sfc /scannow on my fresh Win 10 Pro Install in VM. ............: Code: 2015-08-04 20:34:15, Info CSI 000042b5 [SR] Repairing corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:30{15}]"msprivs.dll.mui" from store 2015-08-04 20:34:24, Info CSI 000043d3 [SR] Repairing corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:26{13}]"mlang.dll.mui" from store 2015-08-04 20:35:16, Info CSI 00004a2a [SR] Repairing corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:68{34}]"Windows.Media.Speech.UXRes.dll.mui" from store 2015-08-04 20:35:16, Info CSI 00004a57 [SR] Repairing 3 components 2015-08-04 20:35:16, Info CSI 00004a59 [SR] Repairing corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:68{34}]"Windows.Media.Speech.UXRes.dll.mui" from store 2015-08-04 20:35:16, Info CSI 00004a5b [SR] Repairing corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:30{15}]"msprivs.dll.mui" from store 2015-08-04 20:35:16, Info CSI 00004a5e [SR] Repairing corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:26{13}]"mlang.dll.mui" from store 2015-08-04 20:35:17, Info CSI 00004a61 [SR] Repair complete 2015-08-04 20:35:17, Info CSI 00004a62 [SR] Committing transaction
Question to you or others with the knowledge - are the files on a Windows install disk usable to replace corrupt files found by SFC using the manual method directly, or do they have to be massaged somewhat before they can be used manually to do that? I have numerous hits about corrupt files that SFC and DISM are not succeeding at replacing - have run simple unsourced DISM and have run DISM pointing at an install.esd (install.wim) file to no avail - thus am more than willing to start doing things manually. EDIT: just read the 2nd link you provided so perhaps this question is now a "Nevermind!"...
Hmmm...this actually breaks horribly. Since I'm working on Windows 8.1 there must be a signficant difference between 8.1's DISM and 10's DISM (and, based off web reading, just about every other version's DISM and 8.1's DISM...). Running a test shows this: Code: C:\Users\myid\Documents>dism /source Deployment Image Servicing and Management tool Version: 6.3.9600.17031 Error: 87 The source option is unknown. For more information, refer to the help by running DISM.exe /?. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log C:\Users\myid\Documents> Using the line in the top quoted part results in the logfiles saying the source file cannot be found - e.g., from the CBS.log: Code: 2015-08-05 19:23:40, Info CBS Exec: Addsource called, Session: 30461909_3274182614, Client: DISM Package Manager Provider, from GPO: No, Path: C:\Users\myid\Documents\esd:G:\sources\install.esd:1 2015-08-05 19:23:40, Warning CBS The alternate source path directory could not be accessed [HRESULT = 0x8007007b - ERROR_INVALID_NAME] 2015-08-05 19:23:40, Info CBS Failed to add new file source [HRESULT = 0x8007007b - ERROR_INVALID_NAME] Note that totally broken path that got generated by the argument to DISM of "/Source:esd:G:\sources\install.esd:1"... dism /? gives the full story on proper arguments. So, anyway, I'll be reading the numerous options of the DISM command that =I've= got and appropriately modify the arguments to get the proper path, then see what happens. Further reading on the web, however, suggests the "corruption" I'm seeing with "sfc /scannow" is actually a false error caused by a Microsoft bug but that's meat for a different thread somewhere.
Yes, the correct line apparently has the ":esd:" removed as well as the trailing ":1", that is: Code: ... /Source:G:/sources/install.esd ..." instead of: Code: ... /Source:esd:G:/sources/install.esd:1 ..." per the online documentation for DISM for Windows 8/8.1: technet.microsoft.com/en-us/library/hh824915.aspx Unfortunately, I cannot try this tonight (9-ish PM here in Virginny) but will first thing tomorrow.
Use the line i gave (it's tested several times now) it works as it is. It's not the syntax that is wrong here it's how you use the Command Prompt!!! Check whether there's an install.wim or install.esd present. RUN the COMMAND PROMPT AS ADMIN!!!!!! Code: WIM: Dism /Online /Cleanup-Image /RestoreHealth /source:wim:X:\sources\install.wim:1 /limitaccess ESD: Dism /Online /Cleanup-Image /RestoreHealth /source:esd:X:\sources\install.esd:1 /limitaccess