The documentation says that the source for DISM must match the installation in version and language. That backslash after the H: meant it saidĭism /Image:H: /windir:H:\windows /Cleanup-Image /RestoreHealth givesģ. The only thing that gave a different error wasĭism /Image:H:\ /Cleanup-Image /RestoreHealth /Source:c:\windows I also tried just H:\ instead of H:\Windows (same error),ĭism /Image:H:\offline /Cleanup-Image /RestoreHealth (same) and triedĭism /Image:H:\windows /Cleanup-Image /RestoreHealth /Source:c:\windows Wouldn’t it need Write? Or is it referring to my own Windows folder there? * I wonder about that bit about Read permissions. – I do have Read permission for H:\Windows and can read files in the WinSXS folder. Make sure that the image path and the Windows directory for the image exist and you have Read permissions on the folder. How do you tell DISM where Windows is? I triedĭISM /Image:H:\windows /Cleanup-Image /RestoreHealth and it says: * I am aware that there are files that IT departments use to re-image their PCs and that they can modify those images, but that is NOT what I am doing: I am trying to repair a windows installation.Ģ. I base that assumption in part on the fact that if you use the /online switch, there is no way to specify where the affected Windows folder is, so it uses C:\
Is the ‘guest’ hard drive offline as far as DISM is concerned? In my head, the definition of ‘online’ is the Windows installation that is currently running (my own PC in this case) and ‘offline’ is everything else - but am I right? Sfc offline scan says ‘Windows Resource Protection could not perform the requested operation’. I have removed the hard drive and stuck it in my PC.
Where the OS partition had been assigned the letter C: and the 100MB FAT32 partition S:Īs a result of that, it now boots as far as a stopcode 0xc000021a, which could be due to corruption of WinLogon or Client Server-Run Time Subsystem (CSRSS) or of a driver, so I am trying to check the install for integrity. I have performed bootrec /fixmbr (which reports successful), bootrec /fixboot (which reports Access Denied) and bootrec /ScanOS which reports no Windows installations found, although the Windows partition and folder can be accessed just fine.
I have the harddrive from a computer that will not boot up but can get into the recovery environment (or I can boot off a Windows 10 installation memory stick). I am struggling to use DISM in any meaningful way, which is no doubt due to my lack of understanding - or misunderstandings.īackground of the current problem - though my questions are general:
Windows Repair 4.0 released: repair Windows software.Dism++ Windows optimizer with impressive functionality.RestoreHealth: Repair-WindowsImage -RestoreHealth.ScanHealth: Repair-WindowsImage -ScanHealth.CheckHealth: Repair-WindowsImage -CheckHealth.You may use DISM in Windows PowerShell as well.
Systems configured to use WSUS by default may be configured to use Windows Update instead for repair operations. You need to specify an alternate source, and may block use of Windows Update.
Tap on the Windows-key to bring up the start menu.You can specify a different source using the Group Policy. To prevent the use of Windows Update:Â /LimitAccess as a parameter.To use a different repair source: Dism /Online /Cleanup-Image /RestoreHealth /Source:d:\test\mount\windows.To repair an offline image: Dism /Image:C:\offline /Cleanup-Image /RestoreHealth.If the scan finds corruption, it attempts to correct the issue using Windows Update by default. Note that the operation may appear stuck at times but this is no cause for concern as scanning should commence after a moment automatically. The scan takes longer to complete if corruption is found during the scan of the image. The /RestoreHealth parameter runs a scan for corruption and attempts to repair any issues that it finds automatically. DISM /Online /Cleanup-Image /RestoreHealth
The scan takes longer to complete and the findings of the scan are returned in the command prompt window. The command scans for component store corruption but does not correct any issues. Previous operations may have flagged the image as corrupt. The scan should not take longer than a second or two. The command checks the image for the corruption flag and returns its findings to you but does not run repair operations.