Results 1 to 10 of 19

Threaded View

  1. #6
    Join Date
    Nov 2015
    Location
    Christchurch, Dorset, United Kingdom
    Posts
    119

    Default Windows image faulty...

    Quote Originally Posted by Dick Berg View Post

    So changing the version or date properties clearly changed the hash, which sfc picked up. In the CBS.log file (attached if you're interested) you can search on "do not match" and see two sets of eight non-matches, at 12:38:46 and 12:38:51, for just the two files msjet40.dll and msrd3x40.dll. No other mismatches were detected anywhere else.


    I don't know if this means anything~~.
    Hello Dick.

    It looks as though your Windows Image, the one that Windows uses for repairs and updates is corrupted, the CBS log states that it could not replace your modified .dll's in the SysWOW64 folder because it thinks the ones in the backup SxS store are corrupted too.

    This happens when updates go awry such as when a roll-back does not complete successfully or the Windows Image inventory manifest that lists all the valid file versions becomes corrupted.
    We see this quite a lot with our student's laptops after they have been in use for a year or two and quite frequently after a major build update to an existing system such as migrating from 1903 to 1909 to 2004 etc.

    If this is on your main observatory computer I would recommend you carry out the following repair to restore the Windows image just in case underlying problems manifest themselves when running your application programs.

    This is a non-destructive method of repairing Windows without having to reload Windows or your apps from scratch and everything *should* work just as before after the fix but it is a good idea to have a backup just in case.
    Our faculty I.T. dept recommend this following method in preference to the built-in re-install Windows option of Windows 10 because unfortunately that method just restores Windows from the current Windows image and update repository on-disk and if that is damaged, as your's appears to be then you just rebuild Windows with the same corrupted files.

    1. Using Edge browser on the system you want to repair type "Windows 10 ISO download" in the search bar and from the result list navigate to your region locale official Microsoft site and download the Microsoft Media Creator tool.

    2. Run the Media Creator tool and select the option to create a Windows 10 ISO file for use with another computer, change the default location for the creation of a Windows 10 ISO file to create the file on your user desktop and not the usual download folder, you need this ISO file on the desktop.
    The tool should automatically detect that you have build 2004 installed (for example) and that is the ISO file you will create but it may offer you a choice of older builds, it is important to select the same build version that you currently have installed, you can't use this repair method to repair another build version than the one you currently have.

    3. The download is large, ~4.7Gb, after download is complete you will have a Windows 10 ISO file on your desktop with the name "windows.iso"

    4. Right-mouse-click the windows.iso file on the desktop and select "Mount" from the context menu to create a temporary virtual DVD drive, an explorer window will open, make a note of the drive letter that has been assigned to the virtual drive, you need this drive letter for the next step.

    5. Close all unnecessary running programs and then open an elevated Command Prompt window as described in the earlier post.

    6. Open notepad and type or copy-paste the following text string into a blank page:


    DISM /Online /Cleanup-Image /RestoreHealth /Source:X:\sources\install.wim /LimitAccess



    edit the text string and replace the drive letter "X" in the term "/Source:X:" with the actual drive letter for the virtual DVD drive that you noted above, if you manually type the text string observe the spaces where appropriate.

    7. Copy the modified text string in notepad and paste it into the Command Prompt Window then hit enter.

    The DISM tool will now rebuild the computers Windows image file from the pristine copy of Windows that you just downloaded. The term at the end of the text string "\LimitAccess" forbids DISM from using the files in the computers existing update folder and it will only rebuild the Windows image from the latest file versions on the ISO so bypassing any problems with your computers update repository.

    8. After DISM has reported completion, which can take upon to an hour, run the sfc /scannow command again in the Command Prompt window to replace the live Windows OS files currently in use with those in the new Windows image you just created.

    9. Finally, and before rebooting, right-mouse-click the windows.iso file on the desktop and click "unmount' in the context menu to clear the virtual DVD drive and "eject" (virtually) the iso file.

    10. Reboot the computer, you should then run a check for updates but normally the .iso you downloaded would have all the latest updates already included and most likely Windows will find no updates are needed.

    That should be it Dick, after running DISM.exe and sfc /scannow using local .iso support you will have rebuilt a clean Windows environment, including the recovery image.

    You can delete the .iso file, there is no need to keep it, you can also recover some disk space if you type "disk cleanup" in the desktop lower toolbar and run the disk cleanup tool, use the options tab in the tool and clear the old backup recovery points and updates store, these are no longer relevant after running DISM with .iso support.

    William.
    Last edited by William Bristow; Aug 2, 2020 at 10:13.

 

 

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Windows 10 2004 coming soon. Any experiences?
    By Colin Haig in forum Hardware/Software/Driver Topics Not Directly Related to Our Software
    Replies: 1
    Last Post: Jun 4, 2020, 23:58
  2. GOOD NEWS: Green Light for Windows Feature Update 1909 and ACP
    By Bob Denny in forum Windows 7 & 10 Operating System & Update Issues
    Replies: 0
    Last Post: Nov 23, 2019, 22:56
  3. Caution: Feature update to Windows 10, version 1607
    By Colin Haig in forum Hardware/Software/Driver Topics Not Directly Related to Our Software
    Replies: 1
    Last Post: Sep 23, 2016, 13:43

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •